Path: utzoo!attcan!uunet!tut.cis.ohio-state.edu!cs.utexas.edu!sun-barr!ziploc!eps
From: eps@toaster.SFSU.EDU (Eric P. Scott)
Newsgroups: comp.sys.next
Subject: Re: Unsupported TIFF question
Message-ID: <689@toaster.SFSU.EDU>
Date: 7 Jun 90 21:52:17 GMT
References: <9865@lindy.Stanford.EDU> <12181@june.cs.washington.edu>
Reply-To: eps@cs.SFSU.EDU (Eric P. Scott)
Organization: San Francisco State University
Lines: 26

In article <12181@june.cs.washington.edu>
	wjs@last.cac.washington.edu (William Shipley) writes:
>giant@lindy.Stanford.EDU (Buc Richards) writes:
>>Can I get a description of this TIFF extension and the associated
>>compression scheme?
>
>Probably not.

BZZZ!  WRONG!

>               Imagine that you were Webster, and NeXT asked you if they
>could take all your pictures and digitize them.  What would you say?
>"Sure, but encode them so they aren't any good on any other machine."
>
>Note: This is my guess, but it's an educated guess.  I've seen this question
>asked before, and I've never seen it answered.

You must not have been paying attention a few months back.  In
any case, version 2.2 of Sam Leffler's tiff package was released
about 3 days ago, so you'll probably want to grab it even if you
had one of the earlier versions.

FTP ucbvax.berkeley.edu:pub/tiff/v2.2.tar.Z and extract
libtiff/tif_next.c--the encoding turns out to be quite
simple.
					-=EPS=-