Re: [tesseract-ocr] Help needed in understanding source. New to tesseract.

You can look at http://zdenop.github.io/tesseract-doc/ http://fossies.org/dox/tesseract-ocr-3.02.02/index.html https://drive.google.com/folderview?id=0B7l10Bj_LprhQnpSRkpGMGV2eE0usp=sharing https://code.google.com/p/tesseract-ocr/wiki/Documentation ShreeDevi

Re: [tesseract-ocr] Help needed in understanding source. New to tesseract.

Thanks a ton. On 1 February 2015 at 17:59, ShreeDevi Kumar shreesh...@gmail.com wrote: You can look at http://zdenop.github.io/tesseract-doc/ http://fossies.org/dox/tesseract-ocr-3.02.02/index.html https://drive.google.com/folderview?id=0B7l10Bj_LprhQnpSRkpGMGV2eE0usp=sharing

Re: [tesseract-ocr] Help needed in understanding source. New to tesseract.

Thanks for the reply. Tracing manually is too much of a pain in this case. I am looking for tools that help me in this regard. On Saturday, 31 January 2015 21:51:14 UTC+5:30, Allistair C wrote: If you start by learning C++ then you will realise the entry point to a C++ program (main), you

Re: [tesseract-ocr] Help needed in understanding source. New to tesseract.

If you start by learning C++ then you will realise the entry point to a C++ program (main), you can then trace the various calls either manually, methodically stepping through files and functions by searching. You could potentially look at tools that allow call stack debugging/tracing. I am not