Conference iosg::all-in-1_v30

1594.0. "Easy Printing of Postscript" by SUBURB::TAFF::Wob (Robert Screene, UK Finance EUC) Mon Oct 12 1992 17:46

Hello,

I am looking into making the printing of Postscript documents easier under 
ALL-IN-1 v3.  

My experience is generally within the Finance function, and the lack of 
knowledge around Postscript printing wastes a lot of time and paper.

I have noticed ALL-IN-1 v3 has a special PS document type, I presume such a 
document should be handled automatically when sent to a Postscript capable 
printer.   This doesn't seem to be the case, as special print formats must 
be added by the User at the print argument form.   I would like to get this 
to happen automatically.

I also propose to add a routine to the standard print script logic, which 
would check the current mail/document and any attachments, to see if they 
contain Postscript-like code within the first few pages.   I intend to 
provide a warning box, which advises that printing Poscsript as ASCII is 
not generally a good idea, then perhaps an offer of sending the Posctsript 
portion alone to the printer, as a correctly formatted PS type document (as 
above).  
e.g.        
	------------------------------------------------------------------	
	WARNING; a large section of your printing appears to be Postscript. 
	         This is used for special high quality output.	

	If this is printed normally it may waste hundreds of pages, 	
	covering them in strange characters.  I can send the Postscript 
	section on it's own to the printer, and have it correctly formatted 
	(as PS).	

	Print the Postscript section specially as advised [Y/N]? 	
------------------------------------------------------------------
If user replies with N:   
  This could be wasteful, do you really want to print normally [Y/N]?

  If user then still replies with Y, do a normal print.  
  Else, exit from print script.


A solution to this problem is mentioned in topic 520, but this involves a 
separate POST option for printing such files.  I want this automated so 
that the user will not have to decide which option is appropriate.

Hmm, wonder what I should do for multiple print jobs?   Also, are there 
many cases of ASCII text following commands in the single document (i.e. 
Distribution list trailers)?

Any other solutions to this around?  I'd like it for free, but am happy to 
develop something myself.

Any thoughts and advice will be appreciated.

Thanks,
Robert.