ftp bug

[artem]

Hello.
I've found a liitle mistake in muCommander - there aren't displayed russian symbols (CP1251) in file and directory name at the ftp.
In ftp-clients such as gFTP there is a possibility to choose the encoding of ftp server - and so this problem is solved. And what is recommended to do with muCommander?

http://www.konotop.net/pic/bug1.png - bug in muCommander
http://www.konotop.net/pic/bug2.png - gFTP

[maxence]

Hi Artem,
Thanks for reporting this bug with screenshots and all. I was easily able to reproduce it.

Here's the changes that were made to the current nightly build to try and overcome the problem :

- Default FTP encoding was changed to UTF-8 (formerly ISO-8859-1) as most modern FTP servers seem to default to UTF-8. I tested this with 'tnftpd' and 'proftpd' servers: extended characters that were previously broken are now properly displayed

- The 'OPTS UTF8 ON' command is sent to the remote server after login. When supported, this command tells the server to expect UTF-8 from the client and output UTF-8 to the client. This command is unfortunately not always implemented by FTP servers.

All in all, this should fix most FTP encoding problems. Could you tell me if that fixed yours ?

Nonetheless, we'll probably have to add a custom FTP encoding option anyway. It's the only solution if the remote FTP server doesn't use UTF-8 by default or can't switch to UTF-8 (doesn't support the opts utf8 command).

Cheers,
Maxence

[maxence]

Erratum : actually, the nightly build hadn't been properly updated. The changes I was talking about are now available.

[artem]

The problem has been modified for a little but still remains. http://voron.konotop.net/pic/bug3.png

I've learned the version of ftp-server - it's "ProFTPD 1.3.0rc5 Server" (probably it'll help).

Looks like the best solution would be allowing the user to change ftp-server's encoding.

[maxence]

The FTP encoding issue has been addressed in the current nightly builds: you can now choose which encoding to use in the FTP panel of the 'Connect to server' dialog (UTF-8 by default).
The FTP encoding is saved with your credentials, which allows muCommander to 'remember' which FTP encoding to use for a particular server. If you choose to save the credentials to disk, the encoding value will be saved and reused next time muCommander is started.

There is however one limitation: you cannot change the encoding of a particular FTP connection 'on the fly'. To change it, you'll need to disconnect any active FTP connection to the server (you can do so in the 'Show active connections' dialog), and then reconnect to the server with the new encoding. This requires more effort than strictly necessary if you need to do some 'trial and error' in order to figure out which encoding an FTP server is using. We might implement a better way to do this in the future...
But in your case, since you seem to know which encoding to use, it should be as easy as 123 :)

I hope that will fix your problem, please us know if it did !

Cheers,
Maxence