TC doesn't detect UTF8 at FTP if connection is not stored

[Mishail]

Initial condition
1. FTP server with UTF8 support (FileZilla Server version 0.9.27 beta in my case)
2. The connection to server above is not stored in the Ctrl+F list
3. Sytem: WinXP SP3

Steps.
1. Press Ctrl+N and enter server adress
2. Navigate to the folder with items (files/subfolders) with non-ASCII names.
3. Observe the issue

Additional info.
1. Server reports the following features:

FEAT
211-Features:
MDTM
REST STREAM
SIZE
MLST type*;size*;modify*;
MLSD
UTF8
CLNT
MFMT
211 End

2. If connection to such server is stored in the Ctrl+F list then non-ASCII items are displayed properly

P.S. Unfortunately I'm yet unable to post links to screenshots

[fenix_productions]

2Mishail
I am not sure it's a bug because TC treats Ctrl+N as new connection and does not check if it exists in Ctrl+F list.

This is rather a missing feature because there is no option to choose encoding in Ctrl+N dialogue.

Support++ for adding encoding dropdown control.

[Mishail]

2fenix_productions

Ctrl+N as new connection and does not check if it exist in Ctrl+F list

I do understand. I meant if I connect to the same server via Ctrl+F dialog (with Auto Detect option by default) then there is no issue.

IMO it would be better to use "auto-detect encoding" by default in connections from Ctrl+N dialog, or, as you rightly noticed, add a dropdown to that.

[fenix_productions]

2Mishail
OK. I've got it.

I though you have some specific encoding (like "UTF-8") stored in Ctrl+F.

[Lefteous]

Add more options to quick connect? It must be ensured that's it's still simple. I would prefer autodetect instead of an option.

[Mishail]

2Lefteous

I would prefer autodetect instead of an option.

That was my point

[ghisler(Author)]

2Mishail
Currently there is no UTF-8 detection mechanism for Ctrl+N. For Ctrl+F (when set to auto-detect), TC uses two methods to detect UTF-8:
1. The server may report it in the SYST command response
2. TC sends OPTS UTF8 ON and checks the server response

I can add these two for Ctrl+N too. I don't quite understand what the "UTF8" line in the "FEAT" response means. Do you have any information on that? For example, the server RaidenFTPD reports UTF8 in response to "FEAT", but it also reports "215 UNIX Type: L8 , CP:1252" in response to "SYST", so UTF-8 doesn't seem to be enabled...

[Mishail]

2ghisler(Author)
I'm not a n expert, but take a look at http://wiki.filezilla-project.org/Character_Set

Looks like solution #2 (2. TC sends OPTS UTF8 ON and checks the server response) is more appropriate.

[fenix_productions]

2ghisler(Author)

I might be wrong but...

According to: http://www.networksorcery.com/enp/rfc/rfc959.txt

SYSTEM (SYST)

This command is used to find out the type of operating
system at the server. The reply shall have as its first
word one of the system names listed in the current version
of the Assigned Numbers document [4].

According to: http://www.networksorcery.com/enp/rfc/rfc2389.txt

Two new commands are added: "FEAT" and "OPTS".

These commands allow a client to discover which optional commands a
server supports, and how they are supported, and to select among
various options that any FTP command may support.

So I understood that in the case of:

For example, the server RaidenFTPD reports UTF8 in response to "FEAT", but it also reports "215 UNIX Type: L8 , CP:1252" in response to "SYST", so UTF-8 doesn't seem to be enabled...

RaidenFTPD identifies itself as server with UNIX based operating system with CP:1252 characters encoding. It also informs that among many features it handles UTF-8.

So it's more like:

SYST -> Windows XP SP3 (Polish); ANSI: WIN-1250
FEAT -> Unicode

[Mishail]

RFC 2640

3.2 Servers compliance

Servers MUST support the UTF-8 feature in response to the FEAT command [RFC2389]. The UTF-8 feature is a line containing the exact string "UTF8".

3.3 Clients compliance

Clients MUST support the FEAT command and recognize the "UTF8" feature (defined in 3.2 above) to determine if a server supports UTF-8 encoding

[ghisler(Author)]

2Mishail
Thanks for the info. Unfortuantely this only tells me that a server supports UTF-8. But how do I enable it, or find out that it is already enabled? As described above, some servers report that they support it, but it's not enabled by default...

[Mishail]

2ghisler(Author)
You've already provided a solution:

2. TC sends OPTS UTF8 ON and checks the server response

It should work for all servers.

[ghisler(Author)]

OK, I will try that for Ctrl+N too, then!

[Spike]

I do not confirm this bug.

FileZilla Server version 0.9.29 beta

FEAT
211-Features:
MDTM
REST STREAM
SIZE
MLST type*;size*;modify*;
MLSD
UTF8
CLNT
MFMT

Host — Vista SP1, same as server.

[ghisler(Author)]

2Spike
Did you really use Ctrl+N to connect? If yes, can you post the connection log, please? Just double click on the two line log window to open it in Lister and copy the data. You can replace server name and IP addresses by others (but keeping the name length).