> > OK, this is interesting... Does it fail to render the > ISO-8859-1 characters on all platforms, or is it only on linux? > > > > There's something I saw in the linux parts of my utf8 code > that might be implicated here... But if it isn't working on > OSX or win32 either it may be a more general problem. Either > way, I expected that this should work so if it does not... > > It's okay on Windows, but fails on Linux with local X display > and remote > (Windows) X display as well.
Hmmm, this maybe ties in with something I'd seen... Some code I have "works" on win32 and OSX, but not on linux, and it seems it might be the same effect you are seeing. However... It could be argued that linux is doing the Right Thing and the other platforms are wrong! > > Do you know what numeric value the offending glyphs have, > BTW? I don't have my ISO-8859-1 stuff here... > > Umlaut / special char.: AE OE UE ae oe ue ss > Umlaut / special char.: Ä Ö Ü ä ö ü ß > -------------------------------------------------------------- > ISO 8859-1 (ISO Latin 1) 196 214 220 228 246 252 223 > -------------------------------------------------------------- Right... That's a pity... I had a theory that it was related to the values of the glyphs lying in the range 0x80 to 0x9F (which are CTRL chars in Unicode, but not necessarily in other encodings.) But your problem glyphs aren't in that range. Hmmm. What font are you using, BTW? If it's something I have, I might try and have a look (work/time permitting or course!) > For non-Germans: the german Umlauts can alternatively be > written as the base > character with an appended 'e' or 'E', resp., the sharp as a > double s, but > pronounced 'sz'. Matthias mentioned something about that before - it's maybe a pity that "ß" isn't transliterated as 'sz' rather than 'ss' actually as that might disambiguate the conversion of 'SS' to lower-case... Or maybe that would mean something totally different too? > I remember that it worked with your utf-8 patch, too, but I > tested only windows. I suspect that's just luck, or you only tested on windows. I don't think there's any reason to believe it worked any better than 1.3. > The other point (input characters): Although FLTK renders the > ISO characters > correctly, it returns utf-8 characters, if the non-ASCII > characters are entered > in an Fl_Input, e.g. (IIRC). I would have to convert this > back to ISO-8859-1 > anyway, because my server "speaks" ISO-8859-1 only (with an > additional Euro sign). The utf-8 patch includes some helper functions that should help with this, or there's always iconv... But yes, it is a nuisance. Maybe fl_utf8toa() or fl_utf8to_mb() or similar might help you? Worth a look, anyway. Cheers, -- Ian SELEX Sensors and Airborne Systems Limited Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list fltk-dev@easysw.com http://lists.easysw.com/mailman/listinfo/fltk-dev
