Red Hat Bugzilla – Bug 651651
[kde-l10n] [subpixel] kickoff does not show any Chinese characters in Chinese locales
Last modified: 2013-07-18 20:07:53 EDT
Created attachment 459296 [details] kickoff for Locale: zh_CN.UTF-8 Description of problem: KDE kickoff menu does not show any Chinese characters in Chinese locales (both zh-CN and zh-TW). While jp and kr do not have this problem. The classical/traditional menu mode acts normally. Version-Release number of selected component (if applicable): kde-l10n-Chinese-Traditional-4.3.4-5.el6.noarch kde-l10n-4.3.4-5.el6.noarch kde-l10n-Chinese-4.3.4-5.el6.noarch How reproducible: Always Steps to Reproduce: 1. Edit /etc/sysconfig/i18n, and add this line LANG="zh_CN.UTF-8" or LANG="zh_TW.UTF-8" 2. Login using kdm 3. Switch to kickoff menu mode. 4. Invoke kickoff menu. Actual results: Chinese characters are not shown. (see attachment) Expected results: Chinese characters are shown. Additional info:
Created attachment 459297 [details] kickoff for Locale: zh_TW.UTF-8
Created attachment 459298 [details] Japanese locale seems normal
I don't think it's fonts missing, as other application and KDE traditional menu can show Chinese properly. Perhaps that's because my special configuration: screen rotation. Previously in fedora-12, it does have refresh problem. Not quite sure it's relevant, I will investigate more.
Created attachment 459595 [details] My xorg.conf which rotate screen to right.
After a few experiment: 1. It does not seem to be related in xorg.conf 2. If I select a Chinese font in System Setting->Look and Feel -> Appearance -> Font -> General. Yes, it act as expected. 3. I have also tested the font substitution qtconfig-qt4. No, that doesn't work. Guess it's font substitution's problem, but I am not really sure where to check the "actual" font substitution rules.
it's definitely the font config setting which causes this problem. You can take a look at $HOME/.fonts.conf, this config file contains the rule for font substitution and you also have take a look at /etc/fonts for global setting.
After another wiped out all the .font* and few more experiment, I find out that if I turn off subpixel support, the problem disappear. When turn the subpixel on, the problem occur. Thus I change the title, and feel free to assign this problem to rightful owner. F.Y.I: Fedora 14 KDE does not have this problem, perhaps we can back port its improvement from it?
This request was evaluated by Red Hat Product Management for inclusion in the current release of Red Hat Enterprise Linux. Because the affected component is not scheduled to be updated in the current release, Red Hat is unfortunately unable to address this request at this time. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux. If you would like it considered as an exception in the current release, please ask your support representative.
and is Fedora ok?
This problem does not occur on Fedora 14 and later. I have also tested F19, (kde-l10n-4.10.1-1, kde-l10n-Chinese-Traditional-4.10.1-1 ) and it went well.
How about for a new user?
New users also have same problem. After further tested, I found that: 1. Font that trigger the bug "Serif", "Sans Serif", "Monospace" and size need to be between 8 and 12.
You also need to install cjkuni-uming-fonts to reproduce the problem.
Installing cjkuni-uming-fonts-0.2.20080216.1-51 from f18 does fix the bug. So I think this can be fix in cjkuni-uming-fonts
Created attachment 733014 [details] Proposed fontconf Hi Ding-Yi Chen, Thanks very much for the help! Please review the new fontconf file.
(In reply to comment #19) > Created attachment 733014 [details] > Proposed fontconf > > Hi Ding-Yi Chen, > Thanks very much for the help! > Please review the new fontconf file. The font config works for me. Thanks!
Verified, it's fixed. Please see the attached screenshot.
Created attachment 761130 [details] Fixed-[zh_CN][zh_TW]KDE-kickoff
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHBA-2013-0962.html