chore: remove invalid –psm 0 option from tessdata_config
#237
Conversation
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
The `–psm 0` option was ignored by Tesseract because it used an en-dash instead of a hyphen, and only a single dash instead of the required double dash. Using the correct `--psm 0` is also not appropriate, as it triggers "Orientation and script detection (OSD) only", which does return any text and causes frog to fail. As a result, the behavior remains unchanged and continues to default to "Fully automatic page segmentation, but no OSD".
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The
–psm 0option was ignored by Tesseract because it used an en-dash instead of a hyphen, and only a single dash instead of the required double dash.Using the correct
--psm 0is also not appropriate, as it triggers "Orientation and script detection (OSD) only", which does not return any text and causes frog to fail.As a result, the behavior remains unchanged and continues to default to "Fully automatic page segmentation, but no OSD".