I think the suggestions are useful. Regarding the most frequent operations:
> - scanning directly from within the OCR application -- Yes and it would be > nice to use Xsane as GIMP does. > - switching between scan and OCR view and/or overlaying them -- > - deleting bad scans -- Ok, simple. > - reordering pages -- Simply by drag&drop in the page list (at left). > - removing noise regions (page borders, stains, etc.) -- If Ocropus > misrecognised some noise as an image region, the user can select and delete > it. > - fixing page thresholding -- Could be manually set in > directory/image/region options. > - marking regions as images or text (if they have been misclassified) -- > OK, the dropdown menu should have this option. (Text, Photograph, Drawing, > Math...) > - adding or removing column separators -- The columns could be detected as > two separate text regions, couldn't they? > - cutting or joining text lines > - fixing OCR errors -- Maintaining the Unix philosophy not to substitute > other programs on their own turf, I would pass this work to some text editor. > Depending on the output format, this can be OpenOffice, Kile, Vim or whatever > else the user choses. > Another very important operation would be some support for OCR training on > scanned data and/or corrected data. Of course, the training process for Tesseract is quite complicated. Sometimes the user would need a new language, sometimes add a subset of rarely used terminology. More often would there be need to train Tesseract to perfectly recognize some particular font of a book... (There would be a lot of possibilities more, but it would need some runtime communication with Tesseract. For instance, it could ask you in case of uncertain characters and learn them while processing.) OK, Python is fine for a graphical frontend. As far as I know there is no problem running Python+GTK apps on MS Windows, so that we can proceed with development of already usable GuiTesseract [1]. Ocropus-GUI, Gocropus? Do you suppose some nice name for this application? Also we could merge TesseractTrainer.py [2] [1]: http://ocropus.googlegroups.com/web/guitesseract.py?gsc=Z8kTHBYAAACg2FwGPC9XOsx4lRLfkDCCq9K8Kz9yQIr4tC0O5ImEZA [2]: http://tesseract-ocr.googlegroups.com/web/tesseractTrainer.py --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "ocropus" 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/ocropus?hl=en -~----------~----~----~----~------~----~------~--~---
