Opened 12 years ago
Closed 12 years ago
#7354 closed Bug report (worksforme)
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.
Change History (1)
comment:1 by , 12 years ago
|Status:||new → closed|
Well, I downloaded the Filezilla server and the client on a Windows 7 box. Then I tried to transfer a file named é (e acute).
And it transfered fine.
Internet Explorer was showing it wrong (it take as default Windows-1252 rather than using UTF8) but saved it fine.
Command line client was showing it wrong... and so I was not able to get it with this client.