Check for (and correct) dbl-spacing when opening files...

[AshleyQuick]

I've seen some posts on the double-spacing issue when opening files and this continues to be an issue at times. I understand this is an issue with the way files are stored and transferred (between Windows and Unix) but is it feasible to add a feature that will check the file to determine if it contains double-spaced, Unix-style lines and, if so, give the option to revert back to single?

The last version of Macromedia Homesite had this feature (see the following screenshot)...




WeBuilder is an outstanding app and among the many aspects that sets it apart from the others is the little things.

[Karlis]

Good idea actually. No promises, but I shall think about this. Seems very reasonable.

[AshleyQuick]

That would be great, thank you for the consideration! Please let me know if you're in need of a tester. I'm (and I don't like admitting this lol) buried in code seven days a week.

[EvilBMP]

+1 for this...

I also have this issue from time to time ... This would end the SEARCH & REPLACE dbl-spacing procedure

[x3po]

+1

[andrispp]

I just had this problem with new 2010 version. Never had with 2008.

I don't get it. If new line is detected by LF in Unix and CR+LF in Windows then where is the problem just to ignore CR and use only LF for detecting where new lines should start ?

[Karlis]

Nothing has changed in this area. Problem happens because files uploaded in binary mode are downloaded in ASCII mode.

Can't ignore CF because there is also Mac format where there is no LF at all.

So to sum up it is a misuse of upload/download modes that causes the problem, but that does not mean we can not help our users fix the error to save them time.

[andrispp]

Removed all extensions from FTP Options Transfer Mode list to disable any conversation.

The strange thing is that all files was previously edit by Webuilder 2008 which had exact FTP file conversation settings as 2010 (Acctualy it seems that both versions share settings).

[anti]

I just posted about this issue:
http://forums.blumentals.net/viewtopic.php?f=4&t=4265
... before seeing this thread.

> but that does not mean we can not help our users fix their errors to save them time.

IMO, putting blame on the user is not valid because the cpanel filemanager editor, UltraEdit and even the FREE PSpad all
handle the CRLF line termination correctly and automatically in the instances I've tested where Webuilder added extra
carriage returns.

Plus, I don't feel that I am 'in error' for wanting to upload/unpack a one, highly-compressed archive file on the
server rather than unpack it on my desktop and upload hundreds of (larger) files individually.

Webuilder is an awesome piece of software. The ftp functionality is amazing; simply the best out of any current editor.
But this rather silly issue lets it down badly, especially since its been complained about for a long time.

[Karlis]

IMO, putting blame on the user is not valid

To make you happy, I updated the content of the post - there is now no user error, just error

[EvilBMP]

The strange thing is that all files was previously edit by Webuilder 2008 which had exact FTP file conversation settings as 2010.

I can confirm this behaviour - nearly every file I edited (via FTP) with the former latest version of WeBuilder 2008 has now double line spacings, when I open them in WeBuilder 2010. I think I could isolate this, but I am not sure. Some months ago - in WeBuilder 2008 - I had discovered that my line endings were stored in Windows format instead of Unix format, so I changed that. So I had files in Windows and in Unix format on the server, and over the time that changes more and more, when I edited some file again. But some files were not edited since a couple of days (over 100 or so).

Now I have WeBuilder 2010 installed and had to edit some of those old files. Although I am not sure, which file has Windows and which has Unix format, I believe that this issue occurs on files, which were saved in Windows format with WeBuilder 2008.
Important note - it does not matter if in my current settings the file format is set to Windows or Unix format - the double line spacings occur in both ways.

Greets Evil

[Karlis]

Probably somebody can give me acccess to an FTP account and point to a particular file which when opened opens with double spacing (I won't break anything). I really can not find anything wrong in this area as we have not changed anything or so it seems at least.

[EvilBMP]

Hi Karlis,

I have to update my latest comment. It seems, that the error does not occur when the files were transfered/ saved via FTP, but via SFTP. I forget about the difference. But the files mentioned in my previous post, where the problem occured, were always loaded via SFTP.

In detail ... older file -> uploaded/saved via SFTP (WB 2008) -> downloaded/opened via SFTP (WB 2010)

After installing a FTP daemon on the server, I downloaded the same file via FTP and compared them:

Left side: SFTP
Right side: FTP


As you can see, via SFTP there is an extra CR...

Greets Evil

[Karlis]

Yes, I confirm if a PHP file uploaded via FTP or SFTP (makes no difference) in binary mode is later downloaded via SFTP in ASCII mode, the extra CRs are addded by the FTP server. Interesting fact is that I can no more reproduce this with FTP. So any files uploaded in any mode via FTP downloaded in any mode seem to be ok. BUT I do suspect that this could be FTP-server software related and be the case only with my ISPs FTP server.

Anyways replacing CRCRLF with CRLF seems like a good idea, that should fix the problem. I'll look into the possibility of doing this.

[EvilBMP]

Anyways replacing CRCRLF with CRLF seems like a good idea, that should fix the problem.

I think so too. Anyways I can not understand why a SSH server should add those extra CRs...