make translatable?

Hans-Christoph Steiner hans at
Wed Apr 29 08:44:07 UTC 2020

Mattia Rizzolo:
> On Tue, Apr 14, 2020 at 02:53:44PM +0000, Holger Levsen wrote:
>> The only issue I see is that we dont want the whole site translatable,
>> eg not those 200 old weekly blogposts nor the five >50 page reports
>> from our summits. I'm unsure whether it's a good idea to translate
>> the new monthly reports (or new summit reports) but I suppose it would be.
> I agree.
> IMHO, we should allow for translation of only:
>  *
>  *
>  * (and all subpages)
>  *
>  *
>  * (and subpages, but not
>    /reports/ or /blog/ even if they are linked here)
>  * (and subpages, but not the
>    reports)
>  *
>  *

I think we achieved this.  It is easy to change in any case.  Its just a
glob in a for loop in bin/  It is also possible to manually
manage the po4a.conf files, then you have to manually manage the
language list and the list of files.

> I didn't check, but is the proposed framework able to properly track
> translation updates?

Of course, that's an essential part of any localization process.  The
maintainers do still need to be aware of the Weblate git repo, and pull
in updates as needed.

> Also, I would really be annoyed to find out at point after the initial
> effort that the translations are not keeping up with the edits, so,
> regardless of the initial prototype, please be sure to have a somewhat
> stable group of translators.

> Having said so, I look forward to the prototype, thank you! :)

The first merge request is ready for review:


PGP fingerprint: EE66 20C7 136B 0D2C 456C  0A4D E9E2 8DEA 00AA 5556

More information about the rb-general mailing list