Yes, I can do that. Perhaps I use FT_LOAD_SUBPIXEL_HINTING instead? Or
do you want to use FT_LOAD_CLEARTYPE_HINTING so that people understand
what this is attempting to duplicate? Just looking at it from a
trademark point-of-view.
I would also like to get others to test the patch before
Yes, I can do that. Perhaps I use FT_LOAD_SUBPIXEL_HINTING instead?
Oh, yes, definitely better.
I would also like to get others to test the patch before formally
submitting anything, to make sure I'm approaching it as generally as
possible, and not specific to the fonts I like.
If the
This one adds back a couple features that the older patches had,
that do apparently follow the whitepaper after all. DejaVu fonts
are fixed as well as Palatino Linotype, italics, and some glyph
shapes (e.g. w x y z). Some regressions in Courier New. Not
intended to be a totally clean
Yes, I used the grayscale hinting setting for a few reasons. Perhaps
I'm not completely understanding what I am doing, but my reasons were this:
- Currently in Freetype, there is a setting for grayscale vs. bi-level
TT hinting, however in reality there exists only TT bi-level hinting.
In
Ah yes, you have found the major weaknesses of the patch. :) I am
still trying to determine why DejaVu doesn't seem to be hinted at all,
or very poorly, and why Palatino doesn't render. On the other hand,
Liberation fonts and most legacy MS fonts look great. Some Apple ones
look good and
Here is an updated patch that does a better job of setting the stage for
a split between grayscale and subpixel. I'm still forcing subpixel in
ttinterp.c because there AFAIK there is no way to set this with
fontconfig currently.
