Path: utzoo!attcan!uunet!nems!mimsy!haven!aplcen!uakari.primate.wisc.edu!zaphod.mps.ohio-state.edu!uwm.edu!cs.utexas.edu!milano!uudell!texbell!texsun!newstop!sun!coherent!next!aozer
From: aozer@next.com (Ali Ozer)
Newsgroups: comp.sys.next
Subject: Re: Unsupported TIFF question
Message-ID: <181@next.com>
Date: 8 Jun 90 00:55:17 GMT
References: <9865@lindy.Stanford.EDU>
Reply-To: Ali_Ozer@NeXT.com (Ali Ozer)
Organization: NeXT, Inc.
Lines: 19

In article <9865@lindy.Stanford.EDU> Buc Richards writes:
>Many of the TIFF files stored on the NeXT library, particularly those
>in the Webster Dictionary pictures file, appear to have a non-standard
>TIFF format.  In particular, the Compression tag field has the value
>32766 (7ffe hex), although the only legal values listed in the
>Version 5.0 TIFF description are 1, 2, 5, and 32773. ...
>Can I get a description of this TIFF extension and the associated
>compression scheme?

You're right --- Those files are compressed with a non-standard 
compression scheme...  If you wish to be able to make just several
of those into standard TIFFs, go ahead and screen capture them with Icon,
which will then save them using no compression.  If you really want to be
able to read a lot of them, then I recommend getting a hold of Sam
Leffler's wonderful TIFF library and using his "tiffcp" to fix up those
files.  Version 2.2 of the library is available from ucbvax.berkeley.edu.
It compiles and runs on the NeXT just fine.

Ali (Ali_Ozer@NeXT.com)