On Sat, May 01, 2004 at 05:25:11PM +0200, Per Olofsson wrote: > It seems like the only reliable way to draw Unicode text with Xlib is > to use XDrawString16?
The problem with this is that you have to make sure you are using an iso10646-1 font. Yet another problem is that those fonts seldom contain all the characters in the range. That's why we have fontsets. But then again, depending on whether you are using Xmb or Xutf8 routines (Xutf8 IIRC, as Ion is using Xmb now), if there's an iso10646-1 font in the fontset, it may block the other fonts that would contain the character/ code point/whatever from being used as the font selection code doesn't check if the font actually contains a particular character. > 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. The problem with simply calling setlocale and not actually using multibyte routines is that if no locale is set, depending on the system and many other things, some routines may start to convert everything non-ASCII to question marks etc. -- Tuomo
