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 I've been wondering about this since Albrecht queried whether fl_utf8fwd() and fl_utf8back() would work in the Fl_Text_Buffer ring buffer, but since then I've been waiting to see what Matt had up his sleeve at the end of the mega-refactoring. I had wondered whether it would be possible to extend next_char() and prev_char() so that they copied the current and next/prev six bytes (max possible utf8 sequence) into a temporary buffer, and then called fl_utf8fwd/back() to determine how many byte positions to move forward/backward. Or to provide Fl_Text_* member function equivalents for fl_utf8fwd() and fl_utf8back() that were "gap aware" and use these exclusively. I have to admit that I haven't looked at the Fl_Text_* code in any detail since the refactoring, so don't know whether this trick could also be used in the other places where the code steps through and compares against 0x80 on a byte-by-byte basis. My own feeling is that although it would simplify life to convert the cp1252 0x80-0x9f C1 control characters to something else, users might not be so happy if their files were silently changed for them. Whether we display ? or [] or an equivalent character is a detail. 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
