JC> I just tried importing each of the utopia bdfs into pfaedit and
JC> generating a ttf. The 18pt and 24pt 75dpi bdfs could not be imported
JC> w/o overwriting 100dpi versions because they had the same PIXEL_SIZE.
JC> I think this is a limitation of pfaedit rather than the ttf/otf format.
It's a limitation of the font format. A strike is identified by two
values, which are the horizontal and vertical em sizes in pixels.
(The two may be different if pixels are not square.)
JC> The resulting ttf worked fine.
Could you tell me whether the hmtx contains a full set of metrics, or
only metrics for .notdef? If you don't know how to do that, could you
please send me the output of
hexdump -C < foo.ttf | head -n 20
JC> OTOH, the pfaedit-generated ttf (or otf) was about 1/6 larger than the
JC> total of the gzip(1)ed pcf files per wc -c, but only 8k larger per du.
I'm getting slightly worse results here:
8x13.pcf: 304676
8x13.pcf.gz: 56523
8x13.ttf: 73644
This should be taken with a grain of salt, as I'm generating a trivial
hmtx table, trusting the rasteriser to do the right thing with EBDT.
The font will be slightly larger if I decide to generate a full hmtx.
On the other hand, this will get smaller when I implement (1) glyph
sharing (encoding multiple identical glyphs only once), (2) composites
detection (encoding a composite glyph as a reference to its
components), (3) segments with uniform metrics and (4) bit-padded (as
opposed to byte-padded) bitmaps.
Juliusz
P.S. And no, it's not ready for distribution.
_______________________________________________
Fonts mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/fonts
