(See PostScript Printer Description Files for more information on PPD keywords.) (See Apple TechNote 1068 for more information.) In the absence of these resources the LaserWriter 8 driver provides a generic user interface for the features in the PPD file that are defined by the *OpenUI/*CloseUI keywords. The LaserWriter 8 driver (specifically version 8.4.1 and later) allows developers to define a custom user interface using 'ppdt', 'PPDA', 'DITL', and 'ALRT' resources in the PPD file. It was designed to work with any PostScript or PostScript-compatible printer connected to a Macintosh computer. The LaserWriter 8 driver is Apple’s general purpose PostScript printer driver for Mac OS 9 and earlier. Provides an overview of PPD files and how OS X handles the filesĭescribes the Printer Features pane in the Print dialogįor detailed information on PPD files, see PostScript Printer Description File Format Specification, available from Adobe Developer Support:
#Adobe postscript driver mac os x how to#
Shows how to specify that certain features should be grouped in the interfaceĭiscusses how OS X searches for PPD filesĪpplication developers might also find this document useful because it Tells what you need to do if you provide a printing dialog extension for your PostScript printer Provides information about localizing PPD filesĭetails the differences between PPD support in OS X and earlier versions of the Mac OS This document is important for printer vendors who are providing PPD files in OS X because itĭescribes where PPD files need to be installed They also contain the PostScript code used to invoke those features. On the Macintosh, PPD files provide all the information necessary to describe a PostScript printer’s features, including options and default settings. PostScript printer description (PPD) files are created by printer vendors to describe the set of printer features available for their PostScript printers.
Links to downloads and other resources may no longer be valid.
Important: This document may not represent best practices for current development.
0 kommentar(er)
