On 2008-11-16, Tuomo Valkonen <[EMAIL PROTECTED]> wrote: > On 2008-11-16, sughosh ganu <[EMAIL PROTECTED]> wrote: >> The problem was that ion did not recognize the locale on my system >> (en_IN). Changing it to en_US.UTF-8 solved the problem. Thanks for the >> help. > > It's not Ion. It's Xlib. en_IN.UTF-8 should work, if it's been > compiled.
I'm not exactly sure why Xlib handles LC_CTYPEs without the encoding part specified in a fucked up manner, but it does have a locale.alias database of its own, /usr/share/X11/locale/locale.alias, which does e.g. list en_IN: en_IN.ISO8859-1 If Xlib uses this database instead of the information from libc, nl_langinfo(CODESET), and libc has been compiled with a different character set for en_IN, it could be why it's fscked up. The modern (read: shit) toolkits afaik pretty much reinvent all this, being utf-8 monoculturistic [ which also results in nobody bothering to fix Xlib, the generic multibyte routines of which handle utf-8 locales very badly ], and xterm also uses the Xutf8 routines instead of Xmb routines when in an utf-8 locale. -- Be an early adopter! Beat the herd! Choose Windows today!
