Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!swrinde!cs.utexas.edu!uunet!rosie!aozer
From: aozer@next.com (Ali Ozer)
Newsgroups: comp.sys.next
Subject: Re: TIFF's under 2.0
Message-ID: <914@rosie.NeXT.COM>
Date: 7 Jun 91 18:13:59 GMT
References: <1638@toaster.SFSU.EDU> <1991Jun6.002304.1187@petunia.CalPoly.EDU> <909@rosie.NeXT.COM>
Sender: news@NeXT.COM
Distribution: usa
Organization: Next Computer, Inc.
Lines: 23
Nntp-Posting-Host: twinpeaks.next.com

In article <909@rosie.NeXT.COM> aozer@next.com (Ali Ozer) writes:
>In article <1991Jun6.002304.1187@petunia.CalPoly.EDU> Alex Raftis writes:
>>TIFF Error: Wrong data type 3 for field "SubfileType".
>>Error #1: Bad Image Format
>The SubfileType field is an obsolete TIFF field which is supposed to
>have one short value. Well, judging from the error message above, your
>file does seem to have the correct type (type 3 is short). Looks like
>there is a bug in NextStep's interpretation of the SubfileType field.

Well, turns out I'm wrong; the bug isn't in the TIFF library but in the 
TIFFs themselves. (Thanks to Sam Leffler for pointing this out...)

I was confused by the error message: The NextStep TIFF library (which is 
based on Sam's TIFF library) refers to the obsolete SubfileType field 
as "OldSubfileType" and refers to the new one as "SubfileType." Thus it seems 
like the TIFF file in question has the new field, but with a short 
value.  The spec says that this field should have a long value, so in 
this case the TIFFs seem to be bad.  

Thus it might be more difficult than I thought to find a program which
can actually read them in.

Ali, Ali_Ozer@NeXT.com