Translation status script

[Warren Block]

On Thu, 9 Jun 2016, Warren Block wrote:

> On Sat, 4 Jun 2016, Federico Caminiti wrote:
>
>> I've finally gotten arround to working on the documentation scripts last
>> week. Using your docdates.sh script as a base, I started writing a script
>> [1] that showed which documents needed to be translated. It is not perfect
>> and there is much room for improvement, but it is a starting point.
> ...
>> I've included an example of the console output with a recent documentation
>> tree  (updated yesterday) [2] and the .csv file output [3]. These are both
>> the results of executing the script as "./translation.sh es_ES" .
>> 
>> Regards,
>> 
>> [1]
>> https://gist.github.com/fdemian/59721b402483f9b30816f895de07cc31#file-translation-sh
>> 
>> [2] http://slexy.org/view/s20Yx1qvmZ
>> 
>> [3] http://slexy.org/view/s2WrJou5fV

Finally had a chance to look at this.  It's quite nifty, giving a useful 
report on the status of translations.  I would adjust the commands in 
the pipeline on line 40 to be predeclared and use the ${} notation.

A suggestion for additional information: use some gettext utility to 
determine the percentage translated for the PO translations.

For old-method translations, show the current translated revision number 
and latest revision number of the English version.  Although finding the 
latest translated version depends on the language team.  The German team 
uses "basiert auf" (based on) in a comment, for example.