redirecting stdout to stderr when loading EasyOCR-Reader to be compliant with ocrmypdf #13
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
redirecting stdout to stderr to be compliant with ocrmypdf. otherwise we brake the usage of ocrmypdf with piped stdin / stdout...
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.
ocrmypdf allows to be called with
- -to read from stdin and write to stdout.when the easyocr model is loaded (also from cache into RAM) it produces output to stdout. this output will then be mixed into you .pdf data stream (at least at the begging).
this is quick fix using contexlib to redirect the output of easyocr loading to stderr.