Thank you TP and Dmitri for the additional info, very helpful. One of the things I find most frustrating about some open source projects is the lack of documentation that would help people like me get a better understanding and ultimately is a barrier to wider adoption and interest. This is not really a criticism but an observation. With just a little fundamental info about how to get the best out of/get started with Tesseract (and by that I mean users not hard core developers) could go a long way to getting additional people contributing and using it. I appreciate that guys like you make the effort, thanks once again.
Paul On Mar 8, 8:21 pm, TP <[email protected]> wrote: > On Thu, Mar 8, 2012 at 12:06 PM, TP <[email protected]> wrote: > > you can use it's "ffind" command to display all (most? > > some?) configuration parameters defined in the tesseract-ocr source > > files > > Addendum: The following TCC/LE ffind command gives a more "complete" > listing of parameters than the one given in [1]: > > ffind /s/v/c/t"_VAR_H" *.h | list/s > > (about 600). I haven't closely looked at this to figure out what the > differences are. I know from looking at the preprocessor output for > string parameters that the _VAR_H macro creates the member but doesn't > initialize it (despite the presence of an initial value arg). It's the > corresponding _MEMBER macro that actually inits the param. Maybe > params whose initial state is zero don't need to be initialialized any > further (although that seems like sloppy programming to me)? > > [1]http://tesseract-ocr.googlecode.com/svn/trunk/vs2008/doc/tools.html#id2 -- 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
