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

Default colour spaces #797

Closed
a20god opened this issue Jun 17, 2017 · 1 comment · Fixed by veraPDF/veraPDF-validation#281
Closed

Default colour spaces #797

a20god opened this issue Jun 17, 2017 · 1 comment · Fixed by veraPDF/veraPDF-validation#281
Assignees
Labels
bug A product defect that needs fixing P1 High priority issues to be scheduled in the upcoming release
Milestone

Comments

@a20god
Copy link

a20god commented Jun 17, 2017

Dev Effort

1D

Description

veraPDF 1.7.19 claims that this document is compliant:
DefaultCS-3.pdf
I can imagine no interpretation of the standards that supports that result. Even ignoring invalid coloour spaces (which is what I suspect veraPDF to do) would not work as the default colour space (DeviceGray) isn't allowed.

This one is questionable (callas pdfToolbox 9.2 claims that it does not comply):
DefaultCS-2.pdf

This one is questionable (callas pdfToolbox 9.2 claims that it does not comply, veraPDF 1.7.19 thinks it does comply, but probably for the wrong reasons as shown by the documents above):
DefaultCS-1.pdf

@BezrukovM
Copy link
Contributor

veraPDF 1.7.57 claims that all these three files are not compliant.
Additional checks required to be sure that it failed on right rules.

@ghost ghost added bug A product defect that needs fixing P1 High priority issues to be scheduled in the upcoming release labels Jan 3, 2019
@ghost ghost added this to the v1.14-m4 milestone Jan 3, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug A product defect that needs fixing P1 High priority issues to be scheduled in the upcoming release
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants