Red Hat Bugzilla – Bug 475743
Japanese desktop defaulting to Chinese fonts
Last modified: 2013-01-09 23:58:06 EST
Description of problem:
Since VLGothic-fonts is upgraded to 20081203, I see many
chinese glyphs on Japanese environment.
Downloading to 20081029 works good.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. For example, the following URL:
Created attachment 326463 [details]
screenshot with VLGothic 20081203
Created attachment 326465 [details]
screenshot with VLGothic 20081029
Also with 20081203 the glyphs of arabic numerals frequently changes.
my rawhide box is broken now so I can't do any testing... so just guessing, is this issue gone if you do remove /etc/fonts/conf.d/64-ttf-arphic-uming.conf or add testing for Chinese like:
<test name="lang" compare="contains">
<edit name="family" mode="prepend" binding="same">
<string>AR PL UMing HK</string>
<string>AR PL UMing CN</string>
instead of preference alias?
(In reply to comment #4)
> this issue gone if you do remove /etc/fonts/conf.d/64-ttf-arphic-uming.conf
It seems this works
> add testing for Chinese like:
> instead of preference alias?
Would you tell me to what file?
Behdad recently wanted to experiment with new syntax to deal with fonts that need locale-specific ordering. You should try to ping him to check if he hasn't a better fontconfig recipe.
(In reply to comment #5)
> Would you tell me to what file?
Try to replace:
<family>AR PL UMing HK</family>
<family>AR PL UMing CN</family>
in 64-ttf-arphic-uming.conf with the above for sans-serif.
(In reply to comment #6)
> Behdad recently wanted to experiment with new syntax to deal with fonts that
> need locale-specific ordering. You should try to ping him to check if he hasn't
> a better fontconfig recipe.
Aha. Cc'ing him.
Behdad, do you have any idea to resolve a kind of locale-specific ordering issue in fontconfig?
(In reply to comment #7)
> (In reply to comment #5)
> > Would you tell me to what file?
> Try to replace:
> <family>AR PL UMing HK</family>
> <family>AR PL UMing CN</family>
> in 64-ttf-arphic-uming.conf with the above for sans-serif.
Thanks. This seems to work for Japanese locale (I cannot test
for Chinese locale because I don't use it and I don't know
where to check...)
Created attachment 326711 [details]
glyphs of arabic numerals
By the way is it a different issue that the glyphs (especially
the widths) of arabic numerals change according to contexts?
I had an idea but I tested quickly and it didn't work. I'll think about it again. I have some other ideas about how to fix the CJK issues in fontconfig. I'm currently working on fontconfig. I'll see if I get to those.
I could lower the ranking of uming (Chinese fonts) by increasing the number of the .conf file.
Which side would you prefer to make the changes? VL Gothic, Uming, or fontconfig?
The Japanese problem seems to be with Sans: eg if one switches the desktop
application font to Monospace then VLGothic is used correctly.
Reverting to fontconfig-2.6.0-3.fc10 also fixes the problem, so this really does look like a fontconfig regression or change of behaviour.
Sample patch. Will modify sans and monospace if needed:
Thanks fixes the Japanese desktop problem for me. :)
I still don't understand the discrepancy between monospace and sans... Behdad, any idea?
If it didn't break some other things, then I'm going to build to rawhide.
(In reply to comment #12)
> I could lower the ranking of uming (Chinese fonts) by increasing the number of
> the .conf file.
> Which side would you prefer to make the changes? VL Gothic, Uming, or
No options for VLGothic-fonts at least because this issue doesn't happen without cjkuni-fonts.
Created attachment 330464 [details]
Still seeing many Chinese glyphs.
Note that this screenshot is taken with fontconfig-2.6.95-1.git.66.gb162bfb.fc11
With reverting to fontconfig-2.6.0-3.fc10 it goes _much_ better,
however it does not remove this problem entirely.
# rpm -qf /etc/fonts/conf.d/* | sort | uniq
(In reply to comment #19)
> Created an attachment (id=330464) [details]
> screenshot again
> Still seeing many Chinese glyphs.
What is the URL for that page?
I could be wrong but it could be a Unihan issue with firefox not knowing what language the page is in?
(In reply to comment #21)
> (In reply to comment #19)
> > Created an attachment (id=330464) [details] [details]
> > screenshot again
> > Still seeing many Chinese glyphs.
> What is the URL for that page?
Note that the glyph is wrong also on the other place
(please look at gnome-panel in the picture: especially the glyph
of "場所" is apparently not Japanese)
The URL is the same as the one in my comment 0.
Created attachment 330518 [details]
This is what it currently looks like for me, but I will try with a fresh rawhide install soon. :)
I just tried on a fresh rawhide install and it still looks good to me.
Tasaka-san, perhaps could you try again?
(Anyway unfortunately this fix/workaround won't be in F11Alpha anyway...)
Well, after some investigation, it seems that
when I hide (i.e. add 'dot' to the file name)
65-baekmuk-ttf-dotum.conf (in baekmuk-ttf-dotum-fonts-2.2-17.fc11.noarch)
it looks good now (even with fontconfig-2.6.95-1.git.66.gb162bfb.fc11)
Ah I see, thank you. Yes, baekmuk dotum is no longer installed by default, but sounds like a similar workaround is needed there too.
would still appreciate some comment from Behdad...
(In reply to comment #24)
> (Anyway unfortunately this fix/workaround won't be in F11Alpha anyway...)
I will push to F11 immediately when it is released.
(In reply to comment #25)
> Well, after some investigation, it seems that
> when I hide (i.e. add 'dot' to the file name)
> 65-baekmuk-ttf-dotum.conf (in baekmuk-ttf-dotum-fonts-2.2-17.fc11.noarch)
> it looks good now (even with fontconfig-2.6.95-1.git.66.gb162bfb.fc11)
Hmm, then I should also work on baekmuk then.
It seems that with baekmuk-ttf-XXX-2.2-19.fc11,
cjkuni-XXXX-0.2.20080216.1-20.fc11 Japanese glyphs are shown
There are .conf templates from package fontpackages. I applied from that.
cjkuni-fonts is patched:
baekmuk-ttf-fonts is patched:
No comment from Behdad so can probably close this for now.
Dunno if it is worth discussing the change of behaviour upstream...
On Fedora-10, the same bug appears after usual update.
Is this also related to this report?
(In reply to comment #32)
> On Fedora-10, the same bug appears after usual update.
It sounds like it could be.
What if you remove the baekmuk fonts?
(They are not default for Hangul anymore anyway.)
fontconfig-2.6.97-3.g945d6a4.fc11 again reproduces this problem......
I have only built on rawhide. Let me backport that.
(In reply to comment #35)
> I have only built on rawhide. Let me backport that.
May be better to test first on f10.
Behdad, could you please update on this important issue?
Created attachment 332187 [details]
screenshot with old fontconfig
(In reply to comment #34)
> fontconfig-2.6.97-3.g945d6a4.fc11 again reproduces this problem......
To clarify this, screenshot again.
This one with (the old) fontconfig-2.6.95-1.git.66.gb162bfb.fc11.i386 .
Created attachment 332188 [details]
screenshot with new fontconfig
And screenshot with new fontconfig fontconfig-2.6.97-3.g945d6a4.fc11
Japanese font glyphs are not used.
Yes, I see un-core-fonts being used on the ja desktop - I will try to get the fontconfig files there updated soon.
At last, I've found that cjkunifonts-uming package is the cause of this problem in my environment.
It seems like gryphs from that package are chosen in some cases, even in Japanese environments.
Japanese period followed by an alphabet is the one example.
After uninstalling that package, the problem goes away.
And I've confirmed that reinstalling this package caused the problem again.
I'll send you a detailed report later.
- Chinese gryphs are shown when you use Monospace even in Japanese locale.
- Some characters seems different in the same context, as different gryphs are selected according to the following characters.
(For example, the width of the space character followed by "A (alphabet)" has different width with the one followed by "a (hiragana)".)
Fontconfig choose proper gryph for virtual fonts, according to the current locale, and the context.
If you write Japanese in Japanese locale, fontconfig seeks to fonts which has Japanese gryphs.
It seems like some Chinese fonts also has Japanese gryphs by some reason.
Maybe, they are in CJ unified regions, so we cannot fix this problem simply by eliminating them.
Talking about the second problem, both Japanese fonts and DejaVu fonts have space characters,
so fontconfig sometimes choose gryphs from Japanese fonts, and sometimes from DejaVu fonts.
Change the gryph selection order of Fontconfig.
In Japanese environment, gryphs from Japanese gryphs should be chosen first.
In Chinese environment, gryphs from Chinese gryphs should be chosen first.
Talking about DejaVu fonts, either locale specific gryphs or DejaVu gryphs should be chosen
independently with the context.
This change maybe require huge change in fonts.conf and might need some patches in the source of fontconfig too.
I'm still confused. From what I understand, an alias I added in recent fontconfig updates is causing this. If that's true, which alias, and if you can move it further down to not cause the bug, what's the patch? Thanks.
Ok - I think we have to wait for an installable rawhide or F11 Beta
for further testing. With various font .conf files added to CJK fonts
I think things are a bit better now but there may still be some
more finer adjusts needed for F11?
Rawhide should be installable, what I need is a clear idea if this is really a beta blocker issue or not.
(In reply to comment #45)
> Rawhide should be installable, what I need is a clear idea if this is really a
> beta blocker issue or not.
Well, I tried the current fontconfig-2.6.99.behdad-3.fc11 and it seems
be working for me. So tagging this fontconfig as f11-beta may be
a good idea.
We just tagged so I'll close this rawhide.