Summary: | incorrect font rendering/missing glyphs from ps2pdf | ||
---|---|---|---|
Product: | Ghostscript | Reporter: | keinbiervorvier <keinbiervorvier> |
Component: | PDF Writer | Assignee: | Igor Melichev <igor.melichev> |
Status: | NOTIFIED FIXED | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | master | ||
Hardware: | PC | ||
OS: | Linux | ||
URL: | http://xxx.lanl.gov/ftp/exports/fig1.eps | ||
Customer: | Word Size: | --- | |
Attachments: |
fig1.eps
loop.ps.gz |
Description
keinbiervorvier
2004-09-07 12:35:42 UTC
Confirmed problems on CVS HEAD, althought not quite the same ones. If I create the pdf with CVS HEAD, Ghostscript can not read the file, failing with /undefined in --get--. Acrobat Reader can read the file, but some of the axis labels are missing. xpdf can't see the numbers on any of the files. Created attachment 885 [details]
fig1.eps
A local copy of the test file.
Comment on attachment 885 [details]
fig1.eps
When made a local copy of the test file, the extension was unintentionally
changed. Now changing it back.
Patch to GS_8_1X : http://www.ghostscript.com/pipermail/gs-cvs/2004-September/004795.html The test file fig1.eps has been added to comparefiles as Bug687660.ps . this patch fixed the incorrect rendering of the sample figure I provided, however it sends ps2pdf13 from current cvs HEAD into an infinite loop on the ps file http://lanl.arxiv.org/ftp/exports/loop.ps.gz i.e. "ps2pdf13 loop.ps" with src/gdevpdte.c revision 1.60 generates a pdf file, while it goes into an infinie loop with revision 1.61 Cheers T. Created attachment 961 [details]
loop.ps.gz
Comment on attachment 961 [details]
loop.ps.gz
Local copy of the sample file.
The problem with loop.ps depends on the bug 687669. A preparation patch http://www.ghostscript.com/pipermail/gs-cvs/2004-October/004922.html Patches http://www.ghostscript.com/pipermail/gs-cvs/2004-October/004926.html http://www.ghostscript.com/pipermail/gs-cvs/2004-October/004927.html The bug in HEAD is now closed, but we keep this bug report open, because we have to fix it in GS_8_1X. |