> 1. Is fltk 1.1.9 the last in the line?
In principle, yes. In practice, there might be a 1.1.10 to sweep up a few enhancements back ported from 1.3.x, but don't hold your breath while waiting... Any changes to the 1.1.x series are unlikely to help with the problem you identify in question 2. > 2. How do i get the correct encodings for 1.1.9 Applications in > 1.3.x > It's a mess. All Words with some carrecter like ö,ä or > ü ar cutted after these. It where cutted everywhere. In > Labels in Textboxes. > > What is to do? What is going on here is that 1.1.x assumes your text strings are written using locale based "code pages" that define how to map from bytes in a string to characters, for any characters outside the basic ASCII set (and sometimes even for a few characters within it!) But 1.3.x has been converted to use UTF-8 for all strings - this is much more flexible and portable, and hugely increases the number of languages and character sets we can handle. But it also means that many of your existing strings will need to be translated from the locale encoding to UTF-8 to work. Most recent text editors will do this translation for you, of course, so it shouldn't be too hard. 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
