Re: [ft] Size problem

[Werner LEMBERG]

> >Snapshots?
> 
> http://img142.imageshack.us/img142/9084/freetypewx4.png
>
> [...]
> - Rendered with FT_Load_Char(...) and bitmap glyph blitting
> - 96dpi
> - Size 20
> - line 3 with ARIAL.TTF
> - line 4 with ARIALBD.TTF

It's obviously the other way round (first bold, then normal).

You've omitted two important details, namely the load flags passed to
FT_Load_Char, and whether native TrueType bytecode handling is
compiled into the FreeType.  Doing a quick test with ftview I see that
FreeType's autohinter changes the spacing of many glyphs in Arial, so
I suspect you don't have TT_CONFIG_OPTION_BYTECODE_INTERPRETER defined
in ftoption.h, which would explain the differences.

Remember: The autohinter's job is to render fonts beautifully on
screen, algorithmically based on the outlines only.  After a global
and local analysis of the glyphs, it has to adjust various parameters
to get decent results, including spacing, height, overall thickness of
glyphs, etc.  It is *not* its duty to provide similar results to the
native TrueType hinter.


    Werner