Quote:
Originally Posted by shalym
Actually, I see references to this all the time, and I just don't understand what the issue is. I use notepad. not Notepad++, just the regular notepad that comes with Windows. I've edited config files for my Kobo and my Kindle, and edited html, vbscript, javascript and probably many other things I'm not remembering, all using plain old vanilla notepad. I've never had a problem with any system not recognizing the line endings.
Maybe people who are having problem are using either Wordpad or MS Word instead of notepad? Neither of those will work for working in code, but again...I've been working with scripts and devices for years, and never had a problem with notepad.
Shari
|
The tests conclusively point to the issue of using CRLF, insomuch as there are utilities or manual editing for switching to *nix line endings, and that is the specific action that gets things working.
Regardless, if you create or edit a file using Windows' built-in Notepad, you will be working with CRLF. That may or may not blow up on you. I have no idea whether this specific file must use *nix line endings (I was not the one who said it was required), but of a surety, there are things that do depend on it.
(As for html and javascript, line endings are optional, so naturally there would be no problem either way. vbscript is a Windows thing, so if it depends on anything it will be DOS line endings...)
One way to test your claim (since it runs contradictory to the experience of, well, every other test by any other human being on the planet) would be to open one of those files with Notepad++, which will tell you whether the file uses *nix or DOS line endings.
And check the manual for the transfer program you use, to find out if it has the helpful feature of auto-correcting line endings. I am pretty sure Filezilla at least does that. EDIT: Yup --
https://wiki.filezilla-project.org/Data_Type