Received: from sgi.sgi.com (192.48.153.1) by cerious.com
 with SMTP (Apple Internet Mail Server 1.1.1); Tue, 4 Mar 1997 03:48:00 -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 AAA27821; Tue, 4 Mar 1997 00:36:18 -0800
Received: (from daemon@localhost) by cthulhu.engr.sgi.com (950413.SGI.8.6.12/960327.SGI.AUTOCF) id HAA06560 for tiff-list; Tue, 4 Mar 1997 07:07:30 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 XAA06555 for <tiff-relay@relay.engr.sgi.com>; Mon, 3 Mar 1997 23:07:27 -0800
Received: from mail.Germany.EU.net (mail.germany.eu.net [192.76.144.65]) by sgi.sgi.com (950413.SGI.8.6.12/950213.SGI.AUTOCF) via ESMTP id XAA13720 for <tiff@sgi.com>; Mon, 3 Mar 1997 23:07:23 -0800
Received: by mail.Germany.EU.net with SMTP (5.59+:34/EUnetD-2.6.1.i) via EUnet
	id IAA15757; Tue, 4 Mar 1997 08:07:06 +0100
Received: from aragorn.v-ppb.zeiss.de by oslo.zeiss.de; Tue, 4 Mar 97 08:05:37 +0100
Received: from aragorn 
	by aragorn.v-ppb.zeiss.de with SMTP (950413.SGI.8.6.12/+CZGEN-1.0+1)
	via CZnet for oslo
	id IAA12261; Tue, 4 Mar 1997 08:05:56 +0100
Message-ID: <331BC9D3.41C6@zeiss.de>
Date: Tue, 04 Mar 1997 08:05:55 +0100
From: Rainer Wiesenfarth <wiesenfarth@zeiss.de>
Organization: Carl Zeiss, Abt. Phm-A
X-Mailer: Mozilla 3.01SGoldC-SGI (X11; I; IRIX 6.3 IP32)
MIME-Version: 1.0
To: "McDougle, Brian" <Brian_McDougle@cissc.canon.com>
CC: "'tiff@sgi.com'" <tiff@sgi.com>
Subject: Re: Questions on proposed replacement TIFF/JPEG Spec.
References: <c=US%a=_%p=Canon_Informatio%l=CISSC002-970304013801Z-8481@cissc002.cisoc.canon.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-tiff@relay.engr.SGI.COM
Precedence: bulk
Status: R

McDougle, Brian wrote:
> 
> I recently downloaded the README file located in the graphics/tiff
> section of the ftp site sgi.com and had some questions regarding the
> proposed replacement for the TIFF 6.0 TIFF/JPEG Specification.
> 
> You mention in the 'Overview of the solution' section that the
> JPEGTables field can be stored only once for a multi-segment TIFF file.
> First, is this 'field' also called a TIFF Tag? Second, am I correct that
> when you refer to a multi-segment TIFF file you are referring to a TIFF
> file with multiple images (i.e. a multipage TIFF file), or is
> "multi-segment" in reference to the JPEG compression? Third, if a
> multipage TIFF file is generated will each image that uses this proposed
> compression scheme require a separate JPEGTables field?
> 

1. Yes, it is a TIFF Tag.
2. No, a multi-segment TIFF _image_ is an image that consists of more
   than one strip or tile. As I understand it, JPEGTables is stored for
   one image and applies to all strips/tiles of this image. These
   strips/tiles are JPEG compressed individually.
3. Yes. JPEG compression is not a matter of a TIFF _file_, but of
   TIFF _images_. If more than one image form a file, each of these
   images has it's own JPEGTables. Furthermore, it is even possible
   (though not common) to have e.g. three images in a file where
   the first is a JPEG compressed RGB image, the second a uncompressed
   greyscale and the third a CCITT whatever compressed bilevel image.

> [...]
> Thank you in advance for your clarifications.
> 
> Sincerely,
> 
> Brian McDougle
> Product Engineer, Imaging Products
> ISV Support Group
> Canon Information Systems, Inc.
> 3187 Red Hill Avenue
> Suite 100
> Costa Mesa, CA 92626 USA
> Ph: (714) 438-7185      Fax: (714) 437-7272
> Email: bmcdougle@cissc.canon.com

Greetings Rainer

-- 
| This mail came from:
| Rainer Wiesenfarth                 Tel: +49 7364 203321
| c/o Carl Zeiss, Div. Phm-A         Fax: +49 7364 202829
| 73446 Oberkochen                e-mail: Wiesenfarth@zeiss.de
| Germany
