Status: Read
Received: from [207.176.88.85] by phillip.cerious.com (NTMail 3.03.0017/7.aaxh) with ESMTP id pcrews for <pcrews@cerious.com>; Thu, 5 Oct 2000 16:46:47 -0400
Received: from localhost (daemon@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) with SMTP id QAA01709;
	Thu, 5 Oct 2000 16:42:47 -0400
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Thu, 5 Oct 2000 16:38:51 -0400
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) id QAA01605
	for tiff-outgoing; Thu, 5 Oct 2000 16:38:51 -0400
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from mailserver.mobiusg.com (mail.mobiusg.com [209.137.82.13])
	by gate7.olympiakos.com (8.9.3/8.9.3) with ESMTP id QAA01602
	for <tiff@olympiakos.com>; Thu, 5 Oct 2000 16:38:49 -0400
Received: by mailserver.ckfr.com with Internet Mail Service (5.5.2650.21)
	id <4KPPHNQC>; Thu, 5 Oct 2000 14:44:01 -0400
Message-ID: <D1DFB211BB3ED111B01F00A0240D15550151E5FD@mailserver.ckfr.com>
From: Chris Losinger <ChrisL@mobiusg.com>
To: tiff@olympiakos.com
Subject: RE: PHOTOMETRIC_YCBCR
Date: Thu, 5 Oct 2000 14:43:59 -0400 
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2650.21)
Content-Type: text/plain;
	charset="iso-8859-1"
Sender: owner-tiff@olympiakos.com

> What do people think about actually writing the code to read 
> these proprietary
> TIFF-variants?  That would mean using clumsy temp files to 
> extract JFIF files
> and using then libjpeg to access a raster in memory, or 
> perhaps some other
> method would work.


	personally, i think it would be fantastic. if we can't get these
companies from creating these OJPEGs, our refusing to read them (via
LibTiff's refusing to read them) only makes us look bad in the eyes of our
customers.

	-c
