Account for inaccurate offsets in getXrefData() #692
Merged
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.
Type of pull request
About
Normally offset pointers to
xref
keywords in a PDF document are exact to the byte. However, in some cases the pointer may point to some whitespace before thexref
keyword. Adobe Acrobat takes these 'errors' in stride, displaying the document anyway, and so should PdfParser.Clean up the getXrefData() function in RawDataParser.php. It now only needs to do one
preg_match_all()
and pushes the caret past whitespace when looking forxref
keywords.Use existing Issue557.pdf to create a new file: Issue673.pdf where the last
/Prev 13486
command has been decremented to/Prev 13485
. Trying to parse this file would cause an Exception without this fix. Resolves #673.Checklist for code / configuration changes
In case you changed the code/configuration, please read each of the following checkboxes as they contain valuable information:
fixes #1234
to outline that you are providing a fix for the issue#1234
.