Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!tut.cis.ohio-state.edu!ucbvax!decwrl!adobe!greid From: greid@adobe.com (Glenn Reid) Newsgroups: comp.lang.postscript Subject: Re: page bounding boxes in EPSF Message-ID: <1039@adobe.UUCP> Date: 2 Aug 89 00:00:30 GMT References: Sender: news@adobe.COM Reply-To: greid@adobe.COM (Glenn Reid) Organization: Adobe Systems Incorporated, Mountain View Lines: 23 In article jcgs@wundt.harlqn.uucp (John Sturdy) writes: >I am working on some utilities that produce EPSF output, and noticed a >little gap in the EPSF spec. You can specify per-document font lists >and BoundingBoxes, and per-page fonts, but not per-page BoundingBoxes ... >Has anybody done something about this? If there is no de facto >standard (and nothing from Adobe about it) I'll use the ``obvious'' >solution of inventing a new comment "%%PageBoundingBox n n n n" to go The EPSF specification is a special case of the Document Structuring Conventions, which is stated in the spec. The Document Structuring Conventions (as of Version 2.1, at least) already contain the %%PageBoundingBox comment (it's on page 22 in my copy, under "Page Comments"). It is used in exactly the manner you suggest. Note that there is also a %%PageTrailer comment and a few others that may be relevant. There is also a %%PageFonts comment for providing the font list on a given page. All of the comments provided by Document Structuring Conventions are valid (and encouraged, where appropriate) within an EPSF file. Glenn Reid Adobe Systems