Received: from [207.113.13.68] by phillip.cerious.com (NTMail 3.03.0017/7.aaxh) with ESMTP id pcrews for <pcrews@cerious.com>; Mon, 14 Jun 1999 11:45:02 -0400
Received: from localhost (bin@localhost)
	by gate7.olympiakos.com (8.8.7/8.8.7) with SMTP id LAA04266;
	Mon, 14 Jun 1999 11:29:26 -0400
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Mon, 14 Jun 1999 11:29:04 -0400
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.8.7/8.8.7) id LAA04244
	for tiff-outgoing; Mon, 14 Jun 1999 11:29:04 -0400
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from private.relium.com ([209.69.134.25])
	by gate7.olympiakos.com (8.8.7/8.8.7) with ESMTP id LAA04241
	for <tiff@olympiakos.com>; Mon, 14 Jun 1999 11:29:01 -0400
Received: from [209.69.134.22] by private.relium.com
 with ESMTP (Eudora Internet Mail Server 1.2.1); Mon, 14 Jun 1999 11:31:44 -0400
X-Mailer: Microsoft Outlook Express for Macintosh - 4.01 (295) 
Date: Mon, 14 Jun 1999 11:30:58 -0400
Subject: Re: Large File Support 
From: "Eric Shapiro" <shapiro@relium.com>
To: TIFF <tiff@olympiakos.com>
Mime-version: 1.0
X-Priority: 3
Content-type: text/plain; charset="US-ASCII"
Content-transfer-encoding: 7bit
Message-ID: <1282762592-177020120@private.relium.com>
Sender: owner-tiff@olympiakos.com


>I agree with that goal, but I think that Frank Warmerdam's idea (allow
>multiple separate TIFF files to be logically "tiled" together to form a
>huge image) is a more practical approach, for the reasons already
>mentioned by him and John Aldridge.
 
One nice thing that Apple did with QuickTime was that if a user opened
a compressed PICT file on a system without QuickTime, the image displayed
was a message suggesting that the user install QuickTime.

You can do this with your "control" file -- put an actual 1 bpp TIFF
image in it with the message "This file requires a newer TIFF viewer".
 
Splitting a single image into multiple files is a kludge, but it does
have the added plus of working with operating systems that don't support
large (> 2GB) files yet.
 
But, in the long run, a real 64-bit image file format is probably needed.
Would the current compressors (LZW, JPEG, etc) scale to 64-bit images, 
though? That is, can you even compress a > 2GB image using the standard
JPEG library? 
 
 -Eric

-------------------------------------------------
 Eric Shapiro                   eric@relium.com
 Relium Corp.                    www.relium.com
-------------------------------------------------
