Bill Spitzak wrote: > ... > I believe this is what is happening. In fltk2 id does not use the Xft > UTF8 functions, it works similar to the other platforms. This allows it > to display most ISO-8859-1 correctly. More importantly, it will draw > something for a piece of text with invalid UTF_8 in it. The Xft > functions quit if they see invalid UTF-8 which is not very desirable > behavior.
Depends on what you want. I'd rather see consistent behavior (don't display invalid UTF-8) than try to support both ISO-8859-1 (or your favorite 8-bit encoding) and UTF-8 inconsistently. Moreover, if FLTK allows a mix of UTF-8 and 8-bit characters, it will be very likely that text fields and other widgets will end up with a mix, leading to really interesting problems when those values are written to a file... So, I'm -1 on supporting both ISO-8859-1 and UTF-8 at the same time through any kind of auto-detect code. -- ______________________________________________________________________ Michael Sweet, Easy Software Products mike at easysw dot com _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
