Nice write-up, Roger. How about some examples for each attribute,
particularly for boundary or other strange situations?
----- Begin Included Message -----
From: Roger K Debry <rdebry at us.ibm.com>
To: <ipp at pwg.org>
Subject: IPP>MOD - new attributes
Date: Fri, 15 Aug 1997 16:59:43 -0400
At the last PWG meeting, I agreed to write up proposed wording for
several changes we had asked for in the model document. Here are some
of these changes for your review. I am assuming that if there is no
comment, these will go into the next version of the model document as
written here ...
4.2.3 copies (integer 1:2**31-1))
This attribute specifies the number of copies to be printed. On many
devices the supported number of collated copies will be limited by the
number of physical output bins on the device, and may be different
from the number of uncollated copies which can be supported. Therefore
the copies-supported attribute specifies a set of ranges; the first
defines the supported range of values for uncollated copies, and the
second the supported range of values for collated printing. The set of
default values for copies specify the default number of uncollated
copies followed by the default number of collated copies.
The effect of this attribute is controlled by the
"multiple-documents-handling" attribute (section 4.2.6).
4.2.19 page-range (1setOf integer)
This attribute specifies the pages of a document which are to be
printed. In most cases, the exact pages to be printed will be generated
by a device driver and this attribute would not be required. However,
when printing an archived document which has already been formatted,
the end user may elect to print just a subset of the pages contained in
the document. In this case, if page-range = n.m is specified, the first
page to be printed will be page n. All subsequent pages of the document
will be printed through and including page m.
Page-range supported is a boolean value indicating whether or not the
printer is capable of supporting the printing of page ranges. This
capability may differ from one PDL to another. The page-range default
value is always zero (0) and indicates that all pages of the document
will be printed if a page-range is not specified.
4.2.20 orientation (type2 enum)
This attribute specifies the orientation of the content on the output
pages to be printed. In most cases, the orientation of the content is
specified within the document format generated by the device driver at
print time. However, some document formats do not support the notion
of page orientation and it is possible to bind the orientation after
the document content has been generated. This attribute provides an
end user with the means to specify orientation for such documents.
Standard values are:
'Portrait" (1): The content will be printed across the short edge of
the media. 'Landscape (2): The content will be printed across the long
edge of the media.
Media available attribute:
I propose that the current media attribute have the connotation of
"media-ready". That is, the media- supported attribute represents media
actually ready to print To support production environments where a
printer operator is normally available to load special papers, the
following additional attribute is proposed:
4.2.21 Media-available (1setOf type4 keyword)
In many production printing environments some media, such as special
pre-printed forms, may be available to be loaded on the printer by an
operator when requested. Under normal conditions, these would not be
reflected in the values of the media-supported attribute, since they
are meant to indicate only what is normally loaded on the printer and
ready to use. However, it is useful for an end user to know what media
are available to be loaded so that the correct media name can be
specified in the 'media' attribute. This allows jobs which require
special media to be loaded to be queued and batched together to be
printed once the correct media is loaded. Thus the attribute not only
provides help in scheduling work but as input to an operator on how to
set up the printer for a particular batch of jobs.
Since the end-user actually specifies the media to be loaded in the
'media' attribute, and the default indicates a ready media, there are
no equivalent job and template attributes.
Roger K deBry
Senior Technical Staff Member
Architecture and Technology
IBM Printing Systems
email: rdebry at us.ibm.com
er, some do
----- End Included Message -----