Re: New uncompatible locale system with glibc2.2 ?
Le Tue, Oct 17, 2000 at 02:59:20AM +0900, Changwoo Ryu écrivait:
> It's not a misinterpretation. glibc *exactly* knows the translated
> messages are ISO-8859-[12] encoded, by the "Content-Type" header. But
> glibc (a) converts them into Unicode texts once, then (b) converts
> them again into the charset of the current locale.
>
> The only problem is that glibc doesn't know about the current charset
> at (b), when setlocale() is not called. "C" locales is assumed in
> this case. So all non-ASCII Unicode characters are printed as
> question marks.
Then the problem is in the apps that don't call setlocale
with LC_ALL and that also don't call setlocale with LC_CTYPE ?
What can be done in glibc then ?
Cheers,
--
Raphaël Hertzog -+- http://strasbourg.linuxfr.org/~raphael/
Naviguez sans se fatiguer à chercher : http://www.deenoo.com
Formation Linux et logiciel libre : http://www.logidee.com
Reply to: