In this particular case, attributes-charset is MANDATORY, i.e. the printer
must
support the attribute, but in the get-jobs reponse it MUST be in the=
operation
attributes
group and it is only in each job attribute group if the client requested the
attribute via the
requested-attributes attribute in the request. Note, even if it is present
in a
job attributes
group it does not affect the charset of those attributes. All attributes in
the entire
response are in the charset specified by attributes-charset in the=
operations
attribute
group, which I still believe must be first in that group (a change we need=
to
make
to the model document).
Note that in the example attributes-natural-language is in one of the job
attribute
groups in order to override the natural-language in the operation=
attributes.=20
As I
have been implementing IPP, I have come to believe that this was a bad idea.=
=20
It again
requires a special ordering, i.e. attributes-natural-language must precede=
all
other
attributes if processing is to be simple.
Bob Herriot
At 03:34 PM 4/3/98 , Carl Kugler wrote:
>Looking at example 9.7, Get-Jobs Response, I don't see an=
attributes-charset
>attribute in any of the three job attributes groups.=A0 But section 4.3 of=
the
>Model document, "Job Description Attributes", says that attributes-charset=
is
>MANDATORY in the "job-description" attribute group.=A0 This is causing me
>cognitive dissonance.
>=20