From 4ab46eb12e0c74dc3d6bfcc44d140d725e6581d9 Mon Sep 17 00:00:00 2001 From: giraffedata Date: Wed, 27 Jun 2018 21:44:40 +0000 Subject: Fix array bounds violation git-svn-id: http://svn.code.sf.net/p/netpbm/code/trunk@3279 9d0c8265-081b-0410-96cb-a4ca84ce46f8 --- converter/other/pstopnm.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'converter/other') diff --git a/converter/other/pstopnm.c b/converter/other/pstopnm.c index a89224ee..73954d86 100644 --- a/converter/other/pstopnm.c +++ b/converter/other/pstopnm.c @@ -334,7 +334,7 @@ computeSizeRes(struct CmdlineInfo const cmdline, Figure out how big the output image should be and what output device resolution Ghostscript should assume (return as *imageDimP). - A resolution number is the number of pixels per inch that the a + A resolution number is the number of pixels per inch that the printer prints. Since we're emulating a printed page with a PNM image, and a PNM image has no spatial dimension (you can't say how many inches wide a PNM image is), it's kind of confusing. @@ -347,7 +347,7 @@ computeSizeRes(struct CmdlineInfo const cmdline, tell Ghostscript that our horizontal output device resolution is 500 pixels per inch. - X and Y in all returned values is with respect to the image, not the + X and Y in all returned values are with respect to the image, not the page. Note that the image might be placed sideways on the page, so that page X and Y would be reversed from image X and Y. -----------------------------------------------------------------------------*/ -- cgit 1.4.1