Return-Path: <tiff-bounces@remotesensing.org>
Received: from inmx013.isp.belgacom.be (inmx013.isp.belgacom.be [195.238.2.216])
        by mailst034.isp.belgacom.be (8.12.11/8.12.11/Skynet-MAILSTORE-2.14) with ESMTP id i92Ef7aU014429
        for <joris.at.lebbeke@skynet.be>; Sat, 2 Oct 2004 16:41:07 +0200
        (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 inmx013.isp.belgacom.be (8.12.11/8.12.11/Skynet-IN-2.32) with ESMTP id i92EelBM023523
        for <joris.at.lebbeke@skynet.be>; Sat, 2 Oct 2004 16:40:50 +0200
        (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 2D06734844C; Sat,  2 Oct 2004 10:40:27 -0400 (EDT)
X-Original-To: tiff@remotesensing.org
Delivered-To: tiff@remotesensing.org
Received: from ahk.pu.ru (ahk.pu.ru [193.124.85.198])
	by xserve.flids.com (Postfix) with ESMTP id EE88D348415
	for <tiff@remotesensing.org>; Sat,  2 Oct 2004 10:40:24 -0400 (EDT)
Received: from wg.pu.ru (wg.pu.ru [193.124.85.219])
	by ahk.pu.ru (8.12.11/8.12.9) with ESMTP id i92EeNRp049276
	for <tiff@remotesensing.org>; Sat, 2 Oct 2004 18:40:23 +0400 (MSD)
	(envelope-from dron@ak4719.spb.edu)
Received: (from uucp@localhost)
	by wg.pu.ru (8.9.1a/8.9.1) with UUCP id OAA28334
	for tiff@remotesensing.org; Sat, 2 Oct 2004 14:40:23 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
	i92EG53M029914
	for <tiff@remotesensing.org>; Sat, 2 Oct 2004 18:16:05 +0400
Received: (from dron@localhost)
	by ak4719.spb.edu (8.12.11/8.12.11/Debian-5) id i92EG5gA029911
	for tiff@remotesensing.org; Sat, 2 Oct 2004 18:16:05 +0400
From: Andrey Kiselev <dron@ak4719.spb.edu>
Date: Sat, 2 Oct 2004 18:16:05 +0400
To: tiff@remotesensing.org
Subject: Re: [Tiff] quad-tile
Message-ID: <20041002141605.GC12254@ak4719.spb.edu>
Mail-Followup-To: tiff@remotesensing.org
References: <415D625F.5090107@pobox.com>
	<001201c4a7c1$6e6165a0$e8c8c950@dfgrrxsknr4e>
Mime-Version: 1.0
Content-Type: text/plain; charset=koi8-r
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <001201c4a7c1$6e6165a0$e8c8c950@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
Content-Transfer-Encoding: 8bit
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: 37578ddcf48809e99c1ae293a65f3fbc

On Fri, Oct 01, 2004 at 04:17:38PM +0200, Joris wrote:
> > The libtiffpic suite (thats where you got this, right?)
> This particular file comes from a compressed file named
> 'pics-3.6.1.tar.gz', that in turn comes from some LibTiff place (don't
> recall where exactly, but somewhere on your pages for sure). I seem to
> remember the was a similar testsuite in the 3.5.7 days, that also
> contained variants of this same image, though I never bothered to look
> at the tagsets more closely at that time. So probably its been around
> for quite a while. So if 'libtiffpic suite' is anything new, than
> you're referring to a source I know nothing about and this image did
> not come from.

Joris,

pics-3.6.1.tar.gz isšthe same testsuite you thinking about. I have added
one or two images to it and it is now packaged with the same naming
scheme as libtiff itself, so users can easily pick-up thwe latest
variant.

> > So, I think the better solution might be to segregate our suite of
> > test images into files considered to be standard and valid, and
> > those that are invalid but that we want to work with anyways for
> > purposes of interoperability.
> 
> Yes, absolutely defenetly.

I'm agree. That will be done for 3.7.0.

> > I have been leaving the sample image management up to Andrey though,
> > so perhaps he will have further thoughts.  I do believe he is
> > planning to augment the set of test images as he works on a libtiff
> > test suite.
> 
> Ah, I was toying with the same idea. Seeing I can contribute so little
> C (let alone makefiles ;-)), perhaps this way I can ease Andrey's
> workload?

The test suite I'm working on right now doesn't use the external image
set. All test images are generated by the test cases from the internal
data arrays and being compared with that images after reading the files
back. Any help will be greatly appreciated.

> If not, perhaps I can at least contribute a suggestion: a
> HTML index into the testimage, explaining what is what, and what is
> valid, and including tag dumps (and maybe even a reference thumbnail
> in a HTML-friendly and independent format like PNG) could increase the
> usefullness of a testimage suite tremendously.

There is a short README file in the pics package, but I'm agree, it is
not enough for good test suite.

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