Re: [Gimp-print-devel] Ghostscript driver

[Robert L K. <rl...@al...>]

   From: sh...@al...
   Date: Sat, 20 May 2000 04:58:17 +0900

   What I think should be done is to write a simple shell script which can
   parse the user's saved printer configuration and call ghostscript with
   the appropriate options.  This shell script can be used as an input
   filter in the printcap file. Whether the options are numerical or string
   is largely irrelevant then, since the user would not need to see them.

By the time we're down at that level, we may not have access to the
user's home directory (if the user even has one on the system where
this is running).  We also don't know who the user is at this point.
Everything's been handed off to the print system by now.

Mike probably has much better ideas than this.  They probably all
involve using CUPS for this purpose.  Either CUPS or PDQ would help
out here on the front end.  The issue is reliably passing arguments to
Ghostscript.

-- 
Robert Krawitz <rl...@al...>      http://www.tiac.net/users/rlk/

Tall Clubs International  --  http://www.tall.org/ or 1-888-IM-TALL-2
Member of the League for Programming Freedom -- mail lp...@uu...
Project lead for The Gimp Print --  http://gimp-print.sourceforge.net

"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton