Bug 687387 - pdf file created by ghostscript displays with boxes instead of spaces
Summary: pdf file created by ghostscript displays with boxes instead of spaces
Status: NOTIFIED INVALID
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PDF Writer (show other bugs)
Version: master
Hardware: All All
: P2 normal
Assignee: Igor Melichev
QA Contact: Bug traffic
URL:
Keywords:
: 688315 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-03-24 08:53 UTC by Jack Moffitt
Modified: 2008-12-19 08:31 UTC (History)
1 user (show)

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


Attachments
test.pdf (3.92 KB, application/pdf)
2004-04-02 02:55 UTC, Igor Melichev
Details
3pageportrait-.ps (14.41 KB, application/postscript)
2004-04-08 03:47 UTC, Igor Melichev
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jack Moffitt 2004-03-24 08:53:32 UTC
Customer reports that after distilling the attached ps file, the resulting pdf
displays fine in Ghostscript, but spaces are replaced by boxes in Acrobat Reader
6.0.1 on Windows.  I've confirmed in 6.0.0 on Windows as well, but 6.0.1 on Mac
OS X seems to display the file correctly.
Comment 1 Jack Moffitt 2004-03-24 08:54:19 UTC
Created attachment 587 [details]
3pageportrait.ps
Comment 2 Igor Melichev 2004-03-25 09:59:38 UTC
Can't reproduce with Adobe reader 6.0.0, 6.0.1 and the current HEAD.
Likely it's a duplicate of the Bug 687351, which was fixed 10 days ago.
Comment 3 Chi-To Shiu 2004-03-26 13:17:47 UTC
I've downloaded the src from HEAD, and built it and is still seeing the problem 
with Adobe Reader 6.0.1 on Windows 2000.

I wonder if the fonts set I have been using is one of the factor.  BTW we are 
using fonts from soft horizons.

Anyhow here is how I have been invoking gs.

gs  -q -dDEBUG -dBATCH -dNOPAUSE -sDEVICE=pdfwrite -I../fonts/Soft_Horizons  -
I../lib -sOutputFile=test.pdf 3pageportrait.ps

Please let me know if I am doing something wrong.
Thanks.
--Chi-To
Comment 4 Igor Melichev 2004-03-30 08:38:10 UTC
Please give me an URL for Soft Horizons fonts, exactly the version you're using.
Comment 5 Igor Melichev 2004-03-30 09:40:49 UTC
Also please attach the PDF created with GS in your environment.
Comment 6 Igor Melichev 2004-04-02 02:55:54 UTC
Created attachment 609 [details]
test.pdf

Attaching a PDF created by the user. It displays fine. Thus the problem is not
related to Ghostscript, something is wrong in the user's system. I intend to
close the bug.
Comment 7 Igor Melichev 2004-04-06 23:47:58 UTC
No responce from the user.
I guess this issue is either an user error or a non-Ghostscript problem in his 
system.
Comment 8 Igor Melichev 2004-04-08 00:33:56 UTC
Rather I can't reproduce boxes, now I can see an unpleasant thing in the 
generated PDF :

24 0 obj
<</Type/Encoding/Differences[
32/.notdef]>>
endobj

With some viewers/fonts it may cause boxes instead spaces. Likely the user's 
system implements .notdef as a box, and my one as a space.
Comment 9 Igor Melichev 2004-04-08 03:47:19 UTC
Created attachment 615 [details]
3pageportrait-.ps

Attaching a reduced test, which reproduces the problem.
Pay attention to the line 
    
    CharCol256Encoding 32 get =

It prints .notdef .
Thus the problem is caused by Adobe's Pscript.dll Version 5.0 bug, which puts
/.notdef instead /space . There is no Ghostscript bug. The problem to be
reported to Adobe.
Comment 10 Igor Melichev 2004-04-08 03:56:41 UTC
Adobe Distiller replaces the buggy encoding with WinAnsiEncoding. It looks as a 
special workaround for the buggy CharCol256Encoding. Once again we can see that 
Adobe products are bug to bug compatible. We could provide a workaround 
specific to CharCol256Encoding. Customers are welcome with a NRE proposal.

I also recommed the customer to analyze where the CharCol256Encoding encoding 
comes from, and how to configure his system with a better encoding.

I close this bug as invalid, because it doesn't need more engineering effort 
unless the customer orders a special workaround for it.

Comment 11 leonardo 2005-10-11 04:30:40 UTC
*** Bug 688315 has been marked as a duplicate of this bug. ***