Re: [Matplotlib-users] very large postscript

[Darren D. <dd...@co...>]

Hi George,

On Tuesday 10 May 2005 6:37 pm, George Nurser wrote:
> I found that  my earlier problem in which matplotlib failed when making
> the font database (in loading pylab the first time)  came from a VT102
> font in my ~/Library/Fonts (on  OSx 10.3). Moving the font to a
> directory off the font path allowed successful loading.
>
> Next problem .... interactive running, using the TkAgg backend, from
> ipython -pylab draws pretty graphs -- very impressive -- and I can save
> to .png fine. But  saving to postscript gives a very large file, which
> moreover seems to be corrupted. Editing the .matplotlibrc file to use
> the PS backend directly & starting up ipython again gives the same very
> large, corrupt, PS file.
>
> matplotlib 0.80, ipython 0.6.13 + zlib, libpng, tk_inter, freetype
> 2.1.9, wx-2.6-mac-unicode, standard Apple Python 2.3, updated to
> MacPython, Numeric. OS X 10.3.9.

Would you send me, off list:=20
1) your .matplotlibrc file if you have customized it
2) the corrupt eps file
3) a script (not ipython output) that I generates the eps file

Also, if you set verbose.level : debug in your .matplotlibrc, does it tell =
you=20
anything pertinent?

Darren