Path: utzoo!yunexus!geac!syntron!jtsv16!uunet!ncrlnk!ncr-sd!hp-sdd!hplabs!ucbvax!agate!garnet.berkeley.edu!ked
From: ked@garnet.berkeley.edu (Earl H. Kinmonth)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: zoo 2.01 part 1/3 - received corrupted
Message-ID: <14680@agate.BERKELEY.EDU>
Date: 25 Sep 88 03:44:59 GMT
Article-I.D.: agate.14680
References: <6618@dasys1.UUCP>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 17

In article <6618@dasys1.UUCP> wfp@dasys1.UUCP (William Phillips) writes:
>
>It appears we received a corrupted copy of zoo201.exe - it contains a

People continue to use old versions of uuencode that produce
spaces at the ends of lines or even blocks of largely blank
lines.  Using a sed script such as

sed -e 's/ /z/g'

to code the file (z is not in the uuencode character set) and

sed -e s/z/ /g'

to clean it up would prevent much of this sort of thing.  (Of
course, a better version of uuencode would be an even happier
solution.)