Differences
This shows you the differences between the selected revisions of the page.
| 2013-10-25 | 2013-12-20 | ||
| beta tags (martin) | 5.5 removing beta tags (martin) | ||
| Line 4: | Line 4: | ||
| [[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 beta 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. &beta | + | //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 |
| - | //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. &beta | + | //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. | ||