I just watched the presentation, which I missed before, so I'll ask a slightly better question as a result.
>From the video, the 3 reasons given for creating Franken+ were: - To find and pick the best exemplars of a character - To easily find places that glyphs were misidentified - To ignore small scanning artifacts The last of these could be done with any box editor by removing the box, but I am not aware of a particularly helpful interface for the first two. Am I correct in thinking that an interface that compared the different examples of each character, grouped by character, is the main reason for Franken+ being built? Presuming that is correct, why didn't you add an extra tab to jTessBoxEditor with such a view? I would have thought that would be easier, but more importantly it wouldn't rely on a proprietary workflow, and more generally (unless I'm missing something) should be more straightforward and faster to work with, as it doesn't require passing the output from one tool into another. I look forward to hearing more, Nick -- -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to tesseract-ocr@googlegroups.com To unsubscribe from this group, send email to tesseract-ocr+unsubscr...@googlegroups.com 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 tesseract-ocr+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
