Request for translation branches and sites #27
Comments
|
Sure, but I would be curious what amount of interest there is in translations, and who would be responsible for reviewing contents of the PRs to different branches (and it would be best if the translator and the reviewer were two different people). I think that should be figured out first and then we can figure out which languages require branches. |
|
Yes. It can be created on request. The Chinese community has been discussing about it for some time. Maybe not every article, but we do want to translate articles of some important events, like oSC, Leap milestones. If the Chinese site is going well, then other community may also join. |
|
Just a thought: could we bring the files here together with Weblate on l10n-o-o? This might broaden the translators base. |
|
Yes, but it would be very hard to limit the amount of articles that would land on Weblate so you would end up with 1600 articles for translation in Weblate right away, and I don't think we need that to be perfectly honest. |
|
Although you know what, considering that jekyll-task-i18n allows for specifying the titles of articles that get translated with a glob or a regex for example, that's actually pretty easy |
|
We can set a limitation (through script probably): only articles published in the last 30 days will appear on weblate. Old articles will be frequently removed from weblate. |
|
We just need to specify non-default rake task, since our infra runs rake automatically if Rakefile exists, and we also need action for running rake and committing back to the repo every week or so |
|
That all sounds a bit too much work "just" to get translations ready. Let's stick with original plan by @guoyunhe. |
|
I would argue it's easier overall, it's not a terrible idea |
|
Okay, sounded more troublesome to me. Don't let yourself get kept back from work. :-) |
|
the original branches solution has an advantage: local communities can publish local news article, like a local meet up, release parties. the weblate solution is a bit hard for scripting. just for the devs. the branch solution is a bit hard for making and reviewing PRs. for every contributors. |
Yes, but luckily they can do all of that even via the web interface here on GH. That makes it easier for not so tech-savvy writers. Btw: I'd go with |
Allows us to avoid having to generate a new certificate for *.news.opensuse.org ;) |
|
Hi, What is the status of this? We would like to have a pt-BR version of news. Hugo has very good support for translations, everything is build-in into it. Migrating from Jekyll won't be that hard. Hugo is still similar and will require some coding knowledge to make it work, but a lot of things can be done with GH Actions and GH Pages. On the other hand, Hugo has good integration with Netlify, and this allows users without coding skills to create, update, and review articles. I would be willing to give it a try, along with some folks from Brazil we could set up and migrate everything. |
|
Currently the effort here mostly moved to newscom, so you should probably ask there. We do have a plugin in jekyll that enables us to do translations though, take a look at https://get.opensuse.org as an example |
The plan is to create branches:
And they will be deployed to:
Or:
How contributors participate translations:
The text was updated successfully, but these errors were encountered: