"fc-list" from the current CVS snapshot of fontconfig
lists pcf even if BDF properties like
FAMILY_NAME "Fixed"
CHARSET_REGISTRY "ISO8859"
CHARSET_ENCODING "15"
are missing. For details see:
http://bugzilla.novell.com/show_bug.cgi?id=150552
As FAMILY_NAME is missing, fontconfig lists the file name instead.
But as fontconfig only supports ISO-8859-1 and ISO-10646-1 encoded
fonts, it cannot use such broken fonts with other encodings anyway, if
trying to use them for example with "xfd", one gets only crashes:
mfabian@magellan:~$ fc-match johabshp16.pcf
johabshp16.pcf.gz: "johabshp16.pcf" "Regular"
mfabian@magellan:~$ fc-match ptpR24.pcf
ptpR24.pcf.gz: "ptpR24.pcf" "Regular"
mfabian@magellan:~$ xfd -fa johabshp16.pcf
Warning: Cannot convert string "johabshp16.pcf" to type XftFont
セグメンテーション違反です (core dumped)
mfabian@magellan:~$ xfd -fa ptpR24.pcf
Warning: Cannot convert string "ptpR24.pcf" to type XftFont
セグメンテーション違反です (core dumped)
mfabian@magellan:~$
Probably fontconfig shouldn't list such fonts in the first place
to avoid such problems.
--
Mike FABIAN <mfabian@xxxxxxx> http://www.suse.de/~mfabian
睡眠不足はいい仕事の敵だ。
_______________________________________________
Fontconfig mailing list
Fontconfig@xxxxxxxxxxxxxxxxxxxxx
http://lists.freedesktop.org/mailman/listinfo/fontconfig
