Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!swrinde!zaphod.mps.ohio-state.edu!rpi!joefritz From: joefritz@pawl.rpi.edu (Jochen M. Fritz) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: which archiver/compresser and encoder/decoder to use? Message-ID: <{#^#GY@rpi.edu> Date: 23 Feb 90 12:37:37 GMT References: <36517@iuvax.cs.indiana.edu> <7806@yunexus.UUCP> <36569@iuvax.cs.indiana.edu> <100118@looking.on.ca> <448@wjh12.harvard.edu> Organization: Rensselaer Polytechnic Institute, Troy NY Lines: 28 In article <448@wjh12.harvard.edu> djb@wjh12.UUCP (David J. Birnbaum) writes: >In article <100118@looking.on.ca> brad@looking.on.ca (Brad Templeton) writes: > >>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. > >Having been bitten by the ASCII<-->EBCDIC problem many times, I recently >surveyed 8-bit/7-bit encoding programs that could survive transmission >between Internet and Bitnet sites. These included ABE/DABE, ASCIFY, >UTIL3, and XXENCODE/XXDECODE. All produced 7-bit files that avoided the >problematic characters used by UUENCODE. > >ABE was the only program with a built-in ability to generate multipart >files; the other programs produced single large files that had to be The uuencode/decode I have (V3.07 by Richard Marks, PC) will fragment files automatically, and even automatically put them pack together. This is done such that if a file has a number in it, it will try to load an idectical file with the next number. EX: you tell it to decode part1.uue; after it finished, it attempts to decode part2.uue, and so on. I believe that I got it from either Simtel20 or Grape. -- ------------------------------------------------------------------------ | Jochen Fritz | For though we live in the world, we do not | | joefritz@pawl.rpi.edu | wage war as the world does.-- 2 Cor. 10:3 | | usergk2s@rpitsmts.bitnet| You have heard it said, Love your neighbor |