Unicode C++
Unicode C++
Set FTP Command and Directory-Listing Charsets
See more FTP Examples
Demonstrates the CommandCharset and DirListingCharset properties, which control how non-ASCII text is encoded in commands (including remote paths and filenames) and how directory-listing responses are decoded.
Background: FTP predates Unicode, so servers vary in how they encode filenames; getting non-ASCII names right means matching the server's encoding on both sides.
CommandCharset (default ANSI) governs outgoing paths and filenames, while DirListingCharset governs decoding of LIST/NLST/MLSD replies. Modern servers typically use UTF-8 — often negotiated automatically via OPTS UTF8 ON — but setting these explicitly resolves mojibake with servers that do not advertise it.Chilkat Unicode C++ Downloads
#include <CkFtp2W.h>
void ChilkatSample(void)
{
bool success = false;
CkFtp2W ftp;
ftp.put_Hostname(L"ftp.example.com");
ftp.put_Username(L"myFtpLogin");
// CommandCharset is the encoding used for commands containing non-ASCII text, including remote
// paths and filenames. The default is ANSI; set utf-8 when the server uses UTF-8 filenames.
ftp.put_CommandCharset(L"utf-8");
// DirListingCharset is used only to decode directory-listing responses (LIST, NLST, MLSD). It
// does not affect commands or paths.
ftp.put_DirListingCharset(L"utf-8");
// Normally you would not hard-code the password in source. You should instead obtain it
// from an interactive prompt, environment variable, or a secrets vault.
ftp.put_Password(L"myPassword");
success = ftp.Connect();
if (success == false) {
wprintf(L"%s\n",ftp.lastErrorText());
return;
}
// Non-ASCII remote paths and listings are now encoded/decoded as UTF-8.
const wchar_t *listing = ftp.getTextDirListing(L"");
if (ftp.get_LastMethodSuccess() == false) {
wprintf(L"%s\n",ftp.lastErrorText());
return;
}
wprintf(L"%s\n",listing);
success = ftp.Disconnect();
if (success == false) {
wprintf(L"%s\n",ftp.lastErrorText());
return;
}
}