AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2012.02.10 11:12 "[Tiff] Versioning and Forks of LibTiff", by Simon Ochsenreither
2012.02.10 15:15 "Re: [Tiff] Versioning and Forks of LibTiff", by Bob Friesenhahn
2012.02.10 16:44 "Re: [Tiff] Versioning and Forks of LibTiff", by Simon Ochsenreither
2012.02.10 17:16 "Re: [Tiff] Versioning and Forks of LibTiff", by John
2012.02.10 17:16 "Re: [Tiff] Versioning and Forks of LibTiff", by Olivier Paquet
2012.02.10 17:18 "Re: [Tiff] Versioning and Forks of LibTiff", by Bob Friesenhahn

2012.02.10 16:44 "Re: [Tiff] Versioning and Forks of LibTiff", by Simon Ochsenreither

Hi Bob,

The page you reference at Aperio seems pretty clear. Aperio libtiff forked from libtiff in 2007, starting with libtiff 3.8.2 code. The code is obviously not the "same" although Aperio libtiff is free to pick up any improvements from libtiff.

Sorry. I didn't intend to ask "stupid" questions, it was just the common release dates which made me assume that there might be collaboration going on between those two projects.

It is certainly possible that using Aperio libtiff will help when reading TIFF files written by Aperio libtiff.

If there is some issue with Aperio libtiff then you should report it to the developers of Aperio libtiff.

Yes of course, I'm not trying to get support for the Aperio stuff here.

I asked the question because I was more or less wondering if anyone knows obstacles which would prevent writing the images with the "real" LibTiff instead of the one from Aperio.

If not, I would suggets to the image creators to use the "real" LibTiff instead of the one from Aperio and hope it fixes the problem.

The only "fancy" thing required is BigTiff support and that seems to be fully supported with LibTiff 4.0.

What do you think?

Thanks and bye!

Simon