I have noticed that when scanning documents where the old practice (going back to typewriters) to use rows of asterisks or equal signs as text separators, tesseract performs poorly.
Esample
Some document
Line one
**************************
Line two
=== === === === === === ===
Line three
On something like this, tesseract would strive to match the line made of asterisks or equal signs to some text, resulting in things like EERKKRKKERKKREAKREKKAKRKKKAK or RRR RRR NETT RRR RRR which is not typically the desired outcome.
It is my understanding that the issue might likely come from the training data rather than the engine itself. If this is so, I wonder if the training sets could be augmented to consider these cases.
I have noticed that when scanning documents where the old practice (going back to typewriters) to use rows of asterisks or equal signs as text separators, tesseract performs poorly.
Esample
On something like this, tesseract would strive to match the line made of asterisks or equal signs to some text, resulting in things like
EERKKRKKERKKREAKREKKAKRKKKAKorRRR RRR NETT RRR RRRwhich is not typically the desired outcome.It is my understanding that the issue might likely come from the training data rather than the engine itself. If this is so, I wonder if the training sets could be augmented to consider these cases.