Re: multibyte C locale

[Joerg.Schilling@xxxxxxxxxxxxxxxxxxx (Joerg Schilling)]

Albert Cahalan <albert@users.sourceforge.net> wrote:

> C.UTF-8 would be damn nice. Dealing with UTF-8 text is rather
> important these days. Unfortunately, locales like en_US.UTF-8
> get all stupid with collating order. 'a' comes after 'Z' damn it!
> (that is, U+0061 is a bigger number than U+005A) Possibly
> there is some hack with multiple locale variables that will make
> things sane, but that's excessively painful for such a common case.
>
> I expect the plain C locale to cover U+0000 through U+00FF,
> but it does not. At least with glibc, stuff like U+00E0 fails the
> isalpha() test. Ouch, this is broken too.

It would make sense to asume ISO8859-1 for the extended charset in a 
single char 8 bit C locale as UNICODE has become the standard of the 
future and as ISO8859-1 is identical to the values 0 .. 255 from UNICODE.

Jörg

-- 
 EMail:joerg@schily.isdn.cs.tu-berlin.de (home) Jörg Schilling D-13353 Berlin
       js@cs.tu-berlin.de                (uni)  
       joerg.schilling@fokus.fraunhofer.de (work) Blog: 
http://schily.blogspot.com/
 URL:  http://cdrecord.berlios.de/private/ ftp://ftp.berlios.de/pub/schily