[2347] in Enterprise Print Delivery Team

home help back first fref pref prev next nref lref last post

Banner Pages

daemon@ATHENA.MIT.EDU (Rocklyn E. Clarke)
Thu Feb 28 19:08:21 2002

Mime-Version: 1.0
Message-Id: <p05010408b8a47474aad9@[18.152.2.129]>
Date: Thu, 28 Feb 2002 19:08:16 -0500
To: Enterprise Printing Delivery Team <PRINTDEL@MIT.EDU>
From: "Rocklyn E. Clarke" <rclarke@MIT.EDU>
Content-Type: text/plain; charset="us-ascii" ; format="flowed"

Hi Team,

I have the banner program working reasonably well on Pillage, but 
there are some restrictions in using it that we should discuss on 
Monday:

1. Standard printcap entries cannot pass a banner from LPRng into IPM.
This means that a postscript printer directly attached to IPM (as is 
currently the case with ep1) cannot receive banners generated by 
LPRng.  If we go back to the old method of attaching the postscript 
printers, then we can have an entry named ep1-direct which can 
generate the banner and pass it to the printer.

The only way around this is to move the banner code into the filter 
code and somehow merge a banner with the incoming spool file.  It's 
probably doable, but I'm not sure that this is a good way to do 
things.

2.  The print job and host information get lost when passing through IPM
This means that they don't make it onto the banner page.  This is 
probably something we can live with, but we should discuss it anyway.

Rocklyn

home help back first fref pref prev next nref lref last post