Return-Path: <tiff-admin@remotesensing.org>
Received: from inmx011.isp.belgacom.be (inmx011.isp.belgacom.be [195.238.3.50])
        by mailst006.isp.belgacom.be (8.12.9/8.12.9/Skynet-MAILSTORE-2.14) with ESMTP id i3MITA50009153
        for <joris.at.lebbeke@skynet.be>; Thu, 22 Apr 2004 20:29:11 +0200
        (envelope-from <tiff-admin@remotesensing.org>)
Received: from yoda.imagelinks.com ([208.24.120.44])
        by inmx011.isp.belgacom.be (8.12.9/8.12.9/Skynet-IN-2.32) with ESMTP id i3MISwVN007188
        for <joris.at.lebbeke@skynet.be>; Thu, 22 Apr 2004 20:29:00 +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 i3MIRCn30187;
	Thu, 22 Apr 2004 14:27:13 -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 i3MIOrn30137
	for <tiff@remotesensing.org>; Thu, 22 Apr 2004 14:24:53 -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 i3MIOM6P023177
	for <tiff@remotesensing.org>; Thu, 22 Apr 2004 11:24:27 -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 i3MIOFkw012538
	for <tiff@remotesensing.org>; Thu, 22 Apr 2004 11:24:18 -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 <0HWL002VM4GF1E@mailsj-v1.corp.adobe.com> for
 tiff@remotesensing.org; Thu, 22 Apr 2004 11:24:16 -0700 (PDT)
From: Chris Cox <ccox@adobe.com>
Subject: Re: [Tiff] Large TIFF files
In-reply-to: <40877668.91E7469F@oce.nl>
X-Sender: ccox@mailsj.corp.adobe.com
To: Tiff mailing list <tiff@remotesensing.org>
Message-id: <p05210605bcadbce2aa04@[153.32.48.223]>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <E1BDui3-0007qF-00@rom.localdomain> <407DEC23.2010300@pobox.com>
 <E1BDwRk-0007wz-00@rom.localdomain> <407E2625.6562720A@oce.nl>
 <407E8F18.9050806@pobox.com> <001301c42426$c4856450$0a7d88d9@dfgrrxsknr4e>
 <4084DF65.CC18045D@oce.nl> <p0521060fbcab39aee8cb@[153.32.48.223]>
 <40862329.61FEB89F@oce.nl> <p05210603bcac61c14dc4@[153.32.48.223]>
 <40877668.91E7469F@oce.nl>
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: Thu, 22 Apr 2004 11:21:31 -0700
X-UIDL: 3b605e6a06631c99c522e5e6347ce1d7

>
>>  And when writing the libraries, it's helpful to be able to read the
>>  file format in a hex editor ;-)
>Real programmers dream in hex :)

Yes, but do they dream in big endian or little endian?

Using ASCII tags would make it readable regardless of byte order.

Of course, that brings up the question: do we still need to support 
two byte orders?
In my experiments, reading from the disk always swamped the time 
needed to swap byte order - so there is no noticable impact from 
using a fixed byte order and forcing conversion on one platform the 
other.

Chris
_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://remotesensing.org/mailman/listinfo/tiff
