I think the best approach would be to stay as far as possible from
modifying the 3rd party code. Take a closer look to ResultIterator and
PageIterator classes. Often they suffice for getting all information
you need about Tess's recognition results.

Warm regards,
Dmitry Silaev





On Mon, Mar 14, 2011 at 1:42 PM, Jose <[email protected]> wrote:
> Hi Dmitry,
> thanks for the help!
> and the end what I did is modify the return result function and include the
> top location of the the bounding box. then I have the following result:
> <value>xxxxx</value><top>yyyyy</top>
> <value>xxxxx1</value><top>yyyyy1</top>
> <value>xxxxx2</value><top>yyyyy2</top>
> <value>xxxxx3</value><top>yyyyy3</top>
> <value>xxxxx4</value><top>yyyyy4</top>
> <value>xxxxx5</value><top>yyyyy5</top>
> <value>xxxxx6</value><top>yyyyy6</top>
> <value>xxxxx7</value><top>yyyyy7</top>
> then I parse the results and I can now that xxxxx1 and xxxxx2 where in the
> same line due looking at the top value. the approach works fine to me but I
> had to modify the sourcecode of tesseract
> regards,
> jose

-- 
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.

Reply via email to