Some of the attributes have values that are text strings and names that are intended for human understanding rather than machine understanding (see the ’text’ and ’name’ attribute syntaxes in Sections 5.1.2 and 5.1.3).
In each operation request, the Client
o identifies the charset and natural language of the request that affects each supplied ’text’ and ’name’ attribute value, and o requests the charset and natural language for attributes returned by the IPP object in operation responses (as described in
Section 4.1.4.1).
In addition, the Client MAY separately and individually identify the Natural Language Override of a supplied ’text’ or ’name’ attribute using the ’textWithLanguage’ and ’nameWithLanguage’ techniques described in Sections 5.1.2.2 and 5.1.3.2, respectively.
All IPP objects MUST support the UTF-8 [RFC3629] charset in all ’text’ and ’name’ attributes supported. If an IPP object supports more than the UTF-8 charset, the object MUST convert between them in order to return the requested charset to the Client according to Section 4.1.4.2. If an IPP object supports more than one natural language, the object SHOULD return ’text’ and ’name’ values in the natural language requested where those values are generated by the Printer (see Section 4.1.4.1).
For Printers that support multiple charsets and/or multiple natural languages in ’text’ and ’name’ attributes, different Jobs might have been submitted in differing charsets and/or natural languages. All responses MUST be returned in the charset requested by the Client.
However, the Get-Jobs operation uses the ’textWithLanguage’ and ’nameWithLanguage’ mechanisms to identify the differing natural languages with each Job attribute returned.
The Printer also has configured charset and natural language
attributes. The Client can query the Printer to determine the list of charsets and natural languages supported by the Printer and what the Printer’s configured values are. See the "charset-configured", "charset-supported", "natural-language-configured", and
"generated-natural-language-supported" Printer Description attributes for more details.
The "charset-supported" attribute identifies the supported charsets.
If a charset is supported, the IPP object MUST be capable of
converting to and from that charset into any other supported charset.
In many cases, an IPP object will support only one charset, and it MUST be the UTF-8 charset.
The "charset-configured" attribute identifies the one supported charset that is the native charset, given the current configuration of the IPP object (Administrator defined).
The "generated-natural-language-supported" attribute identifies the set of supported natural languages for generated messages; it is not related to the set of natural languages that MUST be accepted for Client-supplied ’text’ and ’name’ attributes. For Client-supplied ’text’ and ’name’ attributes, an IPP object MUST accept ALL supplied natural languages. For example, if a Client supplies a Job name that is in ’fr-ca’ but the Printer only generates ’en-us’, the Printer object MUST still accept the Job name value.
The "natural-language-configured" attribute identifies the one
supported natural language for generated messages that is the native natural language, given the current configuration of the IPP object (Administrator defined).
Attributes of types ’text’ and ’name’ are populated from different sources. These attributes can be categorized into the following groups (depending on the source of the attribute):
1. Some attributes are supplied by the Client (e.g., the Client-supplied "job-name", "document-name", and
"requesting-user-name" operation attributes along with the corresponding Job’s "job-name" and "job-originating-user-name"
attributes). The IPP object MUST accept these attributes in any natural language no matter what the set of supported languages for generated messages.
2. Some attributes are supplied by the Administrator (e.g., the Printer’s "printer-name" and "printer-location" attributes).
These can also be in any natural language. If the natural language for these attributes is different than what a Client requests, then they MUST be reported using the Natural Language Override mechanism.
3. Some attributes are supplied by the device manufacturer (e.g., the Printer’s "printer-make-and-model" attribute). These can also be in any natural language. If the natural language for these attributes is different than what a Client requests, then they MUST be reported using the Natural Language Override
mechanism.
4. Some attributes are supplied by the Operator (e.g., the Job’s "job-message-from-operator" attribute). These can also be in any natural language. If the natural language for these attributes is different than what a Client requests, then they MUST be reported using the Natural Language Override mechanism.
5. Some attributes are generated by the IPP object (e.g., the Job’s "job-state-message" attribute, the Printer’s
"printer-state-message" attribute, and the "status-message"
operation attribute). These attributes can only be in one of the "generated-natural-language-supported" natural languages. If a Client requests some natural language for these attributes other than one of the supported values, the IPP object SHOULD respond using the value of the "natural-language-configured" attribute (using the Natural Language Override mechanism if needed).
The ’text’ and ’name’ attributes specified in this version of this document (additional ones will be registered according to the procedures in Section 7) are shown in Table 22.
+---+---+
| Attributes | Source | +---+---+
| Operation Attributes: | | | | | | job-name (name) | Client | | document-name (name) | Client | | requesting-user-name (name) | Client | | status-message (text) | Job or Printer | | detailed-status-message (text) | Job or Printer (note 1) | | document-access-error (text) | Job or Printer (note 1) | | | | | Job Template Attributes: | | | | | | job-hold-until (keyword | name) | Client matches Administrator- | | | configured | | job-hold-until-default (keyword | | Client matches Administrator- | | name) | configured | | job-hold-until-supported (keyword | Client matches Administrator- | | | name) | configured |
| job-sheets (keyword | name) | Client matches Administrator- | | | configured | | job-sheets-default (keyword | | Client matches Administrator- | | name) | configured | | job-sheets-supported (keyword | | Client matches Administrator- | | name) | configured | | media (keyword | name) | Client matches Administrator- | | | configured | | media-default (keyword | name) | Client matches Administrator- | | | configured | | media-supported (keyword | name) | Client matches Administrator- | | | configured |
Note 1: Neither the Printer nor the Client localizes these message attributes, since they are intended for use by the Administrator or other experienced technical persons.