Xref: utzoo alt.comp.compression:165 comp.compression:32
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!sdd.hp.com!spool.mu.edu!uunet!mcsun!hp4nl!charon!dik
From: dik@cwi.nl (Dik T. Winter)
Newsgroups: alt.comp.compression,comp.compression
Subject: Re: Trying to get maximum compression
Message-ID: <3212@charon.cwi.nl>
Date: 25 Mar 91 00:14:48 GMT
Article-I.D.: charon.3212
References: <1991Mar24.152106.6333@pegasus.com> <a+5fs#b@rpi.edu>
Sender: news@cwi.nl
Followup-To: alt.comp.compression
Organization: CWI, Amsterdam
Lines: 23


 > shaw@pegasus.com (Sandy Shaw) writes:
 > 
 > >I am trying to get the maximum compression possible of the following
 > >32 byte hex file(in ASC): 
 > 
 > >f3e9 ec5c 8bec ecdb ece9 ec12 ec3f ecec
 > >0cbb 8bec 5cdb ecdb 5c9c bbec 8bdb 9cec
 > 
 > >The best results I get are using the compact utility(adaptive Huffman). This
 > >gives 21.88% compression or 7 bytes saved. Does anyone out there have a 
 > >scheme that can improve on this? 
 >   Well, if it is a HEX file, why don't you try to compress it by taking two
 > bytes and putting them into one byte (range 0-255)?
But even if those are just 32 bytes, you can compress it to zero bytes with a
general compression/decompression program (specialized for this case of course).
(E.g. if the compressed file is empty the original were those 32 bytes; if
the (only) byte is 0, the original was empty, otherwise it is output from
compress.  This expands slightly on empty files of course.)
But I do not think that was the intention.  So what is the real problem?
--
dik t. winter, cwi, amsterdam, nederland
dik@cwi.nl