Differences
This shows you the differences between the selected revisions of the page.
| 2015-12-16 | 2018-11-01 | ||
| removing recent tags with release of the next major branch 5.8 (martin) | 5.6.2 Bug 1212 Auto-detecting when SFTP server does not use UTF-8 encoding with SFTP-3 and older. (martin) | ||
| Line 7: | Line 7: | ||
| 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 ===== | ||