MVV wrote:I've created a double-extension file and tested it with different TC versions and in Explorer: Explorer and old TC show "exe" at the beginning of name while TC 8.52 and 9.0+ show "exe" at the end of name (or in extension column if extensions are aligned).
I already showed this above.
But this a different thing compared to RLO (U+202E), where all characters mirror, like:
Code: Select all
The user would see in explorer "foo.pdf" when file extensions are masked, or "foo.exe.pdf" when not or when in TC < 8.52.
In opposite to that, the U+202B character will swap whole filename parts
after possibly following RLE chars (Arabian, etc.), but only IF such char(s) will follow. The user would see "exe" at the name's beginning, which might be confusing as a name start, but might still be better than RLO. But it's up to Christian if he wants to block such a case of mixed/non-RLE/RLE chars as well.
ts4242 wrote:but according to your described solution if i set the option to show file extension directly after file name, there should be a warning, but this doesn't happen!
I don't have the test version, but I think it's intended to be the reversed way:
ghisler(Author) wrote:2. Allow to open files containing RTL markers, but only if the name contains Unicode characters from the right to left group: Unicode 0590-08FF
Since your test filename contains such chars, it works as described, issuing no warning any more.