dvips output error revisited...
Eli Zaretskii
eliz@is.elta.co.il
Wed, 29 Sep 1999 16:06:16 +0200 (IST)
On Wed, 29 Sep 1999, ALAN A DUNWELL wrote:
> files are shared by all win/95/98/2000/whatever workstations. They
> just modify their path to see the bin area. So they all end up using
> the same config.ps. Some may want to print to local printers, mostly
> HP laserjet types, or more often to network printer queues, all
> postscript printers. However different folks may want to go to
> different printers or queues, so I can't hardwire that in config.ps.
In that case, the right thing is for each user to have their own printer
configuration file, in addition to the global config.ps. The default
printer is just a tip of the iceberg: before long, you will hear
complaints that other config.ps settings, like amount of memory installed
in the printer, its resolution, etc. are also wrong.
The easiest way to have customized startup file is to set the DVIPSRC
variable in the environment whose value is the full path of a file. That
file has the same format as config.ps, but it is read by dvips *after*
config.ps, and so can override the defaults.
Finally, if the users change their default printer often, or if they use
several different ones, there's the appropriate command-line option.
This is all in the docs, btw.