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 iBIKuktg012777
        for <joris.at.lebbeke@skynet.be>; Sat, 18 Dec 2004 21:56:46 +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 iBIKuaVF005097
        for <joris.at.lebbeke@skynet.be>; Sat, 18 Dec 2004 21:56:38 +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 22A1F52DA6A; Sat, 18 Dec 2004 15:56:20 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from ATALADC1.atalasoft.lcl (host227.155.212.221.conversent.net
	[155.212.221.227])
	by xserve.flids.com (Postfix) with ESMTP id DD48B52DA46
	for <tiff@remotesensing.org>; Sat, 18 Dec 2004 15:56:17 -0500 (EST)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Subject: RE: [Tiff] Q: Fax photometric
Date: Sat, 18 Dec 2004 15:58:01 -0500
Message-ID: <2A7F84B7BBB1CC4F88A9AD71142B91C8046FDF@ATALADC1.atalasoft.lcl>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tiff] Q: Fax photometric
thread-index: AcTlMWu1+FgH6XjqTpa7r1ERukekiAAElfXw
From: "Bill Bither" <bill.bither@atalasoft.com>
To: <tiff@remotesensing.org>
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: d012ba620a5e1932939f228d5bf17736

The question I have about this image is why does photoshop and some
others read it "incorrectly" according to the spec but visually correct?
Is the assumption that any CCIT RLE (1D) image that has
PHOTOMETRIC_MINISBLACK actually encoded as "Min as White"?  Or only with
images encoded from this particular vendor (skyline tools)?

Regards,
Bill Bither
Atalasoft

-----Original Message-----
From: tiff-bounces@remotesensing.org
[mailto:tiff-bounces@remotesensing.org] On Behalf Of Joris
Sent: Saturday, December 18, 2004 1:40 PM
To: Bob Friesenhahn; Chris Losinger
Cc: tiff@remotesensing.org
Subject: Re: [Tiff] Q: Fax photometric

> They may do this because
> some TIFF files are created with the wrong setting and users complain.

They may do this because 'it seems that these popular applications
always assume
the normal case'.

Food for thought, I think. Your universal reasoning 'it's not a bug,
it's a
compatibility feature', consistently results in propagating the bug. In
the end,
we'll need a specification and an extensive bug list overriding that
specification in order to ensure data exchange. Unfortunately, some will
consider the spec the actual specification, and ignore your bug list.
This way,
your 'compatibility feature' reasoning results in incompatible codecs,
and lots
of data that one or the other considers corrupted.

This is why most think bug compensation can be a good thing in readers
only, if
at all possible, but no writer should ever be made to write in buggy
ways for
'compatibility' reasons.

Furthermore, your reasoning 'we should keep the bug because users might
complain', whenever posted in this list, is consistently the answer to
at least
one user complaining about the bug, instead.

Chris, I believe you should make an entry in the bugzilla interface. I
will
first check CVS, and, if still necessary, do the same for the IPTC tag
datatype
bug, when I get around to it.


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



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