On 01.04.2008, at 04:58, Michael Sweet wrote: > MacArthur, Ian (SELEX GALILEO, UK) wrote: >>>> Fl_String: basically typedef'd to "char*" (UTF-8 encoded >>> unicode), but >>>> on WinCE, it would be WCHAR* >>> That's just a bad idea - you'd break source compatibility when >>> compiling on WinCE. While we might have common UTF-8 conversion >>> functions to go to UTF-16 at display-time, for example, we don't >>> want to expose those implementation details to the application >>> developer. >> >> OK, so fltk should be strictly utf-8 internally, and convert to the >> local type (ASCII, utf-8, utf-16, utf32, other MBCS format...) only >> at >> the "edges"? (By edges I mean inputs, outputs, drag/drop, display, >> etc...) >> In that way the programmer can safely assume all strings are utf-8 >> for >> portable code? > > Correct.
I hear you, guys. Will do. Matthias ---- http://robowerk.com/ _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
