: Do you know why I have problems to get the characters above 127 to be : displayed correctly? It does not show U-Umlaut, A-Umlaut etc. Also the fonts : example of FLTK shows question marks for these characters.
What does it show for these characters? You've got a list of all sorts of things that don't work, huh? LOL ;) I don't know FLTK very well and there are several versions out there, some using UTF-8 encoding, others not. I suggest you modify a demo microwindows program first, using the GrText() routine and a scaleable unicode font. Then, the GR_TFUTF8 or GR_TFUC16 flags can be used in the last parameter to specify the text encoding. This will then be translated internally to the font's unicode index and displayed. If the loaded font isn't unicode or doesn't have the translated character index, then of course, it won't work. A special character, usually a box, will be displayed instead. You will need to look into NXLIB XDrawString16 as well as the calls made in FLTK to XDrawString* to determine how they're encoding text for output. Looking at NXLIB, it uses the X11 character encoding, rather than UTF8 or UC16, for XDrawString16. Regards, Greg --------------------------------------------------------------------- To unsubscribe, e-mail: nanogui-unsubscr...@linuxhacker.org For additional commands, e-mail: nanogui-h...@linuxhacker.org
