Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas020.isp.belgacom.be (localhost [127.0.0.1])
        by inav019.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AV-3.00) with ESMTP id k5D8lWGB019237
        for <joris.at.lebbeke@skynet.be>; Tue, 13 Jun 2006 10:47:33 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx006.isp.belgacom.be (inmx006.isp.belgacom.be [195.238.4.106])
        by inas020.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AS-2.03) with ESMTP id k5D8lRwU011500
        for <joris.at.lebbeke@skynet.be>; Tue, 13 Jun 2006 10:47:29 +0200
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx006.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id k5D8lMtL020196
        for <joris.at.lebbeke@skynet.be>; Tue, 13 Jun 2006 10:47:22 +0200
        (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 k5D8Yme6027787;
	Tue, 13 Jun 2006 04:35:57 -0400
Received: from zynlfw01.zylab.com (mx.zylab.com [194.178.9.130])
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id k5D8YZMp027759
	for <tiff@lists.maptools.org>; Tue, 13 Jun 2006 04:34:36 -0400
Received: from zynlms01.ZyLAB.WAN (zynlms01.zylab.wan [192.168.1.10])
	by zynlfw01.zylab.com (Postfix) with ESMTP id B2CD0213;
	Tue, 13 Jun 2006 10:27:36 +0200 (CEST)
X-MimeOLE: Produced By Microsoft Exchange V6.5.7226.0
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Subject: Re: [Tiff] Editing a tiff image using libtiff
Date: Tue, 13 Jun 2006 10:32:13 +0200
Message-ID: <FC840EC0BF7BFA45A0F94548AF36920DABF2AA@zynlms01.ZyLAB.WAN>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: [Tiff] Editing a tiff image using libtiff
Thread-Index: AcaOKr0Bk/pc2GIuTfmFH+cd5WERlQAi1oAgAAMwS9A=
From: "Gerben Vos" <Gerben@zylab.com>
To: <tiff@lists.maptools.org>
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by duke.maptools.org id
	k5D8YZMp027759
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.000017aa
X-MSP-STORE: Tue, 13 Jun 2006 10:47:43 +0200
Status:   

> An additional way to handle space is the introduction of an 
> 'alloc-tag'.
> This tag indicates the size of the 'allocated' block in the file in
> contrast to the size tag which indicates the count of the bytes used.

There are already the FreeByteOffsets and FreeByteCounts (288 and 289) tags for keeping track of unused space. Nothing is specified about in which IFD they belong, though (the first? the last? wherever you want, and use all of them together?). The spec also says: "not recommended for general interchange", probably partly because of this, and also because it's not very nice to give someone a space-wasting file, I guess :-).

					Gerben Vos.

_______________________________________________
Tiff mailing list: Tiff@lists.maptools.org
http://lists.maptools.org/mailman/listinfo/tiff
http://www.remotesensing.org/libtiff/
