Opened 12 years ago

Last modified 5 years ago

#3299 closed Bug report

Problems with files with accents in name

Reported by: bovergaauw Owned by:
Priority: normal Component: FileZilla Client
Keywords: Cc: bovergaauw, Tim Kosse
Component version: Operating system type:
Operating system version:

Description

Hi,

It appears that files with iso 8859-1 accented characters (uploaded for instance by a Windows version of FileZilla) program are not shown in the Linux version of FileZilla 3.0.2.1 if the charset encoding is set to "Autodetect" or "Force UTF-8".

I tested this amongst others with a file called "Là.txt" that I uploaded with FileZilla 3.0.2.1 on a Windows machine with the charset option set to "Autodetect". The file does not show up in FileZilla 3.0.2.1 under SuSE Linux 10.1 on a x86_64 machine (I use the FileZilla binaries created by the FileZilla project), unless I use the custom charset "iso8859-1". I would expect FileZilla to list all files (except for hidden files if FileZilla is not configured to show them, of course), independent of the charset settings, the charset setting should only affect the way their names are displayed.

Best regards,

Bo

Change History (4)

comment:1 Changed 12 years ago by Tim Kosse

According to the FTP specifications, the only two encodings supported by FTP are ASCII and UTF-8. Any other encoding is violating the protocol specifications. Please refrain from using non-English characters or switch to an UTF-8 enabled server.
If the autodetection fails, you can force a custom encoding in the site manager.

comment:2 Changed 12 years ago by bovergaauw

Hi Tim,

First of all, thanks for having created this great program.

I understand that the protocol accepts only ASCII and UTF-8, but that does not mean that files with special characters in their names should not be listed. If they contain special characters from for instance the ISO 8859-1 character set, I would expect them to be listed as if the file names were encoded in UTF-8, meaning with "weird" characters. I discovered the problem with a server that "speaks" UTF-8 perfectly well, and discovered the existence of another file only accessing the remote directory with another tool. As for the fact that one should not use special characters in file names, I tend to agree, but I do not necessarily have control over what *others* put on a server for me to download, often with FileZilla 2 for Windows.

Does the solution I propose make sense to you?

Best regards,

Bo

comment:3 Changed 12 years ago by Tim Kosse

It's not that simple, there is no 1:1 mapping between different encoding. If FileZilla doesn't display a file it is because it cannot convert it into its internal encoding (which is UTF-16), mainly because it doesn't know the source encoding.
Furthermore, encodings have to be consistent on the whole server. You cannot mix them.

comment:4 Changed 12 years ago by bovergaauw

Hi,

Sorry for continuing on this subject, but wouldn't it be possible to at least indicate that there is a file with an invalid file name on the server? In that case the user is at least aware of the existence of a/an additional file on the server, and can try custom encodings. I'm asking this, as that was exactly the problem I encountered: A friend told me that a number of files were waiting on his server, and I thought I had them all whereas in fact there was an additional one with an ISO 8859-1 encoded file name.

Best regards,

Bo

Note: See TracTickets for help on using tickets.