Return-Path: <tiff-admin@remotesensing.org>
Received: from inmx007.isp.belgacom.be (inmx007.isp.belgacom.be [195.238.3.89])
        by mailst006.isp.belgacom.be (8.12.9/8.12.9/Skynet-MAILSTORE-2.14) with ESMTP id i3MMOsgD023614
        for <joris.at.lebbeke@skynet.be>; Fri, 23 Apr 2004 00:24:54 +0200
        (envelope-from <tiff-admin@remotesensing.org>)
Received: from yoda.imagelinks.com ([208.24.120.44])
        by inmx007.isp.belgacom.be (8.12.9/8.12.9/Skynet-IN-2.32) with ESMTP id i3MMOoh8002360
        for <joris.at.lebbeke@skynet.be>; Fri, 23 Apr 2004 00:24:51 +0200
        (envelope-from <tiff-admin@remotesensing.org>)
Received: from yoda.imagelinks.com (localhost.localdomain [127.0.0.1])
	by yoda.imagelinks.com (8.11.6/8.11.6) with ESMTP id i3MMO9n05575;
	Thu, 22 Apr 2004 18:24:09 -0400
Received: from fuzzylog.simplesystems.org (fuzzylog.simplesystems.org [65.66.246.65])
	by yoda.imagelinks.com (8.11.6/8.11.6) with ESMTP id i3MMNqn05557
	for <tiff@remotesensing.org>; Thu, 22 Apr 2004 18:23:53 -0400
Received: from scooby.simplesystems.org (scooby.simplesystems.org [65.66.246.67])
	by fuzzylog.simplesystems.org (8.9.3/8.9.3) with ESMTP id RAA24488;
	Thu, 22 Apr 2004 17:23:33 -0500 (CDT)
From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
X-X-Sender: bfriesen@scooby.simplesystems.org
To: Chris Cox <ccox@adobe.com>
cc: Tiff mailing list <tiff@remotesensing.org>
Subject: Re: [Tiff] Large TIFF files
In-Reply-To: <p0521061cbcadf0a4cb7d@[153.32.48.223]>
Message-ID: <Pine.GSO.4.44.0404221718090.11901-100000@scooby.simplesystems.org>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: tiff-admin@remotesensing.org
Errors-To: tiff-admin@remotesensing.org
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.0.13
Precedence: bulk
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Post: <mailto:tiff@remotesensing.org>
List-Subscribe: <http://remotesensing.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
List-Id: TIFF and libtiff discussion <tiff.remotesensing.org>
List-Unsubscribe: <http://remotesensing.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://remotesensing.org/pipermail/tiff/>
Date: Thu, 22 Apr 2004 17:23:34 -0500 (CDT)
X-UIDL: 1f625cd7237bf762bc5a9e5c70052312

On Thu, 22 Apr 2004, Chris Cox wrote:

> >I agree with you on this.  While there there may be a desire to "fix"
> >and "improve" 64-bit TIFF over 32-bit TIFF, if the changes are not
> >restricted to the minimum required to support large file sizes, then
> >the updates to existing TIFF readers and writers will not be trivial,
> >and it becomes likely that 64-bit TIFF will fail.  If reading/writing
> >64-bit TIFF with existing source code is as trivial as updating some
> >typedefs, and ensuring that calculations don't overflow, then there is
> >a much higher probability that the new format will be generally
> >accepted.
>
> Or we can start with LibTIFF and create a new library for the new format.
> It doesn't have to be one library.
>
> Yes, there is some desire to fix old problems with TIFF in addition
> to extending the file length.

Right.  A libtiff64 could be created from libtiff.  If the TIFF fixes
can be hidden within libtiff64 then there shouldn't need to be much
change in dependent applications.  This approach at least assures that
open source applications, and proprietary applications which use
libtiff, can quickly incorporate TIFF64 support.

This doesn't help software which doesn't already use libtiff though.

If libtiff can be updated to support both classic TIFF and TIFF64 in
the same library, then dependent applications will gain TIFF64 support
for almost "free".

Bob
======================================
Bob Friesenhahn
bfriesen@simple.dallas.tx.us
http://www.simplesystems.org/users/bfriesen

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