Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx012.isp.belgacom.be (inmx012.isp.belgacom.be [195.238.3.90])
        by mailst035.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id j0DDsUgO031360
        for <joris.at.lebbeke@skynet.be>; Thu, 13 Jan 2005 14:54:30 +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 inmx012.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id j0DDsML1001385
        for <joris.at.lebbeke@skynet.be>; Thu, 13 Jan 2005 14:54:24 +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 189B65B7FFD; Thu, 13 Jan 2005 08:54:03 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from outmx010.isp.belgacom.be (outmx010.isp.belgacom.be
	[195.238.3.233])
	by xserve.flids.com (Postfix) with ESMTP id 5FB745B7FD9
	for <tiff@remotesensing.org>; Thu, 13 Jan 2005 08:54:00 -0500 (EST)
Received: from outmx010.isp.belgacom.be (localhost [127.0.0.1])
	by outmx010.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with
	ESMTP id j0DDrwO4001055
	for <tiff@remotesensing.org>; Thu, 13 Jan 2005 14:53:58 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Received: from dfgrrxsknr4e (132-183.245.81.adsl.skynet.be [81.245.183.132])
	by outmx010.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with SMTP
	id j0DDrp1H001005; Thu, 13 Jan 2005 14:53:51 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Message-ID: <002f01c4f977$921bb3d0$84b7f551@dfgrrxsknr4e>
From: "Joris" <joris.at.lebbeke@skynet.be>
To: "Claude Houle" <CHoule@mediagrif.com>,
        "Tiff mailing list" <tiff@remotesensing.org>
References: <A764DEA6961A854E80AE2EAF7E7FB146FF6F4B@stimxchl.dev.mediagrif.com>
	<002701c4f972$e265b200$84b7f551@dfgrrxsknr4e>
Subject: Re: [Tiff] TIFF - Unknown field with tag 34665
Date: Thu, 13 Jan 2005 14:55:40 +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.1478
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1478
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: ea1ea798f057d6deaacd0a1c0361df75

Folks,

Again, the default mailing list reply address is mocking things up. I am getting
very tired of this.

Claude, please note that the default reply address is the sender, not the list.
Thus, if you just hit reply, you're no longer posting on-list. Instead, hitting
reply-all, in most mailing list clients, would do nicely. Alternatively,
manually make sure tiff@remotesensing.org is in the TO or CC list.

Claude wrote to me privatly:
> Take a quick look at the Screenshot of IMDisplay versus the screenshot of
> GIMP, and you will see the difference. It is the same picture, but rendered
> differently somehow. The screenshot from GIMP is right, as is the screenshot
> from MS Photo Editor. But IMDisplay ( Image Magick 6.1.8-3 ) doesn't handle
> it properly ( They use libTIFF 3.5.1 if I remember well ).

Here's a tag dump of the file you've sent me:

SubFileType (1 Long): Zero
ImageWidth (1 Short): 191
ImageLength (1 Short): 224
BitsPerSample (4 Short): 8, 8, 8, 8
Compression (1 Short): Uncompressed
Photometric (1 Short): Seperated
StripOffsets (1 Long): 9376
SamplesPerPixel (1 Short): 4
RowsPerStrip (1 Short): 224
StripByteCounts (1 Long): 171136
XResolution (1 Rational): 300
YResolution (1 Rational): 300
PlanarConfig (1 Short): Contig
ResolutionUnit (1 Short): Inch
Software (20 ASCII): Adobe Photoshop 7.0
DateTime (20 ASCII): 2005:01:12 13:37:30
700 (4649 Byte): 60, 63, 120, 112, 97, 99, 107, 101, 116, 32,...
Photoshop (4420 Byte): 56, 66, 73, 77, 4, 37, 0, 0, 0, 0, 0, 16, 0,...
34665 (1 Long): 180512

See, it's a CMYK file. My guess is that some of your software can't handle CMYK.
Anyway, I could not comment on that, it's an application issue, not a LibTiff
issue, I think.

What could also be related, judging from the screenshots, is that Photoshop
writes CMYK as 255 is no ink, and some others write CMYK as 255 is full ink. Or
so I seem to remember, but I could be mistaking. If this is your problem, I
don't think there's any good solution.

Perhaps you can avoid using CMYK alltogether?


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@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff
