Xref: utzoo comp.sources.d:2119 comp.binaries.ibm.pc.d:252
Path: utzoo!attcan!uunet!husc6!think!bloom-beacon!mit-eddie!rutgers!iuvax!bsu-cs!dhesi
From: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Newsgroups: comp.sources.d,comp.binaries.ibm.pc.d
Subject: Re: Standard for file transmission
Summary: terminology
Message-ID: <3075@bsu-cs.UUCP>
Date: 16 May 88 19:52:55 GMT
References: <292@cullsj.UUCP> <696@fig.bbn.com> <2932@cognos.UUCP> <3055@encore.UUCP> <4776@teddy.UUCP>
Reply-To: dhesi@bsu-cs.UUCP (Rahul Dhesi)
Organization: CS Dept, Ball St U, Muncie, Indiana
Lines: 24

To avoid ambiguity, I suggest the following terminology.

     B = binary
     T = text
     U = uuencoding
     C16 = 16-bit LZW ("compress" default)
     C12 = 12-bit LZW (arc)
     C13 = 13-bit LZW (zoo, squashing)

So, instead of claiming that "uuencoded binary files compressed are
larger than not uuencoding" it is better to say that "BC12UC16 is worse
than BC16", or "BUC16U is worse than BC16" etc.

     BC12UC16 means:
       (B)   take a binary file
       (C12) compress using arc or 12-bit "compress"
       (U)   uuencode it
       (C16) compress using 16-bit "compress"

Also, since binary files differ, it's good to use some standard binary
file in benchmarks, e.g. your UNIX kernel stripped of symbols, so there
is some degree of consistency.
-- 
Rahul Dhesi         UUCP:  <backbones>!{iuvax,pur-ee,uunet}!bsu-cs!dhesi