In 2.54 and now in 3.0 beta3, we still have the problem regarding copying or moving files where the filename contains extended characters or characters from a different locale. For example, create a file called Test.txt and then in Windows explorer, rename it to ┐Test.txt. (That's ALT-191 followed by Test.txt), Salamander sees it +Test.txt and then prevents access to the file. The same problem occurs with filenames that contain characters from Hebrew character sets although Windows Explorer handles them correctly. This also affects the "Open Active Folder" Shift-F3 function when the path is 247 characters long. If the file in this path has an extended character in and the file name is longer than 7 characters excluding the suffix, "Open Active Folder" Shift-F3 will not do anything. If the filename is edited in Explorer, this then works.
This testing was done on Windows 200 R2 Standard with SP1 (x64)
