#, fuzzy msgid "" msgstr "" "Project-Id-Version: cups 1.4b2\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2009-01-10 21:21-0200\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language-Team: LANGUAGE \n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=UTF-8\n" "Content-Transfer-Encoding: 8bit\n" "X-Generator: Translate Toolkit 1.2.1\n" #: ./ppd-compiler.html:1 msgid "Introduction to the PPD Compiler" msgstr "" #: ./ppd-compiler.html:2 msgid "Programming" msgstr "" #: ./ppd-compiler.html:3 msgid "Mini-XML v2.6" msgstr "" #: ./ppd-compiler.html:4 msgid "" "This document describes how to use the CUPS PostScript Printer Description " "(PPD) file compiler. The PPD compiler generates PPD files from simple text " "files that describe the features and capabilities of one or more printers." msgstr "" #: ./ppd-compiler.html:5 msgid "General Information" msgstr "" #: ./ppd-compiler.html:6 msgid "See Also" msgstr "" #: ./ppd-compiler.html:7 msgid "" "Programming: Developing Raster Printer " "Drivers
\tProgramming: Developing " "PostScript Printer Drivers
\tProgramming: Filter and Backend Programming
\tProgramming: Raster API
\tReferences: PPD Compiler Driver Information File Reference
\t" "Specifications: CUPS PPD Extensions" msgstr "" #: ./ppd-compiler.html:8 msgid "Contents" msgstr "" #: ./ppd-compiler.html:9 msgctxt "./ppd-compiler.html:9" msgid "The Basics" msgstr "" #: ./ppd-compiler.html:10 msgctxt "./ppd-compiler.html:10" msgid "Driver Information Files" msgstr "" #: ./ppd-compiler.html:11 msgctxt "./ppd-compiler.html:11" msgid "A Simple Example" msgstr "" #: ./ppd-compiler.html:12 msgctxt "./ppd-compiler.html:12" msgid "Grouping and Inheritance" msgstr "" #: ./ppd-compiler.html:13 msgctxt "./ppd-compiler.html:13" msgid "Color Support" msgstr "" #: ./ppd-compiler.html:14 msgctxt "./ppd-compiler.html:14" msgid "Defining Custom Options and Option Groups" msgstr "" #: ./ppd-compiler.html:15 msgctxt "./ppd-compiler.html:15" msgid "Defining Constants" msgstr "" #: ./ppd-compiler.html:16 msgctxt "./ppd-compiler.html:16" msgid "Conditional Statements" msgstr "" #: ./ppd-compiler.html:17 msgctxt "./ppd-compiler.html:17" msgid "Defining Constraints" msgstr "" #: ./ppd-compiler.html:18 msgctxt "./ppd-compiler.html:18" msgid "The Basics" msgstr "" #: ./ppd-compiler.html:19 msgid "" "The PPD compiler, ppdc(1), is a " "simple command-line tool that takes a single driver information file, " "which by convention uses the extension .drv, and produces one or " "more PPD files that may be distributed with your printer drivers for use " "with CUPS. For example, you would run the following command to create the " "English language PPD files defined by the driver information file " "mydrivers.drv:" msgstr "" #: ./ppd-compiler.html:20 msgid "" "The PPD files are placed in a subdirectory called ppd. The " "-d option is used to put the PPD files in a different location, for " "example:" msgstr "" #: ./ppd-compiler.html:21 msgid "" "places the PPD files in a subdirectory named myppds. Finally, use " "the -l option to specify the language localization for the PPD " "files that are created, for example:" msgstr "" #: ./ppd-compiler.html:22 msgid "" "creates PPD files in German (de), English (en), Spanish (es), French (fr), " "and Italian (it) in the corresponding subdirectories. Specify multiple " "languages (separated by commas) to produce \"globalized\" PPD files:" msgstr "" #: ./ppd-compiler.html:23 msgctxt "./ppd-compiler.html:23" msgid "Driver Information Files" msgstr "" #: ./ppd-compiler.html:24 msgid "" "The driver information files accepted by the PPD compiler are plain text " "files that define the various attributes and options that are included in " "the PPD files that are generated. A driver information file can define the " "information for one or more printers and their corresponding PPD files." msgstr "" #: ./ppd-compiler.html:25 msgid "Listing 1: \"examples/minimum.drv\"" msgstr "" #: ./ppd-compiler.html:26 msgctxt "./ppd-compiler.html:26" msgid "A Simple Example" msgstr "" #: ./ppd-compiler.html:27 msgid "" "The example in Listing 1 shows a driver information " "file which defines the minimum required attributes to provide a valid PPD " "file. The first part of the file includes standard definition files for " "fonts and media sizes:" msgstr "" #: ./ppd-compiler.html:28 msgid "" "The #include directive works just like the C/C++ include directive; " "files included using the angle brackets () are found " "in any of the standard include directories and files included using quotes " "(\"filename\") are found in the same directory as the source or " "include file. The include file defines the standard " "fonts which are included with GPL Ghostscript and the Apple PDF RIP, while " "the include file defines the standard media sizes " "listed in Appendix B of the Adobe PostScript Printer Description File Format " "Specification." msgstr "" #: ./ppd-compiler.html:29 msgid "CUPS provides several other standard include files:" msgstr "" #: ./ppd-compiler.html:30 msgid "" " - Defines all of the rastertoepson driver \tconstants." msgstr "" #: ./ppd-compiler.html:31 msgid "" " - Defines all of the rastertoescpx driver \tconstants." msgstr "" #: ./ppd-compiler.html:32 msgid " - Defines all of the rastertohp driver \tconstants." msgstr "" #: ./ppd-compiler.html:33 msgid "" " - Defines all of the rastertolabel driver \tconstants." msgstr "" #: ./ppd-compiler.html:34 msgid "" " - Defines all of the rastertopclx driver \tconstants." msgstr "" #: ./ppd-compiler.html:35 msgid "" " - Defines all of the CUPS raster format \t" "constants." msgstr "" #: ./ppd-compiler.html:36 msgid "" "Next we list all of the fonts that are available in the driver; for CUPS " "raster drivers, the following line is all that is usually supplied:" msgstr "" #: ./ppd-compiler.html:37 msgid "" "The Font directive specifies the name of a single font or the " "asterisk to specify all fonts. For example, you would use the following line " "to define an additional bar code font that you are supplying with your " "printer driver:" msgstr "" #: ./ppd-compiler.html:38 msgid "" "The name of the font is Barcode-Foo. Since it is not a standard " "text font, the encoding and charset name Special is used. The " "version number is 1.0 and the status (where the font is located) is " "ROM to indicate that the font does not need to be embedded in " "documents that use the font for this printer." msgstr "" #: ./ppd-compiler.html:39 msgid "" "Third comes the manufacturer, model name, and version number information " "strings:" msgstr "" #: ./ppd-compiler.html:40 msgid "" "These strings are used when the user (or auto-configuration program) selects " "the printer driver for a newly connected device." msgstr "" #: ./ppd-compiler.html:41 msgid "" "The list of filters comes after the information strings; for the example in " "Listing 1, we have a single filter that takes CUPS " "raster data:" msgstr "" #: ./ppd-compiler.html:42 msgid "" "Each filter specified in the driver information file is the equivalent of a " "printer driver for that format; if a user submits a print job in a different " "format, CUPS figures out the sequence of commands that will produce a " "supported format for the least relative cost." msgstr "" #: ./ppd-compiler.html:43 msgid "" "Once we have defined the driver information we specify the supported " "options. For the example driver we support a single resolution of 600 dots " "per inch and two media sizes, A4 and Letter:" msgstr "" #: ./ppd-compiler.html:44 msgid "" "The asterisk in front of the MediaSize and Resolution " "directives specify that those option choices are the default. The " "MediaSize directive is followed by a media size name which is " "normally defined in the file and corresponds to a " "standard Adobe media size name. If the default media size is " "Letter, the PPD compiler will override it to be A4 for " "non-English localizations for you automatically." msgstr "" #: ./ppd-compiler.html:45 msgid "" "The Resolution directive accepts several values after it as " "follows:" msgstr "" #: ./ppd-compiler.html:46 msgid "" "Colorspace for this resolution, if any. In the example file, the \tcolorspace " "k is used which corresponds to black. For printer \tdrivers that " "support color printing, this field is usually specified as \t\"-\" for \"no " "change\"." msgstr "" #: ./ppd-compiler.html:47 msgid "" "Bits per color. In the example file, we define 8 bits per color, for \ta " "continuous-tone grayscale output. All versions of CUPS support 1 and \t8 bits " "per color. CUPS 1.2 and higher (Mac OS X 10.5 and higher) also \tsupports " "16 bits per color." msgstr "" #: ./ppd-compiler.html:48 msgid "" "Rows per band. In the example file, we define 0 rows per band to \tindicate " "that our printer driver does not process the page in \tbands." msgstr "" #: ./ppd-compiler.html:49 msgid "" "Row feed. In the example, we define the feed value to be 0 to \tindicate that " "our printer driver does not interleave the output." msgstr "" #: ./ppd-compiler.html:50 msgid "" "Row step. In the example, we define the step value to be 0 to \tindicate that " "our printer driver does not interleave the output. This \tvalue normally " "indicates the spacing between the nozzles of an inkjet \tprinter - when " "combined with the previous two values, it informs the \tdriver how to stagger " "the output on the page to produce interleaved \tlines on the page for " "higher-resolution output." msgstr "" #: ./ppd-compiler.html:51 msgid "" "Choice name and text. In the example, we define the choice name and \ttext to " "be \"600dpi/600 DPI\". The name and text are separated by \tslash " "(/) character; if no text is specified, then the name is \tused as " "the text. The PPD compiler parses the name to determine the \tactual " "resolution; the name can be of the form \tRESOLUTIONdpi for " "resolutions that are equal \thorizontally and vertically or " "HRESxVRESdpi for \tisometric resolutions. Only integer " "resolution values are supported, so \ta resolution name of 300dpi " "is valid while 300.1dpi is \tnot." msgstr "" #: ./ppd-compiler.html:52 msgid "" "Finally, the PCFileName directive specifies that the named PPD file " "should be written for the current driver definitions:" msgstr "" #: ./ppd-compiler.html:53 msgid "" "The filename follows the directive and must conform to the Adobe " "filename requirements in the Adobe Postscript Printer Description File " "Format Specification. Specifically, the filename may not exceed 8 characters " "followed by the extension .ppd. The FileName directive " "can be used to specify longer filenames:" msgstr "" #: ./ppd-compiler.html:54 msgctxt "./ppd-compiler.html:54" msgid "Grouping and Inheritance" msgstr "" #: ./ppd-compiler.html:55 msgid "" "The previous example created a single PPD file. Driver information files can " "also define multiple printers by using the PPD compiler grouping " "functionality. Directives are grouped using the curly braces ({ and " "}) and every group that uses the PCFileName or " "FileName directives produces a PPD file with that name. Listing 2 shows a variation of the original example " "that uses two groups to define two printers that share the same printer " "driver filter but provide two different resolution options." msgstr "" #: ./ppd-compiler.html:56 msgid "Listing 2: \"examples/grouping.drv\"" msgstr "" #: ./ppd-compiler.html:57 msgid "" "The second example is essentially the same as the first, except that each " "printer model is defined inside of a pair of curly braces. For example, the " "first printer is defined using:" msgstr "" #: ./ppd-compiler.html:58 msgid "" "The printer inherits all of the definitions from the parent group " "(the top part of the file) and adds the additional definitions inside the " "curly braces for that printer driver. When we define the second group, it " "also inherits the same definitions from the parent group but none of " "the definitions from the first driver. Groups can be nested to any number of " "levels to support variations of similar models without duplication of " "information." msgstr "" #: ./ppd-compiler.html:59 msgctxt "./ppd-compiler.html:59" msgid "Color Support" msgstr "" #: ./ppd-compiler.html:60 msgid "" "For printer drivers that support color printing, the ColorDevice " "and ColorModel directives should be used to tell the printing " "system that color output is desired and in what formats. Listing 3 shows a variation of the previous example " "which includes a color printer that supports printing at 300 and 600 DPI." msgstr "" #: ./ppd-compiler.html:61 msgid "The key changes are the addition of the ColorDevice directive:" msgstr "" #: ./ppd-compiler.html:62 msgid "" "which tells the printing system that the printer supports color printing, " "and the ColorModel directives:" msgstr "" #: ./ppd-compiler.html:63 msgid "" "which tell the printing system which colorspaces are supported by the " "printer driver for color printing. Each of the ColorModel " "directives is followed by the option name and text (Gray/Grayscale " "and RGB/Color), the colorspace name (w and rgb), " "the color organization (chunky), and the compression mode number " "(0) to be passed to the driver. The option name can be any of the " "standard Adobe ColorModel names:" msgstr "" #: ./ppd-compiler.html:64 msgid "Gray - Grayscale output." msgstr "" #: ./ppd-compiler.html:65 msgid "" "RGB - Color output, typically using the RGB \tcolorspace, but " "without a separate black channel." msgstr "" #: ./ppd-compiler.html:66 msgid "CMYK - Color output with a separate black \tchannel." msgstr "" #: ./ppd-compiler.html:67 msgid "" "Custom names can be used, however it is recommended that you use your vendor " "prefix for any custom names, for example \"fooName\"." msgstr "" #: ./ppd-compiler.html:68 msgid "" "The colorspace name can be any of the following universally supported " "colorspaces:" msgstr "" #: ./ppd-compiler.html:69 msgid "w - Luminance" msgstr "" #: ./ppd-compiler.html:70 msgid "rgb - Red, green, blue" msgstr "" #: ./ppd-compiler.html:71 msgid "k - Black" msgstr "" #: ./ppd-compiler.html:72 msgid "cmy - Cyan, magenta, yellow" msgstr "" #: ./ppd-compiler.html:73 msgid "cmyk - Cyan, magenta, yellow, black" msgstr "" #: ./ppd-compiler.html:74 msgid "The color organization can be any of the following values:" msgstr "" #: ./ppd-compiler.html:75 msgid "" "chunky - Color values are passed together on a line \tas RGB RGB RGB " "RGB" msgstr "" #: ./ppd-compiler.html:76 msgid "" "banded - Color values are passed separately \ton a line as RRRR GGGG " "BBBB; not supported by the Apple \tRIP filters" msgstr "" #: ./ppd-compiler.html:77 msgid "" "planar - Color values are passed separately \ton a page as RRRR RRRR " "RRRR ... GGGG GGGG GGGG ... BBBB \tBBBB BBBB; not supported by the Apple RIP " "filters" msgstr "" #: ./ppd-compiler.html:78 msgid "" "The compression mode value is passed to the driver in the " "cupsCompression attribute. It is traditionally used to select an " "appropriate compression mode for the color model but can be used for any " "purpose, such as specifying a photo mode vs. standard mode." msgstr "" #: ./ppd-compiler.html:79 msgid "Listing 3: \"examples/color.drv\"" msgstr "" #: ./ppd-compiler.html:80 msgctxt "./ppd-compiler.html:80" msgid "Defining Custom Options and Option Groups" msgstr "" #: ./ppd-compiler.html:81 msgid "" "The Group, Option, and Choice directives are used " "to define or select a group, option, or choice. Listing " "4 shows a variation of the first example that provides two custom " "options in a group named \"Footasm\"." msgstr "" #: ./ppd-compiler.html:82 msgid "Listing 4: \"examples/custom.drv\"" msgstr "" #: ./ppd-compiler.html:83 msgid "" "The custom group is introduced by the Group directive which is " "followed by the name and optionally text for the user:" msgstr "" #: ./ppd-compiler.html:84 msgid "" "The group name must conform to the PPD specification and cannot exceed 40 " "characters in length. If you specify user text, it cannot exceed 80 " "characters in length. The groups General, Extra, and " "InstallableOptions are predefined by CUPS; the general and extra " "groups are filled by the UI options defined by the PPD specification. The " "InstallableOptions group is reserved for options that define " "whether accessories for the printer (duplexer unit, finisher, stapler, etc.) " "are installed." msgstr "" #: ./ppd-compiler.html:85 msgid "" "Once the group is specified, the Option directive is used to " "introduce a new option:" msgstr "" #: ./ppd-compiler.html:86 msgid "" "The directive is followed by the name of the option and any optional user " "text, the option type, the PostScript document group, and the sort order " "number. The option name must conform to the PPD specification and cannot " "exceed 40 characters in length. If you specify user text, it cannot exceed " "80 characters in length." msgstr "" #: ./ppd-compiler.html:87 msgid "" "The option type can be Boolean for true/false selections, " "PickOne for picking one of many choices, or PickMany for " "picking zero or more choices. Boolean options can have at most two choices " "with the names False and True. Pick options can have any " "number of choices, although for Windows compatibility reasons the number of " "choices should not exceed 255." msgstr "" #: ./ppd-compiler.html:88 msgid "" "The PostScript document group is typically AnySetup, meaning that " "the option can be introduced at any point in the PostScript document. Other " "values include PageSetup to include the option before each page and " "DocumentSetup to include the option once at the beginning of the " "document." msgstr "" #: ./ppd-compiler.html:89 msgid "" "The sort order number is used to sort the printer commands associated with " "each option choice within the PostScript document. This allows you to setup " "certain options before others as required by the printer. For most CUPS " "raster printer drivers, the value 10 can be used for all options." msgstr "" #: ./ppd-compiler.html:90 msgid "" "Once the option is specified, each option choice can be listed using the " "Choice directive:" msgstr "" #: ./ppd-compiler.html:91 msgid "" "The directive is followed by the choice name and optionally user text, and " "the PostScript commands that should be inserted when printing a file to this " "printer. The option name must conform to the PPD specification and cannot " "exceed 40 characters in length. If you specify user text, it cannot exceed " "80 characters in length." msgstr "" #: ./ppd-compiler.html:92 msgid "" "The PostScript commands are also interpreted by any RIP filters, so these " "commands typically must be present for all option choices. Most commands " "take the form:" msgstr "" #: ./ppd-compiler.html:93 msgid "" "where name is the name of the PostScript page device attribute and " "value is the numeric or string value for that attribute." msgstr "" #: ./ppd-compiler.html:94 msgctxt "./ppd-compiler.html:94" msgid "Defining Constants" msgstr "" #: ./ppd-compiler.html:95 msgid "" "Sometimes you will want to define constants for your drivers so that you can " "share values in different groups within the same driver information file, " "or to share values between different driver information files using the " "#include directive. The #define directive is used to " "define constants for use in your printer definitions:" msgstr "" #: ./ppd-compiler.html:96 msgid "" "The NAME is any sequence of letters, numbers, and the underscore. " "The value is a number or string; if the value contains spaces you " "must put double quotes around it, for example:" msgstr "" #: ./ppd-compiler.html:97 msgid "" "Constants can also be defined on the command-line using the -D " "option:" msgstr "" #: ./ppd-compiler.html:98 msgid "" "Once defined, you use the notation $NAME to substitute the value of " "the constant in the file, for example:" msgstr "" #: ./ppd-compiler.html:99 msgid "" "Numeric constants can be bitwise OR'd together by placing the constants " "inside parenthesis, for example:" msgstr "" #: ./ppd-compiler.html:100 msgctxt "./ppd-compiler.html:100" msgid "Conditional Statements" msgstr "" #: ./ppd-compiler.html:101 msgid "" "The PPD compiler supports conditional compilation using the #if, " "#elif, #else, and #endif directives. The " "#if and #elif directives are followed by a constant name " "or an expression. For example, to include a group of options when \"ADVANCED\" " "is defined:" msgstr "" #: ./ppd-compiler.html:102 msgctxt "./ppd-compiler.html:102" msgid "Defining Constraints" msgstr "" #: ./ppd-compiler.html:103 msgid "" "Constraints are strings that are used to specify that one or more option " "choices are incompatible, for example two-sided printing on transparency " "media. Constraints are also used to prevent the use of uninstalled features " "such as the duplexer unit, additional media trays, and so forth." msgstr "" #: ./ppd-compiler.html:104 msgid "" "The UIConstraints directive is used to specify a constraint that is " "placed in the PPD file. The directive is followed by a string using one of " "the following formats:" msgstr "" #: ./ppd-compiler.html:105 msgid "" "Each option name is preceded by the asterisk (*). If no choice is " "given for an option, then all choices except False and " "None will conflict with the other option and choice(s). Since the " "PPD compiler automatically adds reciprocal constraints (option A conflicts " "with option B, so therefore option B conflicts with option A), you need only " "specify the constraint once." msgstr "" #: ./ppd-compiler.html:106 msgid "Listing 5: \"examples/constraint.drv\"" msgstr "" #: ./ppd-compiler.html:107 msgid "" "Listing 5 shows a variation of the first example " "with an added Duplex option and installable option for the " "duplexer, OptionDuplex. A constraint is added at the end to specify " "that any choice of the Duplex option that is not None is " "incompatible with the \"Duplexer Installed\" option set to \"Not Installed\" " "(False):" msgstr "" #: ./ppd-compiler.html:108 msgid "Enhanced Constraints" msgstr "" #: ./ppd-compiler.html:109 msgid "" "CUPS 1.4 supports constraints between 2 or more options using the " "Attribute directive. cupsUIConstraints attributes define " "the constraints, while cupsUIResolver attributes define option " "changes to resolve constraints. For example, we can specify the previous " "duplex constraint with a resolver that turns off duplexing with the " "following two lines:" msgstr ""