Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Options
Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)

Options

Topic review

martin

Re: The same thing happens with SCP protocol

Anonymous wrote:

The same thing happens with SCP protocol, all the lines with a single LF character get the CR added for Windows, which in most cases is a good thing.

However if you need the file to be maintained exactly character for character for version control systems it is a pain.

So you want to maintain the file binary the same? Then you need to turn force binary transfer mode.
Guest

The same thing happens with SCP protocol

The same thing happens with SCP protocol, all the lines with a single LF character get the CR added for Windows, which in most cases is a good thing.

However if you need the file to be maintained exactly character for character for version control systems it is a pain.
Guest

LF[10](Unix) / sftp protocol version 5

LF[10](Unix) / sftp protocol version 5
martin

Re: ascii file with mixed Unix/Windows line returns

And what's wrong with them? What version of SFTP are you using? What is your session configuration in respect to the end-of-line characters?
Guest

ascii file with mixed Unix/Windows line returns

Hi,

In my work I have to deal with ascii files which contain both Unix and Windows line returns (i.e. CR & CRLF).

I have noticed that these are correctly maintained when transferring to Unix from Windows but not when going back the way i.e. to Windows from Unix.

I have tried this with the latest version of WinSCP using both SFTP and SSH.

Is this a problem with my settings, the server or WinSCP?

Regards,
Danny Poulson.