[wplug] Hylafax produces corrupt tiffs?

[Duncan Hutty]

Mike, thanks for your suggestions.

On Thu, Mar 04, 2004 at 11:13:32AM -0500, Mike Kuentz (2) wrote:
<snip>
> > However, when I attempt to view the .tif, it either errors 
> > with 'bad code word at scan line #' where # implies most 
> > lines or shows a corrupt image, depending on the viewer used.
> 
> On the machine or after it's been emailed if you use that?

on the machine. I'm not emailing, the intention is to use a hylafax client, such as WHFC, and the hylafax protocol.

<snip>
> 
> Try the tiffcheck program that comes with Hylafax.  It tells 
> you if the .tiff is faxable.  If it's faxable, then it's readable.
> man tiffcheck for more info.  You could also try tiffdump.

$ tiffcheck /var/spool/hylafax/recq/fax00008.tif
OK
$

 
> > 
> > Best of all, can anyone please suggest how I can get a usable 
> > tiff? Or is it possible to get hylafax to produce some other 
> > format such as PDF or PNG?
> 
> See (under the hylafx dir) bin/faxrcvd
> TIFF2PS=tiff2ps
> PS2PDF=ps2pdf
> #
> # Permit various types of attachment types: ps, tif, pdf
> # Note that non-ASCII filetypes require metamail.
> # pdf requires tiff2ps and ps2pdf
> #
> FILETYPE=ps
> 

tiff2ps gave many warnings like 'bad code word at scanline x' and 'premature EOL at scanline y', but it created a postscript file which I ran through ps2pdf. The pdf was valid, but looked like garbage not the test page.

> 
> Or if the tiff is valid and it's just your viewer, ImageMagick
> has a program that converts tiffs to just about any image 
> format you want
> 

ImageMagick displayed the tiff without complaining but it looked like garbage.

It seems that the tiff created is valid enough for tiffcheck but just describing the correct pattern. Do you think this implies a problem with the modem, the hylafax/etc/config.ttyS0, the line or something else?

Thanks again for your input.
-- 
Duncan Hutty