The behavor of printing out libc message catalog without calling setlocale()

Chiaki Ishikawa Chiaki.Ishikawa@personal-media.co.jp
Wed Nov 8 01:23:00 GMT 2000


X-PMC-CI-e-mail-id: 14017 

>> This loophole saves the transition in a way, but also gives the
>> programming community excuses not to insert necessary setlocale()
>> calls in the favorite programs any time soon.
>
>Not really.  Since the character set is not set appropriately the
>messages will be garbled for most languages.

I see.
(I guess that the output of df translated in my case after
all the LC_* and LANG were reset were some kind of fluke.
My memory is hazy now, but I thought the message was not garbled.
But I can be wrong here.)

I agree that "LANGUAGE" do have its use in cases like the ones
you mentioned in answering GOTO-san's e-mail.

It is just a matter of inserting setlocale() in many, many popular 
programs now.
(And, to persuade the maintainers that it would be a good idea...)

-- 
     Ishikawa, Chiaki        ishikawa@personal-media.co.jp.NoSpam  or         
 (family name, given name) Chiaki.Ishikawa@personal-media.co.jp.NoSpam
    Personal Media Corp.      ** Remove .NoSpam at the end before use **     
  Shinagawa, Tokyo, Japan 142-0051




More information about the Libc-alpha mailing list