That is what Issue 1.51 asks.
>
>
>>If yes, then it may be simpler for IPP Printer
>>implementations to ALWAYS add the "attributes-natural-language" in the
>>returned Job Attributes (first), whether the job is in that natural
>language
>>or not.
>
>And a more simpler IPP printer implementation, would be to
>always return
>the 'name'
>and 'text' attributes with language, even the response was without.
True. If we agree to make the change for vote 4 of 4.
But if that fails, then we still have to decide about the vote 3 of 4 on NLO
at the job-level for Get-Jobs.
And if we allow redundant job-level NLO, what if the client is requesting
"attributes-natural-language"?
A current implementation that we are testing the scripts with, returns
"attributes-natural-language" twice
with the same value (which our scripts reject). Issue 1.52 is asking
whether returning two "attributes-natural-language" is conforming or not.
If we agree it is, we will change our scripts.
>
>Henrik Holst
>
>
Tom Hastings
(310) 333-6413