Date: Tue, 15 May 2001 22:02:52 +0900 (JST) From: "T.SHIOZAKI" <tshiozak@bsdclub.org> To: bsd-locale@hauN.org Cc: i18n@FreeBSD.ORG, obrien@FreeBSD.ORG, keichii@FreeBSD.ORG, ache@nagual.pp.ru Subject: Re: wchar.h / Citrus import Message-ID: <20010515.220252.112790593.tshiozak@astec.co.jp> In-Reply-To: <20010515160205.A13868@nagual.pp.ru> References: <20010515114142.A9263@nagual.pp.ru> <20010515.204937.39033143.tshiozak@astec.co.jp> <20010515160205.A13868@nagual.pp.ru>
next in thread | previous in thread | raw e-mail | index | archive | help
From: "Andrey A. Chernov" <ache@nagual.pp.ru> Subject: Re: wchar.h / Citrus import Date: Tue, 15 May 2001 16:02:08 +0400 Message-ID: <20010515160205.A13868@nagual.pp.ru> > > 1. Naming convention > > Just FYI, NetBSD locale names is bacically following to > > the primary name of X Window System locale, > > e.g. en_US.ISO8859-1, ja_JP.eucJP, ko_KR.eucKR... > > But, I think we need not to change the names already existing in FreeBSD. > > X11 names are non-standard, there is no such names in IANA registry. Lets > not repeat mistakes of others. I think this is just difference of policy. # I dare to say, wrong is MIME, historically. ;-) > > 4. IANA charset names vs. locale charset names > > I think locale charset names should be used for locale name only, > > except iconv_open(3) should accept both namespaces. > No. There are standard rules how to build locale name from the language, > territory and codeset. All three components are expected to follow > standards, including codeset. I know. "locale charset names" I said means "codeset" you said. "locale charset names" "IANA charset names" (NetBSD) eucJP EUC-JP ISO8859-1 ISO-8859-1 .... .... -- Takuya SHIOZAKI To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-i18n" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010515.220252.112790593.tshiozak>