Latest revision |
Your text |
Line 27: |
Line 27: |
| | | |
| Please help | | Please help |
− | -------------------------------------
| |
− |
| |
− | Same problem here. Used to work fine in transfers between Windows and Linux, but as of a couple years ago (at least), Filezilla won't add the CR to line endings with viewing a server file or downloading a server file to Windows. I've had to resort to to using Notepad++ for all ascii files, which is a pain. (Nice program, but needlessly complicated for most quick edits.) Yes, FZ is configured to transfer text files as ascii rather than binary. My default setting is auto, but I have a long list of ASCII file types. [[User:Zobo|Zobo]] ([[User talk:Zobo|talk]]) 09:35, 15 January 2018 (CET)
| |
− |
| |
− | UPDATE/CORRECTION?? I downloaded my files from server (Linux Apache shared server at GoDaddy), as a backup, and resulting line endings were just LFs. I copied them all to a bottom-level folder, and using Notepad++ I replaced all LF endings in all its files and subfolders with CRLF. Notepadd++ reported changing only a relatively few files, but I took that to mean folders, since all the file types I specified in my filter now end with CRLF. But, oddly, so do all other ASCII files I've spot checked, all of which were problematic before this operation. FileZilla is also showing them as CRLF on my computer now. Yet viewing the (unchanged) files on the server, those still just have LF (unix) endings. Go figure. Well, if somehow FZ or Windows got the desired religion, I'm not complaining. Will come back if the "fix" doesn't stick. [[User:Zobo|Zobo]] ([[User talk:Zobo|talk]]) 10:07, 15 January 2018 (CET)
| |