diff options
| author | Michael Sweet <michael.r.sweet@gmail.com> | 2017-06-15 20:53:04 -0400 |
|---|---|---|
| committer | Michael Sweet <michael.r.sweet@gmail.com> | 2017-06-15 20:53:04 -0400 |
| commit | 2a75f21b6a90dcb02b7333d3c17fd08a1c89a93e (patch) | |
| tree | a9a054724fbfeb093ee4d2de3c4fa030f5e9106b /man | |
| parent | ac032efa3e54de42e1666bdf0f5c72a769f99b85 (diff) | |
| download | cups-2a75f21b6a90dcb02b7333d3c17fd08a1c89a93e.tar.gz | |
Sync up with changes from IPP sample code project.
Diffstat (limited to 'man')
| -rw-r--r-- | man/ipptoolfile.man | 13 |
1 files changed, 8 insertions, 5 deletions
diff --git a/man/ipptoolfile.man b/man/ipptoolfile.man index 795995da0..35b050419 100644 --- a/man/ipptoolfile.man +++ b/man/ipptoolfile.man @@ -9,7 +9,7 @@ .\" which should have been included with this file. If this file is .\" file is missing or damaged, see the license at "http://www.cups.org/". .\" -.TH ipptoolfile 5 "CUPS" "13 June 2017" "Apple Inc." +.TH ipptoolfile 5 "CUPS" "15 June 2017" "Apple Inc." .SH NAME ipptoolfile \- ipptool file format .SH DESCRIPTION @@ -164,9 +164,12 @@ Specifies the default IPP version number to use for the tests that follow. .SS TEST DIRECTIVES The following directives are understood within a \fItest\fR: .TP 5 +\fBATTR \fIout-of-band-tag attribute-name\fR +.TP 5 \fBATTR \fItag attribute-name value(s)\fR Adds an attribute to the test request. -Values are separated by the comma (",") character - escape commas using the "\" character. +Out-of-band tags (admin-define, delete-attribute, no-value, not-settable, unknown, unsupported) have no value. +Values for other tags are separated by the comma (",") character - escape commas using the "\" character. Common attributes and values are listed in the IANA IPP registry - see references below. .TP 5 \fBATTR collection \fIattribute-name \fB{ MEMBER \fItag member-name value(s) ... \fB}\fR [ \fI... \fB,{ \fI... \fB} \fR] @@ -406,7 +409,7 @@ Specifies the maximum number of times to repeat. The default value is 1000. \fBREPEAT\-NO\-MATCH\fR Specifies that the current test should be repeated when the response status-code matches or does not match the value specified by the STATUS directive. .SS OPERATION CODES -Operation codes correspond to the hexadecimal numbers (0xHHHH) and names from RFC 2911 and other IPP extension specifications. Here is a complete list of names supported by +Operation codes correspond to the hexadecimal numbers (0xHHHH) and names from RFC 8011 and other IPP extension specifications. Here is a complete list of names supported by .BR ipptool (8): .nf @@ -479,7 +482,7 @@ Operation codes correspond to the hexadecimal numbers (0xHHHH) and names from RF Validate\-Job .fi .SS STATUS CODES -Status codes correspond to the hexadecimal numbers (0xHHHH) and names from RFC 2911 and other IPP extension specifications. Here is a complete list of the names supported by +Status codes correspond to the hexadecimal numbers (0xHHHH) and names from RFC 8011 and other IPP extension specifications. Here is a complete list of the names supported by .BR ipptool (8): .nf @@ -542,7 +545,7 @@ Status codes correspond to the hexadecimal numbers (0xHHHH) and names from RFC 2 successful\-ok\-too\-many\-events .fi .SS TAGS -Value and group tags correspond to the names from RFC 2911 and other IPP extension specifications. Here are the group tags: +Value and group tags correspond to the names from RFC 8011 and other IPP extension specifications. Here are the group tags: .nf document\-attributes\-tag |