Byeongsik Jeon bsjeon@hanmail.net wrote:
Shouldn't Freetype itself set appropriate interpreter version based on GASP flags instead?
At first, I thought this was a Freetype bug. But when I look at the Freetype API design, it seems intentional. They know this mechanism and they have been keeping this API design for a long time.
Why not ask Freetype developers to take into account gasp flags and appropriately tune the rendering especially if it's known to cause the rendering bugs?
In short, the fonts can be created considering version 35 or version 40 or both. And record that information on the gasp table.
When The program(or OS, etc) uses the fonts, it is optional to render which interpreter version is applied. In this way, MS GDI and DirectWrite rendering results may be different.
In fact, because the Freetype implementation is different from Microsoft, our choices are limited.
Obviously applications running under MacOS or Windows don't have such a problem, and application developers shouldn't even bother or try to accomodate for font renderers bugs.