On Sun, Jun 03, 2012 at 10:27:23PM +0100, zdenko podobny wrote: > it looks like it is ASCII only oriented (at least in report non-ASCII are > malformed...), ftk has only binary distribution, so no possible fix can > expected... > > BTW: tools are at new place: > http://code.google.com/p/isri-ocr-evaluation-tools > ; report can be found at stephenvrice.com/images/AT-1995.pdf
I finally got around to working with these tools a bit. It seems that they do process unicode correctly (though I haven't tested combined characters, and suspect that may not work). You're correct the reports don't seem to output unicode properly, but that's probably easily fixed. The source code for the tools is available now, in the svn repository of the Google project. The build system is annoyingly stupid, but wouldn't be much trouble to bring up to scratch. I may take a look into sorting out the unicode bug report bugs. Is anybody else using the tools? Are there any other bugs people know about? Nick -- -- 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 --- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
