Darren Dale <dd55@...143...> writes:
> Are you saying you will have replace it with auto as a papertype option
> as you suggested previously? Autosizing is a good idea if it can be made
> to work properly since it should negate the requirement to then compute
> a bounding box if you're including the resulting file in LaTeX. This is
> easy enough to do with eps using separate tools, but not for pdf's.
> Hopefully, a pdf backend will appear at some point and when it does mpl
> should support pdfs able to be included directly in pdflatex.
I am considering whether to have an "auto" key, which was suggested by Ted.
For sure, auto sizing will be done behind the scenes for eps files with the
usetex option (necessary to avoid clipping during postprocessing).
It will take a lot of work to support the usetex option with a pdf
backend. We use the PSFrags latex package to insert the text in our
figures, so an intermediate postscript file will be necessary for
the foreseeable future.
Replacing PSFrags is relatively easy - I posted code in January
to do so see:
Essentially, instead of inserting a marker in the postscript at the
position you want your text, and then using psfrag to replace it, you
put the text in the right position using a latex picture environment.
I didn't persue it as I came to the, possibly incorrect, conclusion
that _all_ "dvips -E" output contains postscript commands that are not
valid in eps.
If it were easy to write pdf rather than eps (and I'd been assuming it
would be complicated), then the approach I outlined would avoid the
necessity to use eps.
 Dvips -E is used to produce eps files
 The output contains statusdict and userdict, which I believe to be
not permitted in eps files. Perhaps this is not normally a problem -
otherwise what is the point of dvips -E?
On Friday 10 March 2006 3:14 am, Gary Ruben wrote: