DO NOT REPLY TO THIS MESSAGE.  INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.

[STR Pending]

Link: http://www.fltk.org/str.php?L2348
Version: 1.3-current


What I think is that all text should be stored in FLTK as UTF-8, with
no exceptions. We've all seen how complicated the Fl_Text_* classes
were before in order to store one thing [raw bytes] and display, select,
and edit another [expanded <ctrl> representations].

Every place where text can enter the FLTK system needs to be able to
convert from raw bytes to UTF-8, and raise a flag so that the user knows
if that text has been converted. So from that point of view, and so that
we can make progress towards the 1.3.0 release, I'm happy for you to
apply your patch and we can close this STR.



However, I think that we need to raise an STR/RFE against 1.4 to discuss
how we can support not just the CP1252 superset of ISO-8859-1, but also
all of the other ISO-8859-* character sets (which would give us all of
the characters needed by European languages, and some Arabic and Hebrew
too). I shall raise the question in fltk.development now...


Link: http://www.fltk.org/str.php?L2348
Version: 1.3-current

_______________________________________________
fltk-bugs mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk-bugs

Reply via email to