Replacement for #238 (Fix illegal encoding for MacRomanEncoding) #313
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
because it wasn't triggering the faulty code and can be replaced by testParseFile which goes into more detail.
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.
Replacement for #238, because its code is outdated.
Fix provided by @daneren2005
Fixes #229
No separate test case for the fix required, because the added PDF file (
samples/bugs/Issue229_mac_roman_encoding.pdf) will be parsed byParserTest::testParseFileand would trigger an exception without the fix on PHP 8. See: https://travis-ci.org/github/smalot/pdfparser/jobs/701562931#L257Ready for merge.