make translatable?

Hans-Christoph Steiner hans at
Thu Apr 30 20:11:22 UTC 2020

Daniel Shahaf:
> Hans-Christoph Steiner wrote on Thu, 30 Apr 2020 19:14 +00:00:
>> Daniel Shahaf:
>>> Hans-Christoph Steiner wrote on Wed, 29 Apr 2020 14:05 +0200:
>>>> 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.
>>> My concern was to inform users of a translated page that's behind the
>>> English master that the content they're reading is out-of-date, and
>>> give them a way to access the content the translation lacks, albeit in
>>> English.
>>> I don't see how using --keep=80% would address that.  It would seem that
>>> if a page had been 100% translated and had fallen to 95% because of
>>> a recent update to the English content, there would be no indication of
>>> that in the translated page, so readers of the translated page wouldn't
>>> know there are updates they aren't seeing.  What am I missing?
>> When the translation level of a given page falls below the "keep"
>> percentage, that page is reverted to English. Try clicking on the fdroid
>> docs, you'll see how it works:
> Yes, you already said this once.  I replied that it does not address my
> concern.

I guess I don't understand it then, sorry.  Someone reading the website
with their browser set to a language besides English would not see an
out of date translation since they would see the original English.  Are
you proposing instead that the outdated translation is still displayed,
but with a warning that it is outdated?  That would also be possible
with custom code or manual management.  I haven't see that on any
translated static sites.


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

More information about the rb-general mailing list