Return-Path: owner-tiff@olympiakos.com
Return-Path: <owner-tiff@olympiakos.com>
Received: from localhost (localhost [127.0.0.1])
	by at1895.spb.edu (8.12.3/8.12.3/Debian-9) with ESMTP id g4P4QRb0026128
	for <dron@localhost>; Sat, 25 May 2002 08:26:27 +0400
Received: from eudoramail.com [209.185.123.45]
	by localhost with POP3 (fetchmail-5.9.0)
	for dron@localhost (single-drop); Sat, 25 May 2002 08:26:27 +0400 (MSD)
Received: from gate7.olympiakos.com ([64.32.199.150]) by shared1-mail.whowhere.com; Fri May 24 19:42:50 2002
Received: from localhost (daemon@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) with SMTP id WAA19723;
	Fri, 24 May 2002 22:27:33 -0400
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Fri, 24 May 2002 22:25:05 -0400
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) id WAA19698
	for tiff-outgoing; Fri, 24 May 2002 22:25:05 -0400
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from sys2.ippsoftware.com (leg-64-133-206-114-FTW.sprinthome.com [64.133.206.114])
	by gate7.olympiakos.com (8.9.3/8.9.3) with ESMTP id WAA19695
	for <tiff@olympiakos.com>; Fri, 24 May 2002 22:25:00 -0400
Received: from ippsoftware.com (Scotty [192.168.2.1])
	by sys2.ippsoftware.com (8.10.2/8.10.2) with ESMTP id g4P2OpO00985;
	Fri, 24 May 2002 21:24:51 -0500
Message-ID: <3CEEF65B.5AD845E2@ippsoftware.com>
Date: Fri, 24 May 2002 21:26:35 -0500
From: Scott Weber <scott@ippsoftware.com>
Reply-To: scott@ippsoftware.com
Organization: IPP
X-Mailer: Mozilla 4.73 [en] (WinNT; I)
X-Accept-Language: en
MIME-Version: 1.0
To: "Bostrup, Tore" <TBostrup@teamia.com>
CC: "'tiff@olympiakos.com'" <tiff@olympiakos.com>, davidp@pdainc.com
Subject: Re: How multipage is stored
References: <A49C73B04A70D211B75E00805FAD949C79C20C@TIANT01>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-tiff@olympiakos.com
Precedence: bulk
Status: RO
Content-Length: 3136
Lines: 87

Doh!!  Found it. Thanks.

However, both original images have an FE (NewFileSubType) of:
FE 00 04 00 01 00 00 00 00 00 00 00

And, as a result, the new combined image has this same entry
in both IFD's

Spec says:
bit 0- image is a reduced resolution version of another image in 
 this file
bit 1- Image is a single page in a multipage file 
  (Isn't this what I created? )
bit 2- Image defines a transparency for another image

Shouldn't either bit 0 ot 1 be set?  Should I do it myself?

-Scott

"Bostrup, Tore" wrote:
> 
> ...And if I'm not mistaken, each subsequent IFD represents another page if
> the NewSubfileType tag (254 or FE) has a value of 2.  The first IFD is
> always a full-resolution image, i.e. the first page.
> 
> HTH,
> Tore.
> 
> -----Original Message-----
> From: David Phillips [mailto:davidp@pdainc.com]
> Sent: Friday, May 24, 2002 3:31 PM
> To: 'scott@ippsoftware.com'; Tiff
> Subject: RE: How multipage is stored
> 
> Look at the offset to the next IFD.  This is the pointer to the next IFD.
> If it is zero there are no more images.
> 
> HTH,
> Dave
> 
> -----Original Message-----
> From: Scott Weber [mailto:scott@ippsoftware.com]
> Sent: Friday, May 24, 2002 2:22 PM
> To: Tiff
> Subject: How multipage is stored
> 
> Ok, I've read the spec, and been playing with many pieces.
> 
> We have a need to combine multiple pages into a single file.
> tiffcp does that, so I'm studying the code.  I built a multipage
> tif from individuals, and it's fine.
> I then tried to dissect it with the spec, and can't figure out
> one thing.  How does it know there's a second page?
> 
> There is a directory entry FE which is supposed to indicate
> multipage, but all it's value bits are set to zero.
> 
> It moved the directory (which people call IFD?) to a block after
> the data strip (that's fine because the header points there).
> 
> I found the second directory  after the second data strip, again,
> that's fine.  The second dir has pointer to the data, width values,
> height, etc.  I understand all of it. But I can't see anywhere
> in the way the file is built that links the first page to the second.
> 
> It seems to me when the first page is read, it would think that
> that's all there is.
> As I hand walk through the file, I go through the directory, come to
> the end of the first dir, read the strip, and that's it.
> How would a program know that there is a second page after the
> first one?
> 
> Any help is appreciated!
> -Scott Weber
> scott@ippsoftware.com
> 
> To subscribe or unsubscribe email tiff-request@olympiakos.com with subscribe
> or unsubscribe in the email body.  Libtiff home page: http://www.libtiff.org
> 
> To subscribe or unsubscribe email tiff-request@olympiakos.com with subscribe
> or unsubscribe in the email body.  Libtiff home page: http://www.libtiff.org
> 
> To subscribe or unsubscribe email tiff-request@olympiakos.com with subscribe
> or unsubscribe in the email body.  Libtiff home page: http://www.libtiff.org

To subscribe or unsubscribe email tiff-request@olympiakos.com with subscribe
or unsubscribe in the email body.  Libtiff home page: http://www.libtiff.org

