attachment-0001
<html>
At 5/7/2002 07:55 PM, Norbert Schade wrote:<br>
<blockquote type=cite class=cite cite><font size=2>1. is there interest
to extend our list of DRV_keys to some job and user related
variables???</font><br>
<br>
<font size=2>samples could be:</font>
<ul><font size=2>
<li>job id</font> <font size=2>
<li>user name</font> <font size=2>
<li>user id</font> <font size=2>
<li>workstation</font> <font size=2>
<li>domain</font> <font size=2>
<li>application sending the document</font> <font size=2>
<li>document name</font>
</ul><font size=2>may be you have a longer list.</font><br>
</blockquote><br>
I don't have a problem with this. In fact I would add job name to the
list.<br><br>
<blockquote type=cite class=cite cite><font size=2>2. we still think
about the file formats we might support for pictures, if we support them
in a UI.</font><br>
<font size=2>first idea was JPEG. what about gif???</font><br>
<font size=2>target is to decide on one eventually.</font><br>
</blockquote><br>
I believe that GIF has some patent issues with it.<br><br>
<blockquote type=cite class=cite cite> <br>
<font size=2>3. I request bytes instead of kilobytes in the
band_units_enum.</font><br>
<font size=2>the background I have in mind a quite dirty. may be the
driver is not only concerned about a print head height or maximum input
buffer, but also to create small enough snippets to allow an application
(like a language monitor or what our Linux friends call a client) to hold
the job for a moment and communicate to the device. I know this attribute
would not be enough but it allows small snippets with a byte
number.</font><br>
</blockquote><br>
OK<br><br>
</html>