Path: utzoo!censor!geac!torsqnt!news-server.csri.toronto.edu!cs.utexas.edu!uunet!bfmny0!tneff
From: tneff@bfmny0.BFM.COM (Tom Neff)
Newsgroups: comp.sources.d
Subject: Re: Laser Jet to Postscript posting (disaster)
Message-ID: <15638@bfmny0.BFM.COM>
Date: 6 Jul 90 10:25:50 GMT
References: <1153@syteke.be> <1990Jul5.143004.27885@uwslh.slh.wisc.edu>
Reply-To: tneff@bfmny0.BFM.COM (Tom Neff)
Lines: 19

In article <1990Jul5.143004.27885@uwslh.slh.wisc.edu> lishka@uwslh.slh.wisc.edu (Chris Lishka (King Arthur's roommate) ) writes:
>@#*)(@*#)!  You are right, I should have uuencoded the whole thing.
>As far as I know, the actual *source*code* does not have any control
>characters in it, so that should be fine.  However, the test and
>metrics suite do, so they are completely useless.

Please uuencode ONLY the files that need it, and leave the source code
in plain text.  The standard Usenet source groups should not be used for
thousands of lines of unreadable stuff!!  There have been a couple of
examples of this in the past month, and I'm afraid it's going to
snowball.  Readers should be able to CASUALLY and DIRECTLY inspect
source postings with the ordinary newsreader, to see if they're
interested before installing everything.  Shell archives (shars) are
perfect for this.  People are starting to post *vanilla text files* as
uuencoded compressed TARs.  Very Bad!

-- 
"Take off your engineering hat   = "The filter has      | Tom Neff
and put on your management hat." = discreting sources." | tneff@bfmny0.BFM.COM