Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx014.isp.belgacom.be (inmx014.isp.belgacom.be [195.238.2.217])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id iB7KUZDg017425
        for <joris.at.lebbeke@skynet.be>; Tue, 7 Dec 2004 21:30:35 +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 inmx014.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id iB7KUIDP027948
        for <joris.at.lebbeke@skynet.be>; Tue, 7 Dec 2004 21:30:20 +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 466C54E1EF1; Tue,  7 Dec 2004 15:29:57 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from psmtp.com (exprod6ob6.obsmtp.com [64.18.1.216])
	by xserve.flids.com (Postfix) with SMTP id 0A7E04E1EC7
	for <tiff@remotesensing.org>; Tue,  7 Dec 2004 15:29:46 -0500 (EST)
Received: from source ([193.95.148.142]) by exprod6ob6.obsmtp.com
	([64.18.5.12]) with SMTP; Tue, 07 Dec 2004 12:27:39 PST
Received: from inner-relay-3.corp.adobe.com (inner-relay-3.sea.adobe.com
	[153.32.251.51])
	by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id
	iB7KZhTG021351
	for <tiff@remotesensing.org>; Tue, 7 Dec 2004 12:35:44 -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
	iB7KTh0v014652
	for <tiff@remotesensing.org>; Tue, 7 Dec 2004 12:29:43 -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 <0I8D00A9ECXIQM@mailsj-v1.corp.adobe.com> for
	tiff@remotesensing.org; Tue, 07 Dec 2004 12:29:43 -0800 (PST)
Date: Tue, 07 Dec 2004 12:27:49 -0800
From: Chris Cox <ccox@adobe.com>
Subject: Re: [Tiff] AdobeDeflate (was: Having problems adding IPTC to a TIFF)
In-reply-to: <41B5CBA0.5000209@sidefx.com>
X-Sender: ccox@mailsj.corp.adobe.com
To: Tiff mailing list <tiff@remotesensing.org>
Message-id: <p0521060bbddbc1f684a8@[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]> <41B5CBA0.5000209@sidefx.com>
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: 47f3d0df4509b1c4756720802e3669af

At 10:26 AM -0500 12/7/04, Edward Lam wrote:
>Speaking of Photoshop, why was AdobeDeflate created?

Because someone outside Adobe defined a flate compression value and 
ignored the value defined by Adobe as part of the TIFF standard.

The non-Adobe flate compression value should be read, but never written.
Use the Adobe flate compression value when writing.

Chris



>-Edward
>
>Chris Cox wrote:
>>At 10:13 PM -0600 12/6/04, Bob Friesenhahn wrote:
>>
>>>On Tue, 7 Dec 2004, Joris wrote:
>>>
>>>>
>>>>- The specification says that the IPTC data contains data of 
>>>>different bitsizes
>>>>(byte, word, long, and undefined at the tag container level but 
>>>>anything on the
>>>>IPTC tag level)
>>>
>>>
>>>Which specification in particular are you using?  IPTC NewsPhoto 
>>>record is very old (early 90s) and last I checked (couple of years 
>>>ago), it seemed that IPTC had pulled the spec for IPTC NewsPhoto 
>>>as implemented for RichTIFF.  I did find a bit of information at 
>>>"http://home.earthlink.net/~ritter/tiff/richtiff.html".  The last 
>>>paragraph is most interesting.  It seems that Photoshop has 
>>>implemented IPTC NewsPhoto the way you don't like it and the 
>>>author of the web page sees that as a bug.  As we know, Photoshop 
>>>is the dominant application in this market so it is quite 
>>>influential.
>>
>>
>>Photoshop can read it with any tag type, but writes as type long 
>>for compatibility with some unspecified application (and the 
>>comment has been in there a long time).
>>
>>>I found a specification for RichTIFF (and something called "Solo 
>>>JFIF") at http://www.mtwphoto.com/garganey/.  The document 
>>>provides quite a bit of history behind the format.  The tag is 
>>>described as being type BYTE:
>>>
>>>Tag  = 33723 (83BB hex) and 34152 (8568 hex)
>>>Type = BYTE
>>>N    = length of IPTC data block in bytes
>>
>>
>>I haven't 34152 used anywhere, and Photoshop ignores that tag number.
>>
>>Chris
>>_______________________________________________
>>Tiff mailing list
>>Tiff@remotesensing.org
>>http://xserve.flids.com/mailman/listinfo/tiff

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