Re: Bug #1503114

[Ethan A M. <merritt@u.washington.edu>]

On Tuesday 20 June 2006 07:21 pm, Timoth=E9e Lecomte wrote:
> >  =20
> With the current code, 99% of chance of getting the error "Can't find=20
> PostScript prologue file" out-of-the-box when using the postscript=20
> terminal on Windows=20

Is that because there is not an appropriate README file?
How about if we change the message to:

"Please copy your PostScript prolog files to <somewhere Windowish>"

After all, it doesn't work "out of the box" on unix either.=20
You still have to set up your font paths and add  environmental
variables to your locally customized initialization files.

> and other non-Unix platforms.=20

Do you mean because of the trailing '/' on the directory name?
Other than that I don't see much difference.  But yes, I should
add conditional code for VMS that adds ':' rather than '/'.
Does windows or os2 need it changed to '\'?

> Two alternatives :
> 1- Move them back to the source file (the GNUPLOT_PS_DIR environment=20
> variable can be conserved for flexibility)

Huh?  What does the environmental variable do, if the prolog
is in the driver?

>     * others : include them in the source file at compile time

I think you are over-generalizing. Why assume that it is an=20
issue for all non-unix systems?  I'll report back on VMS, but
I don't see why there should be a problem.  And I doubt we=20
support anything less unix-like than VMS.

=2D-=20
Ethan A Merritt
Biomolecular Structure Center
University of Washington, Seattle 98195-7742