Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.2 9/18/84; site uw-beaver
Path: utzoo!watmath!clyde!burl!ulysses!mhuxr!mhuxb!mhuxn!mhuxm!mhuxj!houxm!vax135!cornell!uw-beaver!info-mac
From: info-mac@uw-beaver
Newsgroups: fa.info-mac
Subject: Fix for broken .hcx files
Message-ID: <644@uw-beaver>
Date: Wed, 30-Jan-85 05:36:30 EST
Article-I.D.: uw-beave.644
Posted: Wed Jan 30 05:36:30 1985
Date-Received: Thu, 31-Jan-85 01:35:22 EST
Sender: daemon@uw-beaver
Organization: U of Washington Computer Science
Lines: 11

From: Gavin_Eadie%UMich-MTS.Mailnet@MIT-MULTICS.ARPA

Another aspect of .HCX files that catches computers out is the fact
that spaces are significant characters.  That was a mistake!  Our
system trims trailing spaces when copying material to a terminal by
default, causing no end of confusion when you use MacTerminal to
capture a .HCX file (KERMIT works fine of course because it was
designed to transfer files).  Before leaping on our system to accuse
it of foolishness remember that the copy operation was designed for
people who have no use for trailing blanks - copying one file to
another doesn't do this ...