standardized text extraction tests #49
Merged
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
added 17 commits
August 22, 2014 13:35
…thods (like pdfminer)
…t.TestCase as necessary
deanmalmgren
pushed a commit
that referenced
this pull request
Aug 25, 2014
standardized text extraction tests
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.
@PrajitR mentioned something like this a while back and I think it could be really useful (#30 (comment)), particularly in light of issues like #48 where we were inadvertently "extracting" text that wasn't actually in the original file. It might be nice to have a set of tests that should have the exact same output, regardless of the filetype, so we can be confident that each extraction method works consistently.