[poppler] Wrong hinting

[Cedric Sodhi]

Great! This is progressing quicker than I hoped. Thank you for your
research. Let me sum this up:

The font is embedded, so poppler does NOT use fontconfig to determine
whether to hint and/or antialias the font but instead uses the
information embedded to determine that.

The font is passed to FT, with, in this case, AA and Hinting enabled.

Freetype fails at rendering the font properly.

This looks pretty straightforward, great!

Any idea why it works for some people and doesn't for others? Can this
be solely a matter of FT configuration/compilation or are there perhaps
other side effects which I did not account for, like a specific setting
that makes poppler DISABLE Hinting on the embedded font (say)?

Cedric

On Mon, Feb 14, 2011 at 06:29:36PM +0900, mpsuzuki at hiroshima-u.ac.jp wrote:
> Hi,
> 
> Oops, so many posts during I was checking the embedded
> font by FreeType2... Now I think this issue is not by
> poppler but by FreeType2.
> 
> The font extracted from sample PDF is:
> 
> 	http://ompldr.org/vN2YyaQ/cedric-font.ttf
> 
> If I show the font by ftview (a small sample program
> of FreeType2), the rasterization result for the case
> hint=on && antialias=on is worse than others.
> The comparison is:
> 
> 	http://ompldr.org/vN2YybA/cedric-font.png
> 
> This is by the latest FreeType2. I will discuss other
> FreeType2 maintainer what I can do for this issue.
> 
> Regards,
> mpsuzuki