DO NOT REPLY TO THIS MESSAGE. INSTEAD, POST ANY RESPONSES TO THE LINK BELOW.
[STR New] Link: http://www.fltk.org/str.php?L2348 Version: 1.3-current To fix the original bug, I can see two ways: 1: Keep the illegal codes in the text editor and render a question mark (or whatever). Advantage: the text will not changed when loaded and save again. Disadvantage: I have to add special code handling all over Fl_Text_*, and it still may crash or misbehave. 2: whenever text is added to the widget, we verify that it is UTF-8. If illegal characters appear, we replace them with whatever may or may not be meant. Advantage: the existing Fl_Text_* code should always work and even display something useful. Disadvantage: the text will be forced to UTF-8, even if its original encoding was something else. Which should it be? 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
