The client may 'badly' create files on Windows, breaking accented letters
|Reported by:||Paul Dufresne||Owned by:|
|Component version:||Operating system type:||Windows|
|Operating system version:||Windows 7|
I had problems with accented letters with Filezilla client freshly downloaded last friday, on a Windows 7 (which I expect to use unicode for filenames).
HYPOTHESIS both of the bug and what is causing it ;-)
I believe that if the filename contains a 'e acute' with unicode value 0xE9 and so have UTF8 value 0xC3 0xA9, then the created file will have the 'e acute' replaced with two unicode characters.
The first being unicode value 0xC3 (A tilde) and the second the unicode value 0xa9 (copyright sign). Which I guess could happens if the createFile windows function called was the non-unicode one rather than the unicode one.