Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!decwrl!labrea!rutgers!ho95e!homxb!mtuxo!mtune!codas!burl!clyde!mcdchg!heiby
From: heiby@mcdchg.UUCP (Ron Heiby)
Newsgroups: news.misc
Subject: Re: Expansion after compression for MS-DOS arc files
Message-ID: <2255@mcdchg.UUCP>
Date: Tue, 3-Nov-87 13:14:07 EST
Article-I.D.: mcdchg.2255
Posted: Tue Nov  3 13:14:07 1987
Date-Received: Sat, 7-Nov-87 09:43:53 EST
References: <3346@uwmcsd1.UUCP>
Reply-To: heiby@mcdchg.UUCP (Ron Heiby)
Distribution: all
Organization: Motorola Microcomputer, Schaumburg, IL
Lines: 20

Christopher N Maag (cmaag@csd4.milw.wisc.edu.UUCP) writes:
> "If you submit a file to one of the newsgroups and you wish to uuencode
>  the file, _do not_ perform any type of file compression to this
>  file before uuencoding it.  This means don't arc the file, (insert
>  other popular compression schemes for other computer systems here).
>  If you do compress the file, it will actually get _larger_ when it is
>  sent than it was originally.  This costs us all money."

I think Chris is going further than I suggested.  I have no evidence that
the problem is compressing before uuencoding, and I suspect that it has
little to do with it.  I was talking about the difference between sending
clear text and sending compressed/uuencoded text.  I think it would be
interesting to check on what Chris is suggesting and get some numbers on
the difference between sending uuencoded binary files vs uuencoded compressed
binary files.  I suspect that a uuencoded compressed binary file would
actually be smaller, but the further impact of the news software's compress
on the resulting files is unknown.
-- 
Ron Heiby, heiby@mcdchg.UUCP	Moderator: comp.newprod & comp.unix
"I know engineers.  They love to change things."  McCoy