Status: Read
Received: from [207.113.13.68] by phillip.cerious.com (NTMail 3.03.0017/7.aaxh) with ESMTP id pcrews for <pcrews@cerious.com>; Thu, 10 Jun 1999 06:06:04 -0400
Received: from localhost (bin@localhost)
	by gate7.olympiakos.com (8.8.7/8.8.7) with SMTP id FAA25177;
	Thu, 10 Jun 1999 05:45:08 -0400
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Thu, 10 Jun 1999 05:44:10 -0400
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.8.7/8.8.7) id FAA25155
	for tiff-outgoing; Thu, 10 Jun 1999 05:44:09 -0400
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from ina.de (hp00290.ina.de [159.51.6.54])
	by gate7.olympiakos.com (8.8.7/8.8.7) with ESMTP id FAA25152
	for <tiff@olympiakos.com>; Thu, 10 Jun 1999 05:44:05 -0400
Received: from ina.de (de00009.ina.de [159.51.14.122])
	by ina.de (8.9.1/8.9.1) with ESMTP id LAA16385
	for <tiff@olympiakos.com>; Thu, 10 Jun 1999 11:43:32 +0200 (METDST)
Message-ID: <375F89D1.B5F87E0B@ina.de>
Date: Thu, 10 Jun 1999 11:48:01 +0200
From: Klaus Bartz <bartzkau@ina.de>
X-Mailer: Mozilla 4.05 [en] (X11; I; OSF1 V4.0 alpha)
MIME-Version: 1.0
To: tiff@olympiakos.com
Subject: Re: Large File Support
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-tiff@olympiakos.com

Hi all,

from time to time there is a discussion on this list of extensions
to TIFF.
There is not only a problem with large files. Six years null-work
( last TTN in 1993 ?) will have it consequence.

I think, to change or expand it is the second step. 
The last revision of TIFF  was released at june 3, 1992. 
I have seen one EMail from a worker at Adobe in this list dated 
with 21 Feb 1997 pronoucing a draft of the TIFF 7.0. 
But after it never seen, never heard somthing of it. 
I think, Adobe will never release a new revision.

Ok, today there are some people which thinking for a extended format.
That is the first point, I think.

TIFF/IT ? For a look to it I should not pay two pence, the
price is over hundred Swiss Franken. To expensive too see, that
the spec will not help me ...

Other formats ? I do not know some which are public and can support all
my requirements - MultiPage, 1 - 32 BitsPerPixel mixed in one file, tiles
for large images, losy and lossless compression, resolution reduced
childs, and so on.
Additional I like the tagged format ( is simple to read with a hex
editor). The other format from Adobe is not so simple ...

PNG ? not the best for 1 bpp and very big images.

An own format ? No, customers will not have it.

I do not know how to create a public format ( RFC's, patent analysis,
and more shit).
I know, it will coast much time.

If a group will be established for it, I will work with - if possible.



My list for a revision is:

1. An active "police" to handle new or/and private extensions.

2. Removing old "shit" ( e.g. FillOrder 2 ).

3. Clear definitons ( e.g. PhotometricInterpretation and EOFB handling
       with CompressionFormat CCITT T.6).

4. A IFD lookup table after the FileHeader ( we have customers which
       means that they must have 1000 or more pages in one file ...).
       Tag 297 is not practicable.

5. New compression formats ( deflate, bzip2, may be as extension
       JBIG, wavlet ... )

6. IFD in front of bin data ( better for JAVA impl. ).

Facultative 64 bit support.


Klaus

-- 
-------------------------------------------------------------------
Dr. Klaus Bartz                                     bartzkau@ina.de
COI GmbH / Abt. KOS3    Industriestr. 1-3    D-91072 Herzogenaurach
Tel: +49 (9132) 82-3433                        Fax: +49-9132-824959
