[
https://issues.apache.org/jira/browse/PDFBOX-1480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13539611#comment-13539611
]
Greg Werner commented on PDFBOX-1480:
-------------------------------------
I see what you see with PDFDebugger. So then the behavior is if there are
multiple BT/ET sections on a page and they are not all in agreement then the
graphics state associated with that page will have a (default) color state of
DeviceGRAY? To further inquire, to distinguish color states one cannot handle
it at the page level but one must go through the content stream to process each
BT/ET differently? From what I have seen, and correct me please if I am wrong,
when I process the stream for say the first page of one of these two documents
I only get back a single graphic state and this graphic state has stroking and
nonstroking color spaces of DeviceGray.
> PDFBox treats some DeviceRGB pdfs as DeviceGRAY
> -----------------------------------------------
>
> Key: PDFBOX-1480
> URL: https://issues.apache.org/jira/browse/PDFBOX-1480
> Project: PDFBox
> Issue Type: Bug
> Affects Versions: 1.7.1
> Reporter: Greg Werner
> Attachments: color.pdf, Test4.pdf
>
>
> Some PDF files are correctly processed by PDFBox as DeviceRGB and the font
> color can be retrieved. Other DeviceRGB files that can be viewed by Acrobat
> Reader as fonts with various colors are treated as DeviceGray by PDFBox. An
> example of creating such a file which is listed as DeviceGray is with Word
> 2010 and then saving as using the MinimumSize option. An example of creating
> a file which is recognized by PDFBox is to save Standard. I believe either
> case should be recognized as DeviceRGB
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
