Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!husc6!cmcl2!adm!smoke!gwyn
From: gwyn@smoke.BRL.MIL (Doug Gwyn)
Newsgroups: comp.sys.apple
Subject: Re: Stripper (LF's=>CR's)
Message-ID: <10182@smoke.BRL.MIL>
Date: 1 May 89 04:41:44 GMT
References: <8904271836.AA01810@crash.cts.com> <17720@cup.portal.com>
Reply-To: gwyn@brl.arpa (Doug Gwyn)
Organization: Ballistic Research Lab (BRL), APG, MD.
Lines: 19

In article <17720@cup.portal.com> Sirald@cup.portal.com (Andrew Lionel Dalrymple) writes:
>UNIX sends the LF instead of CR, that part is true. ...
>UNIX uses POSITIVE-ASCII that is, the high-order bit is set.

Both false.  UNIX text files as stored conventionally use the new-line
(LF) character as a line delimiter, and are in 7-bit ASCII in most non
IBM-mainframe implementations, with the high bit of each character 0.
But what is transmitted down a terminal line is configurable in a number
of ways, including mapping line delimiters to CR and/or LF and parity.
What you actually see on the Apple end of the serial link entirely
depends on the procedure that is used to perform the download.

>APPLE DOS uses NEGATIVE-ASCII, high-order bit off.

Wrong again, for DOS 3.3.  And again what actually happens depends on
the procedure you're using to perform the download.

I don't normally have any trouble at all, using XMODEM protocols
with suitable communications software running at both ends of the link.