Differences
This shows you the differences between the selected revisions of the page.
| faq_utf8 2005-06-26 | faq_utf8 2020-01-11 (current) | ||
| Line 1: | Line 1: | ||
| - | ====== How do I make WinSCP show UTF-8 encoded (Unicode) filenames correctly? ====== | + | ====== How do I make WinSCP show localized and/or UTF-8 encoded (Unicode) filenames correctly? ====== |
| - | [[protocols#sftp|SFTP protocol]] specification requires that client and server uses UTF-8 encoding (Unicode) for file names only since protocol version 4. So, as long as your server supports at least version 4 of SFTP, WinSCP will show UTF-8 encoded filename correctly automatically. However some implementations use UTF-8 encoding even for older version of protocol. In such case you have to enable UTF-8 manually. See session option //[[ui_login_sftp#protocol_options|Server does not use UTF-8]]//. | + | |
| - | With [[protocols#scp|SCP protocol]] WinSCP does not support UTF-8 at all. | + | ===== [[sftp]] SFTP ===== |
| + | [[sftp|SFTP protocol]] specification requires that client and server uses UTF-8 encoding (Unicode) for file names. | ||
| + | |||
| + | 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. | ||
| + | |||
| + | 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 ===== | ||
| + | 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 ===== | ||
| + | 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 | ||