So anyone who use freetype or libraries that use freetype (like
cairo) will have to be make awared of this problem. I'm not sure
how practical this will be.
Graham's suggestion of introducing a flag in FT_Face sounds good.
If I understand his sugguestion correctly, the user always has
With current cvs I get no-ink rendering of cff fonts when using
the light autofitter. Type1 and glyf fonts work correctly.
Fixed in the CVS. Thanks for the report.
Werner
___
Freetype-devel mailing list
Freetype-devel@nongnu.org
That proposal looks right. It, of course, has the advantage of
backwards compatability in that current apps and libs will just work
once ft is upgraded.
Now to deal with the quarter or two metres of snow which fell since I
last posted here. [SIGH] If you don't hear from me again I'm probably
On 2008-12-05, Werner LEMBERG [EMAIL PROTECTED] wrote:
After some thinking I can imagine that the following works.
. Add `FT_FACE_FLAG_TRICKY'. If set, the font is tricky. To access
it, add a macro `FT_IS_TRICKY'. [This is a read-only flag.]
. Change the meaning of
FT_LOAD_NO_HINTING now has a implication: I will do some auto fixing
with the hinting when neccessary unless your also prevent me with
NO_AUTOHINT.
? I fear I don't understand. Please explain what you mean.
Werner
___
Freetype-devel
