Re: New uncompatible locale system with glibc2.2 ?

[Fumitoshi UKAI <ukai@debian.or.jp>]

At Mon, 16 Oct 2000 22:19:14 +0200,
Raphael Hertzog <rhertzog@hrnet.fr> wrote:

> > 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 ?

Probably.
 
> What can be done in glibc then ?

Set environment variable OUTPUT_CHARSET to what codeset you want to get.
For example, I do
  $ export OUTPUT_CHARSET=EUC-JP

Regards,
Fumitoshi UKAI