This is the mail archive of the
mailing list for the glibc project.
Re: LC_MESSAGES problem ?
- To: libc-alpha at sources dot redhat dot com
- Subject: Re: LC_MESSAGES problem ?
- From: Won-kyu Park <wkpark at chem dot skku dot ac dot kr>
- Date: Tue, 21 Nov 2000 02:32:09 +0900
- Cc: Ulrich Drepper <drepper at cygnus dot com>
- References: <20001120175546.A15984@zinc.skku.ac.kr> <firstname.lastname@example.org> <20001121014722.A4539@zinc.skku.ac.kr> <email@example.com>
On Mon, Nov 20, 2000 at 08:55:54AM -0800, Ulrich Drepper wrote:
> Won-kyu Park <firstname.lastname@example.org> writes:
> > But, Why the default charset is ASCII ? translation messages have it's
> > own charset info, like 'charset=EUC-KR'.
> > IMHO, the default guessed charset by intl/loadmsgcat.c have to be fixed by
> > proper manner.
> No. The terminal used (represented by the LC_CTYPE locale) and the
> message catalog selected need not use the same character set.
There are many programs do not use setlocale(LC_CTYPE,"").
some programs are LC_CTYPE sensitive (like isctype() etc.) and then
set the LC_CTYPE as 'C'. but... how can I get a translation messages
under glibc ?
(with OUTPUT_CHARSET ?)
$ LC_MESSAGES=ko_KR ./a.out
Solaris works fine with setlocale(LC_MESSAGES,"") only.
There are many programs using setlocale(LC_MESSAES,"") only.
(the gcc also)
With this 'LC_MESSAGES' problem, Linux users confused with '????? ???'
messages at the East Asia.