Xref: utzoo alt.sources.d:679 comp.sources.d:5631
Newsgroups: alt.sources.d,comp.sources.d
Path: utzoo!telly!robohack!woods
From: woods@robohack.UUCP (Greg A. Woods)
Subject: Re: Unnecessary tar-compress-uuencodes
Organization: R. H. Lathwell Associates:  Elegant Communications, Inc.
Date: Tue, 17 Jul 90 07:01:46 GMT
Message-ID: <1990Jul17.070146.18115@robohack.UUCP>
References: <15652@bfmny0.BFM.COM> <3114@psueea.UUCP> <1990Jul10.203015.27282@eci386.uucp> <5256@plains.UUCP> <3124@psueea.UUCP> <1990Jul13.161441.8339@druid.uucp> <138944@sun.Eng.Sun.COM>
Lines: 26

In article <138944@sun.Eng.Sun.COM> plocher@sally.Sun.COM (John Plocher) writes:
> darcy@druid.uucp (D'Arcy J.M. Cain) writes:
> >Again shar can be banged on a little to handle this.  Simply change the
> >sed command that it generates to translate trigraphs to the proper character.
> >Then shar can convert all troublesome characters and it will be converted back
> >when the script is run.
> 
> Ok, so I generate a new-shar archive that looks like this:
>[blahhh....] 
> And I send it thru a machine that munges the '}' character.
> The orig file won't extract correctly now, even with this
> "smart" sed script tacked on, because now the sed script itself
> is broken.

But at least you only have to fix one [set of] line(s) which you know
all about, instead of a million possible unknown points in a source
file which got munged.

Too bad about the "extra" trigraph in the source.  Perhaps shar could
check for these, and certainly the sender could pack and unpack before
sending to validate the correctness.
-- 
						Greg A. Woods

woods@{robohack,gate,eci386,tmsoft,ontmoh}.UUCP
+1 416 443-1734 [h]   +1 416 595-5425 [w]   VE3-TCP   Toronto, Ontario; CANADA