Path: utzoo!utgpu!jarvis.csri.toronto.edu!rutgers!usc!srhqla!quad1!ttidca!svirsky From: svirsky@ttidca.TTI.COM (Bill Svirsky) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: UUDECODE 3.15 Message-ID: <6496@ttidca.TTI.COM> Date: 29 Sep 89 00:40:14 GMT References: <716@bbking.KSP.Unisys.COM> Reply-To: svirsky@ttidcc.tti.com (Bill Svirsky) Organization: Citicorp/TTI, Santa Monica Lines: 20 In article <716@bbking.KSP.Unisys.COM> rmarks@KSP.Unisys.COM (Richard Marks) writes: +The idea behind UUENCODing is to get data over a minimal +communications line. Such minimal lines may change lower +to upper case, squish down multiple blanks, and do other +horrible things to data. When UUDECODE 3.07 sees the lower +case, it assumes the file is corrupt and quits. Whatever happened to the UUENCODE program that would place a table of the characters used for encoding in front of the 'begin' line. The corresponding UUDECODE would then check this table before decoding to see if any of the characters had been changed. If any had, it would alter its decoding strategy to utilize the new characters. The beauty of it was, that since the table was placed before the 'begin' line, it was completely compatible with older versions of UUDECODE which would just ignore it. -- Bill Svirsky, Citicorp+TTI, 3100 Ocean Park Blvd., Santa Monica, CA 90405 Work phone: 213-450-9111 x2597 svirsky@ttidca.tti.com | ...!{csun,psivax,rdlvax,retix}!ttidca!svirsky