2012.02.10 17:18 "Re: [Tiff] Versioning and Forks of LibTiff", by Bob Friesenhahn

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.

I am not aware of any collaboration (or emnity either) by libtiff maintainers with the developers of Aperio libtiff. If there has been significant interoperability testing between the two libtiffs, I am not aware of it.

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.

As far as we are aware, "real" libtiff is working.

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.

Yes, BigTiff is fully supported with libtiff 4.0.

What do you think?

Obviously, we are biased, but most of the world is using "real" libtiff and it is (or will soon be) widely deployed so it makes sense to use it if it works.

Bob
--
Bob Friesenhahn
bfriesen@simple.dallas.tx.us, http://www.simplesystems.org/users/bfriesen/
GraphicsMagick Maintainer, http://www.GraphicsMagick.org/