Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!crdgw1!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!uwm.edu!linac!att!news.cs.indiana.edu!ariel.unm.edu!cs.umn.edu!thelake!steve From: steve@thelake.mn.org (Steve Yelvington) Newsgroups: comp.sys.atari.st Subject: Re: Is there a joiner for uuencoded file parts? Message-ID: Date: 30 May 91 19:08:20 GMT References: <1991May14.192458.19903@dvorak.amd.com> <1991May15.144538.24655@convex.com> <1991May30.035220.23253@watmath.waterloo.edu> Organization: St. Croix Valley rhubarb and tomato patch Lines: 33 X-UUCP-route: {rutgers,plains,decwrl}!umn-cs!thelake!steve [In article <1991May30.035220.23253@watmath.waterloo.edu>, ljdickey@watmath.waterloo.edu (L.J.Dickey) writes ... ] > In article ralph@laas.fr (Ralph P. Sobek) writes: >>Sorry, I do not understand this shell script. Don't all versions of >>Dumas' uud strip extraneous headers and trailers from uuencoded files? >>The problem arises with all the nonstandard decoders/encoders that >>exist. > > Ralph is right. > One does not need such a complicated script. UUD will ignore the > parts that it does not need. It jumps from the "include", past > the mail or news header, and straight to the next "begin" line. > A good command line might be like this: > > cat somebigf.u?? | uud > > > Silvert's adaptation of the Dumas' code is great. > Highly recommended. Bill's version works fine, but I also have an older UUD that chokes if there's too much junk between include and begin. Remember the GEM-based uuencoder/uudecoder that I mentioned I was working on? Somehow, in ripping the decoder out of WD.C, I managed to break that feature; my program now won't manage concatenated files that include lots of trash. As soon as I have the right combination of spare time and caffeine I should be able to get it fixed and post the program to comp.binaries and comp.souces. ---- Steve Yelvington, Marine on St. Croix, Minnesota, USA / steve@thelake.mn.org