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 iB1KKWqL009190
        for <joris.at.lebbeke@skynet.be>; Wed, 1 Dec 2004 21:20:32 +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 iB1KKMwd002848
        for <joris.at.lebbeke@skynet.be>; Wed, 1 Dec 2004 21:20:23 +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 9C2584C1504; Wed,  1 Dec 2004 15:20:06 -0500 (EST)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from cgp.pu.ru (vlan3.cgp.pu.ru [195.70.196.209])
	by xserve.flids.com (Postfix) with ESMTP id EF3DE4C14E1
	for <tiff@remotesensing.org>; Wed,  1 Dec 2004 15:20:03 -0500 (EST)
Received: from wg.pu.ru ([193.124.85.219] verified)
	by cgp.pu.ru (CommuniGate Pro SMTP 4.2.5)
	with ESMTP id 37746055 for tiff@remotesensing.org;
	Wed, 01 Dec 2004 23:16:30 +0300
Received: (from uucp@localhost)
	by wg.pu.ru (8.9.1a/8.9.1) with UUCP id UAA29269
	for tiff@remotesensing.org; Wed, 1 Dec 2004 20:20:02 GMT
Received: from ak4719.spb.edu (localhost [127.0.0.1])
	by ak4719.spb.edu (8.12.11/8.12.11/Debian-5) with ESMTP id
	iB1KHRNw025903
	for <tiff@remotesensing.org>; Wed, 1 Dec 2004 23:17:27 +0300
Received: (from dron@localhost)
	by ak4719.spb.edu (8.12.11/8.12.11/Debian-5) id iB1KHRkG025900
	for tiff@remotesensing.org; Wed, 1 Dec 2004 23:17:27 +0300
From: Andrey Kiselev <dron@ak4719.spb.edu>
Date: Wed, 1 Dec 2004 23:17:27 +0300
To: tiff@remotesensing.org
Subject: Re: [Tiff] Datatype complex
Message-ID: <20041201201727.GB24731@ak4719.spb.edu>
Mail-Followup-To: tiff@remotesensing.org
References: <001301c4d7da$e193d1e0$7cb2f551@dfgrrxsknr4e>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <001301c4d7da$e193d1e0$7cb2f551@dfgrrxsknr4e>
X-GnuPG-Key: http://www.srces.spb.org/dron/export.home.key
X-Face: "t+se9s~+y~[XUH]L|pmeO3Pt/Q@DNv**S, d@_1-C=}/,
	c%<3Qp]eu!ok<"2lYJm$!9qVcg F?7o*L; |$`6|Q|>Rt-cU%2_y@6tQ|`!Li}TsvZvEKx;
	>fuY=fc(=sX^`7Wmw8%SsR`AvM$a; 0U/eN\ P?B\FTyqD, 0np$U2!*'z_4D,
	VPlFf?bN0&zYf"zF0s!7Tl7?$we)xD0@lL>[h|8bhys0i.g|zLnu@C
	Ti@d]i=[!:j1CB\5/TF[m]`lfHfaqSN[0qn@T3zeosV/[LAss{@p_?],x*j8P_9t[}uHD^X-;
	j~\M! gyTly;fj`}&Y~i{<#bN.#QmkE}#T`dxP.I1\.)_MEN{@#W
User-Agent: Mutt/1.5.6+20040722i
X-Virus-Scanned: clamd / ClamAV version 0.75-1, clamav-milter version 0.75c
	on ak4719
X-Virus-Status: Clean
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: e06d48c52f0341c629491b3d58afae5e

Joris,

On Wed, Dec 01, 2004 at 08:20:45PM +0100, Joris wrote:
> In tiff.h (LibTiff 3.7.0), the highest datatype I'm seeing is TIFF_IFD
> = 13.
> 
> I can't remember where I got it from, but I'm having TIFF_UNICODE =
> 14, and TIFF_COMPLEX = 15. That may be correct, as the first new
> datatype for BigTIFF is TIFF_LONG8 = 16 (according to my own BigTIFF
> page http://www.awaresystems.be/imaging/tiff/bigtiff.html, that was
> based on the Wiki).
> 
> Questions:
> - Can someone confirm these types TIFF_UNICODE and TIFF_COMPLEX?

These two types was mentioned ob the Wiki page by Chris Cox. He said
that these ones are new types and will be described in the upcoming TIFF
specification.

> - If so, perhaps they should be added to tiff.h?

The only place where those types appeared was that Wiki, so I don't
think we should not do nothing to support the new types until the more
verbosive description.

> - The actual question I'm having is however: what is the size and
> layout of the TIFF_COMPLEX datatype (if it indeed exisist)?

That is good question. But it can only be answered by our colleagues
from Adobe.

					Andrey

-- 
Andrey V. Kiselev
Home phone:  +7 812 5970603  ICQ# 26871517
_______________________________________________
Tiff mailing list
Tiff@remotesensing.org
http://xserve.flids.com/mailman/listinfo/tiff
