-
Notifications
You must be signed in to change notification settings - Fork 9.9k
Characters swapped in results from 3.05.01 #1253
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
Comments
If I go back to 8ff183b (the last working commit), then cherry-pick 90db5a1, it starts to fail again. So, heading back to the earliest broken commit (or even the |
That sounds as if it has to be reverted for the 3.05 branch, too. @rfschtkt, what do you think? |
Let's talk next year :-) |
Ray also added this comment to Dict::Load()
|
Soo, is there any chance the fix will be backported? |
is it needed? There is no plan to release new 3.05. We are focused on 4.0 release. |
This issue should be fixed or closed. |
Can you please check 3.05 branch? |
Yep, looks like it's working there now. |
With 3.05.01, the basic English test from pyocr started failing. It supports both OCR via the library or calling out to tesseract. The basic test uses this file, does some conversion, and passes it along to tesseract. I have attached the bitmap file that goes directly into tesseract, though it also works if you pass the png unchanged. The expected text is here. The effective command is:
tesseract input.bmp output -l eng -psm 3
.Environment
Current Behavior:
With 3.05.01, the text comes out as expected except the word "ocr" comes our as "cor".
Expected Behavior:
With 3.05.00, the text matches entirely and tesseract produces "ocr".
Suggested Fix:
I have bisected this change to be somewhere between 8ff183b and acf318a. I could not bisect any further because the commits did not compile (bisect is a great reason to ensure that commits compile!). As all the intervening commits appear to be code cleanup, I believe this change was an unintended regression.
The text was updated successfully, but these errors were encountered: