Red Hat Bugzilla – Bug 582455
Java fontconfig needs to be updated for Japanese
Last modified: 2011-02-02 14:37:44 EST
Currently Japanese default font is VL Gothic and Japanese chars are not shown with Java in Fedora F13/rawhide.
% fc-match monospace:lang=ja-jp
VL-Gothic-Regular.ttf: "VL Gothic" "regular"
/usr/lib/jvm/jre-1.6.0-openjdk.x86_64/lib/fontconfig.Fedora.[bfc|properties.src] needs to be updated.
The following is the fixing script.
$ cat java-font.sh
sed -i -e 's/Sazanami Gothic/VL Gothic/g' \
-e 's/Sazanami Mincho/VL Gothic/g' \
I also checked RHEL6 and it seems fontconfig.RedHat.properties.[bfc|properties.src] doesn't exist.
fontconfig.RedHat.properties.[bfc|properties.src] could be copy of fontconfig.Fedora.[bfc|properties.src] with above my fix.
It would be good to fix Fedora rawhide/13 and RHEL 6.
Probably it would be good the current fontconfig.Fedora.* might be moved to fontconfig.RedHat.5.0.* but not 6.0.
This bug appears to have been reported against 'rawhide' during the Fedora 14 development cycle.
Changing version to '14'.
More information and reason for this action is here:
This is only fixing the symptom.
openjdk should provide access to all the fonts registered in fontconfig by default and not wait for someone to declare them in property files. Those files are a leftover from SUN's “let's reinvent our own private font stack” effort, they don't belong in a properly integrated floss jdk, and they are hampering the use of java on Linux for anything that needs to render text.
added icedtea patch for java's fontconfig files
java-1.6.0-openjdk-220.127.116.11-18.104.22.168.fc14 has been submitted as an update for Fedora 14.
java-1.6.0-openjdk-22.214.171.124-126.96.36.199.fc13 has been submitted as an update for Fedora 13.
java-1.6.0-openjdk-188.8.131.52-184.108.40.206.fc13 has been pushed to the Fedora 13 stable repository. If problems still persist, please make note of it in this bug report.
java-1.6.0-openjdk-220.127.116.11-18.104.22.168.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.