> This problem is probably actualy in tesseract, but I don't know how to run > tesseract to reproduce it. > > This may be http://code.google.com/p/tesseract-ocr/issues/detail?id=265#c0 > also reported as > https://bugs.launchpad.net/ubuntu/+source/tesseract/+bug/565688 > > It is apparently fixed in tesseract 3.0
If that is the case, we will have to wait, as tesseract 3.0 has not yet been released. -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
