On 30 July 2010 23:10, Dmitry Silaev <[email protected]> wrote: >> On the plus side, it turns out that there are functions buried in the >> code to serialise/deserialise the classifier state, so it might be >> useful to run a whole corpus of short images through tess in one >> batch, save the state, and load that at startup. > > Could you please be more specific, what are your findings: which functions > and what they do? I think it might be of interest for many subscribers...
This commit has the conversion to doxygen of the documentation of some of those functions: http://code.google.com/p/tesseract-ocr/source/detail?r=447# -- <Leftmost> jimregan, that's because deep inside you, you are evil. <Leftmost> Also not-so-deep inside you. -- 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.
