attachment-0001
<html>
<font size=3>Tom Hastings: NOTE this is another implementation
issue where we should<br>
probably relax the language from MUST to MAY. I thought that we had<br>
agreed to MAY, but MUST is in the model document.<br>
<br>
Section 3.1.4.2 makes it clear that a server is free to use any value for
the <br>
attribute-natural-language operation attribute.<br>
<br>
Section 3.1.6.2 says that attributes-natural-language MUST be the
first attribute returned<br>
in each Job object whose language differs from the
attributes-natural-language in the<br>
operation attributes. <br>
<br>
I think WE OVERSPECIFIED THIS, especially if one or fewer text/name
attributes<br>
are being returned. It should be the option of the server to
override at the job<br>
level or at the attribute level. This allows the server to be simple or
optimal.<br>
<br>
Bob Herriot<br>
<br>
<br>
<br>
At 03:23 PM 10/8/98 , Brian R Glass wrote:<br>
>All,<br>
><br>
>I find natual language in IPP somewhat confusing.
Usually,<br>
>drawing a picture helps me to clearify the issues. Do the<br>
>following diagrams accurately describe the way natural<br>
>language is supposed to be used in IPP? <br>
><br>
>Key:<br>
> NL = Natural
Language (MOD
section 3.1.4.1)<br>
> NLO = Natural Language
Override (MOD section 4.1.1.2<br>
>
4.1.2.2)<br>
> JNL = Job Natural
Language (MOD section 3.2.6.2)<br>
<font size=3>><br>
><br>
>Example 1: Both client and server are English (en)<br>
><br>
> Request = get-jobs<br>
> Client
(en)
Server (en)<br>
>
--------+
+--------<br>
>
| request NL=en |<br>
>
| -----------------> |<br>
>
|
|<br>
>
| response NL=en |<br>
>
| <---------------- |<br>
><br>
>Example 2: Client is French (fr) and server is English (en)<br>
><br>
> request = get-jobs<br>
> Client
(fr)
Server (en)<br>
>
--------+
+--------<br>
>
| request NL=fr |<br>
>
| -----------------> |<br>
>
|
|<br>
>
| response NL=en |<br>
>
|
JNL=fr |<br>
>
| <---------------- |<br>
><br>
>Example 3: Client is French (fr) and server is English (en).
<br>
> In
addition the client uses NLO=el (Greek) for <br>
>
requesting-user-name<br>
><br>
> request = get-jobs<br>
> Client
(fr)
Server (en)<br>
>
--------+
+--------<br>
>
| request NL=fr |<br>
>
| user name: NLO=el|<br>
>
| -----------------> |<br>
>
|
|<br>
>
| response NL=en |<br>
>
|
JNL=fr |<br>
>
| user name: NLO=el|<br>
>
| <---------------- |<br>
><br>
>Note that all attributes returned are in the JNL language<br>
>(French in this case) except the user name (job-originating-<br>
>user-name) which is in Greek.<br>
><br>
>Example 4: Client1 is French (fr) and server is English (en).
<br>
> In
addition the client uses NLO=el (Greek) for <br>
>
requesting-user-name. Client2 is Greek (el).<br>
> Client3
is German (de)<br>
><br>
> request = print-job<br>
> Client1
(fr)
Server (en)<br>
>
--------+
+--------<br>
>
| request NL=fr |<br>
>
| user name: NLO=el| (job 1)<br>
>
| -----------------> |<br>
>
|
|<br>
>
| response NL=en |<br>
>
|
JNL=fr |<br>
>
| user name: NLO=el|<br>
>
| <---------------- |<br>
><br>
> request = get-jobs<br>
> Client2
(el)
Server (en)<br>
>
--------+
+--------<br>
>
| request NL=el |<br>
>
| -----------------> |<br>
>
|
|<br>
>
| response NL=en |<br>
>
|
JNL=el |<br>
<font size=3>>
| <---------------- | (job 1)<br>
><br>
> request = get-jobs<br>
> Client3
(de)
Server (en)<br>
>
--------+
+--------<br>
>
| request NL=de |<br>
>
| -----------------> |<br>
>
|
|<br>
>
| response NL=en |<br>
>
|
JNL=de |<br>
>
| user name: NLO=el|<br>
>
| <---------------- | (job 1)<br>
><br>
>Note how client2 and client3 differ in their need for NLO.<br>
> <br>
><br>
>Example 5: Client is French (fr) and server is English (en)<br>
><br>
> Request =
get-printer-attributes<br>
> Client
(fr)
Server (en)<br>
>
--------+
+--------<br>
>
| request NL=fr |<br>
>
| -----------------> |<br>
>
|
|<br>
>
| response NL=en |<br>
>
| <---------------- |<br>
><br>
><br>
><br>
>Carl stated in a previous email:<br>
>>There is a precedence hierarchy here:<br>
>><br>
>> 1. Natural Language Override<br>
>> 2. Job object's "attributes-natural-language"
value<br>
>> 3. "attributes-natural-language" operation
attribute of the response.<br>
>><br>
>> 1 overrides 2 and 3, 2 overrides 3.<br>
><br>
>Stated with regards to my
diagrams:
<br>
> 1) all response attributes are returned in the language<br>
> specified by the "response NL" <br>
> 2) Number 1 above is true unless a JNL is being returned<br>
> and then all response attributes are returned in
the <br>
> language specified by the JNL.<br>
> 3) Number 1 and 2 above are true unless a NLO is used for<br>
> a specific attribute.<br>
><br>
><br>
>Does this look correct?<br>
><br>
>Brian<br>
>-- <br>
>=============================================================<br>
>Brian R.
Glass
Tektronix, Inc<br>
>
26600 SW Parkway<br>
>Color Printing & Imaging
Division
PO Box 1000<br>
>
MS 60-368<br>
><a href="mailto:Brian.Glass@tek.com" eudora="autourl"><font size=3>mailto:Brian.Glass@tek.com</a><font size=3>
Wilsonville, OR 97070-1000<br>
><a href="http://www.tek.com/Color_Printers" eudora="autourl"><font size=3>http://www.tek.com/Color_Printers</a><font size=3>
(503) 685-2456<br>
>=============================================================<br>
> </font><br>
</html>