Return-Path: <tiff-bounces@lists.maptools.org>
Received: from inas023.isp.belgacom.be (localhost [127.0.0.1])
        by inav001.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AV-3.00) with ESMTP id l0I8TVt5005907
        for <joris.at.lebbeke@skynet.be>; Thu, 18 Jan 2007 09:29:31 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from inmx020.isp.belgacom.be (inmx020.isp.belgacom.be [195.238.5.139])
        by inas023.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-AS-2.03) with ESMTP id l0I8TJuE026739
        for <joris.at.lebbeke@skynet.be>; Thu, 18 Jan 2007 09:29:22 +0100
        (envelope-from <tiff-bounces@lists.maptools.org>)
Received: from duke.maptools.org (r153.dmsolutions.ca [209.217.116.153] (may be forged))
        by inmx020.isp.belgacom.be (8.12.11.20060308/8.12.11/Skynet-IN-2.32) with ESMTP id l0I8TImS007907
        for <joris.at.lebbeke@skynet.be>; Thu, 18 Jan 2007 09:29:19 +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 l0I89eau020670;
	Thu, 18 Jan 2007 03:10:04 -0500
Received: from poczta.o2.pl (poczta.o2.pl [193.17.41.142] (may be forged))
	by duke.maptools.org (8.12.11/8.12.10) with ESMTP id l0I89bQ4020667
	for <tiff@lists.maptools.org>; Thu, 18 Jan 2007 03:09:37 -0500
Received: from poczta.o2.pl (mx12 [127.0.0.1])
	by poczta.o2.pl (Postfix) with ESMTP id 601B562813B
	for <tiff@lists.maptools.org>; Thu, 18 Jan 2007 09:09:35 +0100 (CET)
Received: from [192.168.0.153] (giy250.internetdsl.tpnet.pl [83.12.232.250])
	(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
	(No client certificate requested)
	by poczta.o2.pl (Postfix) with ESMTP
	for <tiff@lists.maptools.org>; Thu, 18 Jan 2007 09:09:35 +0100 (CET)
Message-ID: <45AF2B46.4050903@go2.pl>
Date: Thu, 18 Jan 2007 09:09:42 +0100
From: mikk <mikk@go2.pl>
User-Agent: Thunderbird 1.5.0.9 (Windows/20061207)
MIME-Version: 1.0
To: tiff@lists.maptools.org
Content-Type: text/plain; charset=ISO-8859-2; format=flowed
Content-Transfer-Encoding: 7bit
Subject: [Tiff] TIFF fields alignment question
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.00001fb6
X-MSP-STORE: Thu, 18 Jan 2007 09:29:36 +0100
Status:   

Hello,

Does the TIFF specification require that fields such as first IFD offset,
number of tags in a directory, tag structure and next IFD offset
must be written at word aligned position in TIFF file?
In other words - when writing these fields to a TIFF file, do they have to
be written in even bytes of data stream and some padding is required to
follow the specification?
I have read the TIFF specification but haven't found anything about that.
When searching in libTIFF sources I've found a comment in tiff.h, but only
about positioning of tag data:
"[...] The values associated with each entry are disjoint and may appear
anywhere in the file (so long as they are placed on a word boundary) [...]".

Can anyone put some light on that?

Thanks in advance,
Kind regards



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