[i18n] Start traditional Chinese translation for Mercurial

[Martin Geisler]

Dongsheng Song <dongsheng.song at gmail.com> writes:

Hi

I've renamed the zh.po file to zh_CN.po for two reasons:

* It's what other software projects seems to be doing. On my Debian
  machine I found no /usr/share/locale/zh directory. On a RedHat machine
  I found just two translations there and 750+ in zh_CN/zh_TW.

* It avoids making zh.po a fallback for zh_XX users who cannot read
  Simplified Chinese, which seems to be a real problem even though there
  are of course people who can read both forms of Chinese.

> 2009/3/29 Martin Geisler <mg at daimi.au.dk>:
>> Believe me, Most of users in
>> Taiwan are more familiar with English than Simplified Chinese.
>
> You can said, I hate SC(Simplified Chinese).
>
> My some friends work in Taiwan corp. at mainland, they said,
> their boss can read and listen SC smoothly, but let they
> write report in TC(Traditional Chinese).
>
> In fact, I have been collaborate with some Taiwan and Hong Kong
> corp., they(Traditional Chinese users) can read and listen SC
> smoothly too.
>
>> I can see that a rename isn't necessary when we get a zh_TW.po file,
>> but right now the Simplified Chinese translation is a poor default
>> when people in Hong Kong and Taiwan cannot read it.
>>
>
> I can understand you hate SC, but you can ONLY delegate your self.
>
> I can not imagine, de_at and de_ch users ask for delete de.po, used
> de_de.po instead.

As I understand it, SC and TC are rather different -- whereas the
differences between (written!) German in Austria and Switzerland are so
minor that users have no problem at all understanding each other.

>> Unless we get a translation with Traditional Chinese quickly, I think
>> it would help users to rename zh.po to zh_CN.po like other projects
>> do.
>>
>
> If you realy don't like see SC, you can send a  zh_TW.po with a few
> translated strings.

That will still leave us with the problem of falling back to zh.po, as
described by willie.

> According to RFC 4646[1] and IANA language subtag registry[2],
> zh_CN, zh_TW, zh_HK is obsoleted or deprecated, zh-Hans and
> zh-Hant is prefered, microsoft has been switched to RFC 4646.

I've only ever seen zh_CN, zh_TW, zh_HK used, so I think we should stick
with that.

> [1] http://tools.ietf.org/html/rfc4646
> [2] http://www.iana.org/assignments/language-subtag-registry

-- 
Martin Geisler

VIFF (Virtual Ideal Functionality Framework) brings easy and efficient
SMPC (Secure Multiparty Computation) to Python. See: http://viff.dk/.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 196 bytes
Desc: not available
Url : http://selenic.com/pipermail/mercurial/attachments/20090331/bf70300c/attachment.pgp