Introduction
I tried those OIDs but it did not return any values. I have done SNMP walks on the APs and found out that clinet node MAC addr are not on the consecutive OIDs. For example one of the nodes I saw on the web page and ten tried to look it up in the snmpwalk was.iso.3.6.1.2.1.17.4.3.1.1.0.7.14.179.132.193. And other one was on. The npm package includes pre-built forge.min.js, forge.all.min.js, and prime.worker.min.js using the UMD format. Each release is published in a separate repository as pre-built and minimized basic forge bundles using the UMD format.
This specification describes the attributes and extensionsthat CUPS adds to Adobe TechNote #5003: PostScript Printer Description File FormatSpecification Version 4.3. PostScript Printer Description('PPD') files describe the capabilities of each printer and areused by CUPS to support printer-specific features and intelligentfiltering.
PPD File Syntax
The PPD format is text-based and uses lines of up to 255characters terminated by a carriage return, linefeed, orcombination of carriage return and line feed. The following ABNFdefinition [RFC4234] defines the general format of lines in a PPDfile:
Auto-Configuration
CUPS supports several methods of auto-configuration via PPD attributes.Currently these methods are only implemented on Mac OS X.
Mac OS X 10.5APAutoSetupTool
*APAutoSetupTool: '/LibraryPrinters/vendor/filename'
This attribute defines a program that sets the default option choices. Itis run when a printer is added from the printer browser instead of thenormal PostScript query and SNMP OID attribute lookups.
The program is provided with two arguments: the printer's device URI andthe PPD file to be used for the printer. The program must write an updatedPPD file to stdout.
Examples:
Mac OS X 10.2?MainKeyword
*?MainKeyword: '
PostScript query code that writes a message using the = operator..
'
*End
The ?MainKeyword attribute defines PostScript code thatdetermines the currently selected/enabled option keyword (choice) for themain keyword (option). It is typically used when communicating with USB,serial, Appletalk, and AppSocket (port 9100) printers.
The PostScript code typically sends its response back using the =operator.
Example:
Mac OS X 10.4OIDMainKeyword
*?OIDMainKeyword: '.n.n.n..'
*OIDMainKeywordOptionKeyword1: 'value'
..
*OIDMainKeywordOptionKeywordN: 'value'
The OIDMainKeyword attribute is used to defineSNMP OIDs that map to installable options. The first (query) linedefines the OID to lookup on the network device. The second andsubsequent attributes define a mapping from OID value to optionkeyword. Since SNMP is an IP-based network protocol, this methodis typically only used to configure AppSocket, IPP, and LPD networkprinters.
Examples:
Color Profiles
CUPS supports three types of color profiles. The first type isbased on sRGB and is used by the standard CUPS raster filters andGPL Ghostscript. The second type is based on ICC profiles and isused by the Quartz-based filters on MacOS X. The final type isbased on well-known colorspaces such as sRGB and Adobe RGB.
Note:At this time, none of the CUPS raster filters support ICC profiles. Thiswill be addressed as time and resources permit.
DeprecatedcupsColorProfile
*cupsColorProfile Resolution/MediaType: 'densitygamma m00 m01 m02 m10 m11 m12 m20 m21 m22'
This string attribute specifies an sRGB-based color profileconsisting of gamma and density controls and a 3x3 CMY colortransform matrix. This attribute is not supported on Mac OS X.
The Resolution and MediaType values may be '-'to act as a wildcard. Otherwise they must match one of theResolution or MediaType attributes defined inthe PPD file.
The density and gamma values define gamma anddensity adjustment function such that:
The m00 through m22 values define a 3x3transformation matrix for the CMY color values. The densityfunction is applied after the CMY transformation:
Examples:
Mac OS X 10.3/CUPS 1.2/Mac OS X 10.5cupsICCProfile
*cupsICCProfileColorModel.MediaType.Resolution/Description: 'filename'
This attribute specifies an ICC color profile that isused to convert the document colors to the devicecolorspace. The ColorModel, MediaType, andResolution keywords specify a selector for colorprofiles. If omitted, the color profile will match any optionkeyword for the corresponding main keyword.
The Description specifies human-readable text thatis associated with the color profile. The filenameportion specifies the ICC color profile to use; if the filenameis not absolute, it is loaded relative to the/usr/share/cups/profiles directory.
Examples:
Customizing the Profile Selection Keywords
The MediaType and Resolution keywords can bereassigned to different main keywords, allowing drivers to docolor profile selection based on different parameters. ThecupsICCQualifier2 and cupsICCQualifier3attributes define the mapping from selector to main keyword:
The default mapping is as follows:
Mac OS X 10.4Custom Color Matching Support
*APSupportsCustomColorMatching: true
*APCustomColorMatchingName name/text: '
*APCustomColorMatchingProfile: profile
*APDefaultCustomColorMatchingProfile: profile
These attributes tell the Mac OS X raster filters that the printerdriver provides its own custom color matching and that generic colorprofiles should be used when generating 1-, 3-, and 4-component rasterdata as requested by the driver. The APCustomColorMatchingProfileand APDefaultColorMatchingProfile attributes specify alternatecolor profiles (sRGB or AdobeRGB) to use for 3-color (RGB) raster data.
Note:Prior to Mac OS X 10.6, the default RGB color space was Apple's 'GenericRGB'.The new default in Mac OS X 10.6 and later is 'sRGB'. For more information, see'Mac OS X v10.6: About gamma2.2' on Apple's support site.
Mac OS X 10.5APCustomColorMatchingName
*APCustomColorMatchingName name/text: '
This attribute defines an alternate name for the color matchingprovided by a driver in the Color Matching print panel.The default is to use the name 'Vendor Matching' or its localizedequivalent.
Examples:
Mac OS X 10.5APCustomColorMatchingProfile
*APCustomColorMatchingProfile: name
This attribute defines a supported RGB color profile that can be usedwhen doing custom color matching. Currently only sRGB,AdobeRGB, and GenericRGB are supported. If not specified, RGBdata will use the GenericRGB colorspace.
Note:If you provide multiple APCustomColorMatchingProfile attributes,you are responsible for providing the necessary user interface controls toselect the profile in a print dialog pane.Add the named profile to the print settings using the keykPMCustomColorMatchingProfileKey.
Examples:
Mac OS X 10.5APDefaultCustomColorMatchingProfile
*APDefaultCustomColorMatchingProfile: name
This attribute defines the default RGB color profile that will be usedwhen doing custom color matching. Currently only sRGB,AdobeRGB, and GenericRGB are supported.
Examples:
Mac OS X 10.4APSupportsCustomColorMatching
*APSupportsCustomColorMatching: boolean
This attribute specifies that the driver provides its own custom colormatching. When true, the default hand-off colorspace will beGenericGray, GenericRGB, or GenericCMYK depending on the number ofcomponents the driver requests. The APDefaultCustomColorMatchingProfileattribute can be used to override the default 3-component (RGB) colorspace.
The default for APSupportsCustomColorMatching is false.
Examples:
Constraints
Constraints are option choices that are not allowed by the driver ordevice, for example printing 2-sided transparencies. All versions of CUPSsupport constraints defined by the legacy Adobe UIConstraints andNonUIConstraints attributes which support conflicts between any twooption choices, for example:
While nearly all constraints can be expressed using these attributes, thereare valid scenarios requiring constraints between more than two option choices.In addition, resolution of constraints is problematic since users and softwarehave to guess how a particular constraint is best resolved.
CUPS 1.4 and higher define two new attributes for constraints,cupsUIConstraints and cupsUIResolver. EachcupsUIConstraints attribute points to a cupsUIResolverattribute which specifies alternate options that resolve the conflict condition.The same cupsUIResolver can be used by multiplecupsUIConstraints.
Note:When developing PPD files that contain constraints, it is very important to use the cupstestppd(1) program to verify that your constraints are accurate and cannot result in unresolvable option selections.
CUPS 1.4/Mac OS X 10.6cupsUIConstraints
*cupsUIConstraints resolver: '*Keyword1 *Keyword2 ..'
*cupsUIConstraints resolver: '*Keyword1 OptionKeyword1 *Keyword2 ..'
*cupsUIConstraints resolver: '*Keyword1 *Keyword2 OptionKeyword2 ..'
*cupsUIConstraints resolver: '*Keyword1 OptionKeyword1 *Keyword2 OptionKeyword2 ..'
*cupsUIConstraints: '*InstallableKeyword1 OptionKeyword1 *Keyword2 OptionKeyword2 ..'
Lists two or more options which conflict. The 'resolver' string is a(possibly unique) keyword which specifies which options to change when theconstraint exists. When no resolver is provided, CUPS first tries the defaultchoice followed by testing each option choice to resolve the conflict.
Examples:
CUPS 1.4/Mac OS X 10.6cupsUIResolver
*cupsUIResolution resolver: '*Keyword1 OptionKeyword1 *Keyword2 OptionKeyword2 ..'
Specifies two or more options to mark/select to resolve a constraint. The'resolver' string identifies a particular action to take for one or morecupsUIConstraints. The same actioncan be used for multiple constraints. The option keyword pairs are treated asan ordered list of option selections to try - only the first N selections willbe used, where N is the minimum number of selections required. BecausecupsResolveConflicts()
will not change the most recent option selection passed to it, at least twooptions from the constraints must be listed to avoid situations where conflictscannot be resolved.
Oids Mac Os Catalina
Examples:
Globalized PPD Support
CUPS 1.2 and higher adds support for PPD files containing multiplelanguages by following the following additional rules:
- The LanguageVersion MUST be English
- The LanguageEncoding MUST be ISOLatin1
- The cupsLanguages attribute MUST be provided and list each of the supported locales in the PPD file
- Main and option keywords MUST NOT exceed 34 (instead of 40) characters to allow room for the locale prefixes in translation attributes
- The main keyword 'Translation' MUST NOT be used
- Translation strings included with the main and option keywords MUST NOT contain characters outside the ASCII subset of ISOLatin1 and UTF-8; developers wishing to use characters outside ASCII MUST provide a separate set of English localization attributes for the affected keywords.
- Localizations are specified using a locale prefix of the form 'll' or 'll_CC.' where 'll' is the 2-letter ISO language code and 'CC' is the 2-letter ISO country code
- A generic language translation ('ll') SHOULD be provided with country-specific differences ('ll_CC') provided only as needed
- For historical reasons, the 'zh' and 'zh_CN' locales map to Simplified Chinese while the 'zh_TW' locale maps to Traditional Chinese
- Locale-specific translation strings MUST be encoded using UTF-8.
- Main keywords MUST be localized using one of the following forms:
*ll.Translation MainKeyword/translation text: '
*ll_CC.Translation MainKeyword/translation text: ' - Option keywords MUST be localized using one of the following forms:
*ll.MainKeyword OptionKeyword/translation text: '
*ll_CC.MainKeyword OptionKeyword/translation text: ' - Localization attributes MAY appear anywhere after the first line of the PPD file
We use a LanguageEncoding value of ISOLatin1and limit the allowed base translation strings to ASCII to avoidcharacter coding issues that would otherwise occur. In addition,requiring the base translation strings to be in English allowsfor easier fallback translation when no localization is providedin the PPD file for a given locale.
Examples:
Custom Options
CUPS supports custom options using an extension of theCustomPageSize and ParamCustomPageSizesyntax:
When the base option is part of the JCLSetup section,the 'command' string contains JCL commands with 'order'placeholders for each numbered parameter. The CUPS API handlesany necessary value quoting for HP-PJL commands. For example, ifthe JCL command string is '@PJL SET PASSCODE=1' and the firstoption value is '1234' then CUPS will output the string'@PJL SET PASSCODE=1234'.
For non-JCLSetup options, the 'order' value is anumber from 1 to N and specifies the order of values as they areplaced on the stack before the command. For example, if thePostScript command string is'<>setpagedevice' and theoption value is '2.0' then CUPS will output the string'2.0 <>setpagedevice'.
The 'type' is one of the following keywords:
- curve - a real value from 'minimum' to 'maximum' representing a gamma correction curve using the function: f(x) = x value
- int - an integer value from 'minimum' to 'maximum'
- invcurve - a real value from 'minimum' to 'maximum' representing a gamma correction curve using the function: f(x) = x 1 / value
- passcode - a string of numbers value with a minimum of 'minimum' numbers and a maximum of 'maximum' numbers ('minimum' and 'maximum' are numbers and passcode strings are not displayed in the user interface)
- password - a string value with a minimum of 'minimum' characters and a maximum of 'maximum' characters ('minimum' and 'maximum' are numbers and password strings are not displayed in the user interface)
- points - a measurement value in points from 'minimum' to 'maximum'
- real - a real value from 'minimum' to 'maximum'
- string - a string value with a minimum of 'minimum' characters and a maximum of 'maximum' characters ('minimum' and 'maximum' are numbers)
Custom options are not directly supported by the Mac OS X Print Dialognor by the CUPS web interface at this time. Vendors that use customoptions on Mac OS X must provide their own user interface via theAPDialogExtension attribute.
Examples:
Writing PostScript Option Commands for Raster Drivers
PPD files are used for both PostScript and non-PostScript printers. For CUPS raster drivers, you use a subset of the PostScript language to set page device attributes such as page size, resolution, and so forth. For example, the following code sets the page size to A4 size:
Custom options typically use other operators to organize the values into a key/value dictionary for setpagedevice. For example, our previous CustomWatermarkText option code uses the roll operator to move the custom string value into the dictionary for setpagedevice:
For a custom string value of 'My Watermark', CUPS will produce the following PostScript code for the option:
The code moves the string value ('My Watermark') from the bottom of the stack to the top, creating a dictionary that looks like:
The resulting dictionary sets the page device attributes that are sent to your raster driver in the page header.
Custom Page Size Code
There are many possible implementations of the CustomPageSize code. For CUPS raster drivers, the following code is recommended:
Supported PostScript Operators
CUPS supports the following PostScript operators in addition to the usual PostScript number, string (literal and hex-encoded), boolean, null, and name values:
- << - Start a dictionary.
- >> - End a dictionary.
- [ - Start an array.
- ] - End an array.
- copy - Copy the top N objects on the stack.
- dup - Copy the top object on the stack.
- index - Copy the Nth from the top object on the stack.
- pop - Pop the top object on the stack.
- roll - Shift the top N objects on the stack.
- setpagedevice - Set the page header values according to the key/value dictionary on the stack.
Never use the unsupported dict or putoperators in your option code. These operators are typically used inoption code dating back to Level 1 PostScript printers, which did notsupport the simpler << or >> operators.If you have old option code using dict or put, you canrewrite it very easily to use the newer << and>> operators instead. For example, the following codeto set the page size:
can be rewritten as:
Supported Page Device Attributes
Table 2 shows the supported page device attributes along with PostScript code examples.
Name(s) | Type | Description | Example(s) |
---|---|---|---|
AdvanceDistance | Integer | Specifies the number of points to advance roll media after printing. | <>setpagedevice |
AdvanceMedia | Integer | Specifies when to advance the media: 0 = never, 1 = after the file, 2 = after the job, 3 = after the set, and 4 = after the page. | <>setpagedevice |
Collate | Boolean | Specifies whether collated copies are required. | <>setpagedevice |
CutMedia | Integer | Specifies when to cut the media: 0 = never, 1 = after the file, 2 = after the job, 3 = after the set, and 4 = after the page. | <>setpagedevice |
Duplex | Boolean | Specifies whether 2-sided printing is required. | <>setpagedevice |
HWResolution | Integer Array | Specifies the resolution of the page image in pixels per inch. | <>setpagedevice |
InsertSheet | Boolean | Specifies whether to insert a blank sheet before the job. | <>setpagedevice |
Jog | Integer | Specifies when to shift the media in the output bin: 0 = never, 1 = after the file, 2 = after the job, 3 = after the set, and 4 = after the page. | <>setpagedevice |
LeadingEdge | Integer | Specifies the leading edge of the media: 0 = top, 1 = right, 2 = bottom, 3 = left. | <>setpagedevice |
ManualFeed | Boolean | Specifies whether media should be drawn from the manual feed tray. Note: The MediaPosition attribute is preferred over the ManualFeed attribute. | <>setpagedevice |
MediaClass | String | Specifies a named media. | <>setpagedevice |
MediaColor | String | Specifies the color of the media. | <>setpagedevice |
MediaPosition | Integer | Specifies the tray or source of the media. | <>setpagedevice |
MediaType | String | Specifies the general media type. | <>setpagedevice |
MediaWeight | Integer | Specifies the media weight in grams per meter2. | <>setpagedevice |
MirrorPrint | Boolean | Specifies whether to flip the output image horizontally. | <>setpagedevice |
NegativePrint | Boolean | Specifies whether to invert the output image. | <>setpagedevice |
NumCopies | Integer | Specifies the number of copies to produce of each page. | <>setpagedevice |
Orientation | Integer | Specifies the orientation of the output: 0 = portrait, 1 = landscape rotated counter-clockwise, 2 = upside-down, 3 = landscape rotated clockwise. | <>setpagedevice |
OutputFaceUp | Boolean | Specifies whether to place the media face-up in the output bin/tray. | <>setpagedevice |
OutputType | String | Specifies the output type name. | <>setpagedevice |
PageSize | Integer/Real Array | Specifies the width and length/height of the page in points. | <>setpagedevice |
Separations | Boolean | Specifies whether to produce color separations. | <>setpagedevice |
TraySwitch | Boolean | Specifies whether to switch trays automatically. | <>setpagedevice |
Tumble | Boolean | Specifies whether the back sides of pages are rotated 180 degrees. | <>setpagedevice |
cupsBorderlessScalingFactor | Real | Specifies the amount to scale the page image dimensions. | <>setpagedevice |
cupsColorOrder | Integer | Specifies the order of colors: 0 = chunked, 1 = banded, 2 = planar. | <>setpagedevice |
cupsColorSpace | Integer | Specifies the page image colorspace: 0 = W, 1 = RGB, 2 = RGBA, 3 = K, 4 = CMY, 5 = YMC, 6 = CMYK, 7 = YMCK, 8 = KCMY, 9 = KCMYcm, 10 = GMCK, 11 = GMCS, 12 = White, 13 = Gold, 14 = Silver, 15 = CIE XYZ, 16 = CIE Lab, 17 = RGBW, 32 to 46 = CIE Lab (1 to 15 inks) | <>setpagedevice |
cupsCompression | Integer | Specifies a driver compression type/mode. | <>setpagedevice |
cupsInteger0 .. cupsInteger15 | Integer | Specifies driver integer values. | <>setpagedevice |
cupsMarkerType | String | Specifies the type of ink/toner to use. | <>setpagedevice |
cupsMediaType | Integer | Specifies a numeric media type. | <>setpagedevice |
cupsPageSizeName | String | Specifies the name of the page size. | <>setpagedevice |
cupsPreferredBitsPerColor | Integer | Specifies the preferred number of bits per color, typically 8 or 16. | <>setpagedevice |
cupsReal0 .. cupsReal15 | Real | Specifies driver real number values. | <>setpagedevice |
cupsRenderingIntent | String | Specifies the color rendering intent. | <>setpagedevice |
cupsRowCount | Integer | Specifies the number of rows of raster data to print on each line for some drivers. | <>setpagedevice |
cupsRowFeed | Integer | Specifies the number of rows to feed between passes for some drivers. | <>setpagedevice |
cupsRowStep | Integer | Specifies the number of lines between columns/rows on the print head for some drivers. | <>setpagedevice |
cupsString0 .. cupsString15 | String | Specifies driver string values. | <>setpagedevice |
Media Attributes
The CUPS media attributes allow drivers to specify alternate custom pagesize limits based on up to two options.
CUPS 1.4/Mac OS X 10.6cupsMediaQualifier2
*cupsMediaQualifier2: MainKeyword
This attribute specifies the second option to use for overriding thecustom page size limits.
Example:
CUPS 1.4/Mac OS X 10.6cupsMediaQualifier3
*cupsMediaQualifier3: MainKeyword
This attribute specifies the third option to use for overriding thecustom page size limits.
Example:
CUPS 1.4/Mac OS X 10.6cupsMinSize
*cupsMinSize .Qualifier2.Qualifier3: 'width length'
*cupsMinSize .Qualifier2.: 'width length'
*cupsMinSize .Qualifier3: 'width length'
This attribute specifies alternate minimum custom page sizes in points.The cupsMediaQualifier2 andcupsMediaQualifier3 attributesare used to identify options to use for matching.
Example:
CUPS 1.4/Mac OS X 10.6cupsMaxSize
*cupsMaxSize .Qualifier2.Qualifier3: 'width length'
*cupsMaxSize .Qualifier2.: 'width length'
*cupsMaxSize .Qualifier3: 'width length'
This attribute specifies alternate maximum custom page sizes in points.The cupsMediaQualifier2 andcupsMediaQualifier3 attributesare used to identify options to use for matching.
Example:
General Attributes
CUPS 1.3/Mac OS X 10.5cupsBackSide
*cupsBackSide: keyword
This attribute requests special handling of the back side of pageswhen doing duplexed (2-sided) output. Table 1shows the supported keyword values for this attribute and their effecton the raster data sent to your driver. For example, when cupsBackSideis Rotated
and Tumble is false, your driverwill receive print data starting at the bottom right corner of the page, witheach line going right-to-left instead of left-to-right. The default value isNormal
.
cupsBackSide replaces the older cupsFlipDuplexattribute - if cupsBackSide is specified, cupsFlipDuplexwill be ignored.
cupsBackSide | Tumble Value | Image Presentation |
---|---|---|
Normal | false | Left-to-right, top-to-bottom |
Normal | true | Left-to-right, top-to-bottom |
ManualTumble | false | Left-to-right, top-to-bottom |
ManualTumble | true | Right-to-left, bottom-to-top |
Rotated | false | Right-to-left, bottom-to-top |
Rotated | true | Right-to-left, top-to-bottom |
Flipped * | false | Left-to-right, bottom-to-top |
Flipped * | true | Right-to-left, top-to-bottom |
* - Not supported in Mac OS X 10.5.x and earlier
Examples:
Also see the related APDuplexRequiresFlippedMarginattribute.
CUPS 1.4/Mac OS X 10.6cupsCommands
*cupsCommands: 'name name2 .. nameN'
This string attribute specifies the commands that are supported by theCUPS command file filter for this device. The command names are separatedby whitespace.
Example:
CUPS 1.3/Mac OS X 10.5cupsEvenDuplex
*cupsEvenDuplex: boolean
This boolean attribute notifies the RIP filters that thedestination printer requires an even number of pages when 2-sidedprinting is selected. The default value is false
.
Example:
cupsFax
*cupsFax: boolean
This boolean attribute specifies whether the PPD defines a facsimile device. The default is false.
Examples:
cupsFilter
*cupsFilter: 'source/type cost program'
This string attribute provides a conversion rule from thegiven source type to the printer's native format using thefilter 'program'. If a printer supports the source type directly,the special filter program '-' may be specified.
Examples:
DeprecatedcupsFlipDuplex
*cupsFlipDuplex: boolean
Due to implementation differences between Mac OS X and Ghostscript,the cupsFlipDuplex attribute is deprecated. Instead, usethe cupsBackSide attribute to specifythe coordinate system (pixel layout) of the page data on the back side ofduplex pages.
The value true
maps to a cupsBackSide valueof Rotated
on Mac OS X and Flipped
withGhostscript.
The default value is false
.
Mac OS X drivers that previously usedcupsFlipDuplex may wish to provide both the old andnew attributes for maximum compatibility, for example:
Similarly, drivers written for other operating systems usingGhostscript can use:
CUPS 1.3/Mac OS X 10.5cupsIPPFinishings
*cupsIPPFinishings number/text: '*Option Choice ..'
This attribute defines a mapping from IPP finishings
values to PPD options and choices.
Examples:
CUPS 1.3/Mac OS X 10.5cupsIPPReason
*cupsIPPReason reason/Reason Text: 'optional URIs'
This optional attribute maps customprinter-state-reasons
keywords that are generated bythe driver to human readable text. The optional URIs stringcontains zero or more URIs separated by a newline. Each URI canbe a CUPS server absolute path to a help file under thescheduler's DocumentRoot
directory, a full HTTP URL('http://www.domain.com/path/to/help/page.html'), or any othervalid URI which directs the user at additional informationconcerning the condition that is being reported.
Since the reason text is limited to 80 characters by the PPD specification,longer text strings can be included by URI-encoding the text with the 'text'scheme, for example 'text:some%20text'. Multiple text
URIs arecombined (with spaces between each URI) by the ppdLocalizeIPPReasoninto a single string that can be displayed to the user.
Examples:
CUPS 1.2/Mac OS X 10.5cupsLanguages
*cupsLanguages: 'locale list'
This attribute describes which language localizations areincluded in the PPD. The 'locale list' string is a space-delimitedlist of locale names ('en', 'en_US', 'fr_CA', etc.)
Example:
cupsManualCopies
*cupsManualCopies: boolean
This boolean attribute notifies the RIP filters that thedestination printer does not support copy generation inhardware. The default value is false
.
Example:
CUPS 1.4/Mac OS X 10.6cupsMarkerName
*cupsMarkerName/Name Text: ' Tech art project 2 (amwilkes) mac os.
This optional attribute maps marker-names
strings that aregenerated by the driver to human readable text.
Examples:
CUPS 1.4/Mac OS X 10.6cupsMarkerNotice
*cupsMarkerNotice: 'disclaimer text'
This optional attribute provides disclaimer text for the supply levelinformation provided by the driver, typically something like 'supply levelsare approximate'.
Examples:
cupsModelNumber
*cupsModelNumber: number
This integer attribute specifies a printer-specific modelnumber. This number can be used by a filter program to adjustthe output for a specific model of printer.
Example:
CUPS 1.3/Mac OS X 10.5cupsPJLCharset
*cupsPJLCharset: 'ISO character set name'
This string attribute specifies the character set that is usedfor strings in PJL commands. If not specified, US-ASCII isassumed.
Example:
CUPS 1.4/Mac OS X 10.6cupsPJLDisplay
*cupsPJLDisplay: 'what'
This optional attribute specifies which command is used to display thejob ID, name, and user on the printer's control panel. 'What' is either 'none'to disable this functionality, 'job' to use '@PJL JOB DISPLAY', or 'rdymsg'to use '@PJL RDYMSG DISPLAY'. The default is 'job'.
Examples:
CUPS 1.2/Mac OS X 10.5cupsPortMonitor
*cupsPortMonitor urischeme/Descriptive Text: 'port monitor'
This string attribute specifies printer-specific 'portmonitor' filters that may be used with the printer. The CUPSscheduler also looks for the Protocols attribute to seeif the BCP or TBCP protocols are supported. Ifso, the corresponding port monitor ('bcp' and 'tbcp',respectively) is listed in the printer'sport-monitor-supported attribute.
The 'urischeme' portion of the attribute specifies the URI schemethat this port monitor should be used for. Typically this is used topre-select a particular port monitor for each type of connection thatis supported by the printer. The 'port monitor' string can be 'none'to disable the port monitor for the given URI scheme.
Examples:
CUPS 1.3/Mac OS X 10.5cupsPreFilter
*cupsPreFilter: 'source/type cost program'
This string attribute provides a pre-filter rule. The pre-filterprogram will be inserted in the conversion chain immediately before the filter that accepts the given MIME type.
Examples:
CUPS 1.4/Mac OS X 10.6cupsSNMPSupplies
*cupsSNMPSupplies: boolean
This attribute tells the standard network backends whether they should querythe standard SNMP Printer MIB OIDs for supply levels. The default value isTrue
.
Example:
cupsVersion
*cupsVersion: major.minor
This required attribute describes which version of the CUPSPPD file extensions was used. Currently it must be the string'1.0', '1.1', '1.2', or '1.3'.
Example:
Mac OS X Attributes
Mac OS X 10.3APDialogExtension
*APDialogExtension: '/Library/Printers/vendor/filename.plugin'
This attribute defines additional option panes that are displayed in theprint dialog. Each attribute adds one or more option panes. See the 'OutputBinsPDE'example and AppleTechnical Q&A QA1352 for information on writing your own print dialogplug-ins.
Note:Starting with Mac OS X 10.5, each plug-in must be compiled '4-way fat'(32-bit and 64-bit for both PowerPC and Intel) with garbage collection enabledin order to be usable with all applications.
Examples:
Mac OS X 10.4APDuplexRequiresFlippedMargin
*APDuplexRequiresFlippedMargin: boolean
This boolean attribute notifies the RIP filters that thedestination printer requires the top and bottom margins of theImageableArea to be swapped for the back page. Thedefault is true when cupsBackSide is Flippedand false otherwise. Table 2 shows howAPDuplexRequiresFlippedMargin interacts with cupsBackSideand the Tumble page attribute.
APDuplexRequiresFlippedMargin | cupsBackSide | Tumble Value | Margins |
---|---|---|---|
false | any | any | Normal |
any | Normal | any | Normal |
true | ManualDuplex | false | Normal |
true | ManualDuplex | true | Flipped |
true | Rotated | false | Flipped |
true | Rotated | true | Normal |
true or unspecified | Flipped | any | Flipped |
Example:
Also see the related cupsBackSideattribute.
APHelpBook
*APHelpBook: 'bundle URL'
This string attribute specifies the Apple help book bundle to use whenlooking up IPP reason codes for this printer driver. ThecupsIPPReason attribute maps'help' URIs to this file.
Example:
Mac OS X 10.6APICADriver
*APICADriver: boolean
This attribute specifies whether the device has a matching Image CaptureArchitecture (ICA) driver for scanning. The default is False.
Examples:
Oids Mac Os Download
Mac OS X 10.3APPrinterIconPath
*APPrinterIconPath: '/Library/Printers/vendor/filename.icns'
This attribute defines the location of a printer icon file to use whendisplaying the printer. The file must be in the Apple icon format.
Examples:
Mac OS X 10.4APPrinterLowInkTool
*APPrinterLowInkTool: '/Library/Printers/vendor/program'
This attribute defines an program that checks the ink/toner/marker levelson a printer, returning an XML document with those levels. See the 'InkTool'example andAppleTechnical Note TN2144 for more information.
Examples:
Mac OS X 10.5APPrinterPreset
*APPrinterPreset name/text: '*Option Choice ..'
This attribute defines presets for multiple options that show upin the print dialog of applications (such as iPhoto) that set the jobstyle hint to NSPrintPhotoJobStyleHint. Each preset maps to one ormore pairs of PPD options and choices as well as providing key/value data forthe application. The following preset names are currently defined:
Photo_with_Paper_Auto-Detect
; Photo printing with paper auto-detectPhoto_with_Paper_Auto-Detect_-_Fine
; Photo printing with paper auto-detect - finePhoto_on_Plain_Paper
; Photo printing on plain paperPhoto_on_Plain_Paper_-_Fine
; Photo printing on plain paper - finePhoto_on_Photo_Paper
; Photo printing on photo paperPhoto_on_Photo_Paper_-_Fine
; Photo printing on photo paper - finePhoto_on_Matte_Paper
; Photo printing on matte paperPhoto_on_Matte_Paper_-_Fine
; Photo printing on matte paper - fine
The value string consists of pairs of keywords, either an option name andchoice (*MainKeyword OptionKeyword) or a preset identifier and value(com.apple.print.preset.foo value). Preset identifiers and their supportedvalues are documented in 'Creating Printing Presets for iPhoto: Printing Presets File Format'.
Presets, like options, can also be localized in multiple languages.
Examples:
Mac OS X 10.3APPrinterUtilityPath
*APPrinterPrinterUtilityPath: '/Library/Printers/vendor/filename.app'
This attribute defines a GUI application that can be used to do printermaintenance functions such as cleaning the print head(s). See .. for moreinformation.
Examples:
Mac OS X 10.6APScannerOnly
*APScannerOnly: boolean
This attribute specifies whether the device has scanning but no printingcapabilities. The default is False.
Examples:
Mac OS X 10.3APScanAppBundleID
*APScanAppBundleID: 'bundle ID'
This attribute defines the application to use when scanning pages fromthe device.
Examples:
Change History
Changes in CUPS 1.4
- Added APICADriver attribute.
- Added cupsCommands attribute.
- Added cupsMarkerName attribute.
- Added cupsMarkerNotice attribute.
- Added cupsPJLDisplay attribute.
- Added cupsSNMPSupplies attribute.
- Added cupsUIResolver and cupsUIConstraints attributes.
- Added cupsMediaQualifier2, cupsMediaQualifier3, cupsMinSize, and cupsMaxSize attributes.
Changes in CUPS 1.3.1
- Added missing Mac OS X AP attributes.
- Added section on auto-configuration including the OIDMainKeyword and ?MainKeyword attributes.
- Minor reorganization.
Changes in CUPS 1.3
- Added cupsBackSide and deprecated cupsFlipDuplex.
- Added text URI information to cupsIPPReason documentation.
- Added APPrinterPreset, cupsIPPFinishings, and cupsPreFilter attributes.
- Added discussion of custom option code, sample CustomPageSize code, and 'do not use dict and put' note.
Changes in CUPS 1.2.8
- Added section on supported PostScript commands for raster drivers
Changes in CUPS 1.2
- Added globalization support attributes
- Added custom option values support
- Added APHelpBook attribute
- Added APDuplexRequiresFlippedMargin attribute
- Added cupsICCProfile attribute
- Added cupsIPPReason attribute
- Added cupsLanguages attribute
- Added cupsPortMonitor attribute
- Removed cupsProtocol attribute
Oids Mac Os 11
Changes in CUPS 1.1
Ods Macros
- Added cupsFlipDuplex attribute
- Added cupsProtocol attribute