On Wednesday 27 February 2008 12:21:18 pm Jochen Voss wrote:
> Hi Darren,
>
> On Wed, Feb 27, 2008 at 11:33:00AM -0500, Darren Dale wrote:
> > Thanks for the images, I see what you are saying.
> >
> > However, when I run your broken.py script I dont see any problems. The ps
> > and eps look like the png output.
>
> Hmmm, this is strange. I remember that things worked a bit earlier on
> my powerbook. Maybe it works on MacOSX (matplotlib installed via
> fink) and does not work on Debian (matplotlib installed from source)?
>
> > This is with mpl-0.91.2, I have the distiller
> > turned off and usetex is false. Have you changed any rc settings that
> > might have effected your output?
>
> I don't think I have changed rc settings outside the script: I deleted
> the ~/.matplotlib/ directory and had it recreated. I do not have an
> /etc/matplotlibrc file. Is there another place where leftover files
> could cause spurious settings to apply?
>
> I have the line
>
> rc('text', usetex=True)
>
> in the script, though. Surprise: if I comment out this line, both
> out.eps and out.ps suddenly look ok!!! Does usetex force this
> distilling stuff to kick in? What external dependencies does this
> use?
usetex has to use a distiller, either ghostscript or xpdf (xpdf is a bad name
for it, it requires ps2pdf and pdftops, the latter is now supplied by
poppler). The reason is that latex with the PSFrag package generates ps and
eps files that cannot be embedded in another postscript file. So we pass it
through a distiller. Trouble like you are seeing is almost always solved by
upgrading your ghostscript. I am using gpl ghostscript-8.61.
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Matplotlib-users mailing list
Matplotlib-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-users
