|
From: | Moony |
Subject: | Re: [ft] Modifying/Enhancing the Truetype Interpreter |
Date: | Mon, 21 Dec 2009 18:57:29 -0600 |
User-agent: | Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.9.1.5) Gecko/20091209 Fedora/3.0-4.fc12 Thunderbird/3.0 |
It's not very difficult, I believe. You probably have to add some flags to one of the internal TrueType interpreter structures to store the results of the bytecode signature scanning. Do you have any ideas how many fonts are affected? Which of them are important/well known?
Off hand, I know that MS core fonts would benefit from this. (Basically, any TT font that was hinted with B/W rasterization in mind). Redhat Liberation fonts also seem to be hinted with B/W in mind, as they supposed to be metrically compatible with the core web fonts.
In my experience, the fonts that are already "optimized" for CT don't suffer nearly as badly.
No, I do not. I have tinkered with the code a bit, but haven't really had a chance to sit down and seriously try something. I was thinking though- is it even necessary to have a resolution to snap to in the X direction? In this scenario perhaps grid-fitting to 1/3 pixel in the X direction would be considered "full hinting" and leaving the X direction alone entirely would be considered "slight hinting"?And finally, do you have a working ClearType emulation, this is, at least tripling the horizontal resolution for calling the bytecode interpreter, then compressing the results again for proper subpixel positioning?
[Prev in Thread] | Current Thread | [Next in Thread] |