Date matching when OCR interprets "i" for 1

[mimifred]

Hello,

I use date matching in Hazel to rename PDF files based on a date matched in the document's OCR.

But sometimes, due to the fonts, the OCR thinks a "1" is a "i".
Like 10.12.2013 -> i0.i2.20i3

Any trick to get around this ?

Thank you.

[Mr_Noodle]

Unfortunately, there's no good way to get around incorrect OCR, at least where the characters being misinterpreted are critical parts of the date. You can try using a text custom token instead of a date one but it won't translate it into a usable date. If you only need to rearrange things, that might be suitable. Also note you can add a text replacement to replace all the i's with 1's.

[mimifred]

That is what I was afraid of... thanks for the fast answer !