Received: by whizzer.wpd.sgi.com (/911001.SGI)
	 id AA09748; Thu, 7 Apr 94 18:56:45 GMT
Received: from sgi.sgi.com by whizzer.wpd.sgi.com via SMTP (/911001.SGI)
	for /usr/people/sam/majordomo/wrapper resend -l tiff -h sgi.sgi.com -f tiff-owner -s -m "-oi -odq -om" tiff-list id AA09736; Thu, 7 Apr 94 11:56:41 -0700
Received: from sugar.NeoSoft.COM by sgi.sgi.com via SMTP (931110.SGI/910110.SGI)
	for tiff-relay@whizzer.wpd.sgi.com id AA18153; Thu, 7 Apr 94 11:56:39 -0700
Received: by sugar.NeoSoft.COM id AA17576
  (5.65c/IDA-1.4.4 for tiff@sgi.com); Thu, 7 Apr 1994 13:56:07 -0500
From: Neuralog <neuralog@sugar.NeoSoft.COM>
Message-Id: <199404071856.AA17576@sugar.NeoSoft.COM>
Subject: Bad Gamma Fax Tiff Files
To: tiff@sgi.sgi.com
Date: Thu, 7 Apr 1994 13:56:04 -0500 (CDT)
X-Mailer: ELM [version 2.4 PL23]
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 728       
Sender: tiff-owner@sgi.sgi.com


Hi,

I'm about to add support for Gamma Fax group 3 tiff files into the
latest v3.3 beta.  But before I start I wanted to see if someone
else had solved the problem.

Basically the problem with the files are that:

1. The RowsPerStrip tag is 0
2. The ImageLength tag is 0

This of course upsets libtiff!
My current work around is to run the files through fax2tiff which
simply gives a few warnings as it passes through the header, but
picks up just fine once it gets to the G3 data.

Using fax2tiff is not an acceptable long term solution so...
If anybody has a better solution please let me know.
With the popularity of GammaLink products I'm sure many 
would benefit from such a fix.


Thanks,
Ken Land
neuralog@neosoft.com



