Xref: utzoo alt.sources.d:672 comp.sources.d:5618
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!texbell!texsun!newstop!sun!sally!plocher
From: plocher@sally.Sun.COM (John Plocher)
Newsgroups: alt.sources.d,comp.sources.d
Subject: Re: Unnecessary tar-compress-uuencodes
Message-ID: <138944@sun.Eng.Sun.COM>
Date: 15 Jul 90 20:01:49 GMT
References: <15652@bfmny0.BFM.COM> <3114@psueea.UUCP> <1990Jul10.203015.27282@eci386.uucp> <5256@plains.UUCP> <3124@psueea.UUCP> <1990Jul13.161441.8339@druid.uucp>
Sender: news@sun.Eng.Sun.COM
Lines: 27

darcy@druid.uucp (D'Arcy J.M. Cain) writes:
>>9) Should we use trigraphs for some of the more troublesome ASCII characters?
>>   The extraction utility could convert them back into real characters.
>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:

	sed "s/???/}/" << EOF
	blah
	EOF

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.  In fact, sed based triglyph translators can corrupt
"correct" text like this:

	Remind:  Should this get fixed ???
...and...
	/* How many cards are there ??*/
...etc...

  -John