3 <!-- SECTION: Programming -->
5 <title>Introduction to the PPD Compiler
</title>
6 <meta name=
"keywords" content=
"Programming">
7 <meta http-equiv=
"Content-Type" content=
"text/html;charset=utf-8">
8 <meta name=
"creator" content=
"Mini-XML v2.11">
9 <meta name=
"author" content=
"Unknown">
10 <meta name=
"copyright" content=
"Unknown">
11 <meta name=
"version" content=
"0.0">
12 <style type=
"text/css"><!--
14 font-family: lucida grande, geneva, helvetica, arial, sans-serif;
17 H1, H2, H3, H4, H5, H6, P, TD, TH {
18 font-family: lucida grande, geneva, helvetica, arial, sans-serif;
22 font-family: monaco, courier, monospace;
27 font-family: monaco, courier, monospace;
31 border-left: solid 2px #777;
40 PRE.command, PRE.example {
67 PRE.command EM, PRE.example EM {
68 font-family: lucida grande, geneva, helvetica, arial, sans-serif;
72 font-family: monaco, courier, monospace;
88 -moz-border-radius: 10px;
93 text-decoration: none;
96 A:link:hover, A:visited:hover, A:active {
97 text-decoration: underline;
104 TR.data, TD.data, TR.data TD {
107 border-bottom: solid 1pt #999999;
111 border-bottom: solid 1pt #999999;
118 border: solid thin #999999;
119 border-collapse: collapse;
135 border: solid thin #cccccc;
142 border-bottom: solid thin #999999;
151 caption-side: bottom;
175 border: thin solid black;
183 H2 SPAN.info, H3 SPAN.info, H4 SPAN.info {
192 border-bottom: solid 2pt #000000;
195 DIV.indent, TABLE.indent {
203 border-collapse: collapse;
206 TABLE.indent TD, TABLE.indent TH {
211 border-collapse: collapse;
219 border-bottom: solid thin #cccccc;
224 vertical-align: bottom;
233 border-bottom: solid thin #eeeeee;
238 TABLE.list TR:nth-child(even) {
242 TABLE.list TR:nth-child(odd) {
261 font-family: monaco, courier, monospace;
265 border: solid thin #999999;
266 border-collapse: collapse;
271 DIV.summary TABLE TD, DIV.summary TABLE TH {
272 border: solid thin #999999;
278 DIV.summary TABLE THEAD TH {
282 /* API documentation styles... */
294 margin-bottom: 0.5em;
299 margin-bottom: 0.5em;
304 margin-bottom: 0.5em;
309 border: solid thin black;
318 div.contents ul.contents {
322 border-bottom: solid 2px gray;
332 border-bottom: solid 2px gray;
335 border-bottom: solid 2px gray;
347 border-bottom: solid 2px gray;
350 border-bottom: solid 2px gray;
353 border-bottom: solid 2px gray;
357 h1, h2, h3, h4, h5, h6 {
358 page-break-inside: avoid;
361 border: solid thin gray;
362 box-shadow: 3px 3px 5px rgba(0,0,0,0.5);
364 page-break-inside: avoid;
366 p code, li code, p.code, pre, ul.code li {
367 background: rgba(127,127,127,0.1);
368 border: thin dotted gray;
369 font-family: monospace;
372 -webkit-hyphens: manual;
373 page-break-inside: avoid;
375 p.code, pre, ul.code li {
382 text-decoration: none;
386 border: solid thin black;
393 h3 span.info, h4 span.info {
394 border-top-left-radius: 10px;
395 border-top-right-radius: 10px;
399 ul.code, ul.contents, ul.subcontents {
400 list-style-type: none;
410 ul.contents li ul.code, ul.contents li ul.subcontents {
414 border-collapse: collapse;
417 table.list tr:nth-child(even) {
418 background: rgba(127,127,127,0.1);]n}
420 border-right: 2px solid gray;
421 font-family: monospace;
422 padding: 5px 10px 5px 2px;
427 padding: 5px 2px 5px 10px;
434 border-bottom: solid 2px black;
437 border-bottom: solid 2px black;
443 PPD compiler documentation for CUPS.
445 Copyright 2007-2012 by Apple Inc.
446 Copyright 1997-2007 by Easy Software Products.
448 These coded instructions, statements, and computer programs are the
449 property of Apple Inc. and are protected by Federal copyright
450 law. Distribution and use rights are outlined in the file "LICENSE.txt"
451 which should have been included with this file. If this file is
452 file is missing or damaged, see the license at "http://www.cups.org/".
455 <h1 class='title'
>Introduction to the PPD Compiler
</h1>
457 <P>This document describes how to use the CUPS PostScript Printer Description
458 (PPD) file compiler. The PPD compiler generates PPD files from simple text files
459 that describe the features and capabilities of one or more printers.
</P>
461 <BLOCKQUOTE><B>Note:
</B>
463 <P>The PPD compiler and related tools are deprecated and will be removed in a future release of CUPS.
</P>
467 <div class='summary'
><table summary='General Information'
>
471 <td>Programming:
<a href='raster-driver.html'
>Developing Raster Printer Drivers
</a><br>
472 Programming:
<a href='postscript-driver.html'
>Developing PostScript Printer Drivers
</a><br>
473 Programming:
<a href='api-filter.html'
>Filter and Backend Programming
</a><br>
474 Programming:
<a href='api-raster.html'
>Raster API
</a><br>
475 References:
<a href='ref-ppdcfile.html'
>PPD Compiler Driver Information File Reference
</a><br>
476 Specifications:
<a href='spec-ppd.html'
>CUPS PPD Extensions
</a></td>
480 <div class=
"contents">
481 <h2 class=
"title">Contents
</h2>
482 <ul class=
"contents">
483 <li><a href=
"#BASICS">The Basics
</a></li>
484 <li><a href=
"#DRV">Driver Information Files
</a><ul class=
"subcontents">
485 <li><a href=
"#SIMPLE">A Simple Example
</a></li>
486 <li><a href=
"#GROUPING">Grouping and Inheritance
</a></li>
487 <li><a href=
"#COLOR">Color Support
</a></li>
488 <li><a href=
"#OPTIONS">Defining Custom Options and Option Groups
</a></li>
489 <li><a href=
"#DEFINE">Defining Constants
</a></li>
490 <li><a href=
"#CONDITIONAL">Conditional Statements
</a></li>
491 <li><a href=
"#CONSTRAINTS">Defining Constraints
</a></li>
493 <li><a href=
"#LOCALIZATION">Localization
</a><ul class=
"subcontents">
494 <li><a href=
"#PPDPO">The ppdpo Utility
</a></li>
495 <li><a href=
"#PPDC_CATALOG">Using Message Catalogs with the PPD Compiler
</a></li>
500 <h2 class='title'
><a name='BASICS'
>The Basics
</a></h2>
502 <P>The PPD compiler,
<a href='man-ppdc.html'
><code>ppdc(
1)
</code></a>, is a
503 simple command-line tool that takes a single
<I>driver information file
</I>,
504 which by convention uses the extension
<VAR>.drv
</VAR>, and produces one or more
505 PPD files that may be distributed with your printer drivers for use with CUPS.
506 For example, you would run the following command to create the English language
507 PPD files defined by the driver information file
<VAR>mydrivers.drv
</VAR>:
</P>
509 <pre class='command'
>
513 <P>The PPD files are placed in a subdirectory called
514 <VAR>ppd
</VAR>. The
<TT>-d
</TT> option is used to put the PPD
515 files in a different location, for example:
</p>
517 <pre class='command'
>
518 ppdc -d myppds mydrivers.drv
521 <P>places the PPD files in a subdirectory named
522 <VAR>myppds
</VAR>. Finally, use the
<TT>-l
</TT> option to
523 specify the language localization for the PPD files that are
524 created, for example:
</P>
526 <pre class='command'
>
527 ppdc -d myppds/de -l de mydrivers.drv
528 ppdc -d myppds/en -l en mydrivers.drv
529 ppdc -d myppds/es -l es mydrivers.drv
530 ppdc -d myppds/fr -l fr mydrivers.drv
531 ppdc -d myppds/it -l it mydrivers.drv
534 <P>creates PPD files in German (de), English (en), Spanish (es),
535 French (fr), and Italian (it) in the corresponding
536 subdirectories. Specify multiple languages (separated by commas) to produce
537 "globalized" PPD files:
</p>
539 <pre class='command'
>
540 ppdc -d myppds -l de,en,es,fr,it mydrivers.drv
544 <h2 class='title'
><a name='DRV'
>Driver Information Files
</a></h2>
546 <P>The driver information files accepted by the PPD compiler are
547 plain text files that define the various attributes and options
548 that are included in the PPD files that are generated. A driver
549 information file can define the information for one or more printers and
550 their corresponding PPD files.
</P>
552 <p class='example'
><a name=
"LISTING1">Listing
1:
"examples/minimum.drv"</a></p>
554 <pre class='example'
>
555 <I>// Include standard font and media definitions
</I>
556 <a href='ref-ppdcfile.html#_include'
>#include
</a> <font.defs
>
557 <a href='ref-ppdcfile.html#_include'
>#include
</a> <media.defs
>
559 <I>// List the fonts that are supported, in this case all standard fonts...
</I>
560 <a href='ref-ppdcfile.html#Font'
>Font
</a> *
562 <I>// Manufacturer, model name, and version
</I>
563 <a href='ref-ppdcfile.html#Manufacturer'
>Manufacturer
</a> "Foo"
564 <a href='ref-ppdcfile.html#ModelName'
>ModelName
</a> "FooJet 2000"
565 <a href='ref-ppdcfile.html#Version'
>Version
</a> 1.0
567 <I>// Each filter provided by the driver...
</I>
568 <a href='ref-ppdcfile.html#Filter'
>Filter
</a> application/vnd.cups-raster
100 rastertofoo
570 <I>// Supported page sizes
</I>
571 *
<a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> Letter
572 <a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> A4
574 <I>// Supported resolutions
</I>
575 *
<a href='ref-ppdcfile.html#Resolution'
>Resolution
</a> k
8 0 0 0 "600dpi/600 DPI"
577 <I>// Specify the name of the PPD file we want to generate...
</I>
578 <a href='ref-ppdcfile.html#PCFileName'
>PCFileName
</a> "foojet2k.ppd"
582 <h3><a name='SIMPLE'
>A Simple Example
</a></h3>
584 <P>The example in
<A HREF=
"#LISTING1">Listing
1</A> shows a driver information
585 file which defines the minimum required attributes to provide a valid PPD file.
586 The first part of the file includes standard definition files for fonts and
589 <pre class='example'
>
590 <a href='ref-ppdcfile.html#_include'
>#include
</a> <font.defs
>
591 <a href='ref-ppdcfile.html#_include'
>#include
</a> <media.defs
>
594 <P>The
<TT>#include
</TT> directive works just like the C/C++ include directive;
595 files included using the angle brackets (
<TT><filename
></TT>) are found
596 in any of the standard include directories and files included using quotes
597 (
<TT>"filename"</TT>) are found in the same directory as the source or include
598 file. The
<TT><font.defs
></TT> include file defines the standard fonts
599 which are included with GPL Ghostscript and the Apple PDF RIP, while the
600 <TT><media.defs
></TT> include file defines the standard media sizes
601 listed in Appendix B of the Adobe PostScript Printer Description File Format
604 <P>CUPS provides several other standard include files:
</P>
608 <LI><TT><epson.h
></TT> - Defines all of the rastertoepson driver
611 <LI><TT><escp.h
></TT> - Defines all of the rastertoescpx driver
614 <LI><TT><hp.h
></TT> - Defines all of the rastertohp driver
617 <LI><TT><label.h
></TT> - Defines all of the rastertolabel driver
620 <LI><TT><pcl.h
></TT> - Defines all of the rastertopclx driver
623 <LI><TT><raster.defs
></TT> - Defines all of the CUPS raster format
628 <P>Next we list all of the fonts that are available in the driver; for CUPS
629 raster drivers, the following line is all that is usually supplied:
</P>
631 <pre class='example'
>
632 <a href='ref-ppdcfile.html#Font'
>Font
</a> *
635 <P>The
<TT>Font
</TT> directive specifies the name of a single font or the
636 asterisk to specify all fonts. For example, you would use the following line to
637 define an additional bar code font that you are supplying with your printer
640 <pre class='example'
>
641 <I>// name encoding version charset status
</I>
642 <a href='ref-ppdcfile.html#Font'
>Font
</a> Barcode-Foo Special
"(1.0)" Special ROM
645 <P>The name of the font is
<TT>Barcode-Foo
</TT>. Since it is not a standard
646 text font, the encoding and charset name
<TT>Special
</TT> is used. The version
647 number is
<TT>1.0</TT> and the status (where the font is located) is
648 <TT>ROM
</TT> to indicate that the font does not need to be embedded in
649 documents that use the font for this printer.
</P>
651 <P>Third comes the manufacturer, model name, and version number information
654 <pre class='example'
>
655 <a href='ref-ppdcfile.html#Manufacturer'
>Manufacturer
</a> "Foo"
656 <a href='ref-ppdcfile.html#ModelName'
>ModelName
</a> "FooJet 2000"
657 <a href='ref-ppdcfile.html#Version'
>Version
</a> 1.0
660 <P>These strings are used when the user (or auto-configuration program) selects
661 the printer driver for a newly connected device.
</p>
663 <P>The list of filters comes after the information strings; for the example in
664 <A HREF=
"#LISTING1">Listing
1</A>, we have a single filter that takes CUPS
667 <pre class='example'
>
668 <a href='ref-ppdcfile.html#Filter'
>Filter
</a> application/vnd.cups-raster
100 rastertofoo
671 <P>Each filter specified in the driver information file is the equivalent of a
672 printer driver for that format; if a user submits a print job in a different
673 format, CUPS figures out the sequence of commands that will produce a supported
674 format for the least relative cost.
</P>
676 <P>Once we have defined the driver information we specify the supported options.
677 For the example driver we support a single resolution of
600 dots per inch and
678 two media sizes, A4 and Letter:
</P>
680 <pre class='example'
>
681 *
<a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> Letter
682 <a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> A4
684 *
<a href='ref-ppdcfile.html#Resolution'
>Resolution
</a> k
8 0 0 0 "600dpi/600 DPI"
687 <P>The asterisk in front of the
<TT>MediaSize
</TT> and
<TT>Resolution
</TT>
688 directives specify that those option choices are the default. The
689 <TT>MediaSize
</TT> directive is followed by a media size name which is normally
690 defined in the
<TT><media.defs
></TT> file and corresponds to a standard
691 Adobe media size name. If the default media size is
<TT>Letter
</TT>, the PPD
692 compiler will override it to be
<TT>A4
</TT> for non-English localizations for
693 you automatically.
</P>
695 <P>The
<TT>Resolution
</TT> directive accepts several values after it as
700 <LI>Colorspace for this resolution, if any. In the example file, the
701 colorspace
<TT>k
</TT> is used which corresponds to black. For printer
702 drivers that support color printing, this field is usually specified as
703 "-" for
"no change".
</LI>
705 <LI>Bits per color. In the example file, we define
8 bits per color, for
706 a continuous-tone grayscale output. All versions of CUPS support
1 and
707 8 bits per color. CUPS
1.2 and higher (macOS
10.5 and higher) also
708 supports
16 bits per color.
</LI>
710 <LI>Rows per band. In the example file, we define
0 rows per band to
711 indicate that our printer driver does not process the page in
714 <LI>Row feed. In the example, we define the feed value to be
0 to
715 indicate that our printer driver does not interleave the output.
</LI>
717 <LI>Row step. In the example, we define the step value to be
0 to
718 indicate that our printer driver does not interleave the output. This
719 value normally indicates the spacing between the nozzles of an inkjet
720 printer - when combined with the previous two values, it informs the
721 driver how to stagger the output on the page to produce interleaved
722 lines on the page for higher-resolution output.
</LI>
724 <LI>Choice name and text. In the example, we define the choice name and
725 text to be
<TT>"600dpi/600 DPI"</TT>. The name and text are separated by
726 slash (
<TT>/
</TT>) character; if no text is specified, then the name is
727 used as the text. The PPD compiler parses the name to determine the
728 actual resolution; the name can be of the form
729 <TT><I>RESOLUTION
</I>dpi
</TT> for resolutions that are equal
730 horizontally and vertically or
<TT><I>HRES
</I>x
<I>VRES
</I>dpi
</TT> for
731 isometric resolutions. Only integer resolution values are supported, so
732 a resolution name of
<TT>300dpi
</TT> is valid while
<TT>300.1dpi
</TT> is
737 <P>Finally, the
<TT>PCFileName
</TT> directive specifies that the named PPD file
738 should be written for the current driver definitions:
</P>
740 <pre class='example'
>
741 <a href='ref-ppdcfile.html#PCFileName'
>PCFileName
</a> "foojet2k.ppd"
744 <P>The filename follows the directive and
<I>must
</I> conform to the Adobe
745 filename requirements in the Adobe Postscript Printer Description File Format
746 Specification. Specifically, the filename may not exceed
8 characters followed
747 by the extension
<VAR>.ppd
</VAR>. The
<TT>FileName
</TT> directive can be used to
748 specify longer filenames:
</P>
750 <pre class='example'
>
751 <a href='ref-ppdcfile.html#FileName'
>FileName
</a> "FooJet 2000"
755 <h3><a name='GROUPING'
>Grouping and Inheritance
</a></h3>
757 <P>The previous example created a single PPD file. Driver information files can
758 also define multiple printers by using the PPD compiler grouping functionality.
759 Directives are grouped using the curly braces (
<TT>{
</TT> and
<TT>}
</TT>) and
760 every group that uses the
<TT>PCFileName
</TT> or
<TT>FileName
</TT> directives
761 produces a PPD file with that name.
<A HREF=
"#LISTING2">Listing
2</A> shows a
762 variation of the original example that uses two groups to define two printers
763 that share the same printer driver filter but provide two different resolution
766 <p class='example'
><a name=
"LISTING2">Listing
2:
"examples/grouping.drv"</a></p>
768 <pre class='example'
>
770 <I>// Include standard font and media definitions
</I>
771 <a href='ref-ppdcfile.html#_include'
>#include
</a> <font.defs
>
772 <a href='ref-ppdcfile.html#_include'
>#include
</a> <media.defs
>
774 <I>// List the fonts that are supported, in this case all standard fonts...
</I>
775 <a href='ref-ppdcfile.html#Font'
>Font
</a> *
777 <I>// Manufacturer and version
</I>
778 <a href='ref-ppdcfile.html#Manufacturer'
>Manufacturer
</a> "Foo"
779 <a href='ref-ppdcfile.html#Version'
>Version
</a> 1.0
781 <I>// Each filter provided by the driver...
</I>
782 <a href='ref-ppdcfile.html#Filter'
>Filter
</a> application/vnd.cups-raster
100 rastertofoo
784 <I>// Supported page sizes
</I>
785 *
<a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> Letter
786 <a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> A4
789 <I>// Supported resolutions
</I>
790 *
<a href='ref-ppdcfile.html#Resolution'
>Resolution
</a> k
8 0 0 0 "600dpi/600 DPI"
792 <I>// Specify the model name and filename...
</I>
793 <a href='ref-ppdcfile.html#ModelName'
>ModelName
</a> "FooJet 2000"
794 <a href='ref-ppdcfile.html#PCFileName'
>PCFileName
</a> "foojet2k.ppd"
798 <I>// Supported resolutions
</I>
799 *
<a href='ref-ppdcfile.html#Resolution'
>Resolution
</a> k
8 0 0 0 "1200dpi/1200 DPI"
801 <I>// Specify the model name and filename...
</I>
802 <a href='ref-ppdcfile.html#ModelName'
>ModelName
</a> "FooJet 2001"
803 <a href='ref-ppdcfile.html#PCFileName'
>PCFileName
</a> "foojt2k1.ppd"
807 <P>The second example is essentially the same as the first, except that each
808 printer model is defined inside of a pair of curly braces. For example, the
809 first printer is defined using:
</P>
811 <pre class='example'
>
813 // Supported resolutions
814 *
<a href='ref-ppdcfile.html#Resolution'
>Resolution
</a> k
8 0 0 0 "600dpi/600 DPI"
816 // Specify the model name and filename...
817 <a href='ref-ppdcfile.html#ModelName'
>ModelName
</a> "FooJet 2000"
818 <a href='ref-ppdcfile.html#PCFileName'
>PCFileName
</a> "foojet2k.ppd"
822 <P>The printer
<I>inherits
</I> all of the definitions from the parent group (the
823 top part of the file) and adds the additional definitions inside the curly
824 braces for that printer driver. When we define the second group, it also
825 inherits the same definitions from the parent group but
<I>none
</I> of the
826 definitions from the first driver. Groups can be nested to any number of levels
827 to support variations of similar models without duplication of information.
</P>
830 <h3><a name='COLOR'
>Color Support
</a></h3>
832 <P>For printer drivers that support color printing, the
833 <TT>ColorDevice
</TT> and
<TT>ColorModel
</TT> directives should be
834 used to tell the printing system that color output is desired
835 and in what formats.
<A HREF=
"#LISTING3">Listing
3</A> shows a
836 variation of the previous example which includes a color printer
837 that supports printing at
300 and
600 DPI.
</P>
839 <P>The key changes are the addition of the
<TT>ColorDevice
</TT>
842 <pre class='example'
>
843 <a href='ref-ppdcfile.html#ColorDevice'
>ColorDevice
</a> true
846 <P>which tells the printing system that the printer supports
847 color printing, and the
<TT>ColorModel
</TT> directives:
</P>
849 <pre class='example'
>
850 <a href='ref-ppdcfile.html#ColorModel'
>ColorModel
</a> Gray/Grayscale w chunky
0
851 *
<a href='ref-ppdcfile.html#ColorModel'
>ColorModel
</a> RGB/Color rgb chunky
0
854 <P>which tell the printing system which colorspaces are supported by the printer
855 driver for color printing. Each of the
<TT>ColorModel
</TT> directives is
856 followed by the option name and text (
<TT>Gray/Grayscale
</TT> and
857 <TT>RGB/Color
</TT>), the colorspace name (
<TT>w
</TT> and
<TT>rgb
</TT>), the
858 color organization (
<TT>chunky
</TT>), and the compression mode number
859 (
<TT>0</TT>) to be passed to the driver. The option name can be any of the
860 standard Adobe
<TT>ColorModel
</TT> names:
</P>
864 <LI><TT>Gray
</TT> - Grayscale output.
866 <LI><TT>RGB
</TT> - Color output, typically using the RGB
867 colorspace, but without a separate black channel.
869 <LI><TT>CMYK
</TT> - Color output with a separate black
874 <P>Custom names can be used, however it is recommended that you use your vendor
875 prefix for any custom names, for example
"fooName".
</P>
877 <P>The colorspace name can be any of the following universally supported
881 <LI><TT>w
</TT> - Luminance
</LI>
883 <LI><TT>rgb
</TT> - Red, green, blue
</LI>
885 <LI><TT>k
</TT> - Black
</LI>
887 <LI><TT>cmy
</TT> - Cyan, magenta, yellow
</LI>
889 <LI><TT>cmyk
</TT> - Cyan, magenta, yellow, black
</LI>
893 <P>The color organization can be any of the following values:
</P>
897 <LI><TT>chunky
</TT> - Color values are passed together on a line
898 as RGB RGB RGB RGB
</LI>
900 <LI><TT>banded
</TT> - Color values are passed separately
901 on a line as RRRR GGGG BBBB; not supported by the Apple
904 <LI><TT>planar
</TT> - Color values are passed separately
905 on a page as RRRR RRRR RRRR ... GGGG GGGG GGGG ... BBBB
906 BBBB BBBB; not supported by the Apple RIP filters
</LI>
910 <P>The compression mode value is passed to the driver in the
911 <TT>cupsCompression
</TT> attribute. It is traditionally used to select an
912 appropriate compression mode for the color model but can be used for any
913 purpose, such as specifying a photo mode vs. standard mode.
</P>
915 <p class='example'
><a name=
"LISTING3">Listing
3:
"examples/color.drv"</a></p>
917 <pre class='example'
>
919 <I>// Include standard font and media definitions
</I>
920 <a href='ref-ppdcfile.html#_include'
>#include
</a> <font.defs
>
921 <a href='ref-ppdcfile.html#_include'
>#include
</a> <media.defs
>
923 <I>// List the fonts that are supported, in this case all standard fonts...
</I>
924 <a href='ref-ppdcfile.html#Font'
>Font
</a> *
926 <I>// Manufacturer and version
</I>
927 <a href='ref-ppdcfile.html#Manufacturer'
>Manufacturer
</a> "Foo"
928 <a href='ref-ppdcfile.html#Version'
>Version
</a> 1.0
930 <I>// Each filter provided by the driver...
</I>
931 <a href='ref-ppdcfile.html#Filter'
>Filter
</a> application/vnd.cups-raster
100 rastertofoo
933 <I>// Supported page sizes
</I>
934 *
<a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> Letter
935 <a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> A4
938 <I>// Supported resolutions
</I>
939 *
<a href='ref-ppdcfile.html#Resolution'
>Resolution
</a> k
8 0 0 0 "600dpi/600 DPI"
941 <I>// Specify the model name and filename...
</I>
942 <a href='ref-ppdcfile.html#ModelName'
>ModelName
</a> "FooJet 2000"
943 <a href='ref-ppdcfile.html#PCFileName'
>PCFileName
</a> "foojet2k.ppd"
947 <I>// Supports color printing
</I>
948 <a href='ref-ppdcfile.html#ColorDevice'
>ColorDevice
</a> true
950 <I>// Supported colorspaces
</I>
951 <a href='ref-ppdcfile.html#ColorModel'
>ColorModel
</a> Gray/Grayscale w chunky
0
952 *
<a href='ref-ppdcfile.html#ColorModel'
>ColorModel
</a> RGB/Color rgb chunky
0
954 <I>// Supported resolutions
</I>
955 *
<a href='ref-ppdcfile.html#Resolution'
>Resolution
</a> -
8 0 0 0 "300dpi/300 DPI"
956 <a href='ref-ppdcfile.html#Resolution'
>Resolution
</a> -
8 0 0 0 "600dpi/600 DPI"
958 <I>// Specify the model name and filename...
</I>
959 <a href='ref-ppdcfile.html#ModelName'
>ModelName
</a> "FooJet Color"
960 <a href='ref-ppdcfile.html#PCFileName'
>PCFileName
</a> "foojetco.ppd"
965 <h3><a name='OPTIONS'
>Defining Custom Options and Option Groups
</a></h3>
967 <P>The
<TT>Group
</TT>,
<TT>Option
</TT>, and
<TT>Choice
</TT>
968 directives are used to define or select a group, option, or
969 choice.
<A HREF=
"#LISTING4">Listing
4</A> shows a variation of
970 the first example that provides two custom options in a group
973 <p class='example'
><a name=
"LISTING4">Listing
4:
"examples/custom.drv"</a></p>
975 <pre class='example'
>
977 <I>// Include standard font and media definitions
</I>
978 <a href='ref-ppdcfile.html#_include'
>#include
</a> <font.defs
>
979 <a href='ref-ppdcfile.html#_include'
>#include
</a> <media.defs
>
981 <I>// List the fonts that are supported, in this case all standard fonts...
</I>
982 <a href='ref-ppdcfile.html#Font'
>Font
</a> *
984 <I>// Manufacturer, model name, and version
</I>
985 <a href='ref-ppdcfile.html#Manufacturer'
>Manufacturer
</a> "Foo"
986 <a href='ref-ppdcfile.html#ModelName'
>ModelName
</a> "FooJet 2000"
987 <a href='ref-ppdcfile.html#Version'
>Version
</a> 1.0
989 <I>// Each filter provided by the driver...
</I>
990 <a href='ref-ppdcfile.html#Filter'
>Filter
</a> application/vnd.cups-raster
100 rastertofoo
992 <I>// Supported page sizes
</I>
993 *
<a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> Letter
994 <a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> A4
996 <I>// Supported resolutions
</I>
997 *
<a href='ref-ppdcfile.html#Resolution'
>Resolution
</a> k
8 0 0 0 "600dpi/600 DPI"
999 <I>// Option Group
</I>
1000 <a href='ref-ppdcfile.html#Group'
>Group
</a> "Footasm"
1002 <I>// Boolean option
</I>
1003 <a href='ref-ppdcfile.html#Option'
>Option
</a> "fooEnhance/Resolution Enhancement" Boolean AnySetup
10
1004 *
<a href='ref-ppdcfile.html#Choice'
>Choice
</a> True/Yes
"<</cupsCompression 1>>setpagedevice"
1005 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> False/No
"<</cupsCompression 0>>setpagedevice"
1007 <I>// Multiple choice option
</I>
1008 <a href='ref-ppdcfile.html#Option'
>Option
</a> "fooOutputType/Output Quality" PickOne AnySetup
10
1009 *
<a href='ref-ppdcfile.html#Choice'
>Choice
</a> "Auto/Automatic Selection"
1010 "<</OutputType(Auto)>>setpagedevice""
1011 <a href='ref-ppdcfile.html#Choice'>Choice</a> "Text/Optimize for Text
"
1012 "<</OutputType(Text)
>>setpagedevice
""
1013 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "Graph/Optimize for Graphics"
1014 "<</OutputType(Graph)>>setpagedevice""
1015 <a href='ref-ppdcfile.html#Choice'>Choice</a> "Photo/Optimize for Photos
"
1016 "<</OutputType(Photo)
>>setpagedevice
""
1018 <I>// Specify the name of the PPD file we want to generate...
</I>
1019 <a href='ref-ppdcfile.html#PCFileName'
>PCFileName
</a> "foojet2k.ppd"
1022 <P>The custom group is introduced by the
<TT>Group
</TT>
1023 directive which is followed by the name and optionally text for
1026 <pre class='example'
>
1027 <a href='ref-ppdcfile.html#Group'
>Group
</a> "Footasm/Footastic Options"
1030 <P>The group name must conform to the PPD specification and
1031 cannot exceed
40 characters in length. If you specify user text,
1032 it cannot exceed
80 characters in length. The groups
1033 <TT>General
</TT>,
<TT>Extra
</TT>, and
1034 <TT>InstallableOptions
</TT> are predefined by CUPS; the general
1035 and extra groups are filled by the UI options defined by the PPD
1036 specification. The
<TT>InstallableOptions
</TT> group is reserved
1037 for options that define whether accessories for the printer
1038 (duplexer unit, finisher, stapler, etc.) are installed.
</P>
1040 <P>Once the group is specified, the
<TT>Option
</TT> directive is
1041 used to introduce a new option:
</P>
1043 <pre class='example'
>
1044 <a href='ref-ppdcfile.html#Option'
>Option
</a> "fooEnhance/Resolution Enhancement" Boolean AnySetup
10
1047 <P>The directive is followed by the name of the option and any
1048 optional user text, the option type, the PostScript document group, and
1049 the sort order number. The option name must conform to the PPD specification
1050 and cannot exceed
40 characters in length. If you specify user text, it
1051 cannot exceed
80 characters in length.
</P>
1053 <P>The option type can be
<TT>Boolean
</TT> for true/false
1054 selections,
<TT>PickOne
</TT> for picking one of many choices, or
1055 <TT>PickMany
</TT> for picking zero or more choices. Boolean
1056 options can have at most two choices with the names
1057 <TT>False
</TT> and
<TT>True
</TT>. Pick options can have any
1058 number of choices, although for Windows compatibility reasons
1059 the number of choices should not exceed
255.
</P>
1061 <P>The PostScript document group is typically
<TT>AnySetup
</TT>,
1062 meaning that the option can be introduced at any point in the
1063 PostScript document. Other values include
<TT>PageSetup
</TT> to
1064 include the option before each page and
<TT>DocumentSetup
</TT>
1065 to include the option once at the beginning of the document.
</P>
1067 <P>The sort order number is used to sort the printer commands
1068 associated with each option choice within the PostScript
1069 document. This allows you to setup certain options before others
1070 as required by the printer. For most CUPS raster printer
1071 drivers, the value
<TT>10</TT> can be used for all options.
</P>
1073 <P>Once the option is specified, each option choice can be
1074 listed using the
<TT>Choice
</TT> directive:
</P>
1076 <pre class='example'
>
1077 *
<a href='ref-ppdcfile.html#Choice'
>Choice
</a> True/Yes
"<</cupsCompression 1>>setpagedevice"
1078 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> False/No
"<</cupsCompression 0>>setpagedevice"
1081 <P>The directive is followed by the choice name and optionally
1082 user text, and the PostScript commands that should be inserted
1083 when printing a file to this printer. The option name must
1084 conform to the PPD specification and cannot exceed
40 characters
1085 in length. If you specify user text, it cannot exceed
80
1086 characters in length.
</P>
1088 <P>The PostScript commands are also interpreted by any RIP
1089 filters, so these commands typically must be present for all
1090 option choices. Most commands take the form:
</P>
1092 <pre class='example'
>
1093 <</name value
>>setpagedevice
1096 <P>where
<TT>name
</TT> is the name of the PostScript page device
1097 attribute and
<TT>value
</TT> is the numeric or string value for
1101 <h3><a name='DEFINE'
>Defining Constants
</a></h3>
1103 <P>Sometimes you will want to define constants for your drivers
1104 so that you can share values in different groups within the same
1105 driver information file, or to share values between different
1106 driver information files using the
<TT>#include
</TT> directive.
1107 The
<TT>#define
</TT> directive is used to define constants for
1108 use in your printer definitions:
</P>
1110 <pre class='example'
>
1111 <a href='ref-ppdcfile.html#_define'
>#define
</a> NAME value
1114 <P>The
<TT>NAME
</TT> is any sequence of letters, numbers, and
1115 the underscore. The
<TT>value
</TT> is a number or string; if the
1116 value contains spaces you must put double quotes around it, for
1119 <pre class='example'
>
1120 <a href='ref-ppdcfile.html#_define'
>#define
</a> FOO
"My String Value"
1123 <P>Constants can also be defined on the command-line using the
<tt>-D
</tt>
1126 <pre class='command'
>
1127 ppdc
-DNAME=
"value" filename.drv
1130 <P>Once defined, you use the notation
<TT>$NAME
</TT> to substitute the value of
1131 the constant in the file, for example:
</P>
1133 <pre class='example'
>
1134 <a href='ref-ppdcfile.html#_define'
>#define
</a> MANUFACTURER
"Foo"
1135 <a href='ref-ppdcfile.html#_define'
>#define
</a> FOO_600
0
1136 <a href='ref-ppdcfile.html#_define'
>#define
</a> FOO_1200
1
1139 <a href='ref-ppdcfile.html#Manufacturer'
>Manufacturer
</a> "$MANUFACTURER"
1140 <a href='ref-ppdcfile.html#ModelNumber'
>ModelNumber
</a> $FOO_600
1141 <a href='ref-ppdcfile.html#ModelName'
>ModelName
</a> "FooJet 2000"
1146 <a href='ref-ppdcfile.html#Manufacturer'
>Manufacturer
</a> "$MANUFACTURER"
1147 <a href='ref-ppdcfile.html#ModelNumber'
>ModelNumber
</a> $FOO_1200
1148 <a href='ref-ppdcfile.html#ModelName'
>ModelName
</a> "FooJet 2001"
1153 <P>Numeric constants can be bitwise OR'd together by placing the constants
1154 inside parenthesis, for example:
</P>
1156 <pre class='example'
>
1157 <I>// ModelNumber capability bits
</I>
1158 <a href='ref-ppdcfile.html#_define'
>#define
</a> DUPLEX
1
1159 <a href='ref-ppdcfile.html#_define'
>#define
</a> COLOR
2
1164 <I>// Define a model number specifying the capabilities of the printer...
</I>
1165 <a href='ref-ppdcfile.html#ModelNumber'
>ModelNumber
</a> ($DUPLEX $COLOR)
1171 <h3><a name='CONDITIONAL'
>Conditional Statements
</a></h3>
1173 <p>The PPD compiler supports conditional compilation using the
<tt>#if
</tt>,
1174 <tt>#elif
</tt>,
<tt>#else
</tt>, and
<tt>#endif
</tt> directives. The
<tt>#if
</tt>
1175 and
<tt>#elif
</tt> directives are followed by a constant name or an expression.
1176 For example, to include a group of options when
"ADVANCED" is defined:
</p>
1178 <pre class='example'
>
1179 <a href='ref-ppdcfile.html#_if'
>#if
</a> ADVANCED
1180 <a href='ref-ppdcfile.html#Group'
>Group
</a> "Advanced/Advanced Options"
1181 <a href='ref-ppdcfile.html#Option'
>Option
</a> "fooCyanAdjust/Cyan Adjustment"
1182 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "plus10/+10%" ""
1183 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "plus5/+5%" ""
1184 *
<a href='ref-ppdcfile.html#Choice'
>Choice
</a> "none/No Adjustment" ""
1185 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "minus5/-5%" ""
1186 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "minus10/-10%" ""
1187 <a href='ref-ppdcfile.html#Option'
>Option
</a> "fooMagentaAdjust/Magenta Adjustment"
1188 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "plus10/+10%" ""
1189 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "plus5/+5%" ""
1190 *
<a href='ref-ppdcfile.html#Choice'
>Choice
</a> "none/No Adjustment" ""
1191 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "minus5/-5%" ""
1192 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "minus10/-10%" ""
1193 <a href='ref-ppdcfile.html#Option'
>Option
</a> "fooYellowAdjust/Yellow Adjustment"
1194 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "plus10/+10%" ""
1195 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "plus5/+5%" ""
1196 *
<a href='ref-ppdcfile.html#Choice'
>Choice
</a> "none/No Adjustment" ""
1197 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "minus5/-5%" ""
1198 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "minus10/-10%" ""
1199 <a href='ref-ppdcfile.html#Option'
>Option
</a> "fooBlackAdjust/Black Adjustment"
1200 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "plus10/+10%" ""
1201 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "plus5/+5%" ""
1202 *
<a href='ref-ppdcfile.html#Choice'
>Choice
</a> "none/No Adjustment" ""
1203 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "minus5/-5%" ""
1204 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "minus10/-10%" ""
1205 <a href='ref-ppdcfile.html#_endif'
>#endif
</a>
1209 <h3><a name='CONSTRAINTS'
>Defining Constraints
</a></h3>
1211 <P>Constraints are strings that are used to specify that one or more option
1212 choices are incompatible, for example two-sided printing on transparency media.
1213 Constraints are also used to prevent the use of uninstalled features such as the
1214 duplexer unit, additional media trays, and so forth.
</P>
1216 <P>The
<TT>UIConstraints
</TT> directive is used to specify a constraint that is
1217 placed in the PPD file. The directive is followed by a string using one of the
1218 following formats:
</P>
1220 <pre class='example'
>
1221 <a href='ref-ppdcfile.html#UIConstraints'
>UIConstraints
</a> "*Option1 *Option2"
1222 <a href='ref-ppdcfile.html#UIConstraints'
>UIConstraints
</a> "*Option1 Choice1 *Option2"
1223 <a href='ref-ppdcfile.html#UIConstraints'
>UIConstraints
</a> "*Option1 *Option2 Choice2"
1224 <a href='ref-ppdcfile.html#UIConstraints'
>UIConstraints
</a> "*Option1 Choice1 *Option2 Choice2"
1227 <P>Each option name is preceded by the asterisk (
<TT>*
</TT>). If no choice is
1228 given for an option, then all choices
<I>except
</I> <TT>False
</TT> and
1229 <TT>None
</TT> will conflict with the other option and choice(s). Since the PPD
1230 compiler automatically adds reciprocal constraints (option A conflicts with
1231 option B, so therefore option B conflicts with option A), you need only specify
1232 the constraint once.
</P>
1234 <p class='example'
><a name=
"LISTING5">Listing
5:
"examples/constraint.drv"</a></p>
1236 <pre class='example'
>
1238 <I>// Include standard font and media definitions
</I>
1239 <a href='ref-ppdcfile.html#_include'
>#include
</a> <font.defs
>
1240 <a href='ref-ppdcfile.html#_include'
>#include
</a> <media.defs
>
1242 <I>// List the fonts that are supported, in this case all standard fonts...
</I>
1243 <a href='ref-ppdcfile.html#Font'
>Font
</a> *
1245 <I>// Manufacturer, model name, and version
</I>
1246 <a href='ref-ppdcfile.html#Manufacturer'
>Manufacturer
</a> "Foo"
1247 <a href='ref-ppdcfile.html#ModelName'
>ModelName
</a> "FooJet 2000"
1248 <a href='ref-ppdcfile.html#Version'
>Version
</a> 1.0
1250 <I>// Each filter provided by the driver...
</I>
1251 <a href='ref-ppdcfile.html#Filter'
>Filter
</a> application/vnd.cups-raster
100 rastertofoo
1253 <I>// Supported page sizes
</I>
1254 *
<a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> Letter
1255 <a href='ref-ppdcfile.html#MediaSize'
>MediaSize
</a> A4
1257 <I>// Supported resolutions
</I>
1258 *
<a href='ref-ppdcfile.html#Resolution'
>Resolution
</a> k
8 0 0 0 "600dpi/600 DPI"
1260 <I>// Installable Option Group
</I>
1261 <a href='ref-ppdcfile.html#Group'
>Group
</a> "InstallableOptions/Options Installed"
1263 <I>// Duplexing unit option
</I>
1264 <a href='ref-ppdcfile.html#Option'
>Option
</a> "OptionDuplexer/Duplexing Unit" Boolean AnySetup
10
1265 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> True/Installed
""
1266 *
<a href='ref-ppdcfile.html#Choice'
>Choice
</a> "False/Not Installed" ""
1268 <I>// General Option Group
</I>
1269 <a href='ref-ppdcfile.html#Group'
>Group
</a> General
1271 <I>// Duplexing option
</I>
1272 <a href='ref-ppdcfile.html#Option'
>Option
</a> "Duplex/Two-Sided Printing" PickOne AnySetup
10
1273 *
<a href='ref-ppdcfile.html#Choice'
>Choice
</a> "None/No" "<</Duplex false>>setpagedevice""
1274 <a href='ref-ppdcfile.html#Choice'>Choice</a> "DuplexNoTumble/Long Edge Binding
"
1275 "<</Duplex true/Tumble false
>>setpagedevice
""
1276 <a href='ref-ppdcfile.html#Choice'
>Choice
</a> "DuplexTumble/Short Edge Binding"
1277 "<</Duplex true/Tumble true>>setpagedevice""
1279 <I>// Only allow duplexing if the duplexer is installed</I>
1280 <a href='ref-ppdcfile.html#UIConstraints'>UIConstraints</a> "*Duplex *OptionDuplexer False
"
1282 <I>// Specify the name of the PPD file we want to generate...</I>
1283 <a href='ref-ppdcfile.html#PCFileName'>PCFileName</a> "foojet2k.ppd
"
1286 <P><A HREF="#LISTING5
">Listing 5</A> shows a variation of the first example with
1287 an added <TT>Duplex</TT> option and installable option for the duplexer,
1288 <TT>OptionDuplex</TT>. A constraint is added at the end to specify that any
1289 choice of the <TT>Duplex</TT> option that is not <TT>None</TT> is incompatible
1290 with the "Duplexer Installed
" option set to "Not Installed
"
1291 (<TT>False</TT>):</P>
1293 <pre class='example'>
1294 <a href='ref-ppdcfile.html#UIConstraints'>UIConstraints</a> "*Duplex *OptionDuplexer False
"
1297 <h4>Enhanced Constraints</h4>
1299 <p>CUPS 1.4 supports constraints between 2 or more options using the
1300 <TT>Attribute</TT> directive. <TT>cupsUIConstraints</TT> attributes define
1301 the constraints, while <TT>cupsUIResolver</TT> attributes define option changes
1302 to resolve constraints. For example, we can specify the previous duplex
1303 constraint with a resolver that turns off duplexing with the following two
1306 <pre class='example'>
1307 <a href='ref-ppdcfile.html#Attribute'>Attribute</a> cupsUIConstraints DuplexOff "*Duplex *OptionDuplexer False
"
1308 <a href='ref-ppdcfile.html#Attribute'>Attribute</a> cupsUIResolver DuplexOff "*Duplex None
"
1311 <h2 class='title'><a name='LOCALIZATION'>Localization</a></h2>
1313 <p>The PPD compiler provides localization of PPD files in different languages
1314 through <i>message catalog</i> files in the GNU gettext or Apple .strings
1315 formats. Each user text string and several key PPD attribute values such as
1316 <tt>LanguageVersion</tt> and <tt>LanguageEncoding</tt> are looked up in the
1317 corresponding message catalog and the translated text is substituted in the
1318 generated PPD files. One message catalog file can be used by multiple driver
1319 information files, and each file contains a single language translation.</p>
1321 <h3><a name='PPDPO'>The ppdpo Utility</a></h3>
1323 <p>While CUPS includes localizations of all standard media sizes and options in
1324 several languages, your driver information files may provide their own media
1325 sizes and options that need to be localized. CUPS provides a utility program to
1326 aid in the localization of drivers called <a
1327 href='man-ppdpo.html'><tt>ppdpo(1)</tt></a>. The <tt>ppdpo</tt> program creates
1328 or updates a message catalog file based upon one or more driver information
1329 files. New messages are added with the word "TRANSLATE
" added to the front of
1330 the translation string to make locating new strings for translation easier. The
1331 program accepts the message catalog filename and one or more driver information
1334 <p>For example, run the following command to create a new German message catalog
1335 called <var>de.po</var> for all of the driver information files in the current
1338 <pre class='command'>
1339 ppdpo -o de.po *.drv
1342 <p>If the file <var>de.po</var> already exists, <tt>ppdpo</tt> will update the
1343 contents of the file with any new messages that need to be translated. To create
1344 an Apple .strings file instead, specify the output filename with a .strings
1345 extension, for example:</p>
1347 <pre class='command'>
1348 ppdpo -o de.strings *.drv
1351 <h3><a name='PPDC_CATALOG'>Using Message Catalogs with the PPD Compiler</a></h3>
1353 <p>Once you have created a message catalog, use the <a
1354 href='ref-ppdcfile.html#_po'><tt>#po</tt></a> directive to declare it in each
1355 driver information file. For example, to declare the German message catalog for
1358 <pre class='example'>
1359 <a href='ref-ppdcfile.html#_po'>#po</a> de "de.po
" // German
1362 <p>In fact, you can use the <tt>#po</tt> directive as many times as needed:</p>
1364 <pre class='example'>
1365 <a href='ref-ppdcfile.html#_po'>#po</a> de "de.po
" // German
1366 <a href='ref-ppdcfile.html#_po'>#po</a> es "es.po
" // Spanish
1367 <a href='ref-ppdcfile.html#_po'>#po</a> fr "fr.po
" // French
1368 <a href='ref-ppdcfile.html#_po'>#po</a> it "it.po
" // Italian
1369 <a href='ref-ppdcfile.html#_po'>#po</a> ja "ja.po
" // Japanese
1372 <p>The filename ("de.po
", etc.) can be relative to the location of the driver
1373 information file or an absolute path. Once defined, the PPD compiler will
1374 automatically generate a globalized PPD for every language declared in your
1375 driver information file. To generate a single-language PPD file, simply use the
1376 <tt>-l</tt> option to list the corresponding locale, for example:</p>
1378 <pre class='command'>
1379 ppdc -l de -d ppd/de mydrivers.drv
1382 <p>to generate German PPD files.</p>