There is a general problem across large numbers of resources with numbers that either scanned in wrong (0's and 1's coming out as o's and l's respectively) or were keyed in by someone who learned how to type on one of those old typewriters that didn't have a 1 key, the kind you used to have to use lower case L's to represent the numeral 1 on, and they still haven't kicked that old habit in the computer age.
As a result there are all kinds of numbers like these (I gave up searching after reporting hundreds of typos):
l0th, 10th, l1th, 1lth, l2th, l3th, l4th, l5th, l6th, l7th, l8th, l9th, 2oth, 3oth, etc.
l972, l988, l982, l970, l973, l974, l965, l980, l984, l985, l987, l996, l954, l966
l846, l867, l844, l885
l721, l729, l733
l603, l600s
l585, l547, l559
191l, 196l, 197l,
185l, 187l
177l
163l, 164l, 165l, 166l
152l
136l
19l3
Then there's the reverse problem, words that are supposed to have O's and I's in them which end up having 0's and 1's in the middle of them, such as this in The Pulpit Commentary: Exodus (Vol. 1):
I've reported that one. But I can't begin to search for all the other occurrences, of which I'm sure there are many. I've seen this before and hadn't bothered reporting it since the words and numbers are still readable, but I realize that it's important to fix them, as it will throw off Searching.
Surely you have some way of doing wildcard searches within your database of words that are in the index to find weird ones that have numbers embedded in them which would otherwise be real words if the 0's and 1's were changed to O's and I's (or lower case L's)?
