Registration of charsets for use in ’charset’ attribute values121

The "attributes-charset" attribute’s syntax is ’charset’. This means that valid values are charsets names. When a charset in the IANA registry has more than one name (alias), the name labeled as "(preferred MIME name)", if present, MUST be used (see Section 4.1.7). IANA is the registry for charsets following the procedures of [RFC2278].

7. Internationalization Considerations

Some of the attributes have values that are text strings and names which are intended for human understanding rather than machine understanding (see the ’text’ and ’name’ attribute syntaxes in Sections 4.1.1 and 4.1.2).

In each operation request, the client

- identifies the charset and natural language of the request which affects each supplied ’text’ and ’name’ attribute value, and - requests the charset and natural language for attributes returned by the IPP object in operation responses (as described in Section 3.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’ technique described section 4.1.1.2 and 4.1.2.2 respectively.

All IPP objects MUST support the UTF-8 [RFC2279] 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 3.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 3.1.4.1).

For Printers that support multiple charsets and/or multiple natural languages in ’text’ and ’name’ attributes, different jobs may 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’ mechanism to identify the differing natural languages with each job attribute returned.

The Printer object also has configured charset and natural language attributes. The client can query the Printer object to determine the list of charsets and natural languages supported by the Printer object and what the Printer object’s configured values are. See the "charset-configured", "charset-supported",

configured", and "generated-natural-language-supported" Printer description attributes for more details.

The "charset-supported" attributed 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 which 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. Just because a Printer object is currently

configured to support ’en-us’ natural language does not mean that the Printer object should reject a job if the client supplies a job name that is in ’fr-ca’.

The "natural-language-configured" attribute identifies the one

supported natural language for generated messages which is the native natural language given the current configuration of the IPP object (administrator defined).

Attributes of type ’text’ and ’name’ are populated from different sources. These attributes can be categorized into 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 object’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 system administrator (e.g., the Printer object’s "printer-name" and "printer-location"

attributes). These too can 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 object’s "printer-make-and-model" attribute). These too can 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 object’s "job-message-from-operator" attribute). These too can 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 object’s "job-state-message" attribute, the Printer object’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 6) are:

Attributes Source --- Operation Attributes

job-name (name) client document-name (name) client requesting-user-name (name) client

status-message Job or Printer object Job Template Attributes:

job-hold-until) client matches administrator-configured (keyword | name

job-hold-until-default client matches administrator-configured (keyword | name)

job-hold-until-supported client matches administrator-configured (keyword | name)

job-sheets client matches administrator-configured (keyword | name)

job-sheets-default client matches administrator-configured (keyword | name)

job-sheets-supported client matches administrator-configured (keyword | name)

media client matches administrator-configured (keyword | name)

media-default client matches administrator-configured (keyword | name)

media-supported client matches administrator-configured (keyword | name)

media-ready client matches administrator-configured (keyword | name)

Job Description Attributes:

job-name (name) client or Printer object job-originating-user-name (name) Printer object job-state-message (text) Job or Printer object output-device-assigned (name(127)) administrator job-message-from-operator (text(127)) operator Printer Description Attributes:

printer-name (name(127)) administrator printer-location (text(127)) administrator printer-info (text(127)) administrator

printer-make-and-model (text(127)) administrator or manufacturer printer-state-message (text) Printer object