Fix Illegal string offset warnings#23
Open
tommynovember7 wants to merge 1 commit intopauln:masterfrom
Open
Conversation
|
Hi ! It's not enough. Function getDictValue() is also bugged and do the same bug at same line. For example, consider this PDF data sample : The function will not work properly because string ">>" is present inside the last crochets (crochets of ColorSpace) Suggested modification : |
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
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.
If a pdf has such an object like the followings,
tcpdf_parserfails to continue parsing the data.getRawObject()is expected to return an array which contains an object and its offset, but it currently returns an object without its offset if the pdf has%comments. It causes Illegal string offset warnings.PDF Object Sample
Warning Example