[Fwd: IPP> ADM - IPP Implementors' Guide Version 01: Discussion]

[Fwd: IPP> ADM - IPP Implementors' Guide Version 01: Discussion]

[Fwd: IPP> ADM - IPP Implementors' Guide Version 01: Discussion]

Carl Kugler kugler at us.ibm.com
Thu Sep 17 11:47:18 EDT 1998


> 
> In reply to:
> http://www.pwg.org/hypermail/ipp/1239.html
> 
> > Question      How should the server handle the situation where the "attributes-charset" of the response itself is "us-ascii", but one or more attributes in that response is in the "utf-8" format?
> >
> > Consider a case where a client sends a Print-Job request with "utf-8" as the value of "attributes-charset" and with the "job-name" attribute supplied.  Later another client
> > sends a Get-Job-Attribute or Get-Jobs request.  This second request contains the "attributes-charset" with value "us-ascii" and "requested-attributes" attribute with
> > exactly one value "job-name".
> >
> > According to the IPP-Mod document (section 3.1.4.2), the value of the "attributes-charset" for the response of the second request must be "us-ascii" since that is the charset
> > specified in the request.  The "job-name" value, however,  is in "utf-8" format.  Should the request be rejected even though both "utf-8" and "us-ascii" charsets are supported by the server? or should the "job-name" value be converted to "us-ascii" and return "successful-ok-conflicting-attributes"  (0x0002) as the status code?
> >
> > Van Dang
> 
> My understanding:  in this situation the Printer is required to convert
> the job-name value from utf-8 charset to us-ascii.  If it can't, it
> shouldn't advertise us-ascii as a attributes-charset-supported.
> 
> One implementation strategy is to convert all incoming text and name
> values to a Unicode internal representation.  This is 16-bit and
> virtually universal.  Then convert to the specified operation
> attributes-charset on output.
> 
>         -Carl Kugler



More information about the Ipp mailing list