> And there is also option #3: > > Convert the title string to UTF-16 to "clean" it as a side effect and > to be consistent on different platforms, and use a corresponding call. > "kCFStringEncodingUTF8" makes me suspect that there would also be > "kCFStringEncodingUTF16"...
Oh, I see what you mean; We call fl_utf8toUtf16(...) on the passed in string first, which should "repair" any bad codepoints (as it appears to do on winXX etc.) then use that for the window title, calling "kCFStringEncodingUTF16" or whatever is appropriate... That would also mean that all the platforms exhibit the same translation behaviour for the "bad" input string... Still, the check for NULL is probably a good idea too. > Of course, this is only fixing symptoms that /should/ not > appear, because > all input strings *should* be (correctly) UTF-8-encoded. ;-) Indeed. I'm sure that will happen... SELEX Galileo Ltd 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
