Hacker News new | past | comments | ask | show | jobs | submit login

I mean - these 'fixes' are common as far as I can tell (working in/around OCR). But then again - I'm not issuing certificates.

Quite often you try to eliminate uncertainty by being clever: Sure, OCR engine: Go ahead and recognize O and l and B if you want. If I know that the context of this text is an amount, I'll still replace those chars with 0 and 1 and 8 afterwards.

(Engines usually allow you to configure the allowed character set, but in practice it seems to be easier/more reliable to work like a parser: Lenient in what you accept and strict in what you pass on)




I'm always amazed at how many Kindle books you buy have clearly not gone through a simple spell check to catch errors like these.


You intervene with humans when you detect /1io0/i.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: