[GOODIE] Freetype/2 antialiased fonts demo ( v2;
knows about styles and is somewhat faster without the plugin )
Bert Freudenberg
bert at impara.de
Thu Mar 25 08:53:10 UTC 2004
Am 25.03.2004 um 02:41 schrieb Yoshiki Ohshima:
>> The BitBlt changes could also benefit TTCFonts which are rendered in
>> a single
>> color. Right now we're caching 32-bit forms rendered in a single
>> color. Using
>> this 8-bit deep encoding would mean that we could save at least 75%
>> of the
>> memory, and more whenever we're rendering the same glyphs in different
>> colors.
>
> Yup. I always wanted to have the rule since Arjen announced his
> code!
A per-component alpha rule would also be nice to allow for subpixel
positioning on LCDs.
>> For reference, I'm using the auto-hinting in Freetype/2 (that is, my
>> version
>> is compiled without the patent-encumbered interpreter).
>
> The FT2 version uses somewhat thinner face?
FT2 snaps vertical lines to the integer pixel grid, which makes the
fonts appear considerably sharper. However, you loose fine nuances in
the line width. If you take the "v", for example, the TTCFont version
makes the left line be thicker than the right one, which is not the
case in the FT2 version. I guess at small font sizes the FT2's "fixed
width" approach makes sense. However, if you had subpixel addressing,
you would gain a three-fold increase in horizontal resolution, allowing
for finer control of line width.
> The 'y' glyph and some others are as blurry as TTCFont version. It
> is interesting.
This is because the snapping only works for vertical (and horizontal)
lines, making sloped lines look blurry.
- Bert -
More information about the Squeak-dev
mailing list
|