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

Anonymous wrote:

Would it be an idea to show also a "unix file size" for the local file (pherhaps as configurable option which is off by default)? Most people know if the server is a unix server and it would help them to know if file has changed or not.

In file panel?
Guest

Would it be an idea to show also a "unix file size" for the local file (pherhaps as configurable option which is off by default)? Most people know if the server is a unix server and it would help them to know if file has changed or not.
martin

Re: compare file size between windows and unix

That's not a bad idea. However it has some drawbacks:

You do not know if the remote file has indeed Unix line endings. But it is actualy not a problem if the size you show with the local file is to indicate actual size after upload.

With FTP protocol and SFTP protocol version 4 and newer, it is actually the remote server that does the conversion and it does it in its own way (unknown to WinSCP), so WinSCP should not anticipate the results.
Freitag

compare file size between windows and unix

When you copy a file from Windows to unix and the file already exists on unix, you are prompted if you want to replace the file.

File attributes are shown including the file size. The windows size includes both CR and LF, but the unix size only has the one. So it gives the appearance that the windows file is larger (sometimes by quite a large amount)

Would parsing the file to count the characters that would actually be transmitted take too long?