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 In attached file Fl_Text_Buffer.patch, I propose changes in the file reading functions of the Fl_Text_Buffer widget that don't change the API. - UTF-8 and CP1252 are accepted as input encodings. - every byte that's not correct UTF-8 is interpreted as CP1252 and transcoded to UTF-8. - all data that enter the Fl_Text_Buffer widget are pure UTF-8. - if the Fl_Text_Buffer data differ from the input data, a warning message is displayed by an fl_alert() call. - multibytes cut between successive buffer reads are correctly handled. - the code is written in the form of a filter, so it can be easily extended in the future to support several filters with the addition of an adequate new class. I believe that putting unchanged non-UTF-8 data in the Fl_Text_Buffer widget, whatever the trick to do that, is incompatible with editing this data because edition will UTF-8-encode any new data. 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
