On 20/11/10 00:34, Michael Sweet wrote: > 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.
Though I am conscious that the HTML5 spec seems to be saying that, at least for characters in the Unicode C1 controls block, then they can (should?) be interpreted as being the CP-1252 characters instead... Now, I know we are not talking about html here per-se, but that does seem to be a tacit acknowledgement that there is an awful lot of text out in the wild that claims to be UTF8 but is in fact hybrid... How we deal with it is of course another issue. But it is hard to consistently support the "hybrid" model, and I suspect the suggestion of going to "pure UTF8" may turn out to be the best solution in the longer term anyway. So lets try that - if it fails, it is probably easier to add hybrid support back in later than it would be to remove it once folk have come to depend on it... _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
