New discovery: If I load the font with fontforge, save it using UTF intead of the original GB encoding, then I got new files that can be listed in fc-list.
So I guess fontconfig ignores fonts encoded in GB encoding. The easiest fix is to ask X.org to deliver these 2 fonts in UTF instead. Which would be a different bug on a different tracker (X.org instead of launchpad), right? ** Attachment added: "The new font file for SongTi saved from fontforge in UTF." https://bugs.launchpad.net/ubuntu/+source/fontconfig/+bug/568855/+attachment/3203185/+files/SongtiMedium-16.pcf.gz -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/568855 Title: "song ti" and other bitmap fonts are not available even if using yes- bitmaps rule To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-translations/+bug/568855/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
