Website translation

[Marcus Hoffmann]

Hi!

On 01.11.23 17:16, Julien Lepiller wrote:
> Hi!
> 
> I've learned at the rb meeting that the website could be translated.
> Currently, the translation process looks like this: you clone the repo,
> figure that you need to add your language to _config.yml (languages),
> run bin/i18n.sh to generate the po files, translate the po files,
> create an account on salsa and send an MR.
> 
> I've started translating and I'm waiting for my account to be validated
> by an admin.
> 
> I manage the translation infrastructure at Guix, where we use Weblate
> for hosting the translations online. I think it's a good choice to make
> it easier, even for technical translators, to focus on their work. It
> includes a shared glossary, lint checks, screenshots, and support for
> automatic update and commit.

A plus one from me for weblate.

> 
> This is what it might look like for Guix:
> 
> https://translate.fedoraproject.org/projects/guix/website/nl/
> 
> Guix is hosted on Fedora's instance because they are open to other
> projects, and because the default instance used to use non-free
> javascript, which we didn't want our translators to be subjected to. It
> seems that it's no longer the case, so I have no strong argument
> against using it anymore. Maybe Debian has an instance or a similar
> system?
> 
> In terms of security, the Weblate instance needs to be allowed to pull
> and push commits to the repository. The server has an SSH key that
> needs to be added to an account on salsa (it could be a dedicated
> account or someone's account).

I maintain the weblate insatallation for Codeberg at 
https://translate.codeberg.org which might be another potential option.
We can (probably) also configure that to work with the gitlab api at 
salsa, which enables creating gitlab merge requests instead of pushing 
to a repo directly.

> 
> What do people think?
Marcus