Re: [Devel] BCI no longer used by default

[Gustavo J. A. M. Carneiro]

Qua, 2004-11-10 às 13:46 +0100, Werner LEMBERG escreveu:
> > What happened?  Does freetype 2.1.9 not use bci by default even if
> > it is compiled in?  Any way I can change this default?  And why was
> > it changed, btw?  Thanks in advance.
> 
> Please do a comparison with the FreeType demo program ftview and
> compare the output (probably using the latest CVS snapshot).  This
> assures that the problem is really with FreeType.

  Yes, the problem is with freetype and it happened between 2.1.8 and
2.1.9.

  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;

        - 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)

  The results in ftview-2.1.9.png and ftview-2.1.9-no-autohinting.png
are identical, and they are much worse than ftview-2.1.8.png.  Some
examples of differences:
        - The '3' in 13: ... is less perfect in 2.1.9;
        - The small 'e's up to size 15 are much worse in 2.1.9;
        - The letters 'c', 'q', and 'o' are worse in 2.1.9 at size 9.

  Something must have caused this regression in 2.1.9... more than
enough to make me downgrade freetype in FC3.

> 
> 
>     Werner
> 
> _______________________________________________
> Devel mailing list
> address@hidden
> http://www.freetype.org/mailman/listinfo/devel
-- 
Gustavo J. A. M. Carneiro
<address@hidden> <address@hidden>
The universe is always one step beyond logic.

smime.p7s
Description: S/MIME cryptographic signature