[gs-devel] Tips for making ps2pdf available (under windows)

Izzy Isabel.Sargent at ordnancesurvey.co.uk
Fri Apr 10 10:20:52 PDT 2009


Thank you both, your comments gave me the confidence to get this sorted.

Firstly, I was put off by the statement in ps2pdf.htm: "In order to use
ps2pdf, the pdfwrite device must be included in the makefile when
Ghostscript was compiled; see the documentation on building Ghostscript for
details: this is currently the case on all platforms, in Ghostscript as we
distribute it. " which to me said that the only way of using ps2pdf (as a
batch file) was to build the application myself. 
	
For other flummoxed like me, I got this working by simply adding the gs bin
and lib directories to my path.  Previously, I'd done this temporarily using
'set PATH ...' but had still encountered an error when I tried to use
ps2pdf. Ray's confidence encouraged me to try this again and I now realise
was to do with spaces in windows directory names - pah!

I also found calling the pdfwrite device for gswin32c as Alex suggested:


Alex Cherepanov wrote:
> 
> gswin32c -dEPSCrop -sDEVICE=pdfwrite -o OUTPUT.PDF -c .setpdfwrite -f
> IMPUT.EPS
> 

worked excellently - setting the papersize was useful as some of the eps
files were not encapsulated as I would have desired.

Finally, a simple bit of python meant that within a few seconds I have
converted nearly 600 files.

Your hints on compilers should also help me with the next matter I need to
tackle... thank you!
-- 
View this message in context: http://www.nabble.com/Tips-for-making-ps2pdf-available-%28under-windows%29-tp22913089p22991470.html
Sent from the Ghostscript - Dev mailing list archive at Nabble.com.



More information about the gs-devel mailing list