adjones@mcnc.org (Amy D. Jones) (08/31/89)
Hello... I just bought an NEC-P5200 & am a bit confused over its behavior. Every- thing that I print out to prt: is double-spaced when it should be single- spaced. This does not happen when I type files to PAR: instead. I'm using the NEC-Pinwriter driver from the 1.3 Extras disk, and all the printer settings are as the factory set them. I tried playing around with Preferences a bit, but had no improvement. Does anyone have any advice? Thanks................................ | //| ' _ | Amy D. Jones | | //-|///|<//| | Route 4, Box 411 | | \X/ //-|///|// | Chapel Hill, NC 27516 | | \X/ // | | | \X/ | adjones@mcnc.org |
mcp@ziebmef.mef.org (Marc Plumb) (09/06/89)
> [Printing to prt: double-spaces; par: doesn't. Help!]
This is the classic symptom of the CR/LF confusion. When ASCII was
defined in 1966, it was an "Information Interchyange" code, not
really designed to be an internal standard (as it is universally today,
except for some older machines and IBM Hulking Giants), and a few odd
choices were made, particularly in the prolixity of control codes
offered. The commitee wanted separate codes for horizontal and
vertical cursor motion and thus came up with CR (to move the print head
to the left margin - no CRT's in those days!) and LF (to move the
print head down a line, or the paper up one, whatever). So
printers were designed to do this, and all was well until all the
8-bit computers (Apple, PET, Atari, TRS-80 etc.) decided that two
characters to say "new line" was stupid, so they started using just CR.
(The ASCII standard encouraged the use of LF, to be called NL, for a
single line terminator, since it would leave CR LF doing The Right Thing.
Unix and Amy follow this standard.)
Printers then added a DIP switch to decide whether CR included a line feed
or not, and many factory defaults became "yes." Of course, if you had
slightly smarter software that followed the ASCII standard, it would
send "CR LF" and get two line feeds (one implicit in the CR, one
explicit in the LF) for the price of one, causing double-spacing
bugs as you're seeing. On your Amiga, prt: is ther smarter software
and par: is the dumb copy-bytes stuff, and you're getting pretty much
that problem.
The solution is either to tell preferences that your printer auto-line-feeds
on CR, or set the printer not to auto-line-feed. The latter is slightly
preferable, as it gives a bit more flexibility, but either will solve
your problem.
Hope this helps, and the meat didn't get lost in the history.
--
-Colin Plumb