dvips output error revisited...

[Rolf S. Arvidson]

Alan,
Might it not be possible to have individual users and/or machines declare an
environmental variable within their shell or command environment, e.g.

"set TEXMFLOCAL = C:/TeX/texmf.local"
or
"set HOMETEXMF= C:/TeX/texmf.local"

and install their own config.ps in that local path (e.g.,
c:\tex\texmf.local\dvips\config\config.ps), that could then be modified
according to individual needs? The global texmf.cnf would have to be set up
to honor the local path first, i.e.,

TEXMF = {$HOMETEXMF,!!$TEXMFLOCAL,!!$TEXMFMAIN}

I don't know offhand if this will work (anybody else know?), but it seems
like it's worth a try.
Cheers, Rolf

----- Original Message -----
From: ALAN A DUNWELL <dunwell@jnov.colorado.edu>
To: <fptex@tug.org>
Sent: Wednesday, September 29, 1999 8:47 AM
Subject: Re: dvips output error revisited...


> Thanks Rolf. I can see where these will work for individual
> machines, I will probably end up with some form of this.
>
> I was not specific enough in my last post as to my environment. I
> have installed ftTeX onto an NT file server machine so that the
> 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.
>
> What I had hoped might be an option would be some environment var or
> some global setting in config.ps that would allow dvips to
> hand off to whatever is defined as the default windows printer.
> This is sort of what happens in UNIX when we just hand off to lpr
> and the system knows what that means. Of course fpTeX is all really
> happening in the DOS level, so maybe that can't work. I am having
> users run through WinEdit for the most part, so maybe some option
> there in the Menu Setup Options. For the time being I've just
> hardwired config.ps to go to a file by commenting out the "o" line.
>
> Thanks,
> Alan Dunwell
>
>
> > From:          "Rolf S. Arvidson" <arvidson@ocean.tamu.edu>
> > To:            <DUNWELL@jila.colorado.edu>
> > Cc:            <fptex@tug.org>
> > Subject:       Re: dvips output error revisited...
> > Date:          Tue, 28 Sep 1999 16:22:05 -0500
>
> > If the printer is postscript, edit the config.ps file to reflect the
> > printer's path
> > o \\pcname\printername
> >
> > If the printer is not a postscript printer but is the default local
windows
> > printer, then pipe through gs:
> > o |c:\gstools\gs5.50\gswin32c -dNOPAUSE -q -sDEVICE=mswinpr2 -
> >
> > In the case of networked non-postscript printers, one should be able to
> > point gs to it by substituting "-sOutputFile= " for -sDEVICE=..."
> > All these have worked for me (running NT sp5).
> > Hope this helps.
> > --Rolf
> >
> > ----- Original Message -----
> > From: ALAN A DUNWELL <dunwell@jnov.colorado.edu>
> > To: <fptex@tug.org>
> > Sent: Tuesday, September 28, 1999 4:39 PM
> > Subject: dvips output error revisited...
> >
> >
> > > In a previous post (attached below) Fabrice you indicate that you
> > > hoped to do something about the default output error from dvips
> > > because of the |lpr command in config.ps. Did this happen? Do you
> > > have any quick and dirty work arounds to get output to a networked
> > > printer other than just making a .ps file and then printing from gv?
> > >
> > > Any hints appreciated,
> > > Alan Dunwell
> > >
> > >
> > > ----------- previous post ----------
> > > > From:          "Fabrice Popineau" <fabrice.popineau@supelec.fr>
> > > > To:            "Eli Zaretskii" <eliz@is.elta.co.il>,
> > > >                "Erling D. Andersen" <e.d.andersen@its.tudelft.nl>
> > > > Cc:            <fptex@tug.org>
> > > > Subject:       Re: dvips
> > > > Date:          Tue, 15 Jun 1999 09:38:04 +0200
> > >
> > > > > Fabrice, I thought that you did some changes to add such a
feature,
> > no?
> > > >
> > > > Not yet finished (hopefully, as soon as the students will leave
there
> > :-) )
> > > > I could have opened PRN: and write there, but I intended to do
something
> > > > more realistic under windows, and print directly to the default
printer,
> > > > piping
> > > > through gs if this printer is not postscript.
> > > >
> > > > Fabrice
> > > >
> > > >
> > >
> > > !--------------------------------------------------------
> > > !Reply to:
> > > ! Alan A. Dunwell, JILA Software Manager,
> > > ! JILA - CB440, Univ. of Colorado, Boulder,Co. 80309
> > > ! E-Mail - dunwell@jila.colorado.edu
> > > ! Voice  - (303) 492-5308   FAX - (303) 492-5235
> > > !--------------------------------------------------------
> > >
> >
> >
>
> !--------------------------------------------------------
> !Reply to:
> ! Alan A. Dunwell, JILA Software Manager,
> ! JILA - CB440, Univ. of Colorado, Boulder,Co. 80309
> ! E-Mail - dunwell@jila.colorado.edu
> ! Voice  - (303) 492-5308   FAX - (303) 492-5235
> !--------------------------------------------------------
>