Repository navigation
Add licensed QPDF inline-image corpus evidence - #2
Merged
Merged
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
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.
The earlier eight-fixture corpus had a maximum retained inline payload of 3,996 bytes. Add a separate, pinned QPDF regression corpus containing a 2,134,990-byte A85+Flate payload, alongside named-color-space and nested-Form cases. Keep the datasets separate and explain their sampling limits.
The three existing upstream PDFs produce three successful pages and eleven inline definitions, with no unknown sample estimates. The JSON records source commits, Git blob/SHA256 hashes, project-license links and reproduction instructions. No PDF bytes are included.
Validation: independently rerun published tool 0.2.0 on Windows CPython 3.12 and 3.13; full reports match. All input hashes, non-overlap with the earlier corpus, summary arithmetic and the two-file publication scope were independently reviewed. Runtime code and version are unchanged. Parsing success is not a conformance or prevalence claim.
Prepared and checked with OpenAI Codex assistance.