me: >> But, mk_wcwidth() uses the proper ISO definition for certain >> control and compose characters, whereas I think both you and >> Albrecht have said that the U+0080 to U+00FF control characters >> are often mapped to Windows-1282 code page equivalents (e.g. euro >> currency character?), so there's the potential for confusion when >> cutting and pasting.
Ian: > Yes - this is a tricky one. > I think it is just the range U+0080 to +009F actually, but there > appear to be a heap of web pages and docs that claim to be utf8 > but have chars from MS cp125x that use that range... The euro > symbol being one such. Oops. I got the code page number wrong too. :-( > I even saw a recommendation (I think in the Unicode docs, maybe > w3c docs) that for the purposes of portability, web browsers and > text viewers and the like, on encountering these codes, should > interpret them as cp125x just to be on the safe side... > > Now, there is an option in the fltk utf8 utility functions > (ERRORS_TO_CP1252 in fl_utf.c) to do that, and it is currently (in > fltk-1.3) ON by default. To start with, I'm just looking at handling the ISO definitions, as is, and will add warnings to the documentation. Then I'll look at this extra mapping. After that we probably need an RFC to discuss it. D. _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
