> Our team is developing a product that uses the toolkit > intensively. At certain point we will need UTF-8 support > there. So, it's crucial for us to get an estimate on when > FLTK 1.3 is going to be released.
Hard to say - we are trying to clear the remaining STR's against it, but resources are constrained, we can only do so much... If you have some resource available, feel free to devise patches to fix the remaining issues, we'll very much appreciate the help! In the meantime, fltk-1.3 is basically stable, so if you are static linking to it, you can probably use what's there without any problems. I'd avoid dynamic linking until we are sure we have frozen the ABI/API level encoding though. At the very least, testing your existing code base against fltk-1.3 then letting us know of any issue you find, would probably be good thing to do. But the answer to your original question is, as with any open source project, "When it's ready." Help welcomed. 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
