> 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 
> 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.) 
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..)


> Character conversion is not a problem as long as I know what 
> to expect.

Of course, if it was strictly utf-8, then maybe no conversion would be
needed!

> My scenario:
> 
> 1- I want special handling of some function keys (FL_Tab 
> etc..) this works fine via Fl::event_key().
> 
> 2- "Ordinary" letters should be send somewhere (composed and 
> with correct case.)

This should be event_text() I think. I'm not sure what you are
describing below - can you expand on the problems you are seeing?

> How can I achieve 2?  event_key() gives me keyboard button 
> codes (where most happens to map as 8859-1), Since these are 
> keycodes they miss shift-symbols and casing etc). 
> event_text() gives me UTF-8 encoded text but correct symbols and case.




SELEX Sensors and Airborne Systems Limited
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 mailing list
[email protected]
http://lists.easysw.com/mailman/listinfo/fltk

Reply via email to