I have much better results with gImageReader and Tesseract.js (haven't tried others) out of the box than tesseract itself, and I wonder why.
I have attached a sample file. With gImageReader out-of-the-box, I get "15 Jan 1805 ". With Tesseract.js out-of-the-box, I get "15 Jan 1805↵↵". With the tesseract simple command line "tesseract img.png result", I get: "Jan 1805 ". Tried with other parameters and I didn't success getting results like gImageReader and Tesseract.js. So what do gImageReader and Tesseract.js use that vanilla tesseract doesn't use? I'd rather use the command line for automatic batch processing. -- 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]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/tesseract-ocr. To view this discussion on the web visit https://groups.google.com/d/msgid/tesseract-ocr/0a6a1d14-9f88-40cf-b730-69aeec1b2c9d%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
