Return-Path: <tiff-admin@remotesensing.org>
Received: from inmx009.isp.belgacom.be (inmx009.isp.belgacom.be [195.238.3.146])
        by mailst006.isp.belgacom.be (8.12.9/8.12.9/Skynet-MAILSTORE-2.14) with ESMTP id i3MIi250019430
        for <joris.at.lebbeke@skynet.be>; Thu, 22 Apr 2004 20:44:02 +0200
        (envelope-from <tiff-admin@remotesensing.org>)
Received: from yoda.imagelinks.com ([208.24.120.44])
        by inmx009.isp.belgacom.be (8.12.9/8.12.9/Skynet-IN-2.32) with ESMTP id i3MIhowO026394
        for <joris.at.lebbeke@skynet.be>; Thu, 22 Apr 2004 20:43:51 +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 i3MIh5n30428;
	Thu, 22 Apr 2004 14:43:05 -0400
Received: from smtp-relay-7.sea.adobe.com (smtp-relay-7.adobe.com [192.150.22.7])
	by yoda.imagelinks.com (8.11.6/8.11.6) with ESMTP id i3MIg2n30397
	for <tiff@remotesensing.org>; Thu, 22 Apr 2004 14:42:02 -0400
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 i3MIfkSP002802
	for <tiff@remotesensing.org>; Thu, 22 Apr 2004 11:41:47 -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 i3MIfgkq013944
	for <tiff@remotesensing.org>; Thu, 22 Apr 2004 11:41:42 -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 <0HWL002TB59I1E@mailsj-v1.corp.adobe.com> for
 tiff@remotesensing.org; Thu, 22 Apr 2004 11:41:42 -0700 (PDT)
From: Chris Cox <ccox@adobe.com>
Subject: Re: [Tiff] Large TIFF files
In-reply-to: <44E68E8A7590D411862200508B9AFC2202089746@zymail.zylab.nl>
X-Sender: ccox@mailsj.corp.adobe.com
To: Tiff mailing list <tiff@remotesensing.org>
Message-id: <p05210609bcadbf81476b@[153.32.48.223]>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <44E68E8A7590D411862200508B9AFC2202089746@zymail.zylab.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:41:27 -0700
X-UIDL: 1f95b398d3cb0e4cc65daecc9cf58d9e

>
>If we take a more revolutionary approach, I think we should liberally
>borrow ideas from the PNG spec, like their ASCII-transfer-detecting
>header and the bit that indicates whether unknown tags should be copied.

Actually, that's something that needs to be improved upon.
I have yet to find a PNG with the preserve information set correctly 
(and in one case a major application says to preserve it's tags, then 
crashes when you preserve them and it tries to read the file back in).
And there is no way to indicate "this tag must be modified if the 
image is modified".

But it does need to be solved - especially thanks to digital cameras 
writing proprietary EXIF tags that will cause problems if they are 
preserved (and complaints if they aren't preserved).


>Also in that case, I would slightly prefer ASCII-like tags, it gives my
>eyes something to hang on to when viewing a TIFF in a hex editor (which
>will remain useful for corrupted files and derived-but-not-quite-TIFF
>formats like Microsoft's Office Document Imaging format).

I agree - but I don't want to bloat the file with tags (otherwise we 
end up with the file blowup of XML).


>I'm sure Chris will bring in the lessons they've learned at Adobe when
>creating their PSB/Large Document Format.

PSB was only a minimal change to the PSD file format to use 64 bit offsets.
But changing the file extension and version number did let me clean 
up some things that were held back by compatibility issues (when you 
have to be compatible with everyone, it's not easy to change the file 
format).

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