Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!samsung!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!cica!iuvax!maytag!looking!brad
From: brad@looking.on.ca (Brad Templeton)
Newsgroups: comp.binaries.ibm.pc.d
Subject: Re: which archiver/compresser and encoder/decoder to use?
Message-ID: <100118@looking.on.ca>
Date: 22 Feb 90 00:37:02 GMT
References: <36517@iuvax.cs.indiana.edu> <7806@yunexus.UUCP> <36569@iuvax.cs.indiana.edu>
Organization: Looking Glass Software Ltd.
Lines: 8
Class: discussion

If the encoder is going to be changed, a switch to xxencode seems pointless.
All it fixes is the use of some characters that ebcdic translations munge.

Even if the chosen encoder is not to be ABE, it should at least be something
a bit fancier than xxencode, with some support for multi-part encodings without
requring unpacking or hand editing.
-- 
Brad Templeton, ClariNet Communications Corp. -- Waterloo, Ontario 519/884-7473