> I read the document about localizing TortoiseSVN, at
> ations.txt for the purpose of starting the translation for my
> native language - Georgian.
If you hurry up, your translation will make it into TortoiseSVN 1.1.3.
> I noticed that in naming the translation files Country ISO
> codes are used, specificly, the document, mentioned above,
> states: "Rename Tortoise.pot to Tortoise_xx.po, where xx is
> your two letter ISO country code." In my humble oppinion this
> is a mistake. Languages and countries do not have one to one
> correspondence, good proof for which is that ISO has separate
> set of codes for locales and countries.
I think we are already doing it the right way, we have:
Chinese, simplified zh_CN
Chinese, traditional zh_TW
Portuguese, Brazil pt_BR
We could name the German translation de_DE, if you are just talking about
"lack of precision" in naming the translation files. Just have a short look
at this thread: http://svn.haxx.se/tsvn/archive-2004-07/0000.shtml
> What are you going to
> use as the country name for common languages like English and
> Spanish that are official languages of many countries?
If someone really wants to create and maintain en_UK and en_US translations
of TortoiseSN he is free to do so, but I won't be happy with it. I prefer to
have as few translations as possible that cover as many languages as
> believe, instead of country codes, locale codes from ISO
> 161723/1198107/ISO_639-1.pdf?nodeid=2496537&vernum=0) Locale
> Codes should be used.
Maybe the problem is just the wording? I think I have to write "ISO-639
language code plus, if neccessary the ISO-3166 two letter country code"
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Mon Jan 17 09:03:15 2005