Hi all,

Remi Thomas thought that:
*
**OCR engine don't need image library and image processing library*. Keep
the code simple, let the developers bundle it with the image lib he
likes/wants to use. The only image processing you can include is
thresholding from 24 bit image.

He pointed out that Tesseract have 3 big problem :
- memory leak.
- too complex code.
- process oriented, it's not designed to be use as a lib

*Tesseract needs a complete rewriting.**
*
The correct direction is to
1) reverse engineer the code and document it
2) complete rewriting from the documentation

*And he is ready to help for a complete rewriting.**
*
What do the others think?

Do you agree that Tesseract needs a complete rewriting?

Can you help in case Ray want to rewrite Tesseract?

Best regards,

-- 
Tien Dung
http://codemonkeycode.blogspot.com/

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"tesseract-ocr" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/tesseract-ocr?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to