Bug 692759 - Anti-Aliased output incorrect
Summary: Anti-Aliased output incorrect
Status: RESOLVED DUPLICATE of bug 692688
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: Graphics Library (show other bugs)
Version: 9.04
Hardware: PC Linux
: P4 normal
Assignee: Chris Liddell (chrisl)
URL:
Keywords:
: 692808 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-12-23 09:48 UTC by Juliusz Gonera
Modified: 2012-04-02 14:25 UTC (History)
1 user (show)

See Also:
Customer:
Word Size: ---

Attachments
pdf input (101.29 KB, application/pdf)
2011-12-23 09:48 UTC, Juliusz Gonera 		Details
output with AA (artifacts) (2.05 MB, image/jpeg)
2011-12-23 09:49 UTC, Juliusz Gonera 		Details
output without AA enabled (2.23 MB, image/jpeg)
2011-12-23 09:50 UTC, Juliusz Gonera 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Juliusz Gonera 2011-12-23 09:48:50 UTC 
Created attachment 8234 [details]
pdf input

Sample pdf input & resulting jpg output included. 


Invocation:
-----------

    ghostscript-9.04 -q -dBATCH -dNOPAUSE -sDEVICE=jpeg -r200x200 -dJPEGQ=90 -dTextAlphaBits=4 -sOutputFile=page_%02d.jpg pg_0019.pdf

The resulting JPG file has processing artifacts (the title of the page is messed up)

Invoking ghostscript without AA gives the expected result:

    ghostscript-9.04 -q -dBATCH -dNOPAUSE -sDEVICE=jpeg -r200x200 -dJPEGQ=90 -dTextAlphaBits=4 -sOutputFile=page_%02d.jpg pg_0019.pdf
Comment 1 Juliusz Gonera 2011-12-23 09:49:38 UTC 
Created attachment 8235 [details]
output with AA (artifacts)
Comment 2 Juliusz Gonera 2011-12-23 09:50:35 UTC 
Created attachment 8236 [details]
output without AA enabled
Comment 3 Ken Sharp 2011-12-23 10:04:26 UTC 
Changed title, looks like this is really a problem with anti-aliasing, since the non-AA output is OK.
Comment 4 Chris Liddell (chrisl) 2012-01-22 12:11:06 UTC 
*** Bug 692808 has been marked as a duplicate of this bug. ***
Comment 5 Henry Stiles 2012-03-22 19:13:39 UTC 
I guess once determined this is not a font problem it should go to Michael along with 692808.
Comment 6 Chris Liddell (chrisl) 2012-04-02 14:25:40 UTC 
Seems to work now - I'd guess as a result of Ray's recent clist fixes.

*** This bug has been marked as a duplicate of bug 692688 ***