benr wrote:I have a "contains match" rule that sets a custom date token based on file content. Some of the content has spaces in the date (e.g. "1 2 / 1 5 / 2 0 2 4") because of less-than-optimal OCR and therefore Hazel doesn't recognize the string as a date. Is there a way I can set a date format that will match this, or some other way to handle this case?
I have been using a ScanSnap S1300i scanner for a long time, and was using the ScanSnap Settings, File Option, check box "Convert to Searchable PDF" . I recently encountered the same problem that you described. As part of troubleshooting this issue, I have now Disabled File option "Convert to Searchable PDF", and created a new Profile that Sends the Scan to the ABBY FineReader app, which performs the Searchable OCR function, without the spaces in the dates. In my case ABBY FineReader was included with the ScanSnap software package, but I had never saw a need to use it.