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 iBIIdqmQ026365
        for <joris.at.lebbeke@skynet.be>; Sat, 18 Dec 2004 19:39:52 +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 iBIIdd9U001187
        for <joris.at.lebbeke@skynet.be>; Sat, 18 Dec 2004 19:39:41 +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 4B11A52C772; Sat, 18 Dec 2004 13:39:24 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from outmx002.isp.belgacom.be (outmx002.isp.belgacom.be
	[195.238.3.52])
	by xserve.flids.com (Postfix) with ESMTP id A9CC452C74F
	for <tiff@remotesensing.org>; Sat, 18 Dec 2004 13:39:21 -0500 (EST)
Received: from outmx002.isp.belgacom.be (localhost [127.0.0.1])
	by outmx002.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with
	ESMTP id iBIIdISk008066
	for <tiff@remotesensing.org>; Sat, 18 Dec 2004 19:39:18 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Received: from dfgrrxsknr4e (218-165.245.81.adsl.skynet.be [81.245.165.218])
	by outmx002.isp.belgacom.be (8.12.11/8.12.11/Skynet-OUT-2.22) with SMTP
	id iBIIdEvN008026; Sat, 18 Dec 2004 19:39:14 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Message-ID: <000901c4e531$01c4f620$daa5f551@dfgrrxsknr4e>
From: "Joris" <joris.at.lebbeke@skynet.be>
To: "Bob Friesenhahn" <bfriesen@simple.dallas.tx.us>,
        "Chris Losinger" <losinger@earthlink.net>
References: <6.2.0.14.2.20041214230049.02e83530@pop.earthlink.net>
	<Pine.SOC.4.60.0412181138300.7604@blade.simplesystems.org>
Subject: Re: [Tiff] Q: Fax photometric
Date: Sat, 18 Dec 2004 19:40:10 +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.1437
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1441
Cc: 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: 7f0d8ee2d2fea64111000418efba3592

> 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
