IPP Mail Archive: Re: Some Comments on ipp92.doc - the issues we didn't get to

Re: Some Comments on ipp92.doc - the issues we didn't get to

Robert Herriot (robert.herriot@Eng.Sun.COM)
Fri, 22 Nov 1996 13:56:58 -0800

> >>
> >> 6. 6.2.8.2 number-up
> >>
> >> ISSUE:
> >> A simpler way to allow end-users to turn of embellishments, is to have
> >> a distinguised value that turns it off. ISO DPA has "0", but a more
> >> user friendly value would be "none". Then any other value, like "1",
> >> or "2", or "4" is free to have any embellishments on it.
> >
> >I am trying to avoid arbitrary distinguished values that only IPP gurus
> know about.
> >The question is whether a user would expect that number-up = 1 gives normal
> printing
> >with essentially no number-up.
>
> No, I was suggesting that any value, except none, is free to include
> emblishments, such as borders, pages numbers, title lines, etc., including
> "1". So "1", "2", "4" all are free to include emblishments depending on
> the site policy.
>
> So "1" is just a way for a submitter to override some default that the
> system administrator set up, say "2", because the SA is concerned about
> saving trees.
>
> I think that it is an important design principle that when a system
> administrator can specify defaults that users have explicit ways to
> specify all values, especially the value ("1" in the case of number-up)
> that normally is used when neither the submitter supplies a value nor
> the SA defines a default).
>
> So the purpose of having a "none" value is for a submitter to be able
> to force no emblishments.
>
> Here is the current spec for number-up:
>
> 6.2.8.2 number-up (positiveInteger)
> This attribute specifies the number of source page images to impose upon a
> single side of an instance of a selected medium.
>
> In general, only certain numeric values are valid for this attribute,
> depending upon the Printer implementation to which the print request is
> directed. Typical supported values are 2 and 4. If this attribute is
> unspecified or has a value of 1, then the Printer does not apply any
> number-up transformation to the pages.
>
> This attribute primarily controls the translation, scaling and rotation of
> page images, but a site may choose to add embellishments, such as borders to
> each logical page.
>
> ISSUE: should there be a separate attribute to control embellishments,
> especially for the 1-up case?
>
>
> Bob,
> If you think allowing an implementor/SA to define emblishments as part of
> the semantics of "1", "2", and "4" is a bad idea, then maybe we should have
> another job attribute which controls emblishments, as suggested by the ISSUE.
>
> Maybe something like:
>
> embelishments (1#type3Enum)
>
> This attribute specifies the emblishments that are to be imposed upon a
> single side of an instance of a selected medium.
>
> Standard values are: "none", "borders", "impression numbers", "title".
>
> When used in combination with number-up, the "borders" emblishment
> means a border around each logical page that is imposed on a side of the
> medium.
>
> The "impression numbers" value means number each impression outside
> the area on which the logical pages are imposed.
>
> The "title" value means put the document name at the top of each impression
> outside the area on which the logical pages are imposed.
>
> Comments?
>
> >
> >>
> >>

I agree with Tom that if the values of number-up are really an enum with values of
none, 1, 2, 4, then 'none' means normal printing and 1, 2 and 4 mean default
embellishments with 1, 2 or 4 pages per impression. The embellishments attribute
is an extra if we believe that printers support multiple embellishments.