attachment-0001
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=iso-8859-1">
<META content="MSHTML 6.00.2600.0" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>We redesigned the classifying identifiers with two-dimensional
parameters.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>1. Virtual units</FONT></DIV>
<DIV><FONT size=2>Is now an element with Predefined_ID/Proprietary_ID
attributes.</FONT></DIV>
<DIV><FONT size=2>Predefined_ID has its own data type for demonstration purpose
and popular values.</FONT></DIV>
<DIV><FONT size=2>The syntax is 'virtualUnits' + '_' + positiveInteger + 'x' +
positiveInteger.</FONT></DIV>
<DIV><FONT size=2>2. Device Resolution</FONT></DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>Is now an element with Predefined_ID/Proprietary_ID
attributes.</FONT></DIV>
<DIV><FONT size=2>Predefined_ID has its own data type for demonstration purpose
and popular values.</FONT></DIV></FONT></DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>The syntax is 'deviceResolution' + '_' + positiveInteger + 'x'
+ positiveInteger. We have changed the values to dpi.</FONT></DIV></FONT></DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>2. Raster Resolution within the raster
objects</FONT></DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>A raster object is now an element with
Predefined_ID/Proprietary_ID attributes.</FONT></DIV>
<DIV><FONT size=2>Predefined_ID has its own data type for demonstration purpose
and popular values.</FONT></DIV></FONT></DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>The syntax is 'rasterResolution' + '_' + positiveInteger + 'x'
+ positiveInteger. We have changed the values to
dpi.</FONT></DIV></FONT></DIV></FONT></DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>2. Positioning</FONT></DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>Is now an element with Predefined_ID/Proprietary_ID
attributes.</FONT></DIV>
<DIV><FONT size=2>Predefined_ID has its own data type for demonstration purpose
and popular values.</FONT></DIV></FONT></DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>The syntax is 'deviceResolution' + '_' + positiveInteger + 'x'
+ positiveInteger. We have changed the values to
dpi.</FONT></DIV></FONT></DIV></FONT></DIV>
<DIV><FONT size=2>We have combined the two attributes for the maximum values to
one attribute 'MaximumValue'.</FONT></DIV>
<DIV><FONT size=2>The syntax is positiveInteger + 'x' + positiveInteger. The
values represent the maximum values for the command sequence. This can be, but
is not necessarily identical to dpi values. There are PDL out there, where these
values are not arbitrary, but have a rather small limit. that means the driver
perhaps has to repeatedly send relative positioning command sequences. This
attribute helps identifying that special condition (e.g. think of some Canon
bubble jets).</FONT></DIV>
<DIV><FONT size=2>With this feature we have some small discussion going on with
devices in mind, which cannot position with x and y dimension in one command
sequence. These are typically banding devices. We will keep you
informed.</FONT></DIV>
<DIV><FONT size=2>Attributes 'Reference' and 'Direction' are now mandatory. The
driver must rely on finding that information.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Norbert Schade<BR>69 Prescott Drive<BR>North Chelmsford, MA
01863<BR>978-251-1017<BR><A
href="mailto:norbertschade@attbi.com">norbertschade@attbi.com</A></FONT></DIV></BODY></HTML>