Fix pdfbox 5250 - #529
Closed
valerybokov wants to merge 3 commits into
Closed
Conversation
Contributor
|
Thanks, this fixes PDFBOX-4077 as well, and a file from the poppler project. I'll run the actual fix now and the test later this week when I have more time. |
asf-gitbox-commits
pushed a commit
that referenced
this pull request
Sep 11, 2026
git-svn-id: https://svn.apache.org/repos/asf/pdfbox/branches/2.0@1938116 13f79535-47bb-0310-9956-ffa450edef68
asf-gitbox-commits
pushed a commit
that referenced
this pull request
Sep 11, 2026
git-svn-id: https://svn.apache.org/repos/asf/pdfbox/branches/3.0@1938117 13f79535-47bb-0310-9956-ffa450edef68
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.
In PDFStreamEngine.processTransparencyGroup(), initialMatrix was captured from the CTM before the transparency group's own /Matrix entry got concatenated into it — the opposite order used by processStream() (the code path for ordinary, non-group forms). Per spec, a pattern's matrix maps pattern space to "the default coordinate system of the pattern's parent content stream," which must include that stream's own /Matrix. So any shading/tiling pattern used inside a transparency group that itself has a non-trivial /Matrix (like the reported case's 0.017 scale) gets positioned using the wrong reference matrix — off by exactly that scale factor.