make this website translatable about reuse-website HOT 8 CLOSED

from reuse-website.

Hey, that's awesome! I'll ping @mxmehl on this, but from my end, I'd love to have the website be translateable.

I know that @mxmehl made https://publiccode.eu/ (https://git.fsfe.org/pmpc/website) translateable using just Hugo. But I don't think that Markdown was used for that website.

One important detail for this project is that---kind of sort of---content and Hugo stuff is separated between https://github.com/fsfe/reuse-docs and https://github.com/fsfe/reuse-website. That might complicate things.

from reuse-website.

Thanks for the offer @eighthave @uniqx!

I know that @mxmehl made https://publiccode.eu/ (https://git.fsfe.org/pmpc/website) translateable using just Hugo. But I don't think that Markdown was used for that website.

The PMPC website uses strings (in i18n) and markdown files (in content/), so all that Hugo provided at this point ;)

One important detail for this project is that---kind of sort of---content and Hugo stuff is separated between https://github.com/fsfe/reuse-docs and https://fsfe/reuse-website. That might complicate things.

That, and I was a bit hesitant towards translations when creating the website because I am afraid of outdated information. Especially with the spec/tutorial/FAQ, but also for instructions for developers (that may change with new tool or API versions) and so on.

In the area of development and license compliance, English is so widely understood that I am not sure whether the benefits (translations are great, wider audience, ease adoptions for everyone) would outweigh the downsides (outdated information, only partly translations).

Just my 2 cents for now, happy for more input!

from reuse-website.

from reuse-website.

Using the po4a workflow, it is possible to only publish translated pages that are 100% current

Sounds like what we need!

I am happy to explore this workflow, given that the extra complexity due to the split between reuse-website and reuse-docs will not be too high.

from reuse-website.

#29 and fsfe/reuse-docs#61 are the first key steps towards localizing this site. Those need to happen regardless of how things are integrated into the translation workflow, so I've done those first. Then we can separately figure out the exact integration and workflow with Weblate.

from reuse-website.

Pull request #29 has been waiting for review since May 4th. It should be easy to review, it just makes things be more standard Hugo style, which makes it a lot easier to localize. Once that is merged, I'll follow up with the actual full localization pull request, which I have locally implemented.

from reuse-website.

Sorry for the long wait, we had to wrap our heads around localisation first and how to deal with differing interpretations. Will follow up on the two PRs individually.

Is there a standard possibility to add some kind of warning text above translations on specific pages? So for instance, it'd be important that on top of spec.md people are aware that the English version is binding, and translations are inofficial. I could think of some Hugo shortcut displaying some translatable text on non-EN pages, but wanted to ask first for best practices.

from reuse-website.