Return-Path: <tiff-admin@remotesensing.org>
Received: from inmx008.isp.belgacom.be (inmx008.isp.belgacom.be [195.238.3.88])
        by mailst006.isp.belgacom.be (8.12.9/8.12.9/Skynet-MAILSTORE-2.14) with ESMTP id i3QHGovG025904
        for <joris.at.lebbeke@skynet.be>; Mon, 26 Apr 2004 19:16:50 +0200
        (envelope-from <tiff-admin@remotesensing.org>)
Received: from yoda.imagelinks.com ([208.24.120.44])
        by inmx008.isp.belgacom.be (8.12.9/8.12.9/Skynet-IN-2.32) with ESMTP id i3QHGdCL002684
        for <joris.at.lebbeke@skynet.be>; Mon, 26 Apr 2004 19:16:40 +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 i3QHG7n09532;
	Mon, 26 Apr 2004 13:16:07 -0400
Received: from smtp-relay-8.adobe.com (smtp-relay-8.adobe.com [192.150.22.8])
	by yoda.imagelinks.com (8.11.6/8.11.6) with ESMTP id i3QHF2n09397
	for <tiff@remotesensing.org>; Mon, 26 Apr 2004 13:15:02 -0400
Received: from inner-relay-3.corp.adobe.com (inner-relay-3 [153.32.251.51])
	by smtp-relay-8.adobe.com (8.12.10/8.12.10) with ESMTP id i3QHEU6P011941
	for <tiff@remotesensing.org>; Mon, 26 Apr 2004 10:14:35 -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 i3QHEPks027412
	for <tiff@remotesensing.org>; Mon, 26 Apr 2004 10:14:26 -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 <0HWS00DSBFW1SH@mailsj-v1.corp.adobe.com> for
 tiff@remotesensing.org; Mon, 26 Apr 2004 10:14:26 -0700 (PDT)
From: Chris Cox <ccox@adobe.com>
Subject: Re: [Tiff] Large TIFF files: explicitly different format
In-reply-to: <fc.0064b57b00efecda3b9aca00f733b2b0.efeed8@ecrm.com>
X-Sender: ccox@mailsj.corp.adobe.com
To: tiff@remotesensing.org
Message-id: <p05210604bcb2f18702be@[153.32.48.223]>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <Pine.GSO.4.44.0404221641250.11901-100000@scooby.simplesystems.org>
 <p0521061cbcadf0a4cb7d@[153.32.48.223]>
 <001e01c428b9$962b7df0$837988d9@dfgrrxsknr4e>
 <p0521061dbcadf8729fcf@[153.32.48.223]> <40890FE4.7080302@informatix.co.uk>
 <000f01c42934$afb6d690$2a57f051@dfgrrxsknr4e> <408CBA8B.B98D90BB@oce.nl>
 <002301c42b75$0b14ff70$e1b588d9@dfgrrxsknr4e> <408CED3A.31E6D7B5@oce.nl>
 <001701c42b81$aad61970$6f7a88d9@dfgrrxsknr4e>
 <408CFAF7.1070805@informatix.co.uk>
 <fc.0064b57b00efecda3b9aca00f733b2b0.efeed8@ecrm.com>
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: Mon, 26 Apr 2004 10:10:23 -0700
X-UIDL: 0a18548ff779c0eb23a8e157e57237e8


I agree with what Dan says here.

It's probably better to make an explicit choice.
If the user saves as TIFF 6 and the file goes over 4 Gig, we 
(Photoshop) can fail and tell the user that the file is too large for 
TIFF and they should try BigTIFF.     Yes, going back and cleaning up 
(either starting with 32 or 64) is possible, but slow and the user 
generally won't understand why their image works with some 
applications and not others.


Chris


PS. "Large Image File Exchange" - now you can tell your clients to 
"get a LIFE".



At 8:53 AM -0400 4/26/04, Dan Smith wrote:
>I'm usually on the side of utter, total, complete, effortless, seamless
>compatibility. But in this particular case, I think that an explicitly
>different format might work.
>
>By an "explicitly different format," I mean one with some different 
>name (BTIFF
>or BIGTIFF or TIFF2004 or TIFF Plus or TIFF Extreme...), and one that the user
>must _consciously_ select when specifying the file format. When such a file is
>sent from one user to another, both the sender and recipient are _consciously_
>aware that it is a big TIFF file, not a classic TIFF file.
...
_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://remotesensing.org/mailman/listinfo/tiff
