Return-Path: <awaresystems.be+caf_=filtered=awaresystems.be@gmail.com>
Delivered-To: filtered@awaresystems.be
Received: from mx-j.one.com (mx-j.one.com [91.198.169.57])
	by mail6.local (Postfix) with ESMTP id 354DE80150A0C
	for <filtered@awaresystems.be>; Fri, 14 Dec 2012 15:15:24 +0100 (CET)
X-Virus-Scanned: by one.com
Received-SPF: pass (mx-j: domain of awaresystems.be+caf_=filtered=awaresystems.be@gmail.com designates 209.85.212.48 as permitted sender)
X-Greylist: whitelisted by SQLgrey-1.8.0-rc2
Received: from mail-vb0-f48.google.com (mail-vb0-f48.google.com [209.85.212.48])
	by mx-j.one.com (Postfix) with ESMTP id C3C91211DCA3
	for <filtered@awaresystems.be>; Fri, 14 Dec 2012 14:15:23 +0000 (UTC)
Received: by mail-vb0-f48.google.com with SMTP id fc21so3951119vbb.21
        for <filtered@awaresystems.be>; Fri, 14 Dec 2012 06:15:23 -0800 (PST)
Received: by 10.59.6.70 with SMTP id cs6mr9334515ved.60.1355494522930;
        Fri, 14 Dec 2012 06:15:22 -0800 (PST)
X-Forwarded-To: filtered@awaresystems.be
X-Forwarded-For: awaresystems.be@gmail.com filtered@awaresystems.be
Delivered-To: awaresystems.be@gmail.com
Received: by 10.58.144.166 with SMTP id sn6csp27179veb;
        Fri, 14 Dec 2012 06:15:22 -0800 (PST)
Received: by 10.58.74.196 with SMTP id w4mr9205782vev.7.1355494521439;
        Fri, 14 Dec 2012 06:15:21 -0800 (PST)
Received-SPF: neutral (google.com: 91.198.169.57 is neither permitted nor denied by best guess record for domain of tiff-bounces@lists.maptools.org) client-ip=91.198.169.57;
Received: by 10.220.117.80 with POP3 id p16mf2975063vcq.18;
        Fri, 14 Dec 2012 06:15:20 -0800 (PST)
X-Gmail-Fetch-Info: info@awaresystems.be 1 pop.awaresystems.be 110 info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-j.one.com (mx-j.one.com [91.198.169.57])
	by mail6.local (Postfix) with ESMTP id C70E780150C20
	for <info@awaresystems.be>; Fri, 14 Dec 2012 15:06:19 +0100 (CET)
X-Greylist: domain auto-whitelisted by SQLgrey-1.8.0-rc2
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144])
	by mx-j.one.com (Postfix) with ESMTP id 87CC5211DC8D
	for <info@awaresystems.be>; Fri, 14 Dec 2012 14:06:19 +0000 (UTC)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by lists.maptools.org (Postfix) with ESMTP id BF84643A026;
	Fri, 14 Dec 2012 09:03:39 -0500 (EST)
Received: from owl.phy.queensu.ca (owl.phy.queensu.ca [130.15.24.27])
	by lists.maptools.org (Postfix) with ESMTPS id AE2C343A026
	for <tiff@lists.maptools.org>; Fri, 14 Dec 2012 09:03:05 -0500 (EST)
Received: from u88.n24.queensu.ca (work2.phy.queensu.ca [130.15.24.88])
	(authenticated bits=0)
	by owl.phy.queensu.ca (8.14.4/8.14.4) with ESMTP id qBEE352l027648
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <tiff@lists.maptools.org>; Fri, 14 Dec 2012 09:03:10 -0500
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Phil Harvey <phil@owl.phy.queensu.ca>
In-Reply-To: <mailman.1.1355418002.3738.tiff@lists.maptools.org>
Date: Fri, 14 Dec 2012 09:03:05 -0500
Message-Id: <6DE4602B-747B-4B54-95E1-8C1D563280C9@owl.phy.queensu.ca>
References: <mailman.1.1355418002.3738.tiff@lists.maptools.org>
To: tiff@lists.maptools.org
X-Mailer: Apple Mail (2.1499)
Subject: Re: [Tiff] Tiff Digest, Vol 103, Issue 4
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org

On 2012-12-13, at 12:00 PM, Bob Friesenhahn wrote:
> From: Bob Friesenhahn <bfriesen@simple.dallas.tx.us>
> This is all very interesting.  If TIFF_LONG is used, what should we do 
> while writing BigTIFF format?  Should TIFF_LONG only be used for 
> Classic TIFF?

This would be my vote.  ie) We can take this opportunity to fix a deficiency in the TIFF specification with BigTIFF.

	- Phil

_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
