View Single Post
Old 11-13-2017, 02:39 AM   #4
Tex2002ans
Wizard
Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.Tex2002ans ought to be getting tired of karma fortunes by now.
 
Posts: 2,306
Karma: 13057279
Join Date: Jul 2012
Device: Kobo Forma, Nook
Quote:
Originally Posted by doubleshuffle View Post
I would also appreciate such a feature. I'm working with a scan right now where the OCR has produced tons of "l" vs. "1" mix-ups. They are very hard to detect with the spellcheck as it is now.
Currently, as a workaround, I use Calibre's Spellcheck (like pictured above).

Then I usually just type the numbers 0-9 in the search box one-by-one, and do a quick scan through the list to see if anything strange pops out.

And I have a few Regex that I use to try to minimize the impact:

Search: [lo]\d
Search: \d[lo]

That tries to catch things like "19l0" or "l910" or "It was 8.o5cm long".

I also try to use this:

Search: (Jan|Feb|Mar|Apr|Aug|Sept|Oct|Nov|Dec)\. [lo]
Search: (January|February|March|April|August|September|Oct ober|November|December) [lo]

to try to catch the odd dates: "Jan. i5, 2017" or "March i, 1910" or "August i982".

Last edited by Tex2002ans; 11-13-2017 at 02:44 AM.
Tex2002ans is offline   Reply With Quote