Folks,
the current CVS code of FreeType contains the following #if
clause as the central part of handling unpatented hinting:
in ttobjs.c:
#if defined( TT_CONFIG_OPTION_UNPATENTED_HINTING) \
!defined( TT_CONFIG_OPTION_BYTECODE_INTERPRETER )
...
However, the
Well, saying
ftgrid -f 1915 20 EPPGLH+DFHSMincho-W3-WIN-RKSJ-H.ttf
I get image A.
Pressing the `h' key I get image B.
BTW, I've compiled FreeType with `make devel', so the images use
the native TT bytecode interpreter.
That's why it works for Werner - I run into
Hello Ryan and all,
I just released a second release candidate for FT-Jam 2.5.3
that contains a fix for these aliasing issues. It's available
from:
http://david.freetype.org/jam/
be sure to get 2.5.3rc2 packages, not previous versions
note that I hope to make it a real release soon, testing
On Sunday 10 June 2007 20:28:50 David Turner wrote:
Hello Ryan and all,
I just released a second release candidate for FT-Jam 2.5.3
that contains a fix for these aliasing issues. It's available
from:
http://david.freetype.org/jam/
be sure to get 2.5.3rc2 packages, not previous versions
Hi Werner,
I believe that unpatented hinting doesn't make sense if you already
have the bytecode interpreter. This is why the code has been updated
some months ago to ignore the UNPATENTED_HINTING macro when
BYTECODE_INTERPRETER is already defined.
I just updated the documentation in ftoption.h
Hello Derek,
FreeType can return glyph paths for these fonts, but you need to
use either the patented or unpatented bytecode interpreter to get
correct results (auto-hinting or even no hinting will return
garbage). this means one of the following:
- activate the patented bytecode interpreter
