attachment-0001
<br><font size=2 face="Courier New">From ipp-owner Tue Jul 1 13:45:24 2003<br>
Received: from palrel13.hp.com (palrel13.hp.com [156.153.255.238])<br>
by pwg.org (8.11.7+Sun/8.9.2) with ESMTP id h61HjOL16828<br>
for <ipp@pwg.org>; Tue, 1 Jul 2003 13:45:24 -0400 (EDT)<br>
Received: from xparelay2.ptp.hp.com (xparelay2.ptp.hp.com [15.1.28.65])<br>
by palrel13.hp.com (Postfix) with ESMTP<br>
id 925AF1C00B05; Tue, 1 Jul 2003 10:45:23 -0700 (PDT)<br>
Received: from xpabh3.ptp.hp.com (xpabh3.ptp.hp.com [15.1.28.63])<br>
by xparelay2.ptp.hp.com (Postfix) with ESMTP<br>
id D6CE61C00AD9; Tue, 1 Jul 2003 10:45:13 -0700 (PDT)<br>
Received: by xpabh3.ptp.hp.com with Internet Mail Service (5.5.2655.55)<br>
id <N5CMGF5V>; Tue, 1 Jul 2003 10:45:13 -0700<br>
Message-ID: <A134E2426B46D711BB4B000347AE6E7CAA599E@xvan02.vcd.hp.com><br>
From: "TAYLOR,BOB (HP-Vancouver,ex1)" <bobt@hp.com><br>
To: Till Kamppeter <till.kamppeter@gmx.net><br>
Cc: printing-driver@freestandards.org, Claudia Alimpich <alimpich@us.ibm.com>,<br>
ipp@pwg.org, printing-jobticket@freestandards.org<br>
Subject: RE: [printing-driver] RE: [printing-jobticket] Proposal to add ne<br>
w IPP print-optimize attribute<br>
Date: Tue, 1 Jul 2003 10:45:04 -0700 <br>
MIME-Version: 1.0<br>
X-Mailer: Internet Mail Service (5.5.2655.55)<br>
Content-Type: text/plain<br>
<br>
My concern is in creating an extra attribute for "other stuff" that is<br>
poorly distinguished from PrintQuality. Let's look at the suggested<br>
enumerations:<br>
<br>
'image': optimize for image clarity<br>
'photo': optimize for photo clarity<br>
'text': optimize for text clarity<br>
'text-and-image': optimize for both text and image clarity<br>
'save-toner': optimize for minimal toner usage<br>
'speed': optimize for printing speed<br>
and from PrintQuality:<br>
'draft': lowest quality available on the printer<br>
'normal': normal or intermediate quality on the printer<br>
'high': highest quality available on the printer<br>
<br>
There really are a few of semantic concepts in here:<br>
<br>
print quality: bad <-> good<br>
performance: slow <-> fast<br>
marker/toner/ink usage: cheap <-> expense <br>
content metadata hints: image, photo, text, text-and-image, etc. <br>
<br>
Realize though that the semantics of things like "print with bad quality",<br>
"print with lousy performance", or "use lots of extra toner" don't make any<br>
practical sense: what you're really trying to do is give the service/device<br>
feedback on the tradeoffs of PQ/performance/marker usage. So, while the<br>
PrintQuality definitions just officially talks about "quality", that's not<br>
what they really are in practice. What is more realistic is:<br>
<br>
'draft': fast & cheap - sacrifice print quality for speed and low marker<br>
usage<br>
'normal': balance - decent print quality with good speed and moderate marker<br>
usage<br>
'high': look good - optimize print quality at the expense of speed and<br>
marker usage<br>
<br>
Many in the industry have extended this list (IPP extension rules<br>
notwithstanding) for things like "econofast" and "bestphoto" - which are<br>
merely additional tradeoff combinations.<br>
<br>
So I'd argue that PrintQuality is already PrintOptimize - they are<br>
effectively doing the same thing, just with different sets of enumerations.<br>
I would much rather we extend the enumerations than create another attribute<br>
to do what we've already done.<br>
<br>
As for the "content metadata hints" - if the intent is a different<br>
PW-performance-marker usage tradeoff, I'd add them to the PrintQuality<br>
enumeration. If we're really trying to provide hints about the coming<br>
document content, then they should be an attribute of the document object,<br>
since they are document metadata. Realize also that this information is<br>
often object specific - optimization is often done to different objects on<br>
the same page of a document (e.g., different halftoning for an image on a<br>
page vs. the bar chart on the same page). I don't think we want to go very<br>
far down the path of document content metadata here - this could get very<br>
messy.<br>
<br>
As a separate note, not all printers use "toner" - save-toner should<br>
probably be something like "save-marker"<br>
<br>
thanks,<br>
<br>
bt<br>
<br>
> -----Original Message-----<br>
> From: Till Kamppeter [mailto:till.kamppeter@gmx.net]<br>
> Sent: Thursday, June 26, 2003 5:19 PM<br>
> To: TAYLOR,BOB (HP-Vancouver,ex1)<br>
> Cc: printing-driver@freestandards.org; Claudia Alimpich;<br>
> ipp@pwg.org; printing-jobticket@freestandards.org<br>
> Subject: Re: [printing-driver] RE: [printing-jobticket] <br>
> Proposal to add ne w IPP print-optimize attribute<br>
> <br>
> <br>
> TAYLOR,BOB (HP-Vancouver,ex1) wrote:<br>
> > Hi Tom,<br>
> > <br>
> > To me, #2 is the issue to really focus on: is this really<br>
> two semantic<br>
> > concepts, or one? If any of these values are semantically<br>
> really just<br>
> > additional enumerations for<br>
> > print-quality, I'd much rather we fix this than do the split it.<br>
> > <br>
> > As for #2, what "semantic meaning would be lost or mixed"<br>
> if we just<br>
> > extended the enumeration for print-quality? Although you can, by <br>
> > having these as two attributes, specify "draft" and "photo" - in <br>
> > practice, this is virtually never done: "photo" is usually<br>
> specified<br>
> > in one of a couple ways:<br>
> > - my media type (i.e., photo-glossy paper model #C239847A)<br>
> > - PrintQuality (quality = Photo4800DPI) - i.e., another<br>
> print-quality<br>
> > enumeration If it's something other than one of these, it's usually <br>
> > what we call in PSI capabilities a "macro feature" - i.e.,<br>
> it's not a<br>
> > real attribute sent to the device, but a feature defined as a macro <br>
> > combination of other features - which I don't think is a concept <br>
> > currently supported by IPP.<br>
> ><br>
> <br>
> These "macro feature"s I have already implemented in Foomatic as the <br>
> so-called "composite options". The "PrintoutMode" option in GIMP-Print<br>
> for example controls 5 options of GIMP-Print when the user <br>
> chooses out <br>
> of Draft, Fraft.Garyscale, Normal, Normal.Garyscale, High, <br>
> High.Grayscale, VeryHigh, VeryHigh.Grayscale, Photo, Photo.Grayscale.<br>
> <br>
> > Fundamentally, "refines the value specified by the print-quality" <br>
> > seems like a weak semantic differentiation, and I believe it is <br>
> > inconsistent with how extensions to the print-quality concept have <br>
> > been applied in at least<br>
> the inkjet<br>
> > segment of<br>
> > the market.<br>
> ><br>
> <br>
> The "PrintoutMode"option is both a quality and an intent option. What <br>
> is tried here in this discussion is to have two options, once quality<br>
> (draft, normal, high, ...) and intent (text, image, text-with-image, <br>
> photo, toner-saving). Most drivers have too few adjustment <br>
> possibilities <br>
> to really fill the matrix of all intent/quality combinations, <br>
> probably <br>
> only GIMP-Print will hardly serve with enough settings. For <br>
> most drivers <br>
> the one-dimensional "PrintoutMode" (or however to call it) is <br>
> enough to <br>
> provide a newbie-friendly quick-setup option (which plays the <br>
> same roll <br>
> as the setting for Normal, Macro, Sports, Night shot ... on <br>
> some digital <br>
> cameras). It also must always be possible to set the <br>
> individual options <br>
> of the driver, so that advanced users can get all out of the <br>
> driver (as <br>
> implemented in Foomatic).<br>
> <br>
> Till<br>
> <br>
</font>
<br>