[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ft] autohinter is still bad for monochrome rendering... :(
From: |
user user |
Subject: |
[ft] autohinter is still bad for monochrome rendering... :( |
Date: |
Fri, 9 Sep 2005 05:45:47 -0700 (PDT) |
[quote="David Turner"][quote="Paul Tanganelli"]
I'm at my wits end here...
I'm trying to render some simple monochrome characters
to a single texture to use as the source for my
interface character set. Take a look at the attached
image to see what I'm shooting for. Everything is
working great, except I just can't get the font
quality up to par. I've tried just about every
combination of load flags in FT_Set_Char_Size, but
nothing seems to look good. Zoom in and notice the
bulky W and the lopsided 8 for instance. Its 12 point
Arial on Win2K.
[/quote]
What version of FreeType are you using ? Have you
manually enabled the bytecode interpreter by tweaking
ftoption.h ?
If not, the output is the result of the autohinting
algorithm, that will never produce glyphs that are as
good as the native TrueType hinter for high quality
fonts like Arial.
Note: the auto-hinter is not correctly optimized for
monochrome rendering.
[/quote]
[quote]
Note: the auto-hinter is not correctly optimized for
monochrome rendering.
[/quote]
Why is that still not fixed yet? Those quotes came
from the FreeType January 2003 mailing list archives,
and the newest version of the FreeType auto-hinting is
still bad for monochrome rendering...
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
- [ft] autohinter is still bad for monochrome rendering... :(,
user user <=