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.

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

Fix use of wrong UNICHARSET #1954

Merged
merged 1 commit into from
Oct 6, 2018
Merged

Conversation

stweil
Copy link
Contributor

@stweil stweil commented Oct 6, 2018

Signed-off-by: Stefan Weil sw@weilnetz.de

Signed-off-by: Stefan Weil <sw@weilnetz.de>
@ghost ghost assigned stweil Oct 6, 2018
@ghost ghost added the review label Oct 6, 2018
@stweil
Copy link
Contributor Author

stweil commented Oct 6, 2018

This should fix issue #1205. I found it by adding an assertion more up in the call stack. There might be more similar code using the wrong UNICHARSET, so I'll try to add more assertions to find it.

@zdenop zdenop merged commit 9efedc1 into tesseract-ocr:master Oct 6, 2018
@ghost ghost removed the review label Oct 6, 2018
@stweil stweil deleted the unicharset branch October 6, 2018 13:21
NexediGitlab pushed a commit to SlapOS/slapos that referenced this pull request Jun 4, 2021
With tesseract v4.0.0-beta.3 we often observe crashes with:

```
contains_unichar_id(unichar_id):Error:Assert failed:in file ../../src/ccutil/unicharset.h, line 511
```

This seems to have been fixed by tesseract-ocr/tesseract#1954

Still, even after updating to 4.1.1, text recognition from PDF in ERP5 is too expensive. We also update Ghostscript to 9.54.0, because this version has built-in OCR, which does not need to convert the PDF to PNG then TIFF as we currently do in ERP5.

See merge request nexedi/slapos!985
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants