> > 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... Thanks, Dmitry -- 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.
