AWARE SYSTEMS
TIFF and LibTiff Mail List Archive

Thread

2004.10.01 06:35 "[Tiff] BigTIFF & PDF & tifftools", by Rob van den Tillaart
2004.10.01 06:58 "Re: [Tiff] BigTIFF & PDF & tifftools", by Joris
2004.10.01 07:22 "[Tiff] BigTIFF extension issue", by Joris
2004.10.01 07:47 "Re: [Tiff] private tags:", by Joris
2004.10.01 13:21 "Re: [Tiff] BigTIFF & PDF & tifftools", by Frank Warmerdam
2004.10.01 13:49 "Re: [Tiff] quad-tile", by Joris
2004.10.01 11:17 "Re: [Tiff] BigTIFF & PDF & tifftools", by Leonard Rosenthol
2004.10.01 21:31 "Re: [Tiff] BigTIFF & PDF & tifftools", by Chris Cox
[...]

2004.10.01 06:58 "Re: [Tiff] BigTIFF & PDF & tifftools", by Joris

Rob,

Discussion was about tifftools, and if/when they would grow 'big' too.

Would these tools become bigtiff specific or would they handle bigtiff and classic tiff transparantly?

Linking them with both lib's could introduce namespace conflicts I guess.

Having separate tools for classic and big would give double code bases for every tool implying a serious synchronisation effort.

I feel it should be perfectly possible to have LibTiff handle the classic/big issue transparently. Thus, there should be no 'both libs', like e.g. is the case for LibJpeg when used to support both 8bit and 12bit per sample jpegs, and which indeed causes nothing but pain and duplication.

As far as I know, having LibTiff handle the classic/big issue transparently, is not just possible, but is also the way Frank intends to enhance LibTiff. It will enable to stick with a single copy of the tools and tools code. Tools will not need to grow big, neither will apps, they'll support BigTIFF by default simply by using the newer LibTiff.

Joris Van Damme
info@awaresystems.be
http://www.awaresystems.be

Download your free TIFF tag viewer for windows here: http://www.awaresystems.be/imaging/tiff/astifftagviewer.html