non ASCII folder names are displayed wrong in FileZilla Client for mac

[Jon Ege Ronnenberg]

I have a website with an IDN name, demægtigevikinger.dk. On mac (OSX 10.9.1) the name is displayed as: /demægtigevikinger.dk

I can live with that, but FileZilla Client for mac creates duplicates of the folder when I upload and setting "Default remote directory" does not work. My work around is currently to sync to a Windows 7 PC via git and use FileZilla from Windows.

I will try to attach a screen shot to the ticket after submission.

[Jon Ege Ronnenberg]

non-ASCII charater bug on mac

[Jon Ege Ronnenberg]

FileZilla Client info:
FileZilla Client

---

Version: 3.7.4.1

Build information:

Compiled for: i686-apple-darwin9
Compiled on: i386-apple-darwin9.8.0
Build date: 2014-02-11
Compiled with: i686-apple-darwin9-gcc-4.2.1 (GCC) 4.2.1 (Apple Inc. build 5577)
Compiler flags: -g -O2 -Wall -g -fexceptions

Linked against:

wxWidgets: 2.8.12
GnuTLS: 3.1.11
SQLite: 3.7.6.2

Operating system:

Name: Mac OS X (Darwin 13.0.0 x86_64)
Version: 16.145

[Tim Kosse]

Does the server in question support UTF-8? When connecting to the server for the first time, watch the reply to the FEAT command, it must contain a line with UTF8.

If your server does not support UTF8, you must either upgrade to a server that supports UTF8 or refrain from using non-ASCII characters. Everything else is not covered by the FTP specifications.

Please reopen iff the server claims UTF8 support in the FEAT reply.

[Jon Ege Ronnenberg]

Yes, the server seems to support UTF-8. I've updated to FileZilla 3.8.0. Below is copy of my log:

Status:	Resolving address of ftp.jakobmuusmann.dk
Status:	Connecting to [hidden]...
Status:	Connection established, waiting for welcome message...
Response:	220---------- Welcome to Pure-FTPd [privsep] [TLS] ----------
Response:	220-You are user number 1 of 50 allowed.
Response:	220-Local time is now 16:51. Server port: 21.
Response:	220-This is a private system - No anonymous login
Response:	220-IPv6 connections are also welcome on this server.
Response:	220 You will be disconnected after 5 minutes of inactivity.
Command:	USER web522586
Response:	331 User web522586 OK. Password required
Command:	PASS ************
Response:	230-OK. Current restricted directory is /
Response:	230 429483 Kbytes used (8%) - authorized: 4889600 Kb
Command:	SYST
Response:	215 UNIX Type: L8
Command:	FEAT
Response:	211-Extensions supported:
Response:	 EPRT
Response:	 IDLE
Response:	 MDTM
Response:	 SIZE
Response:	 REST STREAM
Response:	 MLST type*;size*;sizd*;modify*;UNIX.mode*;UNIX.uid*;UNIX.gid*;unique*;
Response:	 MLSD
Response:	 AUTH TLS
Response:	 PBSZ
Response:	 PROT
Response:	 UTF8
Response:	 ESTA
Response:	 PASV
Response:	 EPSV
Response:	 SPSV
Response:	 ESTP
Response:	211 End.
Command:	OPTS UTF8 ON
Response:	200 OK, UTF-8 enabled
Status:	Connected
Status:	Retrieving directory listing...
Command:	PWD
Response:	257 "/" is your current location
Command:	TYPE I
Response:	200 TYPE is now 8-bit binary
Command:	PASV
Response:	227 Entering Passive Mode ([hidden],[hidden])
Command:	MLSD
Response:	150 Accepted data connection
Response:	226-Options: -a -l 
Response:	226 21 matches total
Status:	Invalid character sequence received, disabling UTF-8. Select UTF-8 option in site manager to force UTF-8.
Status:	Directory listing successful
Status:	Retrieving directory listing...
Command:	CWD demægtigevikinger.dk
Response:	250 OK. Current directory is /demægtigevikinger.dk
Command:	PWD
Response:	257 "/demægtigevikinger.dk" is your current location
Command:	PASV
Response:	227 Entering Passive Mode ([hidden])
Command:	MLSD
Response:	150 Accepted data connection
Response:	226-Options: -a -l 
Response:	226 9 matches total
Status:	Directory listing successful

[Jon Ege Ronnenberg]

Hmm.. Forcing UTF-8 in the Site Manager under Charset seems to resolve the issue. Is it still a server fault? Or how æ turn into æ in the directory listing?

[Tim Kosse]

Status: Invalid character sequence received, disabling UTF-8. Select UTF-8 option in site manager to force UTF-8.

The server is sending invalid data, it's a server issue.