On Nov 19, 2010, at 3:45 PM, Duncan Gibson wrote: > ... > Before we release FLTK-1.3.0 and commit to keeping the same character > set support until at least the next major release after that, we need > to decide on whether we support one of [at least] three options: > > 1. We decide that FLTK-1.3.0 will be the first release that will > support pure UTF-8 only, and that CP1252 data in files, etc. will > be converted to pure UTF-8 during input, with or without warning.
I think we actually want option 1A, namely that we don't do any stinkin' automatic conversions and that everything is UTF-8 only. In theory we could support Bill's original "ISO-8859-1 + UTF-8" hybrid mode, however that adds a lot of complexity and may have issues if we expand it to include CP-1252 (which is a superset of ISO-8859-1). Moreover, it puts the onus on us to correctly guess the encoding and convert every time we draw, since no system API supports the hybrid mode. Windows and UNIX/Linux/Mac OS X already have APIs for converting to/from UTF-8, so my recommendation is to document that FLTK 1.3.x is UTF-8 only and point to the corresponding APIs for those that want/need to support legacy character sets. ________________________________________ Michael Sweet, Easy Software Products
_______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
