Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistent behavior for implicit vs. explicit DeviceGray colour space #978

Closed
a20god opened this issue Aug 21, 2018 · 1 comment · Fixed by veraPDF/veraPDF-validation#274
Assignees

Comments

@a20god
Copy link

a20god commented Aug 21, 2018

veraPDF 1.12.1 reports different results for these documents:
invalid-cs-1.pdf
invalid-cs-2.pdf
Both share the same problem: they use a CalRGB colour space for DefaultGray (and the Gamma entry is incorrect). The difference between the documents is that the second one uses a g operator in the content stream to select DeviceGray whereas the first one does not select a colour space in the content stream and therefore uses DeviceGray by default. veraPDF should report the same result for both documents.

@bdoubrov
Copy link
Contributor

Indeed I confirm the issue with the remapping of initial DeviceGray color space to CalRGB. We'll fix it.

However, validation of the Gamma entry is a part of full ISO 32000-1 validation and is still out of scope of veraPDF. So, after the fix the file would be validated successfully by veraPDF.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants