On Mar 5, 1:12 am, rthomas <remi.tho...@gmail.com> wrote:
> Hi,
>
> I think this project is dead.
> - Many people come here to get an Open Source OCR, do not contribute
> and go.
> - The few contributors can't commit the code because the project is
> locked.
> - Tesseract needs a complete rewriting.
> - There is no Tesseract Guru, because there is no documentation.

It's unfortunate that there's not a more vibrant community, but "dead"
seems like a pretty strong word.

It's not uncommon for the Google style of "open source" to be simply
periodic dumps of internal development (even large projects like
Android do this).  It's not really the collaborative style of
development that people associate with the term "open source" but it's
better than nothing.

If Remi and a team of developers wanted to fork and do the "complete
rewrite" which he says is required, they certainly could, but the risk
is that 6 months from now Google will produce a dump of Tesseract 4.0
which is completely unrelated.  The motivation and available effort
would have to be pretty high to maintain the fork in the face of that
kind of situation.

Having said all that, it would be great if Ray Smith could make more
frequent appearances to let folks know the status of things (not to
answer simple newb questions).

As for the original poster's question, if you ask "Can it do <foo>?"
and no one answers "Yes, and here's how," the answer to your question
is almost certainly "no."  You might have 20 potential responders who
think "I'm 95% certain it doesn't" (or 99% even) but they aren't going
to reply when they don't know for sure.

Tom

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

Reply via email to