Re: [Devel] BCI no longer used by default

[Werner LEMBERG]

> I have put 3 figures at
>
>   http://yang.inescn.pt/~gjc/ftview-comparison/
> 
>       - ftview-2.1.8.png: compiled with freetype 2.1.8 with bytecode
> interpreter enabled;
> 
>       - ftview-2.1.9.png: compiled with freetype 2.1.9 with bytecode
> interpreter enabled;

I get *exactly* the same results with the current CVS as in
ftview-2.1.8.png if I press `f' in ftview to enable the auto-hinter.

>       - ftview-2.1.9-no-autohint.png: compiled with freetype 2.1.9
> with bytecode interpreter enabled and unpatented hinting algorithm
> removed (commented out #define TT_CONFIG_OPTION_UNPATENTED_HINTING)

BTW, my attached images have been created with exactly this setup.

> Some examples of differences:
>       - The '3' in 13: ... is less perfect in 2.1.9;

This is exactly how the glyph is hinted, as can be seen in the
fontforge snapshot after applying all instructions.  The green lines
should actually be splines, but it is not difficult to imagine which
pixels centers are actually within the outline.

>       - The small 'e's up to size 15 are much worse in 2.1.9;

The same here.

Any good guy out there which can provide some glyph snapshots of
Vera.ttf under Windows?  Note that the results we are discussing here
have been produced with a resolution of 72dpi which is not the default
for Windows.  Maybe the deviations are caused by a bug in FreeType's
TT hinting engine...


    Werner