Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx010.isp.belgacom.be (inmx010.isp.belgacom.be [195.238.2.73])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id iB7MHYwS004874
        for <joris.at.lebbeke@skynet.be>; Tue, 7 Dec 2004 23:17:34 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from xserve.flids.com (adsl-065-083-169-202.sip.mco.bellsouth.net [65.83.169.202])
        by inmx010.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id iB7MHJCH027240
        for <joris.at.lebbeke@skynet.be>; Tue, 7 Dec 2004 23:17:22 +0100
        (envelope-from <tiff-bounces@remotesensing.org>)
Received: from adsl-065-083-169-202.sip.mco.bellsouth.net (localhost [127.0.0.1])
	by xserve.flids.com (Postfix) with ESMTP
	id 8331A4E26B1; Tue,  7 Dec 2004 17:17:04 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from psmtp.com (exprod6ob3.obsmtp.com [64.18.1.213])
	by xserve.flids.com (Postfix) with SMTP id EE95D4E266B
	for <tiff@remotesensing.org>; Tue,  7 Dec 2004 17:16:59 -0500 (EST)
Received: from source ([192.150.11.134]) by exprod6ob3.obsmtp.com
	([64.18.5.12]) with SMTP; Tue, 07 Dec 2004 14:15:39 PST
Received: from inner-relay-3.corp.adobe.com ([153.32.251.51])
	by outbound-smtp-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	iB7MBwQY008580; Tue, 7 Dec 2004 14:11:58 -0800 (PST)
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
	iB7MGw0v024157; Tue, 7 Dec 2004 14:16:58 -0800 (PST)
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 <0I8D00G3HHW9P7@mailsj-v1.corp.adobe.com>; Tue,
	07 Dec 2004 14:16:58 -0800 (PST)
Date: Tue, 07 Dec 2004 14:14:41 -0800
From: Chris Cox <ccox@adobe.com>
Subject: Re: [Tiff] Having problems adding IPTC to a TIFF
In-reply-to: <005401c4dc9e$829ac0e0$5eb1f551@dfgrrxsknr4e>
X-Sender: ccox@mailsj.corp.adobe.com
To: Joris <joris.at.lebbeke@skynet.be>,
        Tiff mailing list <tiff@remotesensing.org>
Message-id: <p05210612bddbdb8f8475@[153.32.48.223]>
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii; format=flowed
Content-transfer-encoding: 7BIT
References: <41AF59CD.3090603@rabien.com>
	<20041202183006.GA14794@ak4719.spb.edu>
	<001f01c4dbe6$402fec20$c6a3f551@dfgrrxsknr4e>
	<Pine.SOC.4.60.0412061959120.4000@blade.simplesystems.org>
	<003b01c4dc07$e58d48e0$51a0f551@dfgrrxsknr4e>
	<Pine.SOC.4.60.0412062140410.4000@blade.simplesystems.org>
	<p05210608bddadfc480a5@[153.32.48.223]>
	<002201c4dc3d$05b15500$63b2f551@dfgrrxsknr4e>
	<p0521060abddbc12b5518@[153.32.48.223]>
	<005401c4dc9e$829ac0e0$5eb1f551@dfgrrxsknr4e>
Cc: 
X-BeenThere: tiff@remotesensing.org
X-Mailman-Version: 2.1.2
Precedence: list
List-Id: TIFF and libtiff discussion  <tiff.remotesensing.org>
List-Unsubscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=unsubscribe>
List-Archive: <http://xserve.flids.com/pipermail/tiff>
List-Post: <mailto:tiff@remotesensing.org>
List-Help: <mailto:tiff-request@remotesensing.org?subject=help>
List-Subscribe: <http://xserve.flids.com/mailman/listinfo/tiff>,
	<mailto:tiff-request@remotesensing.org?subject=subscribe>
Sender: tiff-bounces@remotesensing.org
Errors-To: tiff-bounces@remotesensing.org
X-UIDL: cea51121f38c0872609694f11be304bd

At 9:51 PM +0100 12/7/04, Joris wrote:
>Chris,
>
>>  We don't byte swap the IPTC data block.
>>  The data in that block is treated separately from the TIFF containing it.
>
>So this effectively means that Photoshop can't read IPTC data that I 
>write to a
>motorola-order TIFF on my intel-order machine, or that is written to a
>intel-order TIFF on a motorola-order machine, given the current bug 
>in LibTiff.
>LibTiff incorrectly swaps, and Photoshop doesn't swap back to compensate. Am I
>correct?

If you swap incorrectly, then Photoshop cannot read it.
But that would be your mistake (the incorrect swap).

But since YOU can write it with any data type, writing it as byte or 
unspecified will avoid the incorrect data swapping.

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