faq_utf8 » Revisions »

Differences

This shows you the differences between the selected revisions of the page.

2006-01-10		2006-01-10
grammar (martin)		dot for footnote (martin)
	Line 2:		Line 2:
	[[protocols#sftp\|SFTP protocol]] specification requires that client and server uses UTF-8 encoding (Unicode) for file names.		[[protocols#sftp\|SFTP protocol]] specification requires that client and server uses UTF-8 encoding (Unicode) for file names.

-	WinSCP can operate in two modes, either it expects that the local machine and the server uses the same encoding (no conversion is done) or treats remote filenames as UTF-8 (Unicode) encoded. By default, the first mode is used for [[protocols#sftp\|SFTP protocol]] version 3 and lower ((SFTP specification before version 4 has not required UTF-8 explicitly)), the latter mode is used for newer versions. You can force non-default behaviour using session option //[[ui_login_sftp#protocol_options\|Server does not use UTF-8]]//. This is useful especially for servers that use UTF-8 natively, thus even for older versions of SFTP.	+	WinSCP can operate in two modes, either it expects that the local machine and the server uses the same encoding (no conversion is done) or treats remote filenames as UTF-8 (Unicode) encoded. By default, the first mode is used for [[protocols#sftp\|SFTP protocol]] version 3 and lower ((SFTP specification before version 4 has not required UTF-8 explicitly.)), the latter mode is used for newer versions. You can force non-default behaviour using session option //[[ui_login_sftp#protocol_options\|Server does not use UTF-8]]//. This is useful especially for servers that use UTF-8 natively, thus even for older versions of SFTP.

	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.