Description of problem: CJK fonts are not able to be displayed on KDE. Version-Release number of selected component (if applicable): FC2-re0415.0 qt-3.3.1-0.8 kdelibs-3.2.1-1.4 How reproducible: Always Steps to Reproduce: 1. Log in screen (gdm) select KDE as session and any CJK as language 2. Enter username/password 3. Actual results: Unable to display CJK fonts. (see attached screen-shots) Expected results: CJK fonts properly displayed. Additional info:
Created attachment 99466 [details] KDE screen shot in ja_JP.UTF-8 locale
Created attachment 99467 [details] KDE screenshot with ko_KR.UTF8 locale
Created attachment 99468 [details] KDE screenshot in zh_CN.UTF-8 locale
Created attachment 99469 [details] KDE screenshot in zh_TW.UTF-8 locale
it looks like something is broken in fontconfig. The issue does appear in GNOME too. with the same version of Qt/KDE, it works fine in FC1!
Still seems to occur with fontconfig-2.2.1-10 afaict.
Thanks Than for the info. However I have downgraded to RHEL3 fontconfig + freetype but seems it does not fix the problem, but if i downgrade to qt-3.3.1-0.5 the display is okay again. It may be possible that one of the patch in between qt builds that causes the problem. I am trying to debugg it, hopefully we will get some answers soon. Then we know which package should be causing the problem.
Found out it is one of the new code that changes QFontEngine that is having problem. Kochi currently is setting as a symbol font (need to find out why) and new code use this attribute to determine to use which charmap (UNICODE or FT_ENCODING_ADOBE_CUSTOM/FT_ENCODING_APPLE_ROMAN), so Kochi is mapped with APPLE_ROMAN and hence cannot display. I am submitting a patch to fix this problem. However it will unable to use the symbols from symbol font (ie. Dingbats). I will try to find a better way to do that. In the interim please consider this patch. Assigning back to qt.
Created attachment 99580 [details] interim fix for qfontengine
Currently by this coding the fontconfig font aliases are setting all scripts as support. so QFont::UnknownScript is also set in their scripts. Should they get support flag for QFont::UnknownScript? My take is it is better by not setting UnknownScript for alias fonts. Attached is the patch for it. It should fix CJK font display problem on current KDE.
Created attachment 99587 [details] Aliases Unknowscript fix
>interim fix for qfontengine: Leon, i have taken a look in src/kernel/qfontengine_x11.cpp, but did not find the location where it could match your patch!
>Aliases Unknowscript fix Leon, the patch looks fine for me. I will add it in next qt rebuild. thanks for the patch file ;-)
You can search for ~/\/\/ symbol font/ right? It is in the new fontdatabase patch tho. BTW comment #11 replace commment #9's patch so don't apply "interim fix for qfontengine". Let me know when you have the build. Thanks
i'm stupid! of course, it's in fontdatabase.patch. i'm now building qt-3.3.1-1 in dist-fc2-scratch that includes the patches. It would be nice if you cound test it in FC2. Thanks
I am in transit to Raleigh now, but as far as I tested remotely it looks good now! Thanks!
it's fixed in qt-3.3.1-1 or newer. Thanks for your report