Future / Documentation / Roadmap / Stuff of that sort about clstm HOT 4 CLOSED

So I got ocropy to work on Fedora and tried it with the standard model on a simple plain PDF document I had scanned. The results were just as terrible as with the other open source OCRs, if not worse, although it really is a high resolution scan with normal looking fonts. I felt disappointed to be honest.

Error rates even on degraded documents are generally below 1% character error. If you're getting worse than that on clean documents, there's probably something wrong.

To diagnose the source of the error, please provide extracted text lines as samples; you can attach them to this issue.

from clstm.

It would be nice if you kept a detailed TODO list for clstm and ocropy. It would be nice to have a Roadmap for both those projects as a whole where important milestones are defined.

Unfortunately, the development of ocropy and clstm is largely driven by a lot of internal project timelines and other considerations. I'll try to add some comments to the READMEs, though.

from clstm.

does clstm work on windows?

from clstm.

That could mean several things. Porting to MSVC++ is probably a modest amount of work. It should compile with Cygwin. I'd recommend just running Virtualbox or Docker, though.,

from clstm.