Subject: Re: en_US.UTF-2
To: None <>
List: tech-userlevel
Date: 03/30/2001 16:08:06
Subject: en_US.UTF-2
Date: Fri, 30 Mar 2001 07:56:54 +0900
Message-ID: <>

> >Log Message:
> >support nl_langinfo(CODESET).
> 	with this commit en_US.UTF-2 is killed.  is it really appropriate?

Ah, sorry, I forgot to change the Makefile imcompletely.
But, I surely intended to kill it.

> 	"obsolete" means that there's some spec that killed the locale,
> 	or just because of the use of lib/libc/locale/utf2.c?
> 	if the latter, my suggestion is to ship en_US.UTF-2 as an alias of
> 	en_US.UTF-8, to help people who are using en_US.UTF-2.

I think UTF-2 was superceded by UTF-8 long time ago.
As far as I know, there is no platform which has UTF-2 locale.
I guess why 4.4BSD had UTF-2 rune code is a simple historical reason.
Even 4.4BSD didn't have any public UTF-2 locale.

As we didn't take "*.DIS_8859-15" locales from FreeBSD (instead,
we took more appropriate name, ISO8859-15), we should not have merged
en_US.UTF-2 to NetBSD at the outset.
(Sorry, I didn't awake to this thing when you merge it.)
And, as we didn't make aliases for "*.DIS_8859-15" locales,
we need not to prepare the alias for en_US.UTF-2 locale.

Fortunately, there is no public release which has this locale.
We should remove en_US.UTF-2 from the next release.
I guess there is few people who are using it.