>> 	charset table will be /usr/share/locale/*/LC_CTYPE, and
>> 	it will be loaded on demand.  i don't see *code* overbloat in
>> 	this case (yes, data can be huge, but we are talking about code)
>No. What I wrote is "encoding module" (like big5/euc/ecutw/iso2022/
>mskanji/utf8) not isXXXXX() settings, and "charmap" file is nothing 
>related to isXXXXX() functions, either.

	i think we are talking about the same thing.
	even if we use charmap, encoding module won't be that big i guess.
	data (the conversion table generated from charmap) will be big though.

	also, since charmap is a static table (not conversion formula)
	there's no reason for it to require different encoding modules
	per different charmaps.

itojun