Re: [PATCH 1/5] Internationalization of git-gui

[Junio C Hamano <gitster@pobox.com>]

Christian Stimming <stimming@tuhh.de> writes:

>> There are two HUGE problems with that.
>>
>>  * Supporting many languages means looooong lines in that file.
>>    Translators for languages later on the line would have hard
>>    time updating or looking at that file.
>>
>>  * Mixed encodings.  What if next language wants its strings in
>>    UTF-8?  How would you have that and ISO-8859 on a same line?
>>
>> I would suggest having one glossary file per language.
>
> Agreed. I propose to throw away the "add glossary" patch and I'll resubmit, 
> this time in a separate po/glossary/ directory, where each language will get 
> a po file for the glossary. 
>
> As I've written in another thread: In the glossary for the gnucash project [1] 
> we've actually added an extra 
> directory and encourage translators to add an extra po file for their 
> glossary translations. However, the glossary of gnucash has more than 150 
> terms and many of them require to be defined clearly as well, as translators 
> would otherwise be unable to translate them concisely. In git-gui, the 
> glossary is 25 terms so far and I think the git documentation already 
> contains enough definitions of all of them. Nevertheless, maybe it would make 
> a better structure if the translations of the glossary are kept in a separate 
> po file for each language. 

Actually, I would even suggest that we should NOT have a
separate glossary file at all, if gettext suite allows what I
outline below.

How about having it as a part of header comment in each of the
xx.po file?

The division of labor I think would make sense for message l10n
process goes like this:

 - The software developer (primarily Shawn): responsible for
   marking messages subject to i18n;

 - The i18n coordinator (could be Shawn but anybody else can
   volunteer; as things stand, I think Christian and Johannes
   are doing this): responsible for running "make
   po/git-gui.pot; make update-po" from time to time in order to
   keep po/*.po in sync with the vocabulary.

   initially, populate "glossary" part in po/git-gui.pot;

   as needed, add entries "glossary" part in po/git-gui.pot, and
   (if possible) add corresponding placeholders to po/*.po;

 - Translators (one for each language): responsible for updating
   po/xx.po file;

   initially, start by copying po/git-gui.pot to create
   po/xx.po;

   maintainance of "glossary" part of po/xx.po could also be
   made this person's responsibility instead of i18n
   coordinator's.

This way, the translators do not have to be so familiar with the
gettext toolchain nor even have to have gettext installed.