Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas011.isp.belgacom.be (localhost [127.0.0.1])
        by inav005.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AV-3.00) with ESMTP id jBDIIWIZ009713
        for <joris.at.lebbeke@skynet.be>; Tue, 13 Dec 2005 19:18:32 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx010.isp.belgacom.be (inmx010.isp.belgacom.be [195.238.4.73])
        by inas011.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AS-2.03) with ESMTP id jBDIIOsj009783
        for <joris.at.lebbeke@skynet.be>; Tue, 13 Dec 2005 19:18:24 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx010.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id jBDIIBcs029885
        for <joris.at.lebbeke@skynet.be>; Tue, 13 Dec 2005 19:18:12 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id jBDI8rOf012626;
	Tue, 13 Dec 2005 13:10:18 -0500
Received: from outmx014.isp.belgacom.be (outmx014.isp.belgacom.be
	[195.238.4.69])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id jBDI8oTW012623
	for <tiff@lists.maptools.org>; Tue, 13 Dec 2005 13:08:50 -0500
Received: from outmx014.isp.belgacom.be (localhost [127.0.0.1])
	by outmx014.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with
	ESMTP id jBDI8gw5002754
	for <tiff@lists.maptools.org>; Tue, 13 Dec 2005 19:08:43 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Received: from dfgrrxsknr4e (9-164.246.81.adsl.skynet.be [81.246.164.9])
	by outmx014.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with SMTP
	id jBDI8XS6002670; Tue, 13 Dec 2005 19:08:34 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Message-ID: <001001c60010$3ba8c1f0$09a4f651@dfgrrxsknr4e>
From: "Joris" <joris.at.lebbeke@skynet.be>
To: "Paul J. Lucas" <pauljlucas@mac.com>, <tiff@lists.maptools.org>
References: <Pine.LNX.4.63.0512121417170.20603@vgfl.cnhywyhpnf.bet><Pine.SOC.4.60.0512121643050.4804@blade.simplesystems.org><Pine.LNX.4.63.0512121452030.20603@vgfl.cnhywyhpnf.bet><Pine.SOC.4.60.0512121747160.4804@blade.simplesystems.org><Pine.LNX.4.63.0512121813540.20603@vgfl.cnhywyhpnf.bet><001201c5ffa5$6db21040$e2abf551@dfgrrxsknr4e><Pine.LNX.4.63.0512122344310.20603@vgfl.cnhywyhpnf.bet><003301c5fff6$f7f7d860$9fa7f651@dfgrrxsknr4e>
	<Pine.LNX.4.63.0512130923120.20603@vgfl.cnhywyhpnf.bet>
Subject: Re: [Tiff] Writing EXIF data?
Date: Tue, 13 Dec 2005 19:08:32 +0100
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2800.1506
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1506
Cc: 
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
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>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-UIDL: 000000000023ceae.00000f67
X-MSP-STORE: Tue, 13 Dec 2005 19:18:38 +0100
Status:   

Paul,

Paul J. Lucas wrote:
> I *could* do it that way, but, since I knew from the very
> beginning that doing such is currently impossible with libtiff,
> I asked about merely setting the entire EXIF metadata as a
> binary blob in a single shot.  I've already constructed it.

Since EXIF data is an IFD, and some tag values may be longer the 4
bytes, there's offsets there. Thus, how to build that 'blob' depends on
where you're going to write it. I hope you were aware.

> > ... but apart from understanding there's little I can do.
>
> Then you had/have no reason to reply.

Oh, well, that's nice. You know what, I'll give you your money back.

> > I recommend you explain how you wrote the 'blob'
>
> Why is that relevant?

Oh, just me trying to be helpful, anticipating the problem I explained
above, without having a reason to reply.

> This is exactly the
> same as, say, setting the ICC profile via TIFFSetField: I
> already have the ICC profile data as a blob.  How I created it
> is irrelevant.

No it's not at all exactly the same, and yes how you created it is
relevant, because of the above explained offset issue. I hope you were
aware and require no extra help, because I've no reason to reply any
further.


Joris Van Damme
info@awaresystems.be
http://www.awaresystems.be/
Download your free TIFF tag viewer for windows here:
http://www.awaresystems.be/imaging/tiff/astifftagviewer.html

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