On Tue, Mar 03, 2009 at 10:01:46PM +0800, Arne Goetje wrote:
> Christian Perrier wrote:
> > Quoting Arne Goetje (a...@linux.org.tw):
> >> Christian Perrier wrote:
> >>> Damn. This is one of those cases where we suffer from the silly trick
> >>> of using zh_CN and zh_TW to differentiate between two different
> >>> *scripts*. I really dream of different ISO-639 codes for the two
> >>> different written versions of Chinese: Traditional and Simplified.
> >> Err, no. Just use RFC4647 for the whole locale system.
> >> zh-Hans = simplified
> >> zh-Hant = traditional
> >
> >
> > Which, if I'm correct, would mean having zh-Hans_CN and
> > zh-Hant_TW|zh-Hant_HK locales, right ?
>
> Almost. :)
> RFC4647 uses hyphens instead of underscores.
> The format is: langcode-script-territory-variation-x-usertags
> where:
> langcode = ISO 639-{1|2|3}
> script = ISO 15924
> territory = ISO 3166
> variation = a predefined list of variation tags
> x = separator between "official" tags and "user defined tags"
> (literally 'x')
> usertags = user defined tags
> and everything except langcode is optional.
Yes; however, RFC4647 defines locales in the context of the
Accept-Language and/or Accept-Encoding headers of RFC2616 (HTTP), which
use a different format from the LANG and LC_* environment variables on a
Unix system.
It is similar enough that we can adapt it for our needs, but then it'd
have to be something like zh-Hans_CN, indeed.
[...]
--
<Lo-lan-do> Home is where you have to wash the dishes.
-- #debian-devel, Freenode, 2004-09-22
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
