>Doesn't UNIX use just a single linefeed as a newline character? If you know
>there are only LFs and no CRs in the string, then:
>
><cfset cr = Chr(13)>
><cfset lf = Chr(10)>
><cfset mystring = Replace(mystring, "#lf#", "#cr##lf#", "all")>
Yeah, all the online docs I can find have this basic info, UNIX = CR, Mac =
LF, Win = CRLF.
However, when I output the codes for the files I'm working with using
Asc(), I found sequences of 13-13-10, which was mentioned as the UNIX
"double-spaced" sequences in one reference:
http://www.nylug.org/mlist/nylug-talk_mhonarc/2001-01/msg00201.html
Anyways, I just found that the source of my problem was more to do with
CFFILE. In my CF5 book (Rob's O'Reilly one), the ADDNEWLINE attribute is
described like this:
"If set to Yes, a newline character is added to the end of the file."
This seems to be wrong - the attribute adds a newline to the end of every
*line* in the file, creating something that says "Open as double-spaced or
single-spaced lines" when you open in HS. Default is Yes. I explicitly set
it to no and, no double-spaced lines.
I think I can get back to work now, but if anyone's got any references to
explain all this, I'd be interested! Also in how to get HS+ to always open
double-spaced files as single-spaced, skipping the dialogue - the reg key
mentioned in the above web page seems to not be there anymore.
cheers,
Gyrus
[EMAIL PROTECTED]
http://norlonto.net/gyrus/dev/
PGP key available
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
