sikuli-driver team mailing list archive

[RaiMan <question248676@xxxxxxxxxxxxxxxxxxxxx>]

Question #248676 on Sikuli changed:
https://answers.launchpad.net/sikuli/+question/248676

    Status: Open => Answered

RaiMan proposed the following answer:
I strongly recommend, to directly switch to Tess4J for the usage of any Tesseract features in your Groovy case and switch off the Tesseract usage in SikuliX.
You already have your own mid-level functions, so why invest in bringing light into the jungle, when there is a possibility to live in the top of the trees ;-)

The Vision implementation as Java/JNI interface to the native modules using the OpenCV and Tesseract C++ API simply is a mess.
With Tesseract it is even worth since the original developer simply left in mid of revising the text find and OCR feature for the usage Tesseract 3. Since then nothing was done in this area.

During the next months the Vision module will vanish anyway, since I am nearly through with porting the image search feature to the OpenCV Java API level (no need for any C++ code any more for that). (new classes Image, ImageFinder, ImageFind).
The same I will do for the Tesseract usage with support of Tess4J, that I already refactored to make it fit into the SikuliX Maven structure. 

sources and other valuable links: https://github.com/RaiMan/SikuliX-2014

-- 
You received this question notification because you are a member of
Sikuli Drivers, which is an answer contact for Sikuli.