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 Thanks for your comments. Both of Albrecht's suggestions are implemented in the attached file Fl_Text_Buffer3.patch. I agree with Duncan that a class to handle alternative encodings and to declare which are supported would be desirable. But I have no time to code all of this before the release of 1.3. The attached patch only brings minor additions to the 1.1 API, and doesn't go yet in any direction about support of alternative encodings because only UTF-8 and CP1252 are supported (Support for other encodings is not in the API at this point). So I don't think we hinder any future improvements by committing this patch. Duncan: I believe the conclusion of this STR is yours since it's under your name. 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
