Bug 44918 - transparent objects too dark in exported PDF
Summary: transparent objects too dark in exported PDF
Status: RESOLVED DUPLICATE of bug 40143
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Printing and PDF export (show other bugs)
Version:
(earliest affected)
3.4.4 release
Hardware: x86-64 (AMD64) Linux (All)
: medium major
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-01-18 17:48 UTC by markusN
Modified: 2012-01-19 12:30 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Attachments
Single slide with transparent polygons (12.68 KB, application/vnd.oasis.opendocument.presentation)
2012-01-18 17:48 UTC, markusN 		Details
Single page with transparent polygons (10.50 KB, application/vnd.oasis.opendocument.text)
2012-01-18 17:48 UTC, markusN 		Details
PDF showing transparent objects too dark (11.58 KB, text/pdf)
2012-01-18 17:49 UTC, markusN 		Details
Screeshot of Impress showing transparent objects ok while PDF showing them too dark (118.07 KB, image/png)
2012-01-18 17:50 UTC, markusN 		Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description markusN 2012-01-18 17:48:03 UTC 
Created attachment 55757 [details]
Single slide with transparent polygons

When having transparent polygons (e.g. box, see attachment) in a
Impress or Write file, they are way too dark in the exported PDF.

This is a real showstopper, forcing me to reinstall Openoffice just 
for this bug...

Screenshot attached as well.
Comment 1 markusN 2012-01-18 17:48:45 UTC 
Created attachment 55758 [details]
Single page with transparent polygons
Comment 2 markusN 2012-01-18 17:49:22 UTC 
Created attachment 55759 [details]
PDF showing transparent objects too dark
Comment 3 markusN 2012-01-18 17:50:08 UTC 
Created attachment 55760 [details]
Screeshot of Impress showing transparent objects ok while PDF showing them too dark
Comment 4 markusN 2012-01-19 12:30:54 UTC 

*** This bug has been marked as a duplicate of bug 40143 ***