> Understanding more and more about languages, script, glyphs, fonts, > and layouts, I realize that we can never produce a perfect UTF8 > support. So let's keep it fast and light and allow rendering of all > fonts and simple text input. The existing code base is just fine for > that.
Yup - I hear that loud and clear, all right... Of course, it's not utf-8, or even Unicode in general, that's hard - what we have it fine for that. It's all the baggage that is *presumed* to go along with it that makes it so. People, I think, assume that because we can render Unicode glyphs and sequences, then that means we can render arbitrary strings of (for example) Indic scripts. But in reality there's a whole world of difference between being able to render the "raw" glyphs, and being able to appropriately render (or worse, edit!) complex scripts. Editing complex scripts is *hard* - the size, shape and position of the glyphs changes on the screen as you type, depending on the characters preceding them, or the characters you add after them... It's too difficult to support in fltk, and I don't believe we should try. There are other libs dedicated to that task already! -- Ian 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-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
