Here's the problem - the site is hosted on a Unix server, and you are operating on a Windows workstation. The Line break preference should always be set to match the OS on the host not on your local system. The spaces that you are seeing are caused by the fact that Unix uses only Line Feeds to separate lines. When your server line break type is a mismatch DW thinks that the file you just fetched needs to be formatted because the lines run together. In formatting the lines, DW will insert the CR/LF pair, which results in an EXTRA LINE in your code. If you switch your host line break to Unix, then DW knows not to try to correct the missing (non-printable) characters it finds in the fetched file but rather to replace the linefeed with CR/LF.
This is not a bug - it's the intended behavior. And it has been so since DW2.
I appreciate the response, but it does not match the facts.
Examining the file downloaded in binary, it has crlf line breaks.
Examining the same file downloaded by Dreamweaver, each line now has TWO crlf's or crlf crlf.
This is a bug, and it belongs to dreamweaver.
Other ftp programs download the file correctly in both ascii and binary mode.
I didn't post without testing my conclusions, rather my conclusions came from my tests.
Did you upload the file after first creating it with the proper server preference settings?
Irrelevant. There is no excuse for dreamweaver to fail to do a correct ftp transfer when other ftp programs have no problem in doing so.
That is why its a bug. Adobe's program corrupts <some> files during file transfer in <some circumstance> that no other ftp program ever corrupts in any circumstance.
Having said that, I have been doing this 3+ decades, I know how to set settings.
I also know the correct answer to "Your program added thousands of blank lines to my file" is not
"This is not a bug - it's the intended behavior. "