On Saturday 29 December 2007 20:29, Fred Cisin wrote:
On Sat, 29 Dec 2007, Roy J. Tellason wrote:
LF CR?
Not that I've ever seen, the CR usually being sent first because if it's
any kinda mechanical thingy it takes longer.
that makes sense. I have run into LF CR in files, but haven't gotten
around to tracking down what system created them.
Is
'\n' 0Dh? 0Ah? 0Dh 0Ah? 0Ah 0Dh?
I remember back when I first started fiddling with c programming having
to use \n\r in some instances to get what I wanted.
THAT would give LF CR on some systems!
I don't even remember for sure that it was in that order, but I was doing
screen output at the time so it made little difference.
I always
thought it'd be kinda nifty to have one character instead of
two.
Many companies went that route.
For
example,
TRS80 was 0Dh; IBM PC was 0Dh 0Ah
I remember well one Tandy printer that double-spaced lines and there
didn't seem to be any way to disable that "feature".
Some Tandy compatible printers had "smart auto linefeed" - a line feed
would be added to a CR IFF there was not a LF following the CR.
That worked well except for the LF CR case.
I can't recall now what the system was that was feeding the printer in
question, but apparently there was some software sequence (escape sequence
maybe?) that could be fed to the printer to turn that feature off. That
being all the way back in oh, 1984 or thereabouts, the info on just how to
do so was pretty hard to come by, compared to how it might turn out these
days.
--
Member of the toughest, meanest, deadliest, most unrelenting -- and
ablest -- form of life in this section of space, ?a critter that can
be killed but can't be tamed. ?--Robert A. Heinlein, "The Puppet Masters"
-
Information is more dangerous than cannon to a society ruled by lies. --James
M Dakin