Thanks for your bug report.

Can you tell us a bit more about what you mean by "can not read the text"? Do you mean that there is no text to read, or that it is somehow illegible (e.g. badly drawn, noisy or perhaps the wrong glyphs)?

I tried your test case with a range of readers using poppler. It looked pretty bad (noisy fonts, although still readable) using evince 0.8.2 and poppler 0.5.4 (using cairo) on Fedora 7, but it looked quite OK using evince 2.20.2 and poppler 0.6.2 (using cairo) on Fedora 8. It also looked OK using Qt4 test tools on top-of-tree from git.

Can you tell us which version of poppler you are using? (in evince, you can get this from Help->About).

There might be a problem this is showing in poppler though. With 0.6.2, I see a few "cairo context error: NULL pointer" warning/error messages on the command line.

Created attachment 13372 [details]
screenshot

hard to describe. I have poppler 0.6.2. O attached a screenshot.

I'm certainly not seeing that type of corruption.

Do you get this problem with any other file?

I'm not sure, but perhaps the problem is in some other library (perhaps freetype, fontconfig or cairo)? Or possibly you've hit a compiler bug associated with a different compiler or different build options.

I had a quick look at foresight linux's repo (which I assume that you're using, based on your email address), and one thing I can suggest is not using the --enable-zlib configure option. Other than that, I think you're probably on your own here.

Can you still reproduce this with a newer poppler?

I confirm it's not correctly rendered with current poppler, but it's cairo backend specific. There's seems to be a problem rendering Type3 fonts.

This cairo commit broke it:

a2254e56474fcdf5f25232812cdbef30a2b5ea60 is first bad commit
commit a2254e56474fcdf5f25232812cdbef30a2b5ea60
Author: Benjamin Otte <otte@gnome.org>
Date:   Sun Oct 18 22:12:13 2009 +0200

    [gstate] Apply target device offsets to patterns immediately
    
    Previously target device offsets were applied in cairo-surface.c which
    could cause bugs when paths were taken as fallbacks, as for example
    pointed out by ade55037ffa596b690c6a1051394589f76eb1f48 and quick-fixed
    by 79190d89853958ee8252440d35a662fabf122afd. The quick-fix is now
    unnecessary and was removed.

:040000 040000 88a0ecd70991b3e9ff70f936558b42ece770cc4b 8a4ba2e7d100e4938f33b6533a69332b4964694a M	src

I'm not sure whether this is cairo or poppler issue, though. ickle?

This is a cairo bug, fixes pending.

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/cairo/cairo/issues/60.