1# 2# CDDL HEADER START 3# 4# The contents of this file are subject to the terms of the 5# Common Development and Distribution License, Version 1.0 only 6# (the "License"). You may not use this file except in compliance 7# with the License. 8# 9# You can obtain a copy of the license at usr/src/OPENSOLARIS.LICENSE 10# or http://www.opensolaris.org/os/licensing. 11# See the License for the specific language governing permissions 12# and limitations under the License. 13# 14# When distributing Covered Code, include this CDDL HEADER in each 15# file and include the License file at usr/src/OPENSOLARIS.LICENSE. 16# If applicable, add the following below this CDDL HEADER, with the 17# fields enclosed by brackets "[]" replaced with your own identifying 18# information: Portions Copyright [yyyy] [name of copyright owner] 19# 20# CDDL HEADER END 21# 22 23Prologues and a few other PostScript files that are copied to /usr/lib/postscript 24(ie. LIBDIR in ../Makefile) when you do an install. 25 26Default settings for things like the linewidth in posttek and postbgi, have been 27moved to these files. All can be changed without requiring a recompilation of any 28programs supplied with this package. In addition all the translators understand 29the -P option that lets you pass arbitrary PostScript through to the output file. 30The option can be useful if you want to change parameters that are defined in 31the prologue but not tied to specific command line options. 32 33For example, the DMD bitmap translator (postdmd) that assumes a screen resolution 34of 100 dpi. screenres is set to 100 in postdmd.ps, but there's no explicit option 35to change it. If the bitmap resolution happened to be 300 dpi typing either, 36 37 postdmd -P"/screenres 300 def" file 38 39or, 40 41 postdmd -P"/screenres 300" file 42 43sets screenres to 300. In the first case the definition is made immediately after 44the prologue, while in the second it's made when procedure setup is executed. 45 46Another example is postbgi.ps, which can be used as the prologue for both STARE 47and PRISM jobs. Although STARE (black and white) and PRISM (color) jobs are both 48written in BGI, experience shows that PRISM jobs are often fundamentally different 49and often require device specific tuning that's rarely needed for STARE jobs. The 50prologue (postbgi.ps) defines a boolean called prism (initialized to false) while 51the command line, 52 53 postbgi -P"/prism true" file >file.ps 54 55sets prism to true. What you end up getting is the device specific tuning needed 56for most PRISM jobs. 57 58