make translatable?

Hans-Christoph Steiner hans at
Wed Apr 29 12:05:42 UTC 2020

Daniel Shahaf:
> Hans-Christoph Steiner wrote on Wed, 29 Apr 2020 10:44 +0200:
>> Mattia Rizzolo:
>>> 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.
> What happens between the update of an English original and the time an
> update translation is pulled and deployed?  Will there be, say,
> "English last updated on: ${DATE1} / This translation last updated on:
> ${DATE2}" information on the translated page?  (I don't see anything
> like that on fdroid which you linked to, but that doesn't mean much.)

With websites, there isn't clearly defined workflows for this, so you
have to define it.  po4a and Weblate provide tools to do it.  The
easiest is to set po4a's --keep to 80%, which will automatically revert
pages to English if they fall below 80% translated.  Then just take
translation updates as they come from Weblate.

> Personally, I'd even consider putting on the translated page a link to
> a diff view of the changes to the English page between ${DATE2} and
> ${DATE1}, for the benefit of any English-speaking readers of the
> translation.  Ideally we'd link to a rendered markdown diff (because we
> can't assume all readers are comfortable with reading markdown in raw
> form) but gitlab doesn't support that [1], so we'd have to link to the
> regular or side-by-side diff view or to a mirror of the repository.
> [1]

One thing that can easily be added using Liquid scripting is a list of
all languages that a given document is translated into.  I've seen that
on the Apache docs, for example.


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

More information about the rb-general mailing list