It's not the same bug. The document you attached uses Type 3 fonts,
which in theory are drawn using Postscript (not PDF) primitives, but
in practice are just bitmaps. Ghostview and Acrobad do a fine job with
these, but poppler-based readers don't handle them well at all.
The issue being discussed
For the record, the fix that works for me is to change the
#ifdef...#else...#endif block beginning at line 179 of file
SplashFTFont.cc as follows:
// if we have the FT2 bytecode interpreter, autohinting won't be used
// MS: actually, disregard bytecode setting, as it yields poor results anyway
Yes, I did exactly the same, and it works (except that it needs to be
redone every time poppler gets updated...)
Is there any chance of getting the fix incorporated? M
On 2/25/07, Pauli Virtanen <[EMAIL PROTECTED]> wrote:
> I was unable to fix the rendering in evince by tweaking those
> fontconfi
