> I've compiled you fltk118-utf8 tar ball. I found I mast use > the "--enable-xft" > flag when I run ./configure. If not, fltk still can't show > UTF-8 chars. > Am I right?
No, you are wrong, I'm sorry to have to tell you! This tarball can handle UTF-8 text on linux whether compiled with XFT or not. The difference is the set of fonts that are used. I think (as I suggested yesterday when you were testing Oksid's patch) that the X fonts you are using do not have the necessary glyphs to display your Unicode text properly, and *that* is why it fails. When you run the XFT enabled build, you often get a different font file selected (since the Xft layer favours scalable, hinted, fonts) and these font files are often more "modern" and "complete". That said, Xft or not, displaying complex Unicode text with glyphs from many languages is still going to require careful font management in your code - very few fonts are currently Pan-Unicode capable, and the few that are, often have poorer quality glyphs. Also note that the font people are now thinking that Pan fonts are a Bad Idea and that a set of fonts, each specific to a language group, is a better solution... As a specific example - many of the fonts on my linux box are Unicode capable, but have the letters "-LGC" at the end of their name. This denotes that the font has glyphs for the "Latin, Greek, Cyrillic" language range (that being my "native" language range.) If I use one of these fonts to display Japanese or Chinese text, it fails to work, and I have to select a specific font for the task (often denoted as "-CJK" in this case, for Chinese, Japanese, Korean.) A Pan font would contain glyphs for both ranges, of course... As it stands at present, I don't think any of the fltk variants provide a platform independent way to ascertain the coverage of a given font, so you need to use platform specific code to query each font to see which glyphs it contains and what languages it can cover. It's not easy... > PS: > There is not "configure" script in your fltk118-utf8 tar > ball. So I only > run "make" after uncompress it. Is this right? The tarball is not prepared for building, you need to run autoconf on it to create the configure files. I thought it said that in my Readme. Does it not? Anyway, the sequence is; uncompress, then autoconf, then configure, then make. That's pretty standard, so ought to work OK for you, I think. > Are you still working on it? Or it's finished? I am still working on it a little. It will probably never be finished... It works well enough for what I need to do, but will probably never address *all* the issues of handling Unicode text - we'd probably need to link against libICU and/or PanGo to get started on that... -- 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 mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk
