Seems that gs 9.00's bbox driver returns a wrong result. $ gs -sDEVICE=bbox -dNOPAUSE -dBATCH sample.pdf GPL Ghostscript 8.71 (2010-02-10) Copyright (C) 2010 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 1. Page 1 %%BoundingBox: 243 676 348 697 <--- correct %%HiResBoundingBox: 243.647993 676.169979 347.183989 696.383979 $ gs -sDEVICE=bbox -dNOPAUSE -dBATCH sample.pdf GPL Ghostscript RELEASE CANDIDATE 9.00 (2010-09-01) Copyright (C) 2010 Artifex Software, Inc. All rights reserved. This software comes with NO WARRANTY: see the file PUBLIC for details. Processing pages 1 through 1. Page 1 %%BoundingBox: 236 670 343 690 <--- wrong! %%HiResBoundingBox: 236.933993 670.607980 342.665990 689.741979 Due to this problem, some applications like 'LaTeXiT' doesn't work as expected with gs9.
Created attachment 6699 [details] latexit-sample.tex
Created attachment 6700 [details] latexit-sample.pdf
Created attachment 6701 [details] latexit-screenshot.png
This is a problem with the FreeType implementation, exhibited because the content is entirely textual. Using -dDisableFAPI=true gives the expected result. There are only a few pixels different in the rendered output, and the BoundingBox with FreeType is definitely not consistent with the actual bounding box of the rendered output. Assigning to Chris.
Thanks for your hint, Ken. I reinstalled gs9 with '--disable-freetype' and everything is now ok. :-) (In reply to comment #4) > This is a problem with the FreeType implementation, exhibited because the > content is entirely textual. > > Using -dDisableFAPI=true gives the expected result.
Updating the severity status according to discussions on IRC with Chris and Henry.
fixed in revision 11690 (it did cause a build issue which gave rise to revisions 11691 and 11692).