This repository was archived by the owner on Apr 15, 2024. It is now read-only.
Make parser more resilient to bugged files - #159
Open
peterbrittain wants to merge 1 commit into
Open
peterbrittain wants to merge 1 commit into
peterbrittain wants to merge 1 commit into
Conversation
|
I confirm that I understand the parser and this fix. It works correctly for PDF's where some "endobj" keywords are accidentally missing. Parsing of a normal PDF is not affected by this patch. (correct) |
hynekcer
approved these changes
Nov 1, 2016
eladkehat
added a commit
to eladkehat/yapdfminer
that referenced
this pull request
May 1, 2019
|
@hynekcer Are there plans to merge and release the fix in this PR? |
|
I am a user confirming this is still affecting files - can it be merged if all checks have passed? |
This branch has not been deployed
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
4 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.
Proposed fix for #144