You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The following unit test are failing in Tesseract 4.1 build (branch features\321-Tesseract-4):
EngineTests.CanParseText_UsingMode(SingleBlockVertText,"A line of text")
Preliminary investigation indicates the problem is with tesseract itself, however yet to be confirmed (haven't yet reproduced directly using tesseract).
The text was updated successfully, but these errors were encountered:
Completely green on tesseract, just started a project to implement it in a .Net app. When I test with Japanese and --psm 5 I get a line of text, with Japanese and --psm 6 I get a vertical line of text.
Could it be that the English data is not trained on vertical text that is causing the issue?
No idea really, just noted that the associated unit test was failing. Next
thing would probably be to get an official build and test it which would
indicate if the problem's in tesseract or how I built the library.
On Mon., 21 Oct. 2019, 18:12 Robert Karlsson, ***@***.***> wrote:
Completely green on tesseract, just started a project to implement it in a
.Net app. When I test with Japanese and --psm 5 I get a line of text, with
Japanese and --psm 6 I get a vertical line of text.
Could it be that the English data is not trained on vertical text that is
causing the issue?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
<#490?email_source=notifications&email_token=AAB7HSAVJOOZRSBCXPSCMGTQPVI53A5CNFSM4JABFRFKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBZJO2Q#issuecomment-544380778>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAB7HSC6RRKZJRWOGUIVKALQPVI53ANCNFSM4JABFRFA>
.
The following unit test are failing in Tesseract 4.1 build (branch features\321-Tesseract-4):
Preliminary investigation indicates the problem is with tesseract itself, however yet to be confirmed (haven't yet reproduced directly using tesseract).
The text was updated successfully, but these errors were encountered: