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

[Christian Stimming <stimming@tuhh.de>]

Am Samstag, 21. Juli 2007 21:41 schrieb Junio C Hamano:
> While I think keeping a reference for consistent translation
> (within one language's *.po file) is a useful practice,
> the po/glossary.csv file on 'master' seems a way suboptimal
> solution.  Currently it is:
>
>         $ file po/glossary.csv
>         po/glossary.csv: ISO-8859 text

Oops. I created it with utf8 locally. Must have turned into latin1 either in 
my mailer or during Johannes' mbox tweaking.

(Also, the de.po was created in utf8 here and must have been messed up during 
transmission. Johannes, for future reference: All i18n files should probably 
be submitted as utf8, and if they have a different encoding, the submitter 
better gave a clear sign this was intentional.)

>         $ head -n 1 po/glossary.csv
>         "English Term"  "de translation"
>
> which implies that other languages will be added at the end
> separated with <TAB>?
>
> 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. 

Christian

[1] 
http://svn.gnucash.org/trac/browser/gnucash/trunk/po/glossary/gnc-glossary.txt