John, I'd second the request for direct EPS. Sometimes
> you can get away without the bounding box, but not
> always. I've been using ps2epsi to convert my matplot .ps
> files into .eps files (.epsi is .eps with a preview, but
> I don't need the preview). It does a good job of finding
> bounding boxes. That's very important for running
> epstopdf on the images. That gives me pdf images so I can
> run pdflatex and generate a native PDF file from my
> LaTeX.
I'll see if I can get EPS into the ps backend in the near future. As
far as I know, it should just be a matter of adding a bounding box.
Note that you don't need to first convert your images to PDF to
generate PDF from LaTeX (though a PDF backend is on the TODO list). I
routinely generate PDF documents from LaTeX src with *.ps inputs as
follows
# With recent version of gv (7.x or later) do
> dvips -Pcmz -Pamz -G1 -Ppdf -o final3.ps final3.dvi
> ps2pdf final3.ps
This will generate high quality PDF w/o the blurry appearance in
acroread that you sometimes see with PDF generated by LaTeX.
Interesting. My experience is that pdflatex generates crisp and compact
pdf, though I usually use xpdf to view. I hadn't had similar luck with
ps2pdf but the -?mz may help.
-C
JH: > dvips -Pcmz -Pamz -G1 -Ppdf -o final3.ps final3.dvi
JH: > ps2pdf final3.ps
JH:This will generate high quality PDF w/o the blurry appearance in
JH:acroread that you sometimes see with PDF generated by LaTeX.
Either sourceforge is behind or the change didn't fix the xticklabels([]).
If you're around, can you email the file with the fix? In the meantime
I'll try to make sure I'm not using a mirror.
-C
···
--
Charles R. Twardy www.csse.monash.edu.au/~ctwardy
Monash University sarbayes.org
Computer Sci. & Software Eng.
+61(3) 9905 5823 (w) 5146 (fax)