>>>>> On Sat, 4 Sep 2004 13:39:07 +0900 (JST),
	Curt Sampson <cjs@cynic.net> said:

> I don't think that this is needless complexity. Keep in mind that the
> charset name is user input; making it easier for the user to supply this
> value to the system is a definite benefit, IMHO.

Are you typing charset names regularly?
If so, I think your environment is somewhat unusual.

Also, if you really want to support case insenitive things, you should
support environment $lang, $Lang as environment variable as well
as $LANG, for example.
Making codeset names only case insensitive doesn't change much.
Or, do you really want to make everything case-insensitve?

>> In the ideal world, everyone would use just one codeset name for
>> one codeset, and although it's too late for such world, we should
>> not introduce another variants of codeset names.

> The names are out there, and they are official, and used widely. 
> I don't see why we should not just use the existing standard, rather than
> creating our own.

Our codeset names aren't such "our own" things.
Our codeset names conform existing UNIX conventions as far as
possible, so our current names are just exactly compatible with most
commercial UNIX variants.

Changing this is rather "our own" thing, because it makes ours
different from existing UNIX conventions.
--
soda