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.2719.2200" name=GENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=#ffffff>
<DIV><FONT size=2>We are providing the following font related entries in the
event_enum:</FONT></DIV>
<DIV><FONT size=2>1. FontObjects</FONT></DIV>
<DIV><FONT size=2>when entering or leaving the world of fonts in the
printer</FONT></DIV>
<DIV><FONT size=2>2. DeviceFonts</FONT></DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>when entering or leaving the world of resident (not download)
fonts in the printer</FONT></DIV>
<DIV>3. DeviceFont</DIV>
<DIV>the command sequence at start or end of a resident font in the
printer</DIV></FONT></DIV>
<DIV><FONT size=2>4. DeviceFontCharacter</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>1. and 2. are general events and easy to handle.</FONT></DIV>
<DIV><FONT size=2>3. and 4. require more attention. A driver would check all
DeviceFont related events (four in the sample below) when any of the font
attributes on the host platform have changed (e.g. from Arial to TNR, from
upright to italic or else). A driver would check all DeviceFontCharacter
related events (two in the sample below) to find out if the Parameter_ID
of Character.Parameter (please help me check, if attribute
Character_PrintOut is only a duplicate of this parameter and therefore redundant
and can be removed. I haven't been to that detail for quite a while) or of
Character.SymbolSet.Parameter has changed. We assume a device description
developer would create an event per Parameter element.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>A sample data flow could look like</FONT></DIV>
<DIV><FONT size=2>- command sequence reference EnterFontObjects at start of
event FontObjects. no parameter references used.</FONT></DIV>
<DIV><FONT size=2>- c.s.r. EnterResidentFont at start of event DeviceFonts. no
parameter references used.</FONT></DIV>
<DIV><FONT size=2>- c.s.r. StartDeviceFont at start of event DeviceFont.
DeviceFont.Parameter.Parameter_ID used.</FONT></DIV>
<DIV><FONT size=2>- c.s.r. DeviceFontStyle at start of even DeviceFont.
ModifyingAttributes.Style.Parameter.Parameter_ID used.</FONT></DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>- c.s.r. DeviceFontWeight at start of even DeviceFont.
ModifyingAttributes.Weight.Parameter.Parameter_ID used.
<DIV><FONT size=2>- c.s.r. DeviceFontColor at start of even DeviceFont.
ModifyingAttributes.Color.Parameter.Parameter_ID
used.</FONT></DIV></FONT></DIV></FONT></DIV>
<DIV><FONT size=2> Other modifying attributes possible but not used in
this sample.</FONT></DIV>
<DIV>
<DIV><FONT size=2>
<DIV><FONT size=2>- c.s.r. DeviceFontCharacterSymbolSet at start of event
DeviceFontCharacter. Character.SymbolSet.Parameter.Parameter_ID
used.</FONT></DIV>
<DIV>
<DIV><FONT size=2>- c.s.r. DeviceFontCharacterTransparent at start of event
DeviceFontCharacter. Character.Parameter.Parameter_ID used. This is to print
transparent characters. The command sequence is supposed to tell the printer
'interpret the next byte as a character instead of an
escape'.</FONT></DIV></DIV>- c.s.r. LeaveFontObjects at end of event
FontObjects. no parameter references used.</FONT></DIV></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>To make this work I think we need one common
agreement:</FONT></DIV>
<DIV><FONT size=2>If a specific Parameter_ID attribute is empty or the Parameter
element is not assigned, the corresponding command sequence is not sent at all
if and only if the command sequence refers to that Parameter_ID
attribute.</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>That is the first time we specify command sequence handling to
that detail for font handling.</FONT></DIV>
<DIV><FONT size=2>I forgot something?</FONT></DIV>
<DIV><FONT size=2>Any questions or feedback?</FONT></DIV>
<DIV><FONT size=2></FONT> </DIV>
<DIV><FONT size=2>regards</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>