Around 20 o'clock on Aug 13, Juliusz Chroboczek wrote:
> Fonts in that format cannot be compressed -- OTF is intrinsically a > seekable format. On the other hand, sbits are a highly compact > format, allowing among others sharing glyphs (even between different > strokes) and bit-aligned rasters (Mac-style; Microsoft-style are > byte-aligned). I don't see that as a significant problem; the ability to compress the encoding vector solves the dominant cost of using 10646 encodings. We could glue a decompressor front end onto the existing TTF reader in FreeType if it became necessary. > I'm planning to modify mkfontscale to generate scalable entries only > if outlines are present, and to generate non-scalable entries > otherwise by checking what sbit strokes are included. Good. Now to generate something that can write TTF files with only sbit entries. Keith Packard XFree86 Core Team HP Cambridge Research Lab _______________________________________________ Fonts mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/fonts
