Details
-
Type:
Bug
-
Status: Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 6.2.5, 6.3
-
Fix Version/s: 6.3.1
-
Component/s: Core/Parsing
-
Labels:None
-
Environment:any
-
Support Case References:Support Case 14290:- https://icesoft.my.salesforce.com/5000g00001rJ77M?srPos=0&srKp=500
Description
The file in question has in image that is encoded using a Separation colour space. Separation is an interesting colour space as it has no support for alpha perhaps a throwback to its printing press roots.
The colour space takes a named colour as well as a tint value which is used to compose an rgb colour. We've had some trouble doing this correctly in the pastPDF-696, PDF-694 and PDF-337. This test file has helped shed some light on the problem.
The colour space takes a named colour as well as a tint value which is used to compose an rgb colour. We've had some trouble doing this correctly in the past
Activity
- All
- Comments
- History
- Activity
- Remote Attachments
- Subversion
Marking as fixe. d
Show
Patrick Corless
added a comment - Marking as fixe. d
The preferred way to handle the a separation colour space according the spec is to take the named colour if present and apply the tint value to each of the named colour components. Our previous attempts would apply tint as the alpha constant. This works OK in a lot of examples but is against what the color space's basic principles.
The sample pdf had an image with pink bleed though from the background color. Given all the data, it apparently that we needed to apply our own blend against a white background (ie paper) to get the image to render correctly. Our other test cases happily rendered correctly.