Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx013.isp.belgacom.be (inmx013.isp.belgacom.be [195.238.2.216])
        by mailst034.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id i91DL3Ga031729
        for <joris.at.lebbeke@skynet.be>; Fri, 1 Oct 2004 15:21:03 +0200
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx013.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id i91DKlp3015500
        for <joris.at.lebbeke@skynet.be>; Fri, 1 Oct 2004 15:20:48 +0200
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id 92D32343383; Fri,  1 Oct 2004 09:20:31 -0400 (EDT)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from arrow.wiznet.ca (arrow.wiznet.ca [216.138.223.232])
	by xserve.flids.com (Postfix) with ESMTP id 93297343360
	for <tiff@remotesensing.org>; Fri,  1 Oct 2004 09:20:30 -0400 (EDT)
Received: from pobox.com (H156.C195.tor.velocet.net [216.138.195.156])
	by arrow.wiznet.ca (Postfix) with ESMTP
	id 973F29EB1; Fri,  1 Oct 2004 09:20:29 -0400 (EDT)
Message-ID: <415D59BD.2000103@pobox.com>
Date: Fri, 01 Oct 2004 09:21:01 -0400
From: Frank Warmerdam <warmerdam@pobox.com>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040113
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Tiff mailing list <tiff@remotesensing.org>
Subject: Re: [Tiff] BigTIFF & PDF & tifftools
References: <000701c4a64c$79bde570$a805c950@dfgrrxsknr4e>	<415CFABB.29C87B9F@oce.nl>
	<000a01c4a784$0cbbc350$8159f051@dfgrrxsknr4e>
In-Reply-To: <000a01c4a784$0cbbc350$8159f051@dfgrrxsknr4e>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Cc: 
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
X-UIDL: 6db664535b72b5119501cfbb781b1f5d


 >Rob wrote:
>>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.
...
Joris wrote:
> 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.

Folks,

First, it will be Andrey who does the BigTIFF upgrade.  While I am very keen on
it, I am not really prepared to put in the time to ensure it is done right.

And yes, our intent is that we would have a single library that supports both.
There will certainly be some ABI changes to libtiff with the upgrade to BigTIFF
support, and there will presumably be some extra options available to control
whether BigTIFF or classic TIFF should be generated.  So I don't think it will
be completely a transparent upgrade for write purposes if you want to be able
to produce BigTIFF.

But reading BigTIFF or classic TIFF files should be transparent to the
application at the source level.  And I hopefully TIFF reading applications
that don't dig in too deep should not require any source changes either.

The ABI changes are likely to include stuff like toff_t and tsize_t becoming
64 bit types on platforms which support them.

As for Robs first question, I have no idea if PDF supports file sizes larger
than 4GB or if that would be supported by tiff2pdf.  I can't honestly imagine
wanting to produce such a large PDF file for some years to come.

Best regards,
-- 
---------------------------------------+--------------------------------------
I set the clouds in motion - turn up   | Frank Warmerdam, warmerdam@pobox.com
light and sound - activate the windows | http://pobox.com/~warmerdam
and watch the world go round - Rush    | Geospatial Programmer for Rent

_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff
