> The "tricky" fonts like PMingLiU need unpatented hinting. Those
> fonts are unusable at all when programmers accidently turns on
> FT_LOAD_NO_HINTING. So I think freetype should force fonts like
> those to ignore FT_LOAD_NO_HINTING.
This is a fundamental question. My opinion is that shifting of glyph
elements using TrueType instructions clearly is (a kind of) hinting.
In other words, I don't like to change the current behaviour of
FreeType without good reasons.
However, it might be helpful if FreeType emits a warning message that
the font is probably unusable. Hmm.
Opinions, please. Maybe most of you disagree, so please chime in.
> And detecting of tricky font should be outside of this defines:
>
> #if defined( TT_CONFIG_OPTION_UNPATENTED_HINTING ) && \
> !defined( TT_CONFIG_OPTION_BYTECODE_INTERPRETER )
>
> otherwise, the fonts are not detected on my debian box.
This is probably fixed already in the CVS:
2008-11-05 Werner Lemberg <[EMAIL PROTECTED]>
* devel/ftoption.h, include/freetype/config/ftoption.h
[TT_CONFIG_OPTION_BYTECODE_INTERPRETER]: Undefine
TT_CONFIG_OPTION_UNPATENTED_HINTING. This fixes the return
value of `FT_Get_TrueType_Engine_Type' (and makes it work as
documented). Reported in bug #441638 of bugzilla.novell.com.
Please test. Otherwise, please report the vales of those two macros
on your box.
Werner
_______________________________________________
Freetype-devel mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/freetype-devel
