AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2007.01.31 10:53 "[Tiff] Interpreting SubIFDs tag", by mikk
2007.01.31 17:23 "Re: [Tiff] Interpreting SubIFDs tag", by Joris
2007.02.01 09:42 "Re: [Tiff] Interpreting SubIFDs tag", by Gerben Vos
2007.02.01 18:32 "Re: [Tiff] Interpreting SubIFDs tag", by Joris
2007.01.31 19:24 "Re: [Tiff] Interpreting SubIFDs tag", by Phil Harvey
2007.01.31 19:54 "Re: [Tiff] Interpreting SubIFDs tag", by Joris
2007.01.31 22:24 "RE: [Tiff] Interpreting SubIFDs tag", by Grissom, Ed
2007.02.01 18:17 "RE: [Tiff] Interpreting SubIFDs tag", by Phil Harvey
2007.02.01 18:34 "Re: [Tiff] Interpreting SubIFDs tag", by Joris
2007.02.01 18:48 "Re: [Tiff] Interpreting SubIFDs tag", by Phil Harvey
2007.02.01 19:00 "Re: [Tiff] Interpreting SubIFDs tag", by Joris
2007.02.01 19:36 "Re: [Tiff] Interpreting SubIFDs tag", by Phil Harvey
2007.02.01 20:02 "Re: [Tiff] Interpreting SubIFDs tag", by Joris
2007.02.01 15:46 "Re: [Tiff] Interpreting SubIFDs tag", by Phil Harvey

2007.02.01 09:42 "Re: [Tiff] Interpreting SubIFDs tag", by Gerben Vos

In fact, sometimes both are combined, and I've come accross files where the same second and third SubIFD gets pointed to in both ways.

It sounds like a bad idea to write such TIFFs. It's good that you have some reading code which deals with this in a smart way, but TIFF writers shouldn't expect readers in general to handle this. A TIFF copying program will typically duplicate the IFDs and image data that are pointed to multiple times, and this can grow rather fast as the number of paths to an IFD increases.

Gerben Vos.