Subject: Re: bin/12017: how to enable multibyte locale (and problem around it)
To: None <firstname.lastname@example.org, email@example.com>
From: Noriyuki Soda <firstname.lastname@example.org>
Date: 01/23/2001 15:27:56
> >Another encoding modules, for example, an encoding module which can
> >handle any codeset represented by charmap format. (this is required
> >to support localedef correctly).
> 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.
> >Also, special LC_TIME module which can handle programmable date
> >representation may make sense.
> >Perhaps special LC_COLLATE module which can handle programablle
> >collation order, too.
> did they need such thing in glibc? from what i see in glibc-2.2,
> they did not...
I have not checked recent glibc.
But Solaris certainly have a way to extend LC_TIME, LC_COLLATE,
regexp, date/time format parser (Solaris has getdate(3) function), etc.
Please look at /usr/lib/localdef/extensions/generic_eucbc.x, for example.