Hi. There seems to be some strange behavior with Unicode normalization and searches depending on where the original search is typed.
I tried searching for equivalent versions of Unicode characters with diacritics. For example, the letter é can be represented either by one code point (U+00E9) or by two (U+0065 and U+0301).
When searching for the single code point version, DEVONthink correctly always returns results for both the single code point and two code point versions: the correct file results are listed, and selecting a file will list occurrences in the search inspector and highlight them in the preview.
However, when typing the two code point version, the behavior varies depending on where the search was originally typed.
If the two code point version typed in the main search box in the application toolbar, the behavior is the same as the single code point version as described above.
However, if the two code point version is originally typed in a criteria editor text box in an advanced search, the search returns the correct file results, but fails to list individual occurrences in the search inspector and also fails to highlight them in the preview.
Placing the cursor in the search inspector search box and typing enter afterward does list individual occurrences in the selected file and also highlights them in the preview.
It would be preferable if the behavior were always the same as when typed from the main search bar, so that equivalent searches returned the correct results.
I’ve attached a test file that can be used to demonstrate the differences.
Unicode normalization search.pdf (48.5 KB)
Thanks for your help.