Please don't reply off-list. Replies on-list are more likely to be of benefit to the wider community.
> Sorry, I forget to tel about my FLTK version indeed. I have FLTK > 2.0.x-r5940. > I looked *.h files in FLTK dir and found only utf.h. Oh, I don't use fltk-2 much, so what follows is based on my experience with utf8 and fltk-1.1. I don't think it is that different, however. > FL_API unsigned utf8towc(const char*, unsigned, wchar_t*, > unsigned); > FL_API unsigned utf8fromwc(char*, unsigned, const wchar_t*, unsigned); > > Do you want to say, that everytime, when I need to display my codepage > letters I have to convert them from L"...." string to char* with > utf8fromwc function? I thought you said in your previous post that you are on a linux host, and your "code page" was set to a utf8 setting? In which case, why do you have strings in a wide-character representation? If your system is set to utf8, then it should be manipulating strings in utf8, which is a strictly byte-wide representation of the Unicode. No wide-character conversions should be required. If you pass utf8 strings to a fltk-2 program I would expect it to display them correctly, assuming the font that is set for that widget actually contains the glyphs needed to display the characters. Perhaps you just have the wrong font selected? I imagine the "default" fonts that fltk sets may refer to a latin font space? Try setting the font to something you know has Cyrillic glyphs, or maybe to one of the Deja-Vu or similar "LGC" fonts (LGC is latin-greek-cyrillic, and denotes a font that contains "all" the glyphs necessary to cover those language groups.) > And how will these characters be displayed in other > systems (locales). Will my program meet with an old problem when the > text in one language wasn't displayed correctly in other. No, it should work - the point of Unicode in general (and in this case utf8 in particular) is to essentially remove the concept of code pages etc. Once your system is supporting utf8, it should (in principle) be able to display character glyphs from any language correctly. Of course, this assumes that the font you have selected actually has the character glyphs for the languages in question. Most fonts still only support one or two languages well. There are a few so-called "Pan-Unicode" fonts available, but very few of them actually do cover the entire Unicode space, and the quality of the character glyphs they contain is often quite unsatisfactory... 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
