Bug 687111 - Quality of output wth gs8.11 for pdfwrite device is faded as compared to gs6.12
Summary: Quality of output wth gs8.11 for pdfwrite device is faded as compared to gs6.12
Status: NOTIFIED DUPLICATE of bug 687047
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PDF Writer (show other bugs)
Version: 8.11
Hardware: PC Windows 2000
: P1 major
Assignee: Igor Melichev
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-10-28 03:02 UTC by Rakesh Sawan
Modified: 2011-09-18 21:46 UTC (History)
0 users

See Also:
Customer: 130
Word Size: ---


Attachments
Input postscript document (39.15 KB, application/postscript)
2003-10-28 03:04 UTC, Rakesh Sawan
Details
Output PDF document from GS6.12 (4.68 KB, application/pdf)
2003-10-28 03:04 UTC, Rakesh Sawan
Details
Output PDF document from GS8.11 (12.64 KB, application/pdf)
2003-10-28 03:06 UTC, Rakesh Sawan
Details
Command line used for coverting ps to pdf with gs6.12 (157 bytes, text/plain)
2003-10-28 03:07 UTC, Rakesh Sawan
Details
Command line used for coverting ps to pdf with gs8.11 (157 bytes, text/plain)
2003-10-28 03:08 UTC, Rakesh Sawan
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Rakesh Sawan 2003-10-28 03:02:36 UTC
We are using pdfwrite device with gs to convert a postscript file to pdf file.

While migrating from gs6.12 to gs8.11 we found that the quality of output 
generated from pdfwrite device is deteriorated.

The output file generated using gs8.11 when viewed in Acrobat Reader 5.0 
appears faded as compared to the output generated using gs6.12.

Find following documents attached with this bug report. 

1)input.ps - The input postscript document
2)6.12.pdf - Output generated using gs6.12
   pstopdf_6.12.sh - Contains the command line used for converting the 
   document to pdf.

3)8.11.pdf - Output generated using gs8.11
  pstopdf_8.11.sh - Contains the command line used for converting the
  document to pdf.


We performed similar tests with gs8.0 and found that the quality of output was 
worse than it is in gs8.11.
Comment 1 Rakesh Sawan 2003-10-28 03:04:06 UTC
Created attachment 337 [details]
Input postscript document
Comment 2 Rakesh Sawan 2003-10-28 03:04:56 UTC
Created attachment 338 [details]
Output PDF document from GS6.12
Comment 3 Rakesh Sawan 2003-10-28 03:06:14 UTC
Created attachment 339 [details]
Output PDF document from GS8.11
Comment 4 Rakesh Sawan 2003-10-28 03:07:11 UTC
Created attachment 340 [details]
Command line used for coverting ps to pdf with gs6.12
Comment 5 Rakesh Sawan 2003-10-28 03:08:00 UTC
Created attachment 341 [details]
Command line used for coverting ps to pdf with gs8.11
Comment 6 Alex Cherepanov 2003-10-28 11:19:18 UTC
There's no quality deterioration but there are a few issues where GS can improve.

The old file uses /Courier and it is not embedded. Probably, on some systems
standard fonts are rendered in some special way, for instance from a hand-tyned
raster font. This may explain why the old file looks better.

The new file has /NimbusMonL-Regu as an embedded subset. On Acrobat Reader 5
there's little difference, except that /Nimbusmon-L is a bit darker.
However, GS could recognize that the original file is asking for /Courier
and use /Courier in the PDF file. Even for the embedded /NimbusMonL-Regu
it is better to keep the original name unstead of using some random name
the font was renamedin thePS file.

Comment 7 Igor Melichev 2003-10-30 01:32:21 UTC
This bug is related to the bug 687047 .
Actually this one is a duplicate of that.
For a while we keep it open just for testing purpose.
Comment 8 Igor Melichev 2003-10-31 14:18:36 UTC

*** This bug has been marked as a duplicate of 687047 ***
Comment 9 Marcos H. Woehrmann 2011-09-18 21:46:41 UTC
Changing customer bugs that have been resolved more than a year ago to closed.