Re: [hylafax-users] Ghostscript Anti-Aliasing For Better Quality Faxes

[Lee Howard <faxguy@xxxxxxxxxxxxxxxx>]

A. Kalten wrote:

> Specifically, when this
> parameter is set to maximum, -dTextAlphaBits=4, the fax file created
> is significantly better in quality when using text material created
> with OpenOffice or LaTeX or enscript.

However, when using text material created from HylaFAX's textfmt (which 
gets used, for example, when sendfax is told to fax a text file) this 
makes the resulting TIFF unreadable.

These were the two tests that I ran:

echo test | textfmt | gs -q -sDEVICE=tiffg3 -dSAFER=true -dNOPAUSE 
-sPAPERSIZE=letter -dFIXEDMEDIA -r203.29x98 -sOutputFile=foo1.tif -

echo test | textfmt | gs -q -sDEVICE=tiffg3 -dSAFER=true -dNOPAUSE 
-sPAPERSIZE=letter -dFIXEDMEDIA -dTextAlphaBits=4 -r203.29x98 
-sOutputFile=foo2.tif -

foo1.tif looked good, clear, and readable - however foo2.tif was not 
even distinguishable as text.

So, I wonder if those other applications are generating a particular 
type of postscript that benefits from the *AlphaBits=4 setting... and if 
so, I wonder if that is detectable.

I also tried the escher.ps Ghostscript examples file, and while without 
the AlphaBits it looked good, with it the image lost its detail.  In 
fact, none of the examples files that I tested came out better with 
-d*AlphaBits=4 used... so I wonder if it's some particular way that the 
PostScript samples that you're using are being rendered.

Lee.

____________________ HylaFAX(tm) Users Mailing List _______________________
 To subscribe/unsubscribe, click http://lists.hylafax.org/cgi-bin/lsg2.cgi
On UNIX: mail -s unsubscribe hylafax-users-request@xxxxxxxxxxx < /dev/null
 *To learn about commercial HylaFAX(tm) support, mail sales@xxxxxxxxx*