attachment-0001
<html xmlns:v="urn:schemas-microsoft-com:vml" xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns="http://www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=Content-Type content="text/html; charset=us-ascii">
<meta name=Generator content="Microsoft Word 11 (filtered medium)">
<!--[if !mso]>
<style>
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style>
<![endif]-->
<style>
<!--
/* Font Definitions */
@font-face
        {font-family:Helvetica;
        panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
        {font-family:Tahoma;
        panose-1:2 11 6 4 3 5 4 4 2 4;}
@font-face
        {font-family:Cambria;
        panose-1:2 4 5 3 5 4 6 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
        {margin:0in;
        margin-bottom:.0001pt;
        font-size:12.0pt;
        font-family:"Times New Roman";}
a:link, span.MsoHyperlink
        {color:blue;
        text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
        {color:purple;
        text-decoration:underline;}
span.EmailStyle18
        {mso-style-type:personal-reply;
        font-family:Cambria;
        color:blue;
        font-weight:normal;
        font-style:normal;
        text-decoration:none none;}
@page Section1
        {size:8.5in 11.0in;
        margin:1.0in 1.25in 1.0in 1.25in;}
div.Section1
        {page:Section1;}
-->
</style>
</head>
<body lang=EN-US link=blue vlink=purple style='word-wrap: break-word;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>
<div class=Section1>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<div>
<div class=MsoNormal align=center style='text-align:center'><font size=3
face="Times New Roman"><span style='font-size:12.0pt'>
<hr size=2 width="100%" align=center tabindex=-1>
</span></font></div>
<p class=MsoNormal><b><font size=2 face=Tahoma><span style='font-size:10.0pt;
font-family:Tahoma;font-weight:bold'>From:</span></font></b><font size=2
face=Tahoma><span style='font-size:10.0pt;font-family:Tahoma'> Michael Sweet
[mailto:msweet@apple.com] <br>
<b><span style='font-weight:bold'>Sent:</span></b> Monday, April 25, 2011 3:18
PM<br>
<b><span style='font-weight:bold'>To:</span></b> Petrie, Glen<br>
<b><span style='font-weight:bold'>Cc:</span></b> ptykodi@tykodi.com;
ipp@pwg.org<br>
<b><span style='font-weight:bold'>Subject:</span></b> Re: [IPP] Requested
Additions to PWG Raster</span></font><o:p></o:p></p>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
<div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>On Apr 25, 2011, at 9:45 AM, Petrie, Glen wrote:<o:p></o:p></span></font></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' type=cite><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><u1:p>
<div link=blue vlink=blue style='word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
class=apple-style-span><font size=4 color=black face=Helvetica><span
style='font-size:13.5pt;font-family:Helvetica;color:black'>...</span></font></span><font
color=blue><span style='color:blue'> </u1:p></span></font><o:p></o:p></p>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>[gwp] What, this is the very definition of incompatibility; I
a devices receives a CUPS raster file with some vendor-data in the position of
the page number and it does not represent the page number then no telling what
will happen.</span></font><o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>By definition all of these fields are driver-specific and cannot be
interpreted outside that particular driver.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>[gwp] I agree; that does not change my
statement.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>(in this case a PWG Raster driver)<o:p></o:p></span></font></p>
</div>
<div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' type=cite><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><u1:p></u1:p>
<div link=blue vlink=blue style='word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>[gwp] If you change the PWG raster file identifier so it does not
match CUPS raster then is this not produce a conflict; because they would not
longer be the same thing. Right now, no one reading a CUPS raster or PWG
raster change tell which is which.</span></font><o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>Actually, you can - if the PageSize field is all 0's, then it isn't a
CUPS Raster file which will always have the media size in integer points...<span
class=apple-style-span><font color=blue><span style='color:blue'> </span></font><o:p></o:p></span></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>[gwp] Great this says you “have a
unique Id for PWG Raster” and that the PageSize field of CUPS raster can
never be used for PWG raster since the value must be all 0’ to uniquely identify
a PWG Raster. This new identification MUST be stated in the PWG raster
specification as the new identifier.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
</div>
<div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' type=cite><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<div link=blue vlink=blue style='word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><font
size=3 color=blue face=Cambria><span style='font-size:12.0pt;font-family:Cambria;
color:blue'>[gwp] I disagree. You mean that your/the proposed Job Ticket
does have the duplex setting or the layout orientation data. If not, how
can someone ever generate the correct print output!!! </span></font><o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>The job ticket has "sides", which is an instruction to do
duplex printing. However, it doesn't tell the printer how the raster data was
generated.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>[gwp] I don’t understand your
reply.<o:p></o:p></span></font></p>
</div>
<div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' type=cite><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<div link=blue vlink=blue style='word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>
<div>
<div>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
class=apple-style-span><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;font-family:Cambria;color:blue'>The Job Ticket will
specify the output format (duplex, flip, rotate); therefore, transforms data
and information are part of the Job Ticket and the raster must be transformed
to the correct orientation required so that the printer (or any consumer of the
raster) does not know or have to perform the transforms.</span></font></span><o:p></o:p></p>
</div>
</div>
</div>
</blockquote>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype>The
job ticket has "sides" and "orientation-requested". We
don't require the printer support anything other than "portrait"
orientation and the printer tells the client how to send the back side of
duplex pages, so the client may have to pre-rotate/flip the bitmap data (or the
intermediate format that is converted to a bitmap) before sending it to the
printer.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'>However, there is no indication to the printer what rotation or
flipping was actually done for a given page. That information is *not* present
in the job ticket, and I would argue that it is not appropriate for inclusion
in the job ticket because it is a) format-specific and b) informational rather
than directive.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>[gwp] If the printer does not support
anything other than “portrait”; that is given in the printer
capabilities and the printer will not receive a job outside of it capabilities.
If the printer does receive a job outside of its capabilities; it will
best effort and must not be required to “jump through hops” to do
something it could not do. We are sending raster to the printer not an
image.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>[gwp] If the printer is capable of
duplex; it is the client that sets the flip/orientation; and, thus, only the
client worries about how to “flip” or not flip the content. The
printer only knows to do duplex; it does not need to know the flip or
orientation the raster. Remember this is raster, not image. <o:p></o:p></span></font></p>
</div>
<div><u2:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u2:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u2:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u2:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u2:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u2:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' type=cite><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<div link=blue vlink=blue style='word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>
<div>
<div>
<div bgcolor=white link=blue vlink=blue>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
class=apple-style-span><font size=3 color=black face=Helvetica><span
style='font-size:12.0pt;font-family:Helvetica;color:black'>...</span></font></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
</u2:smarttagtype></u2:smarttagtype></u2:smarttagtype></u2:smarttagtype></u2:smarttagtype></u2:smarttagtype>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt'></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><u3:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u3:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u3:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u3:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u3:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u3:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place">
<div link=blue vlink=blue style='word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>
<div>
<div>
<div bgcolor=white link=blue vlink=blue>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
class=apple-style-span><font size=3 face=Cambria><span style='font-size:12.0pt;
font-family:Cambria'>Raster data means the data is rastered-out and should not
require additional transforms (scaling might be an exception); the transforms
here may require the printer to have rotation buffers which could be large and
expensive to implement; not desirable.</span></font></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
</u3:smarttagtype></u3:smarttagtype></u3:smarttagtype></u3:smarttagtype></u3:smarttagtype></u3:smarttagtype>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype>Agreed.<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><br>
<br>
<o:p></o:p></span></font></p>
<u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><u4:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u4:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u4:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u4:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u4:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u4:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><u1:p></u1:p>
<div link=blue vlink=blue style='word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>
<div>
<div>
<div bgcolor=white link=blue vlink=blue>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
class=apple-style-span><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;font-family:Cambria;color:blue'>Therefore, I am opposed
to adding the specific PWR element for Horizontal and Vertical Transform.
If a vendor which to use transforms, then it is part of their driver
specific information but not an official PWG Raster element.</span></font></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</u4:smarttagtype></u4:smarttagtype></u4:smarttagtype></u4:smarttagtype></u4:smarttagtype></u4:smarttagtype>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype>That
isn't the point of these fields - they are informational, not directive. A
low-end printer will likely ignore them since the assumption is that the client
did the right thing. Instead, this is for high-end printers and Cloud services
that may need to "tweak" the raster document before sending it to the
real output device.<o:p></o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'><o:p> </o:p></span></font></p>
<p class=MsoNormal><font size=3 color=blue face=Cambria><span style='font-size:
12.0pt;font-family:Cambria;color:blue'>[gwp] Why would or should any printer “tweak”
the raster. The raster must be in the correct format; otherwise it is not
(printer) raster. This is a raster format, not an image format. If
you want to change the specification to PWG Image specification; then I would
agree that the printer can perform transforms on the image data. But
raster means it be “poured” in the printer and printed as delivered;
that is, the raster was generated for the printer for this reason. <o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
<blockquote style='margin-top:5.0pt;margin-bottom:5.0pt' type=cite><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u1:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><u5:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="Street"><u5:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="PostalCode"><u5:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="State"><u5:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="City"><u5:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="address"><u5:smarttagtype namespaceuri="urn:schemas-microsoft-com:office:smarttags" name="place"><u1:p></u1:p>
<div link=blue vlink=blue style='word-wrap: break-word;-webkit-nbsp-mode: space;
-webkit-line-break: after-white-space'>
<div>
<div>
<div bgcolor=white link=blue vlink=blue>
<p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span
class=apple-style-span><font size=3 color=blue face=Cambria><span
style='font-size:12.0pt;font-family:Cambria;color:blue'>The same logic applies
to the total number of page.</span></font></span><o:p></o:p></p>
</div>
</div>
</div>
</div>
</blockquote>
</u5:smarttagtype></u5:smarttagtype></u5:smarttagtype></u5:smarttagtype></u5:smarttagtype></u5:smarttagtype>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype></u1:smarttagtype>How?<o:p></o:p></span></font></p>
</div>
<div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'><o:p> </o:p></span></font></p>
</div>
</div>
<div><span style='orphans: 2;text-align:auto;widows: 2;-webkit-border-horizontal-spacing: 0px;
-webkit-border-vertical-spacing: 0px;-webkit-text-decorations-in-effect: none;
-webkit-text-size-adjust: auto;-webkit-text-stroke-width: 0px;word-spacing:
0px'>
<div>
<p class=MsoNormal><font size=4 color=black face=Helvetica><span
style='font-size:13.5pt;font-family:Helvetica;color:black'>________________________________________________________________________<br>
Michael Sweet, Senior Printing System Engineer, PWG Chair<o:p></o:p></span></font></p>
</div>
</div>
<p class=MsoNormal><font size=3 face="Times New Roman"><span style='font-size:
12.0pt'></span><o:p> </o:p></span></font></p>
</div>
<br />--
<br />This message has been scanned for viruses and
<br />dangerous content by
<a href="http://www.mailscanner.info/"><b>MailScanner</b></a>, and is
<br />believed to be clean.
</body>
</html>