I've been reading about RTLO (Right-to-Left Override) characters, such as 0x202E and so I thought I would use Dopus to see if a) I have any files named with RTLO characters, and b) If I can find one that I had created myself. I figured I could search the same way I would search for anything with a 'z' in it, namely "z.". So, I searched for "0x202E." in the quick search (except, of course, I copied the string with the actual character in there, so four characters). However, it returns everything in the directory (basically the same as if I had only typed "**.*"). I did find that if I copied and pasted the exact whole filename into quick search it does find the file, but that might still just indicate that it's ignoring the RTLO character.
Next I tried bringing up the advanced find, added one rule Name Match "0x202E.*" but strangely that returned nothing (it did not find the file I created for it to find). Next I tried regular expressions, searching for "[\u202E]+" and that finally worked.
This seems like a bug in the wildcard search? It seems like it shouldn't be so hard to find strings containing RTLO characters, should it? Or is this somehow a feature that I'm just not seeing?
I do need to admit that I have never learned a language that required right-to-left encoding, so maybe this way of working is normal and required to support these languages?
The full regular expression to find any file containing any of the RTLO characters is:
[\u200E\u200F\u202A\u202B\u202C\u202D\u202E\u2066\u2067\u2068\u2069]+