NWX 2.x.x is making it impossible for me to create <b>tab-delimited text files</b> that will import into some applications (such as Now-Up-to-Date).
A file saved as TEXT/ASCII by Nisus Writer places a <b>Linefeed (hex 0A)</b> at the end of every line, instead of a <b>Carriage Return (hex 0D)</b>. Several applications return an error, unable to recognize that as a return (because it actually is not a return character).
How can I save files in NW that will insure a <b>CR</b> at the end of every line?
Carriage Return vs. Newline vs. Linefeed
Welcome to Mac OS X. In line with other Unix-based OS's Mac OS X uses the linefeed char to denote end-of-line in text files whereas the old classic Mac OS used the totally non-standard carriage-return character. All Cocoa apps that produce text files use (or should use) the linefeed character by default (see TextEdit for example). MS-DOS/Windows has always used the old carriage-return & linefeed combination (dating from old teletype machines!) to perform the same function.
Needless to say this madness has caused endless problems when it comes to transferring simple text files from one OS to another. At least now there's only two variations to worry about, unless you are using Classic Mac OS apps of course...
Several 3rd party text editors - Tex-Edit Plus and Text Wrangler for example - can handle and convert the various end-of-line markers and there are shareware utils like Stripper that can convert files from one format to another too.
Needless to say this madness has caused endless problems when it comes to transferring simple text files from one OS to another. At least now there's only two variations to worry about, unless you are using Classic Mac OS apps of course...
Several 3rd party text editors - Tex-Edit Plus and Text Wrangler for example - can handle and convert the various end-of-line markers and there are shareware utils like Stripper that can convert files from one format to another too.