From owner-tiff@olympiakos.com  Sat Jan 29 17:21:11 2000
Received: (from uucp@localhost)
	by smtp02.oce.nl (8.9.3/8.9.3) id RAA12187
	for rvdt@smtp02; Sat, 29 Jan 2000 17:21:10 +0100 (MET)
>Received: from gate7.olympiakos.com ([207.176.88.85])
	by oce.nl (8.9.0/8.9.0) with ESMTP id RAA12360;
	Sat, 29 Jan 2000 17:17:20 +0100 (MET)
Received: from localhost (daemon@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) with SMTP id LAA26441;
	Sat, 29 Jan 2000 11:12:39 -0500
Received: by gate7.olympiakos.com (bulk_mailer v1.9); Sat, 29 Jan 2000 11:12:22 -0500
Received: (from majordom@localhost)
	by gate7.olympiakos.com (8.9.3/8.9.3) id LAA26428
	for tiff-outgoing; Sat, 29 Jan 2000 11:12:21 -0500
X-Authentication-Warning: gate7.olympiakos.com: majordom set sender to owner-tiff@olympiakos.com using -f
Received: from postoffice.effingham.net (Mail.effinghamchamber.org [206.29.80.6])
	by gate7.olympiakos.com (8.9.3/8.9.3) with ESMTP id LAA26425
	for <tiff@olympiakos.com>; Sat, 29 Jan 2000 11:12:19 -0500
Received: from [216.43.19.120] by postoffice.effingham.net
          (Post.Office MTA v3.5.3 release 223 ID# 0-58135U3500L250S0V35)
          with ESMTP id net for <tiff@olympiakos.com>;
          Sat, 29 Jan 2000 10:12:08 -0600
X-Sender: buddy@mail.effingham.net
Message-Id: <v03130300b4b8c0cce342@[216.43.19.15]>
In-Reply-To: <vtu2jx9pj2.fsf@cliwe.ping.de>
References: Paul Kaiser's message of "Fri, 28 Jan 2000 19:15:33 -0600"
 <v03130300b4b7ee487663@[216.43.19.88]>
Mime-Version: 1.0
Date: Sat, 29 Jan 2000 10:12:01 -0600
To: tiff@olympiakos.com
From: Paul Kaiser <buddy@effingham.net>
Subject: Re: tiff2ps: G4 compression in PostScript]
Sender: owner-tiff@olympiakos.com
Content-Type: text/plain; charset="us-ascii"

>Surely the most important property is that the results are identical
>*after* expansion.  I don't remember whether the ITU specifies the
>encoder in such a way that there is exactly one legal encoding of a
>given image.  In fact, I suspect it does not.

Yes, you're right as I look at it closer. There are three methods an
encoder can choose from when encoding, and it can switch at any time
(though it will indicate this switch in the data.) Also, as you say, it can
choose to compress or not

I know that I have put together my PostScript code correctly, and I have
tried G4 compressed images from as many sources as I can get (a whole "2").
Yet it still isn't working.

I suspect that a PostScript interpreter has specific restrictions, then. I
just ordered the "Green Book" on PostScript programming, so I'll see in a
few days. I have all of the other PostScript books, all of the recent
PostScript and PDF stuff of the Adobe site -- none of it sheds light on any
of it. I hope the green book says "it has to be this-a-way" so we can get
on with this.

Take care,
Paul Kaiser



