Generate a PDF/A compliant CIDSet instead of using hardcoded FFFFFFFFC0#1704
Merged
blikblum merged 1 commit intofoliojs:masterfrom Mar 18, 2026
Merged
Generate a PDF/A compliant CIDSet instead of using hardcoded FFFFFFFFC0#1704blikblum merged 1 commit intofoliojs:masterfrom
blikblum merged 1 commit intofoliojs:masterfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
When PDF/A-1 support was initially added, the CIDSet was hardcoded to
FFFFFFFFC0which causes issues with veraPDF when verifying (namely, this rule fails). With this change, we generate a proper CIDSet instead and allow PDF/A-1 to verify successfully.Bug fix
What kind of change does this PR introduce?
Instead of defaulting to a harcoded CIDSet to satisfy some PDF/A verifiers, build a proper CIDSet to be compliant.
Checklist: