Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Problem with .uzn file for tesseract #3837

Closed
simas2275 opened this issue Jun 7, 2022 · 5 comments
Closed

Problem with .uzn file for tesseract #3837

simas2275 opened this issue Jun 7, 2022 · 5 comments
Labels
bug regression

Comments

@simas2275
Copy link

Environment

  • Tesseract Version: 5.1.0
  • Platform: Windows 10 64bit

Problem with .uzn file

After working with tesseract 4.1.0 everything worked perfectly. I used command tesseract inputPhotoName.png outputName -l eng --oem 1 --psm 4 hocr and tesseract automatically picked up inputPhotoName.uzn zone file and returns word which I have specified with coordinates. After I upgraded tesseract version from 4.1.0 to 5.1.0, tesseract 5.1.0 no longer takes inputPhotoName.uzn zone file and returns all founded words in image.
After a lot of searching I cant find a solution how can I pass inputPhotoName.uzn file to tesseract 5.1.0. Maybe tesseract 5.1.0 no longer support .uzn files?

inputPhotoName.uzn file content: 215 3334 95 19
Tesseract 4.1.0/5.1.0 commands: tesseract inputPhotoName.png outputName -l eng --oem 1 --psm 4 hocr
@zdenop
Copy link
Contributor

zdenop commented Jun 7, 2022

Can you please provide example files for testing (image+uzn)?

zdenop added a commit that referenced this issue Jun 7, 2022
@zdenop
do not use '\0' in std::string => fixes issue #3837 (loading uzn file)
67841aa
@zdenop
Copy link
Contributor

zdenop commented Jun 7, 2022

Please try the latest code.

@simas2275
Copy link
Author

Please try the latest code.

Now everything is working perfectly. Thanks!

@amitdo amitdo closed this as completed Jun 8, 2022
@amitdo amitdo added the bug label Jun 8, 2022
@stweil
Copy link
Member

stweil commented Jun 8, 2022

The bug which is now fixed was introduced in commit 4b84a56.

@amitdo
Copy link
Collaborator

amitdo commented Jun 8, 2022

A new unittest for testing this functionality would be useful.

@stweil stweil mentioned this issue Jun 10, 2022
Open
@zdenop zdenop mentioned this issue Jul 9, 2022
Closed
@AlexPieczynski AlexPieczynski mentioned this issue Jul 12, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug regression
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@zdenop @stweil @amitdo @simas2275