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?
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?