So I'd like to make the following changes to David's proposal:
All of this looks very promising. I think the final decision on the
table format can only be done after converting a bunch of BDFs forth
and back.
Werner
___
Fonts mailing list
I also recall discussions which discovered that the .otb extension
was otherwise unused in most of the world. It doesn't matter at all
to me; I ask FreeType to try and open the font, completely ignoring
the extension has proven a valuable property, although it does
sometimes challenge the
In order to preserve bitmap font names as we switch to sfnt for
XFree86, I need to have fonttosfnt put the original font name in
some place where mkfontscale can find it.
The proper way would be to formally define a new sfnt table, for
example ``XF86''. However, I think it is simpler and
1. FreeType crashes at ttgload.c:103 if hhea-number_Of_HMetrics
is 0. The problem is with k, which is assumed to be at least 1.
I've just added a guard, thanks.
2. FreeType refuses to get an sbit that has a glyph index beyond
maxp-numGlyphs. Note that the OpenType spec explicitly
I'm attaching a little test program that you should run on 8x13.bdf
and 8x13.pcf. Please notice the (x, y) couple printed for every
glyph, which are, respectively,
face-glyph-metrics.horiBearingX and
face-glyph-metrics.horiBearingY.
The 8x13 font has a bounding box of (0, -2)
RG (I tested it with Arphic TTF which be distributed with most
RG Linux distributions and all *BSD.)
Hmm, there may be problems with this font; I'm told it has bugs.
Maybe the FreeType folks can comment?
Yes, Just's ttDump reports a problem with the `glyf' table (and
dies :-) -- all other
