Randy McMurchy wrote:
Alexander E. Patrakov wrote these words on 10/12/05 21:59 CST:
GGV allows tinkering with Ghostscript settings. Last time I looked at
Evince, it didn't have this feature. Has this changed?
I'm not sure how else to say this other than just to come out and
say the first thing that comes to mind.
I'm proposing a change. You're asking questions which I don't have
the time nor desire to research. If you doubt the proposal, please
do the proper research to either provide a good technical argument
against it, or agree with it, or say you don't have any comment.
This is not "against evince". This is: "maybe we should keep both for
some time".
What I am complaining about is in fact an image quality issue with
certain PostScript files (1-bit high-resolution bitmaps in disguise)
that GGV has an easy runtime workaround for, and evince doesn't. As a
PDF viewer, evince is very good.
Testcase:
Scan a page from your favourite book using xsane as lineart (not
grayscale!) at 600 dpi, save the result in PostScript format. View it in
GGV and in Evince with the default settings. The result is unacceptably
bad in both: no antialiasing. The issue is easily correctable in GGV:
Edit -> PostScript Viewer Preferences, go to the Ghostscript tab, add
the following to the "Antialias" edit box:
-dDOINTERPOLATE
For some other types of documents, adding -dTextAlphaBits=4
-dGraphicsAlphaBits=4 also improves rendering quality at the cost of CPU
time.
Such setting is just not available in evince at runtime. In recent
versions of evince, it is available at compile time, though, by sedding
the AA_PARMS variable in the ./configure script. Please add such
instructions to the evince page.
--
Alexander E. Patrakov
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
