4 ms·
It just occurred to me... The title, "Contents", was set in very heavy type which happened to be an unexpected edge case in the classifier and it matched the "
by gngeal 13y ago
It just occurred to me...
The title, "Contents", was set in very heavy type which happened to be an unexpected edge case in the classifier and it matched the "o" with the "e" and "n" and output "Contoots".
Wouldn't it be a good idea to perform OCR - using a language model, the works - before you start classifying the JBIG2 symbols? That way, you'd have additional contextual information to say "Aha, 'contoots' is probably not what it reads here" at least in some of the cases.
Although, I realize that on "Google scale", such a complex solution could be a problem.
- cmarschner 13y agoLanguage model would give you the opposite problem - eg you scan a print of _this_ page containing the word "contoots" which your language model corrects to "contents"...
- ygra 13y agoJBIG2 [91] suggests using OCR to verify that you didn't mangle anything. If the compressed result has a lower success rate in matching words than the original, then you did something wrong. [91] http://jbig2.com/ http://jbig2.com/