Subject: en_US.UTF-2
To: None <tshiozak@netbsd.org>
From: None <itojun@iijlab.net>
List: tech-userlevel
Date: 03/30/2001 07:56:54
>Modified Files:
>	sharesrc/share/locale/ctype: Makefile en_US.ASCII.src
>	    en_US.DIS_8859-15.src en_US.ISO_8859-1.src en_US.ISO_8859-2.src
>	    en_US.ISO_8859-4.src en_US.UTF-2.src en_US.UTF-8.src
>	    ja_JP.CTEXT.src ja_JP.ISO-2022-JP-2.src ja_JP.ISO-2022-JP.src
>	    ja_JP.SJIS.src ja_JP.eucJP.src ko_KR.eucKR.src ru_RU.CP866.src
>	    ru_RU.ISO_8859-5.src ru_RU.KOI8-R.src uk_UA.KOI8-U.src
>	    zh_CN.eucCN.src zh_TW.BIG5.src zh_TW.eucTW.src
>
>Log Message:
>support nl_langinfo(CODESET).

	with this commit en_US.UTF-2 is killed.  is it really appropriate?
	"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.

itojun