dvips

[Bob Howlett]

Most people here, on the department's unix system, get a ps
file when they use dvips -- I think it depends on whether
or not they have an environment variable of some kind set.
So I don't accept that sending the ps output to a file is
inconsistent with the best dvips traditions.
In any event, fptex is a windows system; so if the output is
to be sent to lpr then the system should incorporate an lpr
that will actually print the output instead of giving an
error message. (Myself, I much prefer a ps file to be created,
since I always want to look at the output with gsview before
printing it.)

Bob Howlett

-------------------

Jody Klymak wrote:
> 
> Dear Erling,
> 
> I disagree - dvips originated as a UNIX program, and it should continue
> to behave like one.  That means the behaviour of the defaults and
> options should stay the same as its UNIX brother as much as possible.
> That way people can take scripts back and forth across the machines as
> painlessly as possible.
> 
> Imagine your chagrin if you were used to typing on your win32 "dvips
> boo" and getting a file 600 page "boo.ps" which you then took to a UNIX
> machine, typed "dvips boo" and instead got 600 pages spit out on your
> printer.
> 
> Cheers,  Jody
> 
> > -----Original Message-----
> > From: owner-fptex@tug.org [mailto:owner-fptex@tug.org]On Behalf Of
> > Erling D. Andersen
> > Sent: Monday, June 14, 1999 12:35 PM
> > To: fptex@tug.org
> > Subject: dvips
> >
> >
> > Hi,
> >
> > In the new fptex installation dvips sends output to ->lpr. To
> > me it seems
> > a bit strange default on a PC based system. I think sending to
> > a file would be more reasonable.
> >
> > Erling
> >