Return-Path: <tiff-admin@remotesensing.org>
Received: from inmx010.isp.belgacom.be (inmx010.isp.belgacom.be [195.238.2.73])
        by mailst006.isp.belgacom.be (8.12.9/8.12.9/Skynet-MAILSTORE-2.14) with ESMTP id i3F4kCJG000861
        for <joris.at.lebbeke@skynet.be>; Thu, 15 Apr 2004 06:46:12 +0200
        (envelope-from <tiff-admin@remotesensing.org>)
Received: from yoda.imagelinks.com ([208.24.120.44])
        by inmx010.isp.belgacom.be (8.12.9/8.12.9/Skynet-IN-2.32) with ESMTP id i3F4k1A0006084
        for <joris.at.lebbeke@skynet.be>; Thu, 15 Apr 2004 06:46:03 +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 i3F4j7n19978;
	Thu, 15 Apr 2004 00:45:07 -0400
Received: from smtp-relay-7.sea.adobe.com (smtp-relay-7.adobe.com [192.150.22.7])
	by yoda.imagelinks.com (8.11.6/8.11.6) with ESMTP id i3F4ikn19954
	for <tiff@remotesensing.org>; Thu, 15 Apr 2004 00:44:46 -0400
Received: from inner-relay-3.corp.adobe.com (inner-relay-3 [153.32.251.51])
	by smtp-relay-7.sea.adobe.com (8.12.10/8.12.10) with ESMTP id i3F4iVSP009611
	for <tiff@remotesensing.org>; Wed, 14 Apr 2004 21:44:32 -0700 (PDT)
Received: from calsj-dev (calsj-dev.corp.adobe.com [153.32.1.193])
	by inner-relay-3.corp.adobe.com (8.12.9/8.12.9) with ESMTP id i3F4iIkq026969
	for <tiff@remotesensing.org>; Wed, 14 Apr 2004 21:44:28 -0700 (PDT)
Received: from [153.32.48.223] (noname.corp.adobe.com [153.32.48.223])
 by mailsj-v1.corp.adobe.com
 (iPlanet Messaging Server 5.2 HotFix 1.21 (built Sep  8 2003))
 with ESMTP id <0HW7000IH3TTJF@mailsj-v1.corp.adobe.com> for
 tiff@remotesensing.org; Wed, 14 Apr 2004 21:44:18 -0700 (PDT)
From: Chris Cox <ccox@adobe.com>
Subject: Re: [Tiff] Large TIFF files
In-reply-to: <E1BDwRk-0007wz-00@rom.localdomain>
X-Sender: ccox@mailsj.corp.adobe.com
To: tiff@remotesensing.org
Message-id: <p05210600bca3c295fbd6@[153.32.48.223]>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <E1BDui3-0007qF-00@rom.localdomain> <407DEC23.2010300@pobox.com>
 <E1BDwRk-0007wz-00@rom.localdomain>
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: Wed, 14 Apr 2004 21:41:58 -0700
X-UIDL: 2c7b5ff732bb80f93cfe862c010b4102

>With the AMD-64 and Intel 64-bit clone of it, we are on the verge of a
>transition to inexpensive 64-bit computer systems.

And yet most applications still can't deal with files over 2 Gig....

>  TIFF needs to
>evolve in preparation for 64-bit systems.  The file format probably
>needs a extension for large files with 64 bit offsets, and it would be
>nice if these files could be read on 32-bit systems.


Unfortunately, anything that uses 64 bit offsets would no longer be TIFF.
TIFF can't evolve that way.
But we can create a new, TIFF-like format that can handle larger file 
sizes (and hopefully reuse most of the libTIFF code).

Also, 32 bit systems can read 64 bit offset file formats without any 
problems (assuming they use the correct file APIs).

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