Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!wuarchive!gem.mps.ohio-state.edu!ginosko!uunet!zephyr.ens.tek.com!tekcrl!tekgvs!keithe From: keithe@tekgvs.LABS.TEK.COM (Keith Ericson) Newsgroups: comp.binaries.ibm.pc.d Subject: Re: c.b.i.p troubles? Keywords: uudecode of latest postings Message-ID: <6001@tekgvs.LABS.TEK.COM> Date: 26 Sep 89 20:08:21 GMT References: <3458@cbnewsc.ATT.COM> Reply-To: keithe@tekgvs.LABS.TEK.COM (Keith Ericson) Distribution: na Organization: Tektronix, Inc., Beaverton, OR. Lines: 24 In article <3458@cbnewsc.ATT.COM> msc@cbnewsc.ATT.COM (michael.s.cross) writes: >Did anyone else have troubles uudecoding Rahul's latest postings? They >seem to check out OK with brik(1), but I get an 'Illegal Character' message >out of my PC based uudecode (Richard Mark's latest ... or was that Robert). >My UNIX(R) uudecode doesn't complain about it? Am I the only one? > My UNIX uudecode DID complain; I essentially sent the article through the following pipeline to extract the stuff: cat article | sed '/^[!-`]./s/[a-z]$//' | sed '/^END-/,/^BEGIN-/d'| uudecode And if you're wondering why the multiple "sed's" it's because the "sed ... | uudecode" already exists as an alias (and so does the first part, now). (Don't send mail about more efficient pipelines or sending it directly from rn, either, OK?) The uuencoded portion included lowercase alphabet characters, in descending order, tacked onto the end of each line. I guess a "correct" uudecode would simply determine the proper number of characters to include in the uudecoding and ignore the rest...? kEITHe