Path: utzoo!attcan!uunet!lll-winken!lll-ncis!helios.ee.lbl.gov!pasteur!ucbvax!UCONNVM.BITNET!SEWALL
From: SEWALL@UCONNVM.BITNET (Murph Sewall)
Newsgroups: comp.sys.apple
Subject: RE: Re:  Problems Unpacking Kermit 3.84
Message-ID: <8901121629.aa17661@SMOKE.BRL.MIL>
Date: 12 Jan 89 21:14:57 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The Internet
Lines: 30

>This is an addendum to my earlier comments on unpacking KERMIT 3.84/3.85, and
>on Murph Sewall's reply.  Apple does not store line feeds after carriage
>returns
>in its text files, but it doesn't remove them if they are already there either!
The point is, because the LF's are NOT standard for Apple text files, the ONLY
way they get there is if they are IMPORTED from somewhere else (usually
by XModem or ASCII capture).

If you can get rid of them with TEX on the VAX, do so.  You'll only have to
do that ONCE (to create a working Kermit-65).  UNLIKE XModem, Kermit KNOWS
that most of the World uses CR-LF while Apple uses only CR :-).  Actually,
the Kermit on EACH END knows what the appropriate text format is for the
system it's on (one of the reasons for differentiating between 'text' and
'binary' file transfers).  If you download with Kermit, it will make the
LF's go away AND set the 8th bit correctly for the operating system it's
running under.

XModem is strictly "what you see is what you get" while Kermit is transparent
only for 'binary' file transfers.

Murph Sewall                       Vaporware? ---> [Gary Larson returns 1/1/90]
Prof. of Marketing     Sewall@UConnVM.BITNET
Business School        sewall%uconnvm.bitnet@mitvma.mit.edu          [INTERNET]
U of Connecticut       {psuvax1 or mcvax }!UCONNVM.BITNET!SEWALL     [UUCP]

-+- I don't speak for my employer, though I frequently wish that I could
            (subject to change without notice; void where prohibited)

According to the American Facsimile Association, more than half the calls
from Japan to the U.S. are fax calls.  FAX it to me at: 1-203-486-5246