tesseract: [FIX] pdf pre-processing #468
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
detect the mimetype of the input, also when using invoice2data as a library
|
Thanks for handling this. |
|
It turns out, this really did not make a difference. The guess_type function also looks at the file extension. It turned out that the problem was in the program calling invoice2data. |
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.
Before this PR the mimetype of the input file was detected by it's extension.
It works fine for cli usage.
It fails when invoice2data is used as a library and a tempfile/stream is used as an input. (as there is no extension available)
Making it impossible to parse pdf files when using invoice2data as a library.
As tesseract cannot handle pdf files as an input.
After this pr, the mimetype is also detected when using invoice2data as a library.
@m3nu , @rmilecki I'm consideirng this as a hotfix, so fasttracking this one.