> > but instead I will have to type the > > fonts as shown here to be able to have them displayed in my > > application: > > http://www.seriss.com/people/erco/fltk/utf8-japanese-songs.cxx > > Yes.
Oh! One thing I forgot to say - if you have a UTF8 aware text editor, you can use that to enter the strings directly in your code. You *do not* have to encode them in "raw hex" as Greg did in his example. I think he only did it that way to make the code robust, so that it can be safely viewed and tested on platforms that do not have UTF8 aware text editing yet. In general, if you open a UTF8 encoded file in an ASCII-only text editor, the UTF8 text strings all get badly mangled. By encoding them as raw hex, that problem is avoided, but it makes the stings rather opaque. If you are using a proper UTF8 capable text editor, then that problem does not arise and you can enter your strings directly in the code. 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
