As discussed in bug #12143 we're trying to do a better job of ensuring that poppler bugs detected by the cairo test suite get reported to poppler. At the current point, there are already 4 PDF tests that are disabled in the cairo test suite. They are: gradient-alpha, linear-gradient, text-pattern, trap-clip I believe that all of these tests were disabled due to a single bug in poppler having to do with transparency in gradients. But I don't have much more detail at the moment. I can attach some images here if desired, or someone can generate them by re-enabling the tests in cairo's test suite, (edit the pdf_ignored_tests list in cairo/boilerplate/cairo-boilerplate-pdf.c and then run "make test"). Sorry for the vague report---I just wanted to ensure this issue didn't go on forgotten. -Carl
I think file http://people.mandriva.com/~fcrozat/IC-MCC09-NEW2.pdf , generated on OS X, has the same issue Carl is reporting.
there's also an ubuntu report here: https://bugs.edge.launchpad.net/ubuntu/+source/poppler/+bug/330972 which is presenting a similar issue with these pdf: http://www.whiteestate.org/vez/oct08/VeZ_Sports-web.pdf
Attached to bug #10942 there's a patch that implements linear gradients in the cairo backend.
$ ./cairo-test-suite gradient-alpha linear-gradient text-pattern trap-clip TESTING cairo-test-suite Compiled against cairo 1.9.3, running on 1.9.3. Compiled against pixman 0.15.19, running on 0.15.19. TESTING gradient-alpha gradient-alpha.pdf.argb32 [0]: PASS gradient-alpha.pdf.rgb24 [0]: PASS TESTING linear-gradient linear-gradient.pdf.argb32 [0]: PASS linear-gradient.pdf.rgb24 [0]: PASS TESTING text-pattern text-pattern.pdf.argb32 [0]: PASS text-pattern.pdf.rgb24 [0]: PASS TESTING trap-clip trap-clip.pdf.argb32 [0]: PASS trap-clip.pdf.rgb24 [0]: PASS Frederic: I'm not sure whether it's the same issue or not, but your document look good now too. Pedro: that document seems to have another issues, could you file a new bug report for it, please?
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.