Bugfix for "Unable to find startxref" exception #764
Conversation
This file contains 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
Error location: src/Smalot/PdfParser/RawData/RawDataParser.php:952 Fix: getXrefData(): regex (passed to preg_match_all() call that sets $startxrefPreg) now supports e.g. "startxref 1746580". (Previously required newline before offset value.) PDF details: Creator: DocuPrint CM225/228 PDF version: 1.7
Updated regex in src/Smalot/PdfParser/RawData/RawDataParser.php:getXrefData()
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.
Type of pull request
About
Addresses inadequacies in handling startxref statement before EOF marker.
Currently, getXrefData() uses a regex that requires a newline before the offset value.
This fix allows:
For more detail see #756
TO DO