Hi Matt,
> I'm also not sure how these two files are different, or if maybe DangAmbigs is > from an earlier version of Tesseract or something. I'm using 3.02. Yes, that guess was correct. unicharambigs used to be called DangAmbigs before Tesseract 3. That is mentioned at: http://code.google.com/p/tesseract-ocr/wiki/TrainingTesseract3 > answers another question I have about unicharambigs: is any > ambiguity found taken into account before or after dictionary lookup. Is the > unicharambigs processed before or after the dictionary is consulted? I'm not sure, but I think the unicharambigs step happens before the dictionary step. You'd have to check the code to be sure. > Also, I'm finding unicharambigs only seems to really work when I've got more > than one character on either side of the "equation". For single character > substitutions (t -> r, or vice versa) it doesn't really work so well. I'm > curious whether anyone else is finding the same thing. I have found in general that using the '2' ('DEFINITE_AMBIG') option didn't make as much difference as I was expecting. Nick -- -- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To post to this group, send email to tesseract-ocr@googlegroups.com To unsubscribe from this group, send email to tesseract-ocr+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/tesseract-ocr?hl=en --- You received this message because you are subscribed to the Google Groups "tesseract-ocr" group. To unsubscribe from this group and stop receiving emails from it, send an email to tesseract-ocr+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
