[
https://issues.apache.org/jira/browse/PDFBOX-1128?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13125047#comment-13125047
]
Daniel Wilson commented on PDFBOX-1128:
---------------------------------------
I had hoped this would resolve some test failures I've seen recently, but it
didn't resolve all of them.
ARCHIVERGB is showing 2 problems:
1. The stencil mask is missing completely
2. Some of the letters are not being filled. I've seen this in other cases
that I have not yet received permission to release ... a group of letters will
have only the first filled with the fill color.
Back in August, these items were working better ... so one of us made a mistake
somewhere.
If you prefer me to post a new issue, I certainly can.
> Wrong color space used for DeviceN operator without color space specified
> -------------------------------------------------------------------------
>
> Key: PDFBOX-1128
> URL: https://issues.apache.org/jira/browse/PDFBOX-1128
> Project: PDFBox
> Issue Type: Bug
> Components: PDFReader, PDModel
> Affects Versions: 1.6.0
> Reporter: Simon Maskell
> Assignee: Andreas Lehmkühler
> Priority: Minor
> Fix For: 1.7.0
>
> Attachments: DeviceN.patch, test4.pdf, test4.pdf-1.png
>
>
> I have a PDF that uses a DeviceN color space, but when using the PDFToImage
> utility I noticed that some of the text comes out as cyan.
> I tracked the issue down to when the scn or SCN operator is used without
> setting the color space explicitly (ie using the current color space). I
> have attached a patch which resolves the issue by reinstating the original
> (DeviceN) color space after using the alternate color space, otherwise the
> alternate color space (in this case CMYK) was seen as the current color space
> and the attribute of 1 for the scn operator, which was meant for the DeviceN
> color space, is used in the CMYK color space resulting in the cyan.
> I have also attached an example PDF and the result for the PDFToImage
> conversion.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
