attachment
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<TITLE>Message</TITLE>
<META content="MSHTML 5.50.4926.2500" name=GENERATOR></HEAD>
<BODY>
<DIV><SPAN class=822260615-21082003><FONT face="Courier New" color=#0000ff
size=2>Looking at the dates, it looks to me that some of Harry's email to the
<FONT face=Tahoma color=#000000>[printing-jobticket] list just got un-stuck in
some email server: these are over a month old.</FONT></FONT></SPAN></DIV>
<DIV><SPAN class=822260615-21082003><FONT face=Tahoma
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=822260615-21082003><FONT face=Tahoma
size=2>bt</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr
style="PADDING-LEFT: 5px; MARGIN-LEFT: 5px; BORDER-LEFT: #0000ff 2px solid; MARGIN-RIGHT: 0px">
<DIV></DIV>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left><FONT
face=Tahoma size=2>-----Original Message-----<BR><B>From:</B> Wagner,William
[mailto:WWagner@NetSilicon.com] <BR><B>Sent:</B> Thursday, August 21, 2003
6:28 AM<BR><B>To:</B> Harry Lewis; TAYLOR,BOB (HP-Vancouver,ex1)<BR><B>Cc:</B>
IPP@pwg.org; printing-driver@freestandards.org;
printing-jobticket@freestandards.org; Zehler, Peter<BR><B>Subject:</B> RE:
[printing-jobticket] RE: [printing-driver] RE: IPP> Print Quality Issue
resolution<BR><BR></FONT></DIV>
<DIV><SPAN class=450381513-21082003><FONT face=Arial color=#0000ff size=2>It
is quite a surprise to see this discussion still going on. When the idea of
two varaiables was brought up in Portland, it seemed quite reasonable. At
least with the implementations I am aware of, the techniques
for quality improvement (e.g., increased pseudo-resolution) are different
with the techniques for marker saving (bias voltage
adjustment, sparse writing in solid areas). Further, although
there is interaction in the effect upon the output, the user
motivation in selecting quality level is more likely to be
speed while the motivation for marker saving is cost. As is
suggested, each marketing group will put is own spin on these variables,
but I do think that having two variables makes
sense.</FONT></SPAN></DIV>
<DIV><SPAN class=450381513-21082003><FONT face=Arial color=#0000ff
size=2></FONT></SPAN> </DIV>
<DIV><SPAN class=450381513-21082003><FONT face=Arial color=#0000ff size=2>Bill
Wagner</FONT></SPAN></DIV>
<BLOCKQUOTE dir=ltr style="MARGIN-RIGHT: 0px">
<DIV class=OutlookMessageHeader dir=ltr align=left><FONT face=Tahoma
size=2>-----Original Message-----<BR><B>From:</B> Harry Lewis
[mailto:harryl@us.ibm.com]<BR><B>Sent:</B> Monday, July 14, 2003 6:05
PM<BR><B>To:</B> TAYLOR,BOB (HP-Vancouver,ex1)<BR><B>Cc:</B> IPP Discussion
List (IPP@pwg.org); printing-driver@freestandards.org;
printing-jobticket@freestandards.org; Zehler, Peter<BR><B>Subject:</B>
[printing-jobticket] RE: [printing-driver] RE: IPP> Print Quality Issue
resolution<BR><BR></FONT></DIV><BR><FONT face="Courier New" color=blue
size=2>>My main question with TonerSaving/InkSaving/MarkerSaving is how
this is any different than PrintQuality(High|Normal|Draft)</FONT> <BR><FONT
face=sans-serif size=2>To answer this question, straightforward, there are
implementations where you can select High|Normal|Draft independently from
"Saver". Administrators may want to configure policy that "Saving"
must always be on yet still allow the choice of High|Normal|Draft, within
that context. </FONT><BR><BR><FONT face="Courier New" color=blue
size=2>>PrintQuality=High & MarkerSaving=False would seem to say
"print in high quality, and waste toner/ink for no good reason</FONT>
<BR><FONT face=sans-serif size=2>I think people would expect:</FONT>
<BR><FONT face=sans-serif size=2> PQ=High|Saving=Off to result in the
BEST possible quality. </FONT><BR><FONT face=sans-serif
size=2> PQ=High|Saving=On to result in the best possible quality while
still saving marker (toner, ink ...)</FONT> <BR><FONT face=sans-serif
size=2> PQ=Draft|Saving=Off to result in the FASTEST possible
printing</FONT> <BR><FONT face=sans-serif size=2> PQ=Draft|Saving=On to
result in the fastest possible printing with legibility that may not stand
up to close scrutiny because marker (toner, ink...) has been used sparingly.
</FONT><BR><BR><FONT face=sans-serif
size=2>---------------------------------------------- <BR>Harry Lewis
<BR>Chairman - IEEE-ISTO Printer Working Group<BR>http://www.pwg.org<BR>IBM
Printing Systems
<BR>http://www.ibm.com/printers<BR>303-924-5337<BR>----------------------------------------------
</FONT><BR><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="40%"><FONT face=sans-serif size=1><B>"TAYLOR,BOB
(HP-Vancouver,ex1)" <bobt@hp.com></B> </FONT><BR><FONT
face=sans-serif size=1>Sent by: owner-ipp@pwg.org</FONT>
<P><FONT face=sans-serif size=1>07/14/2003 02:36 PM</FONT> </P>
<TD width="59%">
<TABLE width="100%">
<TBODY>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif
size=1>printing-driver@freestandards.org, "Zehler, Peter"
<PZehler@crt.xerox.com></FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>"IPP Discussion List
(IPP@pwg.org)" <IPP@pwg.org>,
printing-jobticket@freestandards.org</FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif
size=1>Subject</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>RE:
[printing-driver] RE: IPP> Print Quality Issue
resolution</FONT></TD></TR></TBODY></TABLE><BR>
<TABLE>
<TBODY>
<TR vAlign=top>
<TD>
<TD></TD></TR></TBODY></TABLE><BR></TD></TR></TBODY></TABLE><BR><BR><BR><FONT
face="Courier New" color=blue size=2>My main question with
TonerSaving/InkSaving/MarkerSaving is how this is any different than
PrintQuality(High|Normal|Draft). We as well have nifty algorithms for
saving "marker" without impacting quality - but I don't know why we'd ever
want to turn it "off" seperately from the notion of PQ/performance/economy
tradeoff (which I maintain is what PrintQuality actually is). The
semantics of this as a separate attribute seem somewhat odd to me - i.e.,
PrintQuality=High & MarkerSaving=False would seem to say "print in high
quality, and waste toner/ink for no good reason", and PrintQuality=Draft
& MarkerSaving=False would seem to say "print in poor quality, but waste
tone/ink anyway". IMHO, a "separate" TonerSaving mode is really a
vendor-specific extension of PrintQuality, which as Ira noted as already
supported (though they are supposed to be IANA-registered, which I'm
guessing most vendors have not bothered to do).</FONT> <BR><FONT
size=3> </FONT> <BR><FONT face="Courier New" color=blue
size=2>thanks,</FONT> <BR><FONT size=3> </FONT> <BR><FONT
face="Courier New" color=blue size=2>bt</FONT> <BR><FONT face=Tahoma
size=2>-----Original Message-----<B><BR>From:</B> Harry Lewis
[mailto:harryl@us.ibm.com] <B><BR>Sent:</B> Friday, July 11, 2003 6:49
AM<B><BR>To:</B> Zehler, Peter<B><BR>Cc:</B> IPP Discussion List
(IPP@pwg.org); printing-driver@freestandards.org;
printing-jobticket@freestandards.org; Zehler, Peter<B><BR>Subject:</B>
[printing-driver] RE: IPP> Print Quality Issue
resolution<BR></FONT><BR><FONT face=sans-serif size=2><BR>My concern is that
"save toner" is probably the most concrete concept compared to "Good,
Better, Best" or "Text, Image, Graphics". The later has efficient
application only in special cases (some of which may be very significant,
like printing photo's). Otherwise, people stare at their mixed object
document and wonder. I feel "save toner" should be explicit. </FONT><FONT
size=3><BR></FONT><FONT face=sans-serif size=2><BR>We went from a flat set
of descriptors to a pairing.. perhaps we should really go to a matrix
(although I don't like the perceived complexity)</FONT><FONT size=3>
<BR></FONT><FONT face=Courier size=2><BR>Good - Better - Best</FONT><FONT
size=3> </FONT><FONT face=Courier size=2><BR>Text - Text+Graphics - Graphics
- Image</FONT><FONT size=3> </FONT><FONT face=Courier
size=2><BR>TonerSaving</FONT><FONT size=3> <BR></FONT><FONT face=sans-serif
size=2><BR>---------------------------------------------- <BR>Harry Lewis
<BR>Chairman - IEEE-ISTO Printer Working Group<BR>http://www.pwg.org<BR>IBM
Printing Systems
<BR>http://www.ibm.com/printers<BR>303-924-5337<BR>----------------------------------------------
</FONT><FONT size=3><BR><BR></FONT>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="27%"><FONT face=sans-serif size=1><B>"Zehler, Peter"
<PZehler@crt.xerox.com></B> </FONT>
<P><FONT face=sans-serif size=1>07/11/2003 04:54 AM</FONT><FONT
size=3> </FONT></P>
<TD width="72%"><BR>
<TABLE width="100%">
<TBODY>
<TR>
<TD width="13%">
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD vAlign=top width="86%"><FONT face=sans-serif size=1>Harry
Lewis/Boulder/IBM@IBMUS, "Zehler, Peter"
<PZehler@crt.xerox.com></FONT><FONT size=3> </FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>"IPP Discussion List
(IPP@pwg.org)" <IPP@pwg.org>,
printing-driver@freestandards.org,
printing-jobticket@freestandards.org</FONT><FONT size=3> </FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif
size=1>Subject</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>RE: IPP> Print
Quality Issue resolution</FONT></TD></TR></TBODY></TABLE><BR><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="49%">
<TD
width="50%"></TD></TR></TBODY></TABLE><BR></TD></TR></TBODY></TABLE><BR><FONT
size=3><BR><BR></FONT><FONT face=Arial color=#000080
size=2><BR>Harry,</FONT><FONT size=3> </FONT><FONT face=Arial color=#000080
size=2><BR>We felt that there are many different attributes involved in
heuristics for saving toner and printing fast. Some of those are
"resolution", "media" and aspects of the document content. We felt the
requirements were met by keeping the existing "print-quality" values and
augmenting them with hints on how to process the document content to achieve
'draft' 'normal' and 'high'. The assumption is that draft is fastest
and uses the least toner.</FONT><FONT size=3> </FONT><FONT face=Arial
color=#000080 size=2><BR>Pete</FONT><FONT size=3> </FONT><FONT face=Arial
color=#000080 size=2><BR></FONT><FONT size=3> </FONT>
<P><FONT face=Impact color=#000080 size=3>Peter Zehler</FONT><FONT
face="Times New Roman" color=#000080 size=3> </FONT><FONT color=red
size=3><BR>XEROX</FONT><FONT face="Times New Roman" color=#000080 size=3>
</FONT><FONT face=Tahoma color=#000080 size=2><BR>Xerox Innovation
Group</FONT><FONT face="Times New Roman" color=#000080 size=3> </FONT><FONT
face=Arial color=#000080 size=2><BR>Email: PZehler@crt.xerox.com</FONT><FONT
face="Times New Roman" color=#000080 size=3> </FONT><FONT face=Arial
size=2><BR>Voice: (585) 265-8755</FONT><FONT
face="Times New Roman" color=#000080 size=3> </FONT><FONT face=Arial
size=2><BR>FAX: (585) 422-</FONT><FONT face=Arial
color=#000080 size=2>7961</FONT><FONT face="Times New Roman" color=#000080
size=3> </FONT><FONT face=Arial color=#000080 size=2><BR>US Mail: Peter
Zehler</FONT><FONT face="Times New Roman" color=#000080 size=3> </FONT>
<P><FONT face=Arial color=#000080 size=2> Xerox
Corp.</FONT><FONT face="Times New Roman" color=#000080 size=3> </FONT><FONT
face=Arial color=#000080 size=2><BR> 800 Phillips
Rd.</FONT><FONT face="Times New Roman" color=#000080 size=3> </FONT><FONT
face=Arial color=#000080 size=2><BR> M/S
128-25E</FONT><FONT face="Times New Roman" color=#000080 size=3>
</FONT><FONT face=Arial color=#000080 size=2><BR>
Webster NY, 14580-9701</FONT><FONT face="Times New Roman" color=#000080
size=3> </FONT><FONT face=Tahoma size=2><BR>-----Original
Message-----<B><BR>From:</B> Harry Lewis [mailto:harryl@us.ibm.com]
<B><BR>Sent:</B> Thursday, July 10, 2003 11:26 PM<B><BR>To:</B> Zehler,
Peter<B><BR>Cc:</B> IPP Discussion List (IPP@pwg.org);
printing-driver@freestandards.org;
printing-jobticket@freestandards.org<B><BR>Subject:</B> Re: IPP> Print
Quality Issue resolution</FONT><FONT size=3> </FONT><FONT
face="Times New Roman" size=3><BR></FONT><FONT size=3> </FONT><FONT
face=sans-serif size=2><BR><BR>> </FONT><FONT face="Courier New"
size=2>We finally agreed that the two values</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'save-toner' and</FONT><FONT face="Times New Roman" size=3>
</FONT><FONT face="Courier New" size=2>'speed' are implied by
the</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>"print-quality".</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>Since they were not required, they were removed.</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face=sans-serif size=2><BR><BR>I
think this warrants further examination. I have known toner saving methods
that do a very good job of preserving print quality.
<BR>---------------------------------------------- <BR>Harry Lewis
<BR>Chairman - IEEE-ISTO Printer Working Group<BR>http://www.pwg.org<BR>IBM
Printing Systems
<BR>http://www.ibm.com/printers<BR>303-924-5337<BR>----------------------------------------------
</FONT>
<P>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="27%"><FONT face=sans-serif size=1><B>"Zehler, Peter"
<PZehler@crt.xerox.com></B> <BR>Sent by:
owner-ipp@pwg.org</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face=sans-serif size=1>07/10/2003 01:41 PM</FONT><FONT
face="Times New Roman" size=3> </FONT></P>
<TD width="72%"><BR>
<TABLE width="100%">
<TBODY>
<TR>
<TD width="13%">
<DIV align=right><FONT face=sans-serif size=1>To</FONT></DIV>
<TD vAlign=top width="86%"><FONT face=sans-serif size=1>"IPP
Discussion List (IPP@pwg.org)" <IPP@pwg.org>,
printing-jobticket@freestandards.org,
printing-driver@freestandards.org</FONT><FONT
face="Times New Roman" size=3> </FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif size=1>cc</FONT></DIV>
<TD vAlign=top><FONT face="Times New Roman"
size=3> </FONT><FONT size=3> </FONT>
<TR>
<TD>
<DIV align=right><FONT face=sans-serif
size=1>Subject</FONT></DIV>
<TD vAlign=top><FONT face=sans-serif size=1>IPP> Print
Quality Issue resolution</FONT></TD></TR></TBODY></TABLE><BR><FONT
face="Times New Roman" size=3><BR></FONT><FONT size=3> </FONT>
<P><BR>
<TABLE width="100%">
<TBODY>
<TR vAlign=top>
<TD width="61%"><FONT face="Times New Roman"
size=3> </FONT><FONT size=3> </FONT>
<TD width="38%"><FONT face="Times New Roman"
size=3> </FONT></TD></TR></TBODY></TABLE><BR></P></TD></TR></TBODY></TABLE>
<P><FONT face="Times New Roman" size=3><BR><BR></FONT><FONT face=Arial
size=2><BR><BR>All,</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face="Courier New" size=2>During the PWG/FSG meeting in Portland we
had a discussion about the IPP</FONT><FONT face="Times New Roman" size=3>
</FONT><FONT face="Courier New" size=2>"print-quality" attribute and FSG's
desire to add two new values,</FONT><FONT face="Times New Roman" size=3>
</FONT><FONT face="Courier New" size=2>'economy' and</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'fine', where</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>'economy' is lower than</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'draft' and</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>'fine' is higher than</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'high'.</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>The FSG further proposed the addition of a new
attribute, called</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>"print-optimize", that</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New" size=2>would
augment</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>"print-quality" with values of</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'image',</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>'photo',</FONT><FONT face="Times New Roman"
size=3> </FONT><FONT face="Courier New" size=2>'text',</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'text-and-image',</FONT><FONT face="Times New Roman" size=3>
</FONT><FONT face="Courier New" size=2>'save-toner' and</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'speed'.</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face="Courier New" size=2>With regard to</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'economy' and</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>'fine', we agreed that</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'economy' would map to</FONT><FONT face="Times New Roman" size=3>
</FONT><FONT face="Courier New" size=2>"print-quality"='draft'
and</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>'fine' to</FONT><FONT face="Times New Roman"
size=3> </FONT><FONT face="Courier New" size=2>"print-quality"='high'.
There may be end user</FONT><FONT face="Times New Roman" size=3>
</FONT><FONT face="Courier New" size=2>visible features that map to
multiple</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>attributes. We leave it to specific
print</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>domains to</FONT><FONT face="Times New Roman"
size=3> </FONT><FONT face="Courier New" size=2>model these higher
level</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>aggregate</FONT><FONT face="Times New Roman"
size=3> </FONT><FONT face="Courier New" size=2>features. When
appropriate we will add needed elements to the Semantic Model.</FONT><FONT
face="Times New Roman" size=3> </FONT>
<P><FONT face="Courier New" size=2>There was a lot of push back
on</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>"print-optimize". The main concern was
that</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>"print-optimize" contained a mixed bag of items.
The two main categories were content metadata and</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>rendering hints. We finally agreed that the two
values</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>'save-toner' and</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'speed' are implied by the</FONT><FONT face="Times New Roman" size=3>
</FONT><FONT face="Courier New" size=2>"print-quality".</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>Since they were not required, they were removed. The remaining
values are needed to direct the type of optimization/processing that will be
performed on the content. It does not necessarily mean the</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New" size=2>value
describes the</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>content. </FONT><FONT face="Times New Roman"
size=3> </FONT><FONT face="Courier New" size=2>To clarify this we
changed the attribute name to</FONT><FONT face="Times New Roman" size=3>
</FONT><FONT face="Courier New" size=2>"print-content-optimize".
</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>Finally the value</FONT><FONT
face="Times New Roman" size=3> </FONT><FONT face="Courier New"
size=2>'image' seemed the same as</FONT><FONT face="Times New Roman" size=3>
</FONT><FONT face="Courier New" size=2>'photo'. The name for this was
changed to</FONT><FONT face="Times New Roman" size=3> </FONT><FONT
face="Courier New" size=2>'graphic'.</FONT><FONT face="Times New Roman"
size=3> </FONT>
<P><FONT face="Courier New" size=2>As a result the following attribute will
be added to the JobX specification in it next revision.</FONT><FONT
face="Times New Roman" size=3> </FONT>
<P><FONT face="Courier New" size=2> print-content-optimize
(type2 keyword)</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face="Courier New" size=2> This attribute
refines the value specified by the print-quality</FONT><FONT
face="Times New Roman" size=3> </FONT>
<P><FONT face="Courier New" size=2>
attribute.</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face="Courier New" size=2> The standard keyword
values are:</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face="Courier New" size=2>
'graphic': optimize for graphic clarity</FONT><FONT
face="Times New Roman" size=3> </FONT>
<P><FONT face="Courier New" size=2>
'photo': optimize for photo clarity</FONT><FONT face="Times New Roman"
size=3> </FONT>
<P><FONT face="Courier New" size=2> 'text':
optimize for text clarity</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face="Courier New" size=2>
'text-and-graphic': optimize for both text and graphic
clarity</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face=Impact size=3>Peter Zehler</FONT><FONT face="Times New Roman"
size=3> </FONT>
<P><FONT face="Times New Roman" color=red size=3>XEROX</FONT><FONT
face="Times New Roman" size=3> </FONT>
<P><FONT face=Tahoma size=2>Xerox Innovation Group</FONT><FONT
face="Times New Roman" size=3> </FONT>
<P><FONT face=Arial size=2>Email: PZehler@crt.xerox.com</FONT><FONT
face="Times New Roman" size=3> </FONT>
<P><FONT face=Arial size=2>Voice: (585) 265-8755</FONT><FONT
face="Times New Roman" size=3> </FONT>
<P><FONT face=Arial size=2>FAX: (585)
422-7961</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face=Arial size=2>US Mail: Peter Zehler</FONT><FONT
face="Times New Roman" size=3> </FONT>
<P><FONT face=Arial size=2> Xerox
Corp.</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face=Arial size=2> 800 Phillips
Rd.</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face=Arial size=2> M/S
128-25E</FONT><FONT face="Times New Roman" size=3> </FONT>
<P><FONT face=Arial size=2> Webster NY,
14580-9701</FONT><FONT face="Times New Roman" size=3> </FONT>
<P></P></BLOCKQUOTE></BLOCKQUOTE></BODY></HTML>