Summary: | Add CairoOutputDev::drawSoftMaskedImage | ||
---|---|---|---|
Product: | poppler | Reporter: | Pablo Rodríguez <freedesktop> |
Component: | general | Assignee: | Jeff Muizelaar <jmuizelaar> |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | CC: | amayer, ed, jmuizelaar, josuealcalde, wrobell |
Version: | unspecified | ||
Hardware: | x86 (IA32) | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: | ||
Attachments: |
document with wrong displayed image on first page
an ugly patch to add smask support to the cairo backend smask support for the cairo backend |
Description
Pablo Rodríguez
2006-01-07 23:20:27 UTC
Created attachment 4279 [details]
document with wrong displayed image on first page
looks like this is caused by missing smask support Works in development branch Doesn't work with cairo backend yet though. Created attachment 4326 [details] [review] an ugly patch to add smask support to the cairo backend *** Bug 5304 has been marked as a duplicate of this bug. *** As my bug was duped, I humbly add the URL with PDFs that I was complaining about: http://www.escapistmagazine.com/ All (?) of the Escapist PDFs don't render correctly with poppler, so any PDF from there should be a test-case. *** Bug 3098 has been marked as a duplicate of this bug. *** change title The patch I posted here is broken for some pdfs. I haven't had time to track down the problem yet. Wouldn't we also need CairoOutputDev::drawMaskedImage to attain parity with splash backend; or is that another bug? Yes drawMaskedImage should be added as well, however, it is used less often so not as high priority. (I don't recall seeing many documents that used that feature.) *** Bug 3020 has been marked as a duplicate of this bug. *** Created attachment 4667 [details] [review] smask support for the cairo backend still ugly but should work this time. should be fixed in cvs |
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.