Language/Country code question

Hi, I have a question on the messages/templates directory naming. Somewhere on the net, I learned that LOCALE should be a combination of Language/Country with a form of la_CO with the country part optional. So, there should be zh_TW and zh_CN instead of big5 and gb. Am I right? A chinese student of our university started translation and this question arose to us. TIA for your consideration. -- Tokio

Hi Tokio, I think you are right, we should use zh_TW and zh_CN. It's great someone is doing the translation. I have already translated templates for simplified chinese, which is in the attachment. You may use it. There are some tools to do translations between GB and Big5, I can find it if you need it. Thanks! Best Regards Max -----原始邮件----- 发件人: mailman-i18n-admin@python.org [mailto:mailman-i18n-admin@python.org]代表 Tokio Kikuchi 发送时间: 2001年11月13日 10:40 收件人: mailman-i18n@python.org 主题: [Mailman-i18n] Language/Country code question Hi, I have a question on the messages/templates directory naming. Somewhere on the net, I learned that LOCALE should be a combination of Language/Country with a form of la_CO with the country part optional. So, there should be zh_TW and zh_CN instead of big5 and gb. Am I right? A chinese student of our university started translation and this question arose to us. TIA for your consideration. -- Tokio _______________________________________________ Mailman-i18n mailing list Mailman-i18n@python.org http://mail.python.org/mailman/listinfo/mailman-i18n

Somewhere on the net, I learned that LOCALE should be a combination of Language/Country with a form of la_CO with the country part optional.
That is common, indeed. See below for the relevance of encodings, though.
So, there should be zh_TW and zh_CN instead of big5 and gb. Am I right?
Not sure what mailman is doing, however, either appears to be wrong, based on the following rationale: - a locale/catalog should not, per se, be based on the encoding. Instead, at run-time, the program should convert from one encoding to another. Is it true that big5 and gb can be converted forth and back for all practical purposes? - The locales zh_TW and zh_CN may differ, but the catalogs should *only* differ if the translations are actually different. There is no point in duplicating work if the Chinese and the Taiwanese translator come up with the same translation (perhaps in a different encoding). If you want to put the encoding into a locale, it normally goes after the country, i.e. zh_TW.big5 and zh_CN.gb; other combinations should also be possible, like zh_TW.gb or zh_CN.UTF-8. Regards, Martin

Martin von Loewis wrote:
Not sure what mailman is doing, however, either appears to be wrong, based on the following rationale:
- a locale/catalog should not, per se, be based on the encoding. Instead, at run-time, the program should convert from one encoding to another. Is it true that big5 and gb can be converted forth and back for all practical purposes?
- The locales zh_TW and zh_CN may differ, but the catalogs should *only* differ if the translations are actually different. There is no point in duplicating work if the Chinese and the Taiwanese translator come up with the same translation (perhaps in a different encoding).
If you want to put the encoding into a locale, it normally goes after the country, i.e. zh_TW.big5 and zh_CN.gb; other combinations should also be possible, like zh_TW.gb or zh_CN.UTF-8.
Usally we use zh_TW.Big5, zh_CN.GB2312 and zh_CN.GB18030 if put the encoding into a locale. Best Regards Max
participants (3)
-
Martin von Loewis
-
Max Yu
-
Tokio Kikuchi