faq_line_breaks » Revisions »

Differences

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

2019-12-15		2020-06-24
Restored revision 1569845402. Undoing revision 1576412378. (martin) (hidden)		no summary (216.104.81.200) (hidden) (untrusted)
	Line 16:		Line 16:
	===== Text/ASCII Transfer Mode =====		===== Text/ASCII Transfer Mode =====

-	For this reason, file transfer clients and servers support a text/ASCII [[transfer_mode\|transfer mode]]. When transferring a file in this mode, the file gets (ideally) converted from a format native to a source system, to a format native to a target system. For example, when uploading a text file using text mode from Windows to Unix system, the file line endings get converted from CR+LF to LF. Opposite to the text/%%ASCII%% transfer mode is a binary transfer mode that transfer the file as is (binary identical).	+	For this reason, file transfer clients and servers support a text/ASCII [[transfer_mode\|transfer mode]].
		+	When transferring a file in this mode, the file gets (ideally) converted from a format native to a source system, to a format native to a target system. For example, when uploading a text file using text mode from Windows to Unix system, the file line endings get converted from CR+LF to LF. Opposite to the text/%%ASCII%% transfer mode is a binary transfer mode that transfer the file as is (binary identical).

	WinSCP by default uses the binary transfer mode for all //regular file transfers//. Learn how to configure it to [[transfer_mode#changing\|use the text/ASCII transfer mode]]. You may also need to configure [[ui_login_environment\|correct server-side text file format]].		WinSCP by default uses the binary transfer mode for all //regular file transfers//. Learn how to configure it to [[transfer_mode#changing\|use the text/ASCII transfer mode]]. You may also need to configure [[ui_login_environment\|correct server-side text file format]].