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 5.50.4611.1300" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>The latest booklet spec has a Predefined_ID with only
'Unsorted' and 'Sorted'. Not yet on the web site!</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>The code flow for a booklet implementation is supposed to work
as follows:</FONT></DIV>
<DIV><FONT size=2>If 'Sorted' is selected, the driver has to provide a proper
page flow. Implicitely this setting tells the driver that two logical pages per
physical page are required as well as a duplex setting of
short-edge.</FONT></DIV>
<DIV><FONT size=2>If 'Unsorted' is selected, this impies a duplex setting of
simplex.</FONT></DIV>
<DIV><FONT size=2>A booklet setting overwrites the duplex setting, but we
recommend to write a proper interdependency additionally.</FONT></DIV>
<DIV><FONT size=2>Booklet pages are supposed to be positioned centered by
default.</FONT></DIV>
<DIV><FONT size=2>That would do for a simple booklet feature, realized as a
check box.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>If booklet is part of a composite feature (the driver has to
check for that), check whether target size is part of the composite feature as
well. If so, check whether the target allows for two original sizes (e.g. Letter
on Ledger, A4 on A3). If not, the driver is supposed to realize booklet by
scaling. If so, by imposition.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>If MediaScaling is part of that c.f., check the setting.
Default is centered! This would take affect in a sample like 'A5 on A3 Booklet',
which would not be the standard case.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>We do not support virtual sizes for booklet printing. That
means, if A5 is not part of the media size list, 'A5 on A4 Booklet' can not be
realized.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Comments???</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>Somebody like me may design a 'Media' c.f. with booklet as a
component. This may result in the following records:</FONT></DIV>
<DIV><FONT size=2> Letter/Auto tray</FONT></DIV>
<DIV><FONT size=2> Letter/Tray1</FONT></DIV>
<DIV><FONT size=2> Letter/Tray2</FONT></DIV>
<DIV><FONT size=2> Letter/Auto tray Booklet</FONT></DIV>
<DIV><FONT size=2> Letter/Auto tray on Ledger
Booklet</FONT></DIV>
<DIV><FONT size=2>Verify that the application is always thinking in Letter
size.</FONT></DIV>
<DIV><FONT size=2>When you practice that, you should fully understand the
implications. Otherwise ask now, as this is the time.</FONT></DIV>
<DIV><FONT size=2>This is my (personal!!!) approach how to implement a media
feature. The user has one selection for a media with all media features selected
in the background. This is not supported by any other device description than
UPDF available today, not even close. By this implementation the driver
can prevent the user from a number of errors he/she can do with other
drivers.</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@mediaone.net">norbertschade@mediaone.net</A></FONT></DIV></BODY></HTML>