Page 1 of 1

"Contents Contain match" fails with Umlaut characters

PostPosted: Thu Jul 04, 2013 4:08 pm
by WorkflowsGuy
Hi,

when creating my document naming rules, I discovered that the "contain match" rule will not find words that contain umlaut characters in pdf documents (I verified this by searching for the words in Preview; they were found there).
This also affects date search patterns with month names; the rules will fail for month names that contain umlauts.

Cheers,
Stefan

Re: "Contents Contain match" fails with Umlaut characters

PostPosted: Fri Jul 05, 2013 3:20 pm
by Mr_Noodle
Can you give me specific examples? Or email support with a sample file and rule?

Re: "Contents Contain match" fails with Umlaut characters

PostPosted: Sun Jul 07, 2013 9:42 am
by WorkflowsGuy
I have sent a detailed description and files to reproduce the issue to Support.

Regards,

Steve

Re: "Contents Contain match" fails with Umlaut characters

PostPosted: Mon Jul 08, 2013 12:30 pm
by Mr_Noodle
Thanks. I can replicate the problem here and am looking into it.

Re: "Contents Contain match" fails with Umlaut characters

PostPosted: Mon Jul 15, 2013 5:03 pm
by xaMax
Hi,

I have the same problem here. I tried for two hours to get some rules working and couldn't explain the behavior as it sometimes worked and sometimes not.

Thank you for the hint with Umlaut characters. :)

One of my rules has a "contain match" for "München, MM/DD/YYYY(<--DatePattern)".
It didn't work.
As I deleted the first two characters "Mü" and just searched for "nchen, MM/DD/YYYY" -
the rule worked!

So you can fix it by just deleting some parts of your words - but this does not work for date patterns. :/

I hope, it will be fixed in Hazel 3.1.3?

Kind regards!

Re: "Contents Contain match" fails with Umlaut characters

PostPosted: Tue Jul 16, 2013 1:58 pm
by Mr_Noodle
It should be. If you want to run a test build, email support.