The intention is that if event_text() is not empty then you should insert it as letters. If it is empty then you should use event_key() to figure out what key to use.
In future versions event_text() will always be UTF-8. For now if it is one byte long is it probably iso8859-1. jakob wrote: > Hello, and thanks for your answer! > >>> Using FLTK 1.1.9 (X11) event_text() gives me UTF-8 encoded text. >>> Is this always the case?, can I count on it being UTF-8 on=20 >>> all platforms? >> Are you sure it is utf-8? >> On 1.1.9 I'd expect it is more likely to be some ASCII code page >> (although for many western code pages, that's indistinguishable from >> utf-8, for small character values, of course.)=20 >> With 1.1.x series, which is not properly utf aware, I don't think you >> can count on the same encoding behaviour across platforms. >> There are utf-8 aware patches for the 1.1.x series that should do the >> "right thing" across platforms, and fltk-2 is utf-8 aware, and fltk-1.3 >> is going to be RSN (but I don't think it's been patched yet..) > _______________________________________________ fltk mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
