On Fri, 2008-04-11 at 09:11 +0200, Giuseppe Sacco wrote:
> Hi Ross,
> libtiff (used by hylafax) currently cannot manage 16bit depth images.
> Could you please try to run "convert" with option "-depth 8" in your
> script?
>
> Bye,
> Giuseppe
>
That fixed it. Thank you very much.
There's still t
Hi Ross,
libtiff (used by hylafax) currently cannot manage 16bit depth images.
Could you please try to run "convert" with option "-depth 8" in your
script?
Bye,
Giuseppe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
I double-checked that the output of convert is 16 bit, since I realized
the document might have received further processing before ending up in
docq. The 16 bits are from convert:
$ convert -density 80.00x77.00 -units PixelsPerCentimeter \
-geometry 1687x2120! silly.png tiff:silly.tiff
$ i
The old documents output by imagemagick convert seem to be 8 bit, while
the new ones are 16 bit. Here's the result of identify on the file I
just sent privately, and then on one that I was able to fax a month ago:
corn:/var/spool/hylafax/docq# identify -verbose doc320.tif.72
Image: doc320.tif.72
Hi Ross,
could you please send me, privately, these three files?
Thanks,
Giuseppe
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Package: hylafax-server
Version: 2:4.4.4-5
Severity: normal
I am unable to send a fax which consists of 3 files: a postscript cover
page (produced by kword) and 2 images which start as png files and are
manipulated (resized) by imagemagick.
If this is a general problem, it warrants higher severi
6 matches
Mail list logo
