Found some links of interest: "ABBYY Cloud OCR SDK service is implemented using REST software architecture principles and can be accessed through API by HTTP or HTTPS requests."
https://github.com/abbyysdk/ocrsdk.com/tree/master/Python http://ocr4linux.com/en:start http://ocrsdk.com/producttour/programming-languages/ My idea with this action item is create something like apps/converter/backends/, with a driver file for each OCR implementation that can be selected via a configuration setting, ie: OCR_BACKEND = 'ocr.backends.tesseract' or OCR_BACKEND = 'ocr.backends.abbyy_rest' I've use Requests (http://docs.python-requests.org/en/latest/) for talking with API with good results. --Roberto On Thursday, January 17, 2013 7:56:11 PM UTC-4, Lachlan Musicman wrote: > > Does ABBYY have an API? > > Might need to write a python wrapper for it..? > > Cheers > L. > > > On Fri, Jan 18, 2013 at 10:54 AM, Roberto Rosario < > [email protected] <javascript:>> wrote: > >> Hi Simon, >> >> At the moment the code is dependent on Tesseract, it was the only free >> OCR engine I had access to at the time, but this is an item on the TO DO >> list ( >> https://docs.google.com/document/d/19F5fUjAvsAHXLcPWOGnIpYtWAHQ_CwWLNi6jv8oeQCc/edit) >> >> for this development cycle. >> >> >> * >> >> - Abstract usage of Tesseract OCR >> - To allow switching of the OCR engine in the future >> >> * >> >> >> --Roberto >> >> >> On Thursday, January 17, 2013 7:17:55 PM UTC-4, simon thompson wrote: >>> >>> the OCR element does not seem to work that well for my documents, does >>> mayan support using 3rd party OCR software such as ABBYY ? >>> >>> Thanks >>> Simon >>> >>> >> -- >> >> >> >> > > > > -- > ...we look at the present day through a rear-view mirror. This is > something Marshall McLuhan said back in the Sixties, when the world was in > the grip of authentic-seeming future narratives. He said, “We look at the > present through a rear-view mirror. We march backwards into the future.” > > http://www.warrenellis.com/?p=14314 > --
