#12908 closed Bug report (worksforme)

Unicode characters in filenames (server side) not shown properly

Reported by: php4fan Owned by:
Priority: low Component: FileZilla Client
Keywords: Cc:
Component version: Operating system type: Linux
Operating system version: Manjaro


Seems like I'll have to upload the attachments afterwards.

I have uploaded a bunch of files to a server, with unicode characters in the file names.

I'll attach a screenshot of how such characters look like in fileziulla in the server panel.

For comparison, I'll attach a screenshot of a terminal where I'm connected via SSH to the very same server and I've run a "ls" command: you can see the unicode characters properly rendered in the output.

Attachments (2)

filezilla.png (44.2 KB ) - added by php4fan 13 months ago.
filezilla screenshot
ssh.png (29.1 KB ) - added by php4fan 13 months ago.
terminal screenshot

Download all attachments as: .zip

Change History (5)

by php4fan, 13 months ago

Attachment: filezilla.png added

filezilla screenshot

by php4fan, 13 months ago

Attachment: ssh.png added

terminal screenshot

comment:1 by php4fan, 13 months ago

This is way more serious than I thought. Not only are the filenames with unicode characters not displayed properly, but that also prevents you from doing anything with those files.

For example:

  • click on a file whose name has non-ascii characters
  • rename it with a name with no non-ascii characters

Expected: should rename the file
Observed: fails on the server side with error message saying the file does not exist, probably because FileZilla sent the wrong filename to the server.

comment:2 by php4fan, 13 months ago

Priority: highcritical

Changing to critical because: see last comment

comment:3 by Tim Kosse, 13 months ago

Priority: criticallow
Resolution: worksforme
Status: newclosed

Make sure to use an UTF-8 locale, make sure your filesystem uses UTF-8, make sure the files were originally saved using UTF-8 filenames on your local system, and make sure that the remote server too uses UTF-8.

As long as these trivial requirements are met, FileZilla has absolutely zero issues with transferring filenames with Unicode characters.

Using any other character encoding on any step in the chain is invoking nasal demons.

Note: See TracTickets for help on using tickets.