ChaoWei wrote: > Don't xft support chinese font naming?
TrueType font can have multiple naming tables. If one of its naming encoding is in ASCII, then Xft will recognize it. Otherwise, Xft thinks the font name is NULL and you won't be able to use the font. One solution is to add/translate the naming table in ASCII/UTF-8. Also, the font can be used by Xft if it has a Unicode CMap. I don't know if that will be changed in the future. I have written a small utility to deal with the problem, if you are interested, you can try it at http://sourceforge.net/projects/oto/ > I test some chinese fonts under KDE, if with no anti-aliasing, these > fonts work fine; but with > anti-aliasing, at some sizes (like 9, 10, 12, 13) all glyphs are gone > and every window become > unlimitedly extended; but at other sizes(<8, 11, >13) work fine again. I have encountered the same problem before. After play with it for a while, I found that those fonts have embeded bitmap font in it, at those point sizes. You can use ftdump from ft2demo to check with your font to verify that. Even worse, I have a font with embeded bitmap font at two point size. I can not see glyphs at those two point size with ftview. Don't know why. Something to do with the font itself I think. If Xft/freetype have an option to ignore any embeded bitmap font in it, it should be very helpful. Regards, Yao Zhang _______________________________________________ Render mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/render
