On Sat, May 01, 2004 at 02:20 +0300, Tuomo Valkonen wrote: > The reason why -i18n is not enabled by default is that in an UTF-8 > locale it may take an intolerably long time to load the fonts using > the kludge in de/fontset.c
Yes, I noticed that when I tried to use -i18n. > and also Xlib string drawing routine support for UTF-8 is totally > broken and unlikely to be fixed. :-( It seems like the only reliable way to draw Unicode text with Xlib is to use XDrawString16? > However, as the Ion drawing engine configuration files do not > specify an encoding for fonts, it could be that Xlib or X server or > whatever defaults to ISO-8859-1 encoding as the first choice when no > locale is set. Yes, that's what I'm worrying about. I don't know how that selection works. I wonder if it's the server who decides or if you have to call setlocale, which Ion doesn't do unless you invoke it with -i18n. -- Pelle
