Received: from sgi.sgi.com (192.48.153.1) by cerious.com
 with SMTP (Apple Internet Mail Server 1.1.1); Tue, 11 Feb 1997 22:34:47 -0500
Received: from cthulhu.engr.sgi.com (cthulhu.engr.sgi.com [192.26.80.2]) by sgi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id TAA23898; Tue, 11 Feb 1997 19:31:27 -0800
Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id CAA16651 for tiff-list; Wed, 12 Feb 1997 02:38:06 GMT
Received: from sgi.sgi.com (sgi.engr.sgi.com [192.26.80.37]) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) via ESMTP id SAA16646 for <tiff-relay@relay.engr.sgi.com>; Tue, 11 Feb 1997 18:38:05 -0800
Received: from sss.sss.pgh.pa.us (sss.pgh.pa.us [206.210.65.6]) by sgi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id SAA15257 for <tiff@fddi-sgi.engr.sgi.com>; Tue, 11 Feb 1997 18:38:00 -0800
Received: from sss.sss.pgh.pa.us (localhost [127.0.0.1])
	by sss.sss.pgh.pa.us (8.8.5/8.8.5) with ESMTP id VAA06584;
	Tue, 11 Feb 1997 21:37:36 -0500 (EST)
To: Henri Schueler <hschuele@Comnetix.COM>
cc: tiff@fddi-sgi.engr.sgi.com
Subject: Re: TIFF 6.0 JPEG or OJPEG_SUPPORT 
In-reply-to: Your message of Tue, 11 Feb 1997 19:23:43 -0500 
             <1.5.4.32.19970212002343.006ec03c@comnetix.com> 
Date: Tue, 11 Feb 1997 21:37:36 -0500
Message-ID: <6582.855715056@sss.pgh.pa.us>
From: Tom Lane <tgl@sss.pgh.pa.us>
Sender: owner-tiff@relay.engr.SGI.COM
Precedence: bulk
Status: R

Henri Schueler <hschuele@Comnetix.COM> writes:
> I have some jpeg tiff images that were created on a NeXTStep computer.
> tiffutil tells me they are 'Old-style JPEG', which is what I expect.
> I'm not able to build the software in a way to read them.

libtiff does not have, and never has had, support for the TIFF 6.0
(old-style) JPEG definition.  There are a few hooks where such support
could be added, but nothing to hook onto them.

TIFF Tech Note #2 explains all the ambiguities and other problems with
the 6.0 spec's handling of JPEG.  Given those problems, I suspect Sam's
not real interested in adding OJPEG support any more.

This of course leaves you with the problem of converting your NeXT files.
Your best bet might be a self contained, quick-and-dirty program to
extract the compressed data and write it out as a JFIF JPEG.  This would
be very easy if NeXT uses the "JPEGInterchangeFormat" convention, and
probably not too much harder if it doesn't.  But since I don't know just
how NeXT interpreted the ambiguities in TIFF 6.0, I can't say exactly
what you need to do.

Has anyone already looked at this problem and written a converter for
NeXT TIFF/JPEG files?

			regards, tom lane
			organizer, Independent JPEG Group
