Bug 691456 - Page size not correct
Summary: Page size not correct
Status: NOTIFIED INVALID
Alias: None
Product: Ghostscript
Classification: Unclassified
Component: PS Interpreter (show other bugs)
Version: master
Hardware: PC All
: P2 normal
Assignee: Alex Cherepanov
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-12 19:33 UTC by Marcos H. Woehrmann
Modified: 2011-09-18 21:46 UTC (History)
0 users

See Also:
Customer: 580
Word Size: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Marcos H. Woehrmann 2010-07-12 19:33:41 UTC
Ghostscript incorrectly renders the attached file as an 8.5 x 11 inch document, when the correct size is 1006 x 1531 points.  Adding the -dEPSCROP option doesn't help.  Acrobat 9.3.3 correctly opens the file (see attached TIFF files).

The command line I'm using:

  bin/gs -sDEVICE=tiff24nc o test.tif ./101CM.1.RZ.16042010.1003236.1.ps

Adding -dDEVICEWIDTHPOINTS=1006 -dDEVICEHEIGHTPOINTS=1531 to the command line causes the file to render correctly.  The page size can be found by using the following command:

grep -a BoundingBox 101CM.1.RZ.16042010.1003236.1.ps | head -1
Comment 4 Ray Johnston 2010-07-12 21:48:51 UTC
This PS file has a "header" that defeats the -dEPSCrop option. The comments
in the header PS file identify it as:

% Level 2 Separation (c) Frank Siegert 7/1999
% Start Separation L2 von D:\TEMPPFAD\E27149.BEL

We cannot arbitrarily scan past PostScript prefix files and attempt to guess
what page size to use, and I suspect that there are cases where Adobe guesses
wrong.

If I remove the header and trailer having to do with the separation stuff,
-dEPSCrop sets the PageSize correctly. Without this option, on the modified
file, I get the warning:

  **** Warning: Some of the BoundingBox for the EPS file will be clipped.
                Use -dEPSCrop or -dEPSFitPage to avoid clipping.

which indicate that the file is being recognized as an EPSF and that the
-dEPSCrop is working as expected and documented.

Closing as INVALID since Ghostscript is performing as expected as a PostScript
interpreter and the -dEPSCrop also works as expected.
Comment 5 Marcos H. Woehrmann 2011-09-18 21:46:10 UTC
Changing customer bugs that have been resolved more than a year ago to closed.