On Friday 18 of April 2003 22:52, Noah Levitt wrote:
> I came across the same problem. Keith said, "Looks like that
> font is missing the 'ENCODING' property". I opened it and
> saved it with xmbdfed, and then fontconfig was able to see
> it.
Thanks. But since mkfontdir somehow generates a correct entry with iso10646-1
encoding for such fonts, couldn't fontconfig be fixed to accept them as well?
--
__("< Marcin Kowalczyk
\__/ qrczak@xxxxxxxxxx
^^ http://qrnik.knm.org.pl/~qrczak/
