Non-ANSI characters in file name produce errors

[Ohar]

I can't download file with unicode file name (e. g. cyrillic) via NppFTP.
I can create it on the server side, also I can upload it to the server side. But I can't donwload it from server side

Example: I mistyped in file name and can`t change it or even read it now via NppFTP.

-> RETR /example.com/�onfig.php  
550 /example.com/�onfig.php: No such file or directory
Download of /example.com/�onfig.php failed

[AutopilotNN]

+1
#50

En: Usually in clients put a choice of the coding of the server. In NppFTP it isn't present.
Rus: Обычно в клиентах ставят выбор кодировки сервера. В NppFTP этого нет.

[wandererkh]

I think the problem is in this line:
m_localName = SU::Utf8ToTChar(m_name); //FileObject.cpp:71
As I can understand, it's utf-8 to ansi transition. Please leave filename in utf-8 - I hope it will solve the problem.

[chcg]

@wandererkh Do you know a public available FTP server to test this against?

[wandererkh]

@chcg I've sent you credentials for private account on e-mail, thank you

[chcg]

Also fails on ftp:heise.de with anonymous at:

200 Switching to Binary mode.
-> SIZE /pub/konferenzen/ipv6-2014/Donnerstag_22052014/In-Depth/Weber_2014-05-22 Zugeho��rigkeit von MAC- und IPv6-Adressen speichern.pdf  
550 Could not get file size.
-> PASV  
227 Entering Passive Mode (193,99,144,79,97,64)
-> RETR /pub/konferenzen/ipv6-2014/Donnerstag_22052014/In-Depth/Weber_2014-05-22 Zugeho��rigkeit von MAC- und IPv6-Adressen speichern.pdf  
550 Failed to open file.
Download of /pub/konferenzen/ipv6-2014/Donnerstag_22052014/In-Depth/Weber_2014-05-22 Zugeho��rigkeit von MAC- und IPv6-Adressen speichern.pdf failed

[wandererkh]

I've found FTP_synchronize plugin: https://sourceforge.net/projects/npp-plugins/files/FTP_synchronize/
It can read content of these files and folders, but can't upload after editing.
FTP_synchronize_0_9_5_0_src.zip has source codes

[wandererkh]

I've chosen profile cache folder and now FTP_synchronize can upload files after editing

[chcg]

See https://tools.ietf.org/html/draft-ietf-ftpext-utf-8-option-00 and https://www.ghisler.ch/board/viewtopic.php?t=22402. So OPTS UTF8 ON could be actively used by the client to request UTF8 and check the response. Maybe later on there will be the need to really check if the server supports UTF-8, for now just assume if UTF8 is received it could also be used to access the dir or file with UFT8.

[wandererkh]

@chcg thanks a lot!
Now I can see utf-8 filenames and foldernames and read it's content.
Next step - it saves downloaded files and folders with non-utf-8 names and because of this it can't upload it right after edit.
Please fix it later and have a Happy New Year )