Return-Path: <tiff-bounces@lists.maptools.org>
X-Original-To: info@awaresystems.be
Delivered-To: info@awaresystems.be
Received: from mx-j.b-one.net (mx-j.one.com [91.198.169.57])
	by mail9.b-one.net (Postfix) with ESMTP id 2D0D240013D
	for <info@awaresystems.be>; Tue, 14 Jul 2009 20:36:08 +0200 (CEST)
X-Virus-Scanned: by one.com
X-Spam-Score: 0
X-Spam-Level: 
X-Spam-Status: No, score=0 tagged_above=0 required=6 tests=[none]
X-Greylist: domain auto-whitelisted by SQLgrey-1.7.4
Received: from lists.maptools.org (lists.maptools.org [65.39.174.144])
	by mx-j.b-one.net (Postfix) with ESMTP id 78B964A926F
	for <info@awaresystems.be>; Tue, 14 Jul 2009 20:36:07 +0200 (CEST)
Received: from localhost.localdomain (localhost.localdomain [127.0.0.1])
	by lists.maptools.org (Postfix) with ESMTP id AC8AB1D4ACCA4;
	Tue, 14 Jul 2009 13:35:33 -0500 (EST)
Received: from owl.phy.queensu.ca (owl.phy.QueensU.CA [130.15.24.27])
	by lists.maptools.org (Postfix) with ESMTPS id D0D3B1D19623F
	for <tiff@lists.maptools.org>; Tue, 14 Jul 2009 12:56:14 -0500 (EST)
Received: from [130.15.24.88] (phil-mactel [130.15.24.88] (may be forged))
	(authenticated bits=0)
	by owl.phy.queensu.ca (8.13.8/8.13.8) with ESMTP id n6EHuDV5028904
	(version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO)
	for <tiff@lists.maptools.org>; Tue, 14 Jul 2009 13:56:13 -0400
Mime-Version: 1.0 (Apple Message framework v753.1)
In-Reply-To: <mailman.7.1247158802.7217.tiff@lists.maptools.org>
References: <mailman.7.1247158802.7217.tiff@lists.maptools.org>
Message-Id: <2F402529-967A-45EB-BE25-D6FEB91BCFAA@owl.phy.queensu.ca>
From: Phil Harvey <phil@owl.phy.queensu.ca>
Date: Tue, 14 Jul 2009 13:56:12 -0400
To: tiff@lists.maptools.org
X-Mailer: Apple Mail (2.753.1)
X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by
	milter-greylist-3.0 (owl.phy.queensu.ca [130.15.24.27]);
	Tue, 14 Jul 2009 13:56:13 -0400 (EDT)
Subject: Re: [Tiff] TIFFTAG_RICHTIFFIPTC definition
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 9-Jul-09, at 1:00 PM, Joris Van Damme wrote:
> My humble advice when it comes to writing is using the datatype  
> TIFF_BYTE or
> TIFF_UNDEFINED. The latter is probably the most 'correct' as it  
> literaly
> signifies that the data is of mixed type and byte order and widths  
> of data
> members is defined outside the scope of TIFF. The datatype  
> TIFF_BYTE can be
> used as amounting to the same thing, though, mostly.

I must comment on this.  TIFF_BYTE is VERY different from  
TIFF_UNDEFINED, and the two should not be interchanged.  There are  
many cases where TIFF_BYTE is used incorrectly.  It should NEVER be  
used in mixed data records.  In the C language there might not be  
much difference between an array of bytes and a block of undefined  
data, but trust me -- they have very different representations in  
some other languages!

- Phil

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