From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; ja-JP; rv:1.2.1) Gecko/20030225 Description of problem: We've disabled using the bitmap font on CJK Desktop before. but the bitmap font are used for the rendering on Japanese. of course it depends on which size the font has, though. I'm not sure where it appeared since. at least I can see this problem on Cambridge-re0612.2. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.choose the Japanese as the language on gdm 2.log in GNOME 3. Actual Results: the bitmap font are used for the rendering Expected Results: the outline font should be used as well as other languages. Additional info:
This is: http://www.fontconfig.org/cgi-bin/bugzilla/show_bug.cgi?id=98 I'll wait a bit for Keith to come up with a fix before tackling it myself... it's a complicated portion of code that I don't understand very well.
Look like other CJKs (I checked TC on Severn) are using hinting right now because of this bug.
I don't want to backport the fontconfig changes to the stable version we are shipping because they are just too big and likely to break stuff. So, I took the simple route and just listed all the CJK fonts we ship explicitely. I fixed this a while ago in our package CVS repository and in the RHEL 3 beta packages, but it hasn't been rebuilt yet in Cambridge because of some problems with Perl include paths. I'm trying the another build now to see if that's been fixed. * Fri Sep 19 2003 Owen Taylor <otaylor> 2.2.1-5.0 - Tweak fonts.conf to get right hinting for CJK fonts (#97337)
Now in the Cambridge tree; leaving open so that I remember to switch the fonts.conf back when we move to the next release of fontconfig.
*** Bug 105898 has been marked as a duplicate of this bug. ***
Does the hinting for CJK we have in Cambridge is no longer like the hinting in 9 or Taroon?
Sorry false alarm. It was just my illusion :)
As you have mentioned, is it possible to build the latest fontconfig into fc2 so that we can start testing it?
I built the latest fontconfig, 2.2.92, myself and have been using it with no problems for quite a while on Fedora. I think it's very stable and worth using for the way it fixes this problem.
The link in comment 1 is now <http://pdx.freedesktop.org/cgi-bin/bugzilla/show_bug.cgi?id=98>.
Rechecking the list and now it works fine. Closing the bug now.