Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx016.isp.belgacom.be (inmx016.isp.belgacom.be [195.238.2.219])
        by mailst034.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id i91MN0f3004651
        for <joris.at.lebbeke@skynet.be>; Sat, 2 Oct 2004 00:23:00 +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 inmx016.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id i91MMq55019704
        for <joris.at.lebbeke@skynet.be>; Sat, 2 Oct 2004 00:22:53 +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 94CD7345330; Fri,  1 Oct 2004 18:22:34 -0400 (EDT)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from psmtp.com (exprod6ob2.obsmtp.com [64.18.1.212])
	by xserve.flids.com (Postfix) with SMTP id 893BB345304
	for <tiff@remotesensing.org>; Fri,  1 Oct 2004 18:22:31 -0400 (EDT)
Received: from source ([192.150.22.7]) by exprod6ob2.obsmtp.com ([64.18.5.12])
	with SMTP; Fri, 01 Oct 2004 15:22:30 PDT
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
	i91MMUNf009770
	for <tiff@remotesensing.org>; Fri, 1 Oct 2004 15:22:30 -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
	i91MMUkq012216
	for <tiff@remotesensing.org>; Fri, 1 Oct 2004 15:22:30 -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 <0I4X00DEPFHHIN@mailsj-v1.corp.adobe.com> for
	tiff@remotesensing.org; Fri, 01 Oct 2004 15:22:30 -0700 (PDT)
Date: Fri, 01 Oct 2004 15:22:19 -0700
From: Chris Cox <ccox@adobe.com>
Subject: Re: [Tiff] Re: BigTIFF extension issue
In-reply-to: <6.0.0.22.1.20041001135607.0263e220@pop.earthlink.net>
X-Sender: ccox@mailsj.corp.adobe.com
To: tiff@remotesensing.org
Message-id: <p05210607bd837ef12142@[153.32.48.223]>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <4.3.2.7.2.20041001123059.016e72d0@mailsrv1>
	<415D8B80.5000300@pobox.com> <p06110403bd833f3c7cf9@[153.32.220.138]>
	<001d01c4a7de$cf92f6f0$e8c8c950@dfgrrxsknr4e>
	<6.0.0.22.1.20041001135607.0263e220@pop.earthlink.net>
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: 7e13f8e104341ecc550bd32130d175ff


I agree with Chris.

I think that using the same file extension as "classic TIFF" will 
create confusion and support problems.

And we can't go back and update Photoshop 4.0 (still in use!) to 
support BigTIFF, or to make it give a reasonable  error message -- 
it's just going to say "this isn't a valid TIFF file".

Using a different file extension (and name) will make it clear to 
users that this is something "not-quite-classic-tiff", and 
applications that don't support bigTIFF won't even try to read it.

Chris




At 2:03 PM -0400 10/1/04, Chris Losinger wrote:
>>While LibTiff does not yet support BigTIFF, it could be very easy to
>>nevertheless update it to already recognize at least the BigTIFF 
>>header already,
>>and return the appropriate error message you mention here, instead 
>>of a generic
>>'not a tiff file' - ish error. Since many apps stay reasonably up to LibTiff
>>date, that should already come a long way towards meeting your wish.
>
>         But not all apps use LibTiff; and not all that use LibTiff 
>are going to be able to upgrade to the latest version (ex. I'm still 
>stuck at 3.5.7 because of EXIF issues).
>
>         Introducing a new incompatible TIFF-ish format, while using 
>the same file extension as classic TIFF is only going to anger users 
>who don't understand why their favorite reader can't open this 
>"Foo.Tif" file they got from their co-worker. Then, at best, they'll 
>complain to the software vendor who might not even know that there's 
>even such a thing as BigTIFF; at worst, they'll decide the software 
>is simply broken and move on to something else.
>
>         Why even consider creating such headaches?
>
>         JPEG2000 didn't try to piggy-back on the ".JPG" extension, 
>and we're all thankful for it.
>
>         -c

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