Use later value for duplicate xref entries in PdfParser #7102
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.
Resolves #7084
The issue attempts to append an image to a PDF, but Pillow raises an error, "xref entry duplicated (and not identical)". This error was added in #2965 with the rest of the PDF appending functionality.
Reading https://blog.idrsolutions.com/what-are-pdf-xref-tables/ to learn more about xref tables, I found
And indeed, skipping past the duplicate value fixes the issue. We're already using the later value, because Pillow is reading the trailers in reverse order.
I created the test image using Pillow, modified the xref tables so that there is a duplicate entry with a different value, and then asserted that the later value, 1197, is used rather than the earlier value, 1196.