Character level recognition gives the same results as the word level recognition. #877
Comments
|
Page segmentation mode (PSM) has no impact on the format or level of granularity of the output. Running with PSM If you want more granular output with character-level bounding boxes, look at the |
|
Thankyou for giving an insight, will close after experimenting o7 |
|
@Balearica While working on my project I have created some good beginner friendly and advanced programs which could be added in the example docs, shall I add them and open a pull request? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Tesseract.js version (version number for npm/GitHub release, or specific commit for repo)
Latest release version 5.0.4
Describe the bug
A clear and concise description of what the bug is.
Running Tesseract.js code in 2 different PSM modes gives the same output.
Is tesseract configured to give word level outputs only?
Am I guessing it right that PSMs just refine the recognition scope, but do not affect the output because it will always will be in words?
Running in
SINGLE_CHARandPSM_SINGLE_WORDgives the same output from the same sample.I want to sort the result character by character and in order to do that, I want the bbox data of each character detected to be extracted, and used further. Is this possible?
Device Version:
Windows 11
Edge
The text was updated successfully, but these errors were encountered: