Differences
This shows you the differences between the selected revisions of the page.
| faq_utf8 2013-12-20 | faq_utf8 2020-01-11 (current) | ||
| Line 1: | Line 1: | ||
| ====== How do I make WinSCP show localized and/or UTF-8 encoded (Unicode) filenames correctly? ====== | ====== How do I make WinSCP show localized and/or UTF-8 encoded (Unicode) filenames correctly? ====== | ||
| - | ===== SFTP ===== | + | ===== [[sftp]] SFTP ===== |
| [[sftp|SFTP protocol]] specification requires that client and server uses UTF-8 encoding (Unicode) for file names. | [[sftp|SFTP protocol]] specification requires that client and server uses UTF-8 encoding (Unicode) for file names. | ||
| - | //With the latest release//, WinSCP by default uses UTF-8 encoding. You can force non-default behaviour using session option //[[ui_login_environment#utf|UTF-8 encoding for filenames]]//, particularly when your server does not use UTF-8. &recent | + | WinSCP by default uses UTF-8 encoding. You can force non-default behavior using session option //[[ui_login_environment#utf|UTF-8 encoding for filenames]]//, particularly when your server does not use UTF-8. |
| - | + | ||
| - | //With previous releases//, WinSCP by default expects that the local machine and the server uses the same encoding (no conversion is done) for [[sftp|SFTP-3]] and lower ((SFTP specification before version 4 has not required UTF-8 explicitly.)), and uses UTF-8 encoding for newer versions. You can force non-default behaviour using session option //[[ui_login_environment#utf|UTF-8 encoding for filenames]]//. This is useful especially for servers that use UTF-8 natively, thus even for older versions of SFTP. &recent | + | |
| Please be aware that if your server does not support UTF-8 encoding, but uses its local legacy encoding instead, it is its fault. The problem is not on WinSCP side. You should push your server provider to add support for UTF-8, and not ask for support of legacy encoding in WinSCP. | Please be aware that if your server does not support UTF-8 encoding, but uses its local legacy encoding instead, it is its fault. The problem is not on WinSCP side. You should push your server provider to add support for UTF-8, and not ask for support of legacy encoding in WinSCP. | ||
| + | |||
| + | By default WinSCP will automatically fallback to legacy Windows encoding, when a server returns a directory listing with file names not in UTF-8 encoding. For this reasons, you might get an inconsistent behavior during operations with files, depending on whether you visited a folder with non-ASCII file names before or not (or did not visit any directory at all, such as in [[scripting]]). To get a consistent behavior with a server that does not use UTF-8, disable UTF-8 encoding explicitly in session settings. | ||
| ===== FTP ===== | ===== FTP ===== | ||
| For [[ftp|FTP]] protocol, usage of UTF-8 is also controlled by session option //[[ui_login_environment#utf|UTF-8 encoding for filenames]]//. | For [[ftp|FTP]] protocol, usage of UTF-8 is also controlled by session option //[[ui_login_environment#utf|UTF-8 encoding for filenames]]//. | ||
| - | ===== SCP ===== | + | ===== [[scp]] SCP ===== |
| - | For [[scp|SCP]] protocol filename encoding conversion is not supported at all. | + | For [[scp|SCP]] protocol, usage of UTF-8 is also controlled by session option //[[ui_login_environment#utf|UTF-8 encoding for filenames]]//. |
| + | |||
| + | ===== WebDAV ===== | ||
| + | With WebDAV, a client and a server are required to use UTF-8. No configuration is necessary. | ||
| + | |||
| + | ===== [[ansi]] Legacy ANSI Encoding ===== | ||
| + | |||
| + | When not using UTF-8 encoding, WinSCP assumes the server is using the same legacy ANSI encoding as configured for local machine in //Control Panel > Clock and Region > Region > Administrative > Language for non-Unicode programs//. &wincp | ||