> In the misc/cp1252.txt example, these 0x80-0x9f bytes appear as
> standalone bytes in the text. The Fl_Text_{Buffer,Display,Editor}
> code iterates through arrays of bytes. If the top bit is not set,
> it is plain old ascii: tabs, C0 control codes 0x01-0x1f and DEL 0x7fHmmm - is Fl_Text_* using the functions from fl_utf.c etc? If so, they should be "aware" of the "errors to cp1252" flag and do the right thing... Or... does Fl_Text_* have its own implementations that don't know about "errors to cp1252" - is that maybe what the problem is? -- Ian SELEX Galileo Ltd Registered Office: Sigma House, Christopher Martin Road, Basildon, Essex SS14 3EL A company registered in England & Wales. Company no. 02426132 ******************************************************************** This email and any attachments are confidential to the intended recipient and may also be privileged. If you are not the intended recipient please delete it from your system and notify the sender. You should not copy it or use it for any purpose nor disclose or distribute its contents to any other person. ******************************************************************** _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
