Yes, I'm pretty sure it's a bounding box issue. I don't want to go the way of manually specifying bounding box, as I don't really have the time, and want the training to work for the general case anyway.
I think I'll just have to declare it as "good enough" for now (and it really is pretty good!) Thanks again Nick On Tue, Jul 17, 2012 at 07:28:14AM -0700, Steve wrote: > I've had some issues where some letters are persistently misrecognized, > even though there's only a single character being evaluated, and even when > I used my own training data. For example, sometimes B gets persistently > mistaken for X or K. My guess is that it has something to do with how > Tesseract is generating the bounding box, but I don't know how to control > this, or how to show the bounding box graphically. But if you know of a > way to manually specify the bounding box around your character, maybe that > might help? -- 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
