Charles Weld

Unfortunately no, the problem is that this information isn't exposed through the capi in Tesseract 3.02. I'll check the latest tesseract sources and see if its since been added later...

Just checked 3.04 (master branch) and can confirm this functionality isn't currently exposed. I'll get in contact with the tesseract team and see if I can get it added. However...

If you need this now a few possible solutions come to mind: - create your own micro ocr engine in C++ and expose it through a capi or messaging api....

Put in an official request to have this added to tesseract's CAPI (https://groups.google.com/forum/#!topic/tesseract-dev/WvJwZVJJO3M).

This functionality has now been added to tesseract 3.04 (see issue 1388).

Just realized I haven't exposed this functionality, moving to next release.

No there's no limit like this that I'm aware of. On Mon, 1 Nov 2021, 20:23 esraince1, ***@***.***> wrote: > I try to initialize tesseract ocr in a custom exe....

Can you try the latest release (4.1.1)?

Can't really provide much assistance with Linux, do a search of the issues as others had to go through some loops to get it working properly. From memory it was...

Looks like you're comparing different versions of tesseract (we use 4.1 not 4.0). The version of the library we use has also disabled avx instructions etc for comparability with older...