Re: [ft] anti-aliasing question

[Dave Calkins]

> On a related note, do I run into patent/license issues as a result of 
> hinting? I recall reading that on the FreeType site and based on that 
> description am thinking that using the hinting might actually mean I 
> need to secure a license. At what point, in regards to the hinting in 
> FreeType do I end up needing to deal with a license?

More specifically, I'm trying to understand how the below maps into code.

>>>
Is FreeType 2 Affected by the Patents?
The answer is no for any recent build of FreeType 2, since it comes with 
an ‘auto-hinting’ module that was specifically designed to completely 
ignore the TrueType bytecode instructions.

However, the source code for the bytecode interpreter is still available 
and can be toggled on at compile time, for those that want to use it 
anyway (because they purchased a license from Apple, or because they are 
in a country where the patents do not apply, etc.). For details please 
check the documentation that comes with your FreeType source package (it 
normally involves changing one configuration macro).
>>>

It sounds from the above that if I use FT_LOAD_DEFAULT, then it will be 
using the true type hinting byte-code potentially using the patented 
instructions but that I am required to use FT_LOAD_FORCE_AUTOHINT to 
avoid the patented instructions. Is that correct?