Use VeraPDF to validate PDF/A compliance during testing #788
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
fooman
force-pushed
the
pdfa-validation
branch
from
41c0cdf to
d658e25
Compare
fix examples update all references to PDF/A-3b
fooman
force-pushed
the
pdfa-validation
branch
from
d658e25 to
9e5051e
Compare
williamdes
approved these changes
Feb 12, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request amends the shell based test run to validate the generated pdfs based on the included PDF/A version using VeraPDF (Applies to Example 65 and 66).
During testing I found out that the generated pdfs will fail validation for PDF/A with this error:
Changing the PDF/A version to version 3 fixes it.
The expected output during the test
