Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx015.isp.belgacom.be (inmx015.isp.belgacom.be [195.238.2.218])
        by mailst034.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id i94Io5xc021663
        for <joris.at.lebbeke@skynet.be>; Mon, 4 Oct 2004 20:50:05 +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 inmx015.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id i94InnRk024259
        for <joris.at.lebbeke@skynet.be>; Mon, 4 Oct 2004 20:49:51 +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 CDF27352770; Mon,  4 Oct 2004 14:49:23 -0400 (EDT)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from hog3.hogserve1.com (hog3.hogserve1.com [217.199.182.233])
	by xserve.flids.com (Postfix) with ESMTP id 1FD5535274A
	for <tiff@remotesensing.org>; Mon,  4 Oct 2004 14:49:20 -0400 (EDT)
Received: from 81-178-2-108.dsl.pipex.com ([81.178.2.108] helo=PLATO)
	by hog3.hogserve1.com with smtp (Exim 4.34)
	id 1CEXtX-0004DO-IS; Mon, 04 Oct 2004 19:49:11 +0100
Message-ID: <062001c4aa42$de1de0c0$0200a8c0@PLATO>
From: "Andy Cave" <andy.cave@hamillroad.com>
To: "Steve Carlsen" <scarlsen@adobe.com>,
        "Bob Friesenhahn" <bfriesen@simple.dallas.tx.us>,
        "Joris" <joris.at.lebbeke@skynet.be>
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><p05210607bd837ef12142@[153.32.48.223]><005401c4a81e$228281c0$e8c8c950@dfgrrxsknr4e><Pine.SOC.4.60.0410012039410.2727@blade.simplesystems.org><02ec01c4a869$6139d8f0$0200a8c0@PLATO><Pine.SOC.4.60.0410031048390.2727@blade.simplesystems.org><01b501c4a9ef$a7591e90$0200a8c0@PLATO>
	<41613416.2688D0A8@oce.nl><Pine.SOC.4.60.0410040950060.2727@blade.simplesystems.org><002f01c4aa26$251db6c0$052ac850@dfgrrxsknr4e><Pine.SOC.4.60.0410041035240.2727@blade.simplesystems.org><000a01c4aa2a$653ecf60$052ac850@dfgrrxsknr4e><Pine.SOC.4.60.0410041054130.2727@blade.simplesystems.org>
	<p06110403bd872d933b96@[10.0.1.3]>
Subject: Re: [Tiff] Re: BigTIFF extension issue
Date: Mon, 4 Oct 2004 19:49:22 +0100
MIME-Version: 1.0
Content-Type: text/plain; format=flowed; charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2180
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2180
X-AntiAbuse: This header was added to track abuse,
	please include it with any abuse report
X-AntiAbuse: Primary Hostname - hog3.hogserve1.com
X-AntiAbuse: Original Domain - remotesensing.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - hamillroad.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
Cc: tiff@remotesensing.org
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: 24df09cd1014fc22e689aa8704291405

Hi All.

If we use a new extension, given "jpg & jp2" I would vote on "tif & tf2" (as 
opposed to png (worse) or btf or tf8). However, even there, jp2 is because 
it's named JPEG2000 from which the jp and 2 come from which is not quite the 
case here. I would still vote for .tif[f].

Since customers are mentioned, imagine what a customer is going to say :

sales person - "you should upgrade to v2.x 'cause it supports 
tf2/tf8/bigtif/..."
customer - "oh - I've never heard about that - what is tf2/tf8/bigtif/..."
sales person - "hum - actually it's tiff"
customer - "ugh? why's it called tf2/tf8/bigtif/... then and not tiff?"
sales person - "hum... 'cause it's bigger"
customer - "what do you mean it's bigger?"
sales person - "it allows for larger image/file sizes"
customer - "oh - so it's a tiff file, but bigger"
sales person - "yes, you've got it"
customer - "so how big is big"
sales person - "it's very big..."
...

Andy.

----- Original Message ----- 
From: "Steve Carlsen" <scarlsen@adobe.com>
To: "Bob Friesenhahn" <bfriesen@simple.dallas.tx.us>; "Joris" 
<joris.at.lebbeke@skynet.be>
Cc: <tiff@remotesensing.org>
Sent: Monday, October 04, 2004 5:50 PM
Subject: Re: [Tiff] Re: BigTIFF extension issue


> Does anyone want to attempt to impartially summarize the key arguments for 
> and against keeping the extension as ".tif"?
>
> I'm assuming that minimizing customer confusion and inconvenience is main 
> thing that we're all aiming for.
>
> (Incidentally, I'd like throw into the ring "TIFF2" as the name, and 
> ".tf2" as the extension, if we decide to do a new extension. "BigTIFF" and 
> ".btf" sounds a little goofy, 8-byte TIFF and ".tf8" is a little too 
> technical.)
> _______________________________________________
> Tiff mailing list
> Tiff@remotesensing.org
> http://xserve.flids.com/mailman/listinfo/tiff
>
>
> 


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