Noodlesoft Forums

Is there a way to get Hazel to be more tolerant of separators when matching to a custom date format? I am trying to match dates in the contents of documents that have been OCR'd. For a date like "January 1, 2015" the OCR process often leaves out the space between the comma and the year or turns the comma into a period. I'd like the match to work in these cases too.

In such cases, it pays to not be overly specific. Try using the "anything" token to match any fudge in between the date components.