Ian: > As you may be aware, I've been wrestling with support for surrogate = > pairs encoding Unicode supplementary plane glyphs on Win32 recently = > (though I may now be seeing some light at the end of that tunnel..) > ... > Thoughts?
In all of the discussions about the initial level of UTF-8 and Unicode support that would be incorporated into FLTK-1.3.x, surrogate pairs were one of the things that were deliberately excluded. Ironic, no? I wonder whether one platform or another is going to require that FLTK also supports composing characters, or one of the other things that appeared to be "optional" at the beginning, for implementation later. It is starting to look like we need to stop dealing with different layers of the onion, and just have a catch all "fl_everything_to_utf8()" conversion as the user facing part of the API ... :-( I don't work with Windows/Mac, so I'm unable to contribute at the mo :-( Sorry D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
