GNOME Bugzilla – Bug 326859
Some postscript files are not displayed correctly
Last modified: 2006-01-16 07:59:46 UTC
Please describe the problem: There are some postscript files which are not rendered correctly. Text and images and more text overlaps and it is impossible to read the text. Reloading, Scrolling and/or resizing the evince window there appears the "Loading..." and after a while an error. Steps to reproduce: 1. Open this postscript file with evince: http://www.cs.umanitoba.ca/~eclipse/1-Install.ps and scroll down a little bit. You are not able to read the text (the chaos starts on page 2). 2. resize the evince window, scroll fast down (and back) and/or click view -> reload until the "Loading..." appears. 3. Wait a little bit. The error message appears. Actual results: There are some postscript files with images, that are not displayed correctly. The images overlap the text and text overlaps, too. It does not happen with all postscript files and there are postscript files containing images which work, too. The postscript files evince is unable to render correctly are those found here, for example: http://www.cs.umanitoba.ca/~eclipse/ I do not know if this is a duplicate of bug #317412 because scrolling too fast or resizing evince causes blank pages with a big "Loading..." on every page. Waiting a while, the "Loading..." disappears and there is an error message at least on the first page, sometimes on the first two pages. ERROR: undefined OFFENDING COMMAND: F0SB'/ STACK: nothing more. Expected results: Does this happen every time? Yes. Other information: My System: Debian Sid, evince and poppler from CVS (0.5.0), i386, Gnome Desktop. The Postscript Files are created (i got this information out of the properties of the files) with "PScript5.dll Version 5.2".
Microsoft word creates really bad postscripts :(
This document is really broken, It has %%BeginResource included in the first page (after %%Page), rather in prolog. I wonder if we can suggest clean and appropriate fix for that problem. File a bug to MS Word :) We had similar problem with Firefox recently, and they have fixed this issue.
Ok... well, I don't think that the MS crew will respond as quick as the mozilla people. ;-) And as I do not use MS Word... ps2pdf (from the GhostScript files) is able to convert this bad PostScript to a readable PDF (perhaps that makes it easier to implement "bad ps rendering"), so there is no problem.