Note to GPD Authors
This topic is not current. For the most current information, see the Print Schema Specification.
For those authors of PrintCapabilities documents who are familiar with GPD files, some GPD keywords have no equivalents in the PrintCapabilities document. The following table contains the GPD keywords without a PrintCapabilities document equivalent, and the reason there is no equivalent.
|Constraints are not defined in the PrintCapabilities document because PrintCapabilities clients are not expected to process, enforce, or resolve them. These tasks are left for the PrintTicket provider to perform during PrintTicket validation. Unidrv plug-ins can provide their own PrintTicket validation code, or they can rely on Unidrv to carry out this validation. In the latter case, Unidrv enforces any constraints defined in the GPD file.
Monolithic drivers must provide their own PrintTicket validation code, and must provide their own method of expressing and enforcing constraints.
||There is a PrintTicket method that returns a default PrintTicket, which by definition has all the default settings for each Feature.
||A Feature can be divided into three different categories:
A Feature whose settings are defined in a PrintTicket. This type of Feature is called document-sticky because these settings directly determine the manner in which a document is processed.
A Feature whose settings reflect physical device attributes that are not user controlled, such as the amount of memory in the device, or that indicate the presence of optional add-ons such as paper feeders or duplexers. This type of Feature is called device-sticky or printer-sticky. The state of this type of Feature is important because it can constrain an Option belonging to a document-sticky Feature.
A device-sticky or printer-sticky Feature can be further categorized as either a user interface (UI) printer-sticky Feature or an auto printer-sticky Feature. A UI printer-sticky Feature must be displayed in a user interface that an administrator can set. The device automatically detects an auto printer-sticky Feature.
|*Switch ... *Case
||A PrintCapabilities provider must implement a method that creates a PrintCapabilities document that enumerates either printer-sticky or document-sticky Features, depending on the type specified by the caller. For this reason there is no need to present the same information through the PrintCapabilities document itself.