#47 Russian characters are replaced with question marks in FTP

[andrey-zh]

I know, you explicitly state that you do not support accented characters by the FTP server.

But if a file name contains Russian Cyrillic characters only, the characters are displayed as question marks and file size is shown as zero on the client. It also seems me that it is impossible to manipulate such files as well, though I have not been able to investigate this in details.

I believe that the problem can be narrowed down to the Unicode/UTF-8 support. I also assume that this is not a priority for you.

If I provide a fix for this issue, would you like to incorporate it into the codebase? Of course, I cannot promise any deadlines.

The implementation in question is Windows FTP server, I am not sure about behaviour on other platforms and other SFK tools.

[stahlworks]

this is not just about cyrillic characters; for example,
german special characters in filenames will not work as well,
at least with a linux ftp server, or whenever client and server
use a different code page.

so it would require:

1) a correct implementation of RFC 2640 for ftp with unicode support,
both for client and server (you can't just make the sfk ftp client
RFC compliant and leave the sfk server as is)

2) using special windows apis for wide character handling
of filenames, when using sfk select ... +ftp mput

3) using code page conversions on handling single filenames
passed by the command line, like on sfk ftp ... put filename

4) codepage conversions whenever printing filenames to terminal,
like on sfk ftp ... dir

with 2), 3) and 4) requiring many, deep changes within sfk
with possible endless side effects to the 100 other commands.

I do NOT promise to take over any code changes.

top prority for the main sfk is to keep it simple and maintainable,
and that's the reason why there is no support for non english languages.
the complexity may expand massively, i will not release changes
that i have not tested, and i don't want to end up testing how
to upload files from system a with codepage 123 to a server b with utf
then download to system c with codepage 456 and guessing
why there are so many errors.

sfk is open source, so you may create your own ftp client tool
based on sfk, release it on your homepage, and handle support
for that by yourself. if the tool is still BSD licensed
you can be sure i will take a look at the source code,
but only to think how changes and side effects might be reduced
to a minimum if it would be integrated, which might be impossible.