[printing-discuss] RE: [printing-driver] proposal of what features the communication toaprinter driver should support

[Till Kamppeter]

In case of the ink running out, the current page should be repeated 
after replacing the cartridges, if one prints Duplex an already printed 
back side must be repeated, too. Or one must declare the cartridge empty 
  when it still contais a little rest of ink, to avoid that it runs out 
in the middle of the page. The threashold to declare a cartridge as 
empty should perhaps depend on the paper size of the printer/the current 
page or even on the bitmap of the current page, especially for 
large-format printers (Epson Stylus Pro 10000 and so). One could even 
consider this separately for all the colors (C, M, Y, K, c, m). One 
could perhaps even hold a job when it comes to a page for which the 
current cartridges have not enough ink any more and let a job with a 
smaller paper size/ink density pass by.

    Till


Glen Petrie wrote:

> Actually, for out of ink or out of paper scenarios, you do not abort the
> job at all.  The printer is usually offline in those cases.  How about
> the ability to restart a job at a certain page?  I haven't come across
> a printer command that aborts a page, but I don't see the problem in
> providing both the ability to abort a job and abort a page.
> [glen]   Isn't restarting a job at a certain page more overhead for the
> print manager process than just stopping and sending the page in
> error/question.  And actually, to the driver the "restart job at a certain
> page" is just a new job (with less pages) since, based on the comment below,
> the driver never sees the entire job.    So this approach is supported by
> virtue of executing another job.
>