Re: [gtk-i18n-list] `.pcf' font not accessible from pango


On Sun, 15 Jan 2006 17:24:49 +0100
pottendo <pottendo utanet at> wrote:
>> for right fix, both of fontconfig and pango/gtk+ should
>> be modified, I think.
>Any comments by others on this list?

Although the Subject of this thread includes PCF,
we only tested BDF only.

Tracing the behaviour of fc-cache, I found there's
another reason in FreeType, either. fontconfig gets
infos of charset/encoding by FreeType's "face"
structure. The "face" is originally designed for
TrueType, the charset/encoding info of BDF/PCF are
returned as if the font were TrueType. The variety
of infos that can be passed by "face" is restriced
to TrueType's "cmap" specification. On the other
hand, the charset/encoding info of BDF/PCF is just
string. There's no restriction. To "synthesize"
charset/encoding info from given font, FreeType
returns platform=Apple & charset/encoding=Roman
(US-ASCII), if there's no way. This is why we cannot
use non-ASCII PCF/BDF via fontconfig.


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]