Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 15 May 2001 21:08:40 +0900 (JST)
From:      Noriyuki Soda <soda@sra.co.jp>
To:        i18n@FreeBSD.ORG
Cc:        "T.SHIOZAKI" <tshiozak@astec.co.jp>, bsd-locale@hauN.org, obrien@FreeBSD.ORG, keichii@FreeBSD.ORG
Subject:   Re: wchar.h / Citrus import
Message-ID:  <200105151208.VAA24023@srapc342.sra.co.jp>
In-Reply-To: <20010515160205.A13868@nagual.pp.ru>
References:  <20010515044454.A6122@nagual.pp.ru> <20010514203700.A16280@peorth.iteration.net> <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
>>>>> On Tue, 15 May 2001 21:03:00 +0900,
	"Andrey A. Chernov" <ache@nagual.pp.ru> said:
>> 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.

Huh?
X11 names conform to OpenGroup (i.e. UNIX) standard.
And IANA registery is nothing related to UNIX codeset names.

Are you suggesting that FreeBSD should become different from
any other UNIXen?

>> 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.

Yes. And that is what citrus locale choosed.
--
soda

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?200105151208.VAA24023>