Daniel,
Technically you are correct. A "nn_NO" value is not proper since "NO" is
redundant. But it will be used.
I should have said POSIX style locales since there is a difference between
"ja_JP.Shift_JIS" and "ja_JP.EUC-JP" or between "fr_FR" and "fr_FR@EURO".
I will go one step further and suggest that time zone is also a part of the
locale. Thus you might want to extend the POSIX standard to include time
zone for example: "fr_FR.iso-8859-15@EURO#Europe/Paris" or
"en_US.utf-8#America/Los_Angeles".
Carl
> -----Original Message-----
> From: unicode-bounce@unicode.org [mailto:unicode-bounce@unicode.org]On
> Behalf Of Daniel Biddle
> Sent: Thursday, July 26, 2001 4:00 PM
> To: unicode@unicode.org
> Subject: Re: Locale codes (WAS: RE: RTF language codes)
>
>
> On Thu, Jul 26, 2001 at 01:04:29AM -0700, Yves Arrouye wrote:
> > > If you have a cross platform system you should use RFC 1766
> > > style locales
> > > between systems and convert them to LCIDs on Windows.
> >
> > RFC 3066 was published in January. Check it out.
> > http://www.ietf.org/rfc/rfc3066.txt
>
> Note that neither RFC 1766 nor RFC 3066 refer to locales;
> they just define language identification tags.
>
> --
> Daniel Biddle <deltab@osian.net>
>
This archive was generated by hypermail 2.1.2 : Thu Jul 26 2001 - 21:51:34 EDT