Return-Path: <eric.vergnaud@jlynx.com>
Received: from inmx006.isp.belgacom.be (inmx006.isp.belgacom.be [195.238.2.106])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id iB7AYd5j015830
        for <joris.at.lebbeke@skynet.be>; Tue, 7 Dec 2004 11:34:39 +0100
        (envelope-from <eric.vergnaud@jlynx.com>)
Received: from smtp5.wanadoo.fr (smtp5.wanadoo.fr [193.252.22.26])
        by inmx006.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id iB7AYVvS008614
        for <joris.at.lebbeke@skynet.be>; Tue, 7 Dec 2004 11:34:31 +0100
        (envelope-from <eric.vergnaud@jlynx.com>)
Received: from me-wanadoo.net (localhost [127.0.0.1])
	by mwinf0502.wanadoo.fr (SMTP Server) with SMTP id 114221C00166
	for <joris.at.lebbeke@skynet.be>; Tue,  7 Dec 2004 11:34:31 +0100 (CET)
Received: from [192.168.0.4] (AToulouse-152-1-44-124.w82-125.abo.wanadoo.fr [82.125.154.124])
	by mwinf0502.wanadoo.fr (SMTP Server) with ESMTP id C619C1C001EC
	for <joris.at.lebbeke@skynet.be>; Tue,  7 Dec 2004 11:34:30 +0100 (CET)
User-Agent: Microsoft-Entourage/10.1.4.030702.0
Date: Tue, 07 Dec 2004 11:34:29 +0100
Subject: Re: [Tiff] Having problems adding IPTC to a TIFF
From: Eric VERGNAUD <eric.vergnaud@jlynx.com>
To: Joris <joris.at.lebbeke@skynet.be>
Message-ID: <BDDB45C5.2C8D4%eric.vergnaud@jlynx.com>
In-Reply-To: <002301c4dc3d$05e5d280$63b2f551@dfgrrxsknr4e>
Mime-version: 1.0
Content-type: text/plain; charset="ISO-8859-1"
Content-transfer-encoding: quoted-printable
X-UIDL: 1ebce12d019bb053fe6a48099731dfcd

le 7/12/04 10:12, Joris =E0 joris.at.lebbeke@skynet.be a =E9crit=A0:

>> I agree with most of your arguments except that it is necessary to
>> balance technical correctness against what the industry is primarily
>> actually doing and what libtiff users are currently expecting.
>=20
> Very scary.
>=20

I agree with Bob in the sense that plenty of existing software is expecting
a long tag for richiptc, so writing it as undefined would certainly lead to
more problems that what it would solve, provided those software are
presumably aware of the issue, and ready to handle uncorrectly byte-swapped
iptc data.

However, I think we should take this opportunity to say that iptc is
deprecated anyway. Iptc has moved to XMP, and the IIMv4 format is dropped.
So modern software should be writing XMP, and provide IPTC only for
backwards compatibility.

Eric
-------------------------------
Eric VERGNAUD - JLynx Software
Cutting-edge technologies and
services for software companies
web: http://www.jlynx.com
-------------------------------


