Path: utzoo!attcan!uunet!seismo!sundc!pitstop!sun!amdcad!ames!ncar!tank!nic.MR.NET!xanth!mcnc!thorin!unc!steele
From: steele@unc.cs.unc.edu (Oliver Steele)
Newsgroups: comp.sys.next
Subject: Re: A sample of Voice Mail!
Message-ID: <5284@thorin.cs.unc.edu>
Date: 12 Nov 88 21:44:14 GMT
References: <7329@orstcs.CS.ORST.EDU> <13401@oberon.USC.EDU>
Sender: news@thorin.cs.unc.edu
Reply-To: steele@unc.UUCP (Oliver Steele)
Organization: University Of North Carolina, Chapel Hill
Lines: 26

annala@neuro.usc.edu (A J Annala) writes:
>Voice mail looks like an excellent candidate for some data compression
>technique.  I used the simple minded BSD4.3 UNIX compress utility and
>achieved 30 % compression on the voice mail message attached to the
>above referenced article.

This is a little misleading.  Keep in mind that what was posted has been
expanded into ASCII (mail-able) characters, and you were comparing it
against a binary description.  Once I trimmed the header and the spaces
at the beginnings of lines, I got
	voice		47060
	voice.Z		32775	(30.4% savings)
	voice.uu	45177	( 6.0% savings)
for the original file, the compress-ed file, and the compress+uuencode-ed
one, which is hardly as dramatic.

In fact, I would guess that the file has already been compressed.  Can
anyone say?  Does NExt voice-mail follow RFCs 741 and/or 978 (to which I
don't have access right now, else I might could figure out)?

 ---------------------------------------------------------------------------
 Oliver Steele					  ...!decnet!mcnc!unc!steele
 UNC-CH							   steele@cs.unc.edu

 "It may not be the easy way --
  but it's the cowboy way!"		- Riders in the Sky