PrintDeviceCapabilities PrintDeviceCapabilities is a new format we are investigating which uses the PrintSchema keywords, but also allows us to describe constraints, and static options which affect PDL generation. Windows will use this file, plus a language-specific resource file to generate a PrintSchema PrintCapabilities document on the client, and to validate constraints. This will be the only configuration format we consume on Windows Phone. PrintCapabilities The operating system will produce PrintCapabilities out of the PrintDeviceCapabilities document. PrintTicket The operating system will produce PrintTicket documents based on the information in the PrintCapabilities document. Merge, validate and DEVMODE conversion operations will be handled on the client. Localized Resources PrintSchema-specified keywords are localized by the operating system. All vendor-specified keywords MUST provide a display name in a per-locale *.resx file. Localized strings are defined using a derivative of the fully qualified keyword name from the PrintDeviceCapabilities file. The name attribute of every name element is defined as the namespace url, without the protocol (eg “http://”), followed by a forward slash “/” and then the keyword name. <?xml version="1.0" encoding="utf-8"?> <root xmlns:xml="http://www.w3.org/XML/1998/namespace" <data name="schemas.contoso.com/windows/2014/01/printing/printschemakeywords/Main"> <value>Main paper tray</value> </data> <data <value>600 x 600 dots per inch</value> </data> <data x 1200 dots per inch</value> </data> <data name="schemas.contoso.com/windows/2014/01/printing/printschemakeywords/Secondary"> <value>Secondary paper tray</value> </data> <data <value>Contoso GoodPaper</value> </data>
PrintDeviceCapabilities PrintDeviceCapabilities is a new format we are investigating which uses the PrintSchema keywords, but also allows us to describe constraints, and static options which affect PDL generation. Windows will use this file, plus a language-specific resource file to generate a PrintSchema PrintCapabilities document on the client, and to validate constraints. This will be the only configuration format we consume on Windows Phone. PrintCapabilities The operating system will produce PrintCapabilities out of the PrintDeviceCapabilities document. PrintTicket The operating system will produce PrintTicket documents based on the information in the PrintCapabilities document. Merge, validate and DEVMODE conversion operations will be handled on the client. Localized Resources PrintSchema-specified keywords are localized by the operating system. All vendor-specified keywords MUST provide a display name in a per-locale *.resx file. Localized strings are defined using a derivative of the fully qualified keyword name from the PrintDeviceCapabilities file. The name attribute of every name element is defined as the namespace url, without the protocol (eg “http://”), followed by a forward slash “/” and then the keyword name. <?xml version="1.0" encoding="utf-8"?> <root xmlns:xml="http://www.w3.org/XML/1998/namespace" <data name="schemas.contoso.com/windows/2014/01/printing/printschemakeywords/Main"> <value>Main paper tray</value> </data> <data <value>600 x 600 dots per inch</value> </data> <data x 1200 dots per inch</value> </data> <data name="schemas.contoso.com/windows/2014/01/printing/printschemakeywords/Secondary"> <value>Secondary paper tray</value> </data> <data <value>Contoso GoodPaper</value> </data>
Developing_printers_that_support_Windows_10_Mobile.docx