Received: from inav038.isp.belgacom.be (localhost.localdomain [127.0.0.1])
	by inav038.isp.belgacom.be (Postfix) with ESMTP id A4679B6F85
	for <joris.at.lebbeke@skynet.be>; Tue, 19 Dec 2006 16:14:20 +0100 (CET)
Received: from inas038.isp.belgacom.be (inas038.isp.belgacom.be [195.238.6.217])
	by inav038.isp.belgacom.be (Postfix) with ESMTP id 982A0B6F75
	for <joris.at.lebbeke@skynet.be>; Tue, 19 Dec 2006 16:14:20 +0100 (CET)
Received: from inmx015.isp.belgacom.be (inmx015.isp.belgacom.be [195.238.4.218])
        by inas038.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-AS-2.03) with ESMTP id kBJFEEFl009588
        for <joris.at.lebbeke@skynet.be>; Tue, 19 Dec 2006 16:14:17 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx015.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id kBJFE9CH006134
        for <joris.at.lebbeke@skynet.be>; Tue, 19 Dec 2006 16:14:09 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (duke.maptools.org [127.0.0.1])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id kBJDx5wT004003;
	Tue, 19 Dec 2006 09:00:32 -0500
Received: from outmx017.isp.belgacom.be (outmx017.isp.belgacom.be
	[195.238.4.116])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id kBJDx13t003994
	for <tiff@lists.maptools.org>; Tue, 19 Dec 2006 08:59:02 -0500
Received: from outmx017.isp.belgacom.be (localhost [127.0.0.1])
	by outmx017.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22)
	with ESMTP id kBJDww3D009442
	for <tiff@lists.maptools.org>; Tue, 19 Dec 2006 14:58:58 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Received: from dfgrrxsknr4e (163.181-245-81.adsl-dyn.isp.belgacom.be
	[81.245.181.163])
	by outmx017.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-OUT-2.22)
	with SMTP id kBJDwp66009358; Tue, 19 Dec 2006 14:58:51 +0100
	(envelope-from <joris.at.lebbeke@skynet.be>)
Message-ID: <001f01c72375$de69a600$a3b5f551@dfgrrxsknr4e>
From: "Joris" <joris.at.lebbeke@skynet.be>
To: "Anurag Singh" <contact.anurag@gmail.com>,
        "Tiff" <tiff@lists.maptools.org>
References: <11848b2f0612160214h26f2c8f3xbf7b01b13afe01d2@mail.gmail.com>
	<11848b2f0612190524u54d110cdxe3a1f242b1710cd8@mail.gmail.com>
Subject: Re: [Tiff] Order of Image IFD and Strip Data
Date: Tue, 19 Dec 2006 14:59:13 +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.1807
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1896
Cc: 
X-BeenThere: tiff@lists.maptools.org
X-Mailman-Version: 2.1.4
Precedence: list
List-Id: TIFF and libtiff discussion <tiff.lists.maptools.org>
List-Unsubscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=unsubscribe>
List-Archive: <http://lists.maptools.org/mailman/private/tiff>
List-Post: <mailto:tiff@lists.maptools.org>
List-Help: <mailto:tiff-request@lists.maptools.org?subject=help>
List-Subscribe: <http://lists.maptools.org/mailman/listinfo/tiff>,
	<mailto:tiff-request@lists.maptools.org?subject=subscribe>
Sender: tiff-bounces@lists.maptools.org
Errors-To: tiff-bounces@lists.maptools.org
X-UIDL: 000000000023ceae.00001e7d
X-MSP-STORE: Tue, 19 Dec 2006 16:14:29 +0100
Status:   

Anurag,

Anurag Singh wrote:
> Please help me, it's really very important for me to know that is
> there any posibility to specify order. I had already read
> tif_open.c but didn't get such kind of option. Please tell me about
> the possibility.

There is no such possibility to the best of my knowledge.

You keep asking for support for operations on TIFF that totally go
against the spirit of TIFF. TIFF has no concept of order of data blocks,
all blocks are relocatable, thus two files with the exact same blocks in
a different order, are exactly the same TIFF. Even if someone would be
willing to add the requested functionality and let you determine the
order of blocks, I'd vote against any such code in LibTiff.

Suppose you'd find support to do this. Next, you'll be faced with TIFF
files with 'holes' in them that are a consequence of 'deleting' IFDs or
'updating' tag data or such, i.e. spaces in the file that are not
pointed to. You'll be asking for support for copying meaningless
garbage.

Suppose you'd find support to deal with that, too. Next, you'll be faced
with TIFF files of writers that don't align properly, i.e. don't start
separate blocks of data on mulitples of 2 or 4 bytes. And you'll be
asking for support to misalign.

The mess is endless. If you want to work with TIFF, understand and
comply with its spirit, because its spirit is a consistent whole and any
violation of it results in an avalanche of problems, many of which you
will not be able to foresee.

I've said this before, like I asked you before to quote properly and
post plain text only. If you want someone's help, it's a good idea to
try and understand their replies. If you don't agree with those replies,
well, then feel free to disagree, and bare the consequences that I'm
sure you fully thought through.


Best regards,

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@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
