On Monday 01 October 2007 01:25:11 pm Tom Johnson wrote:
> On 9/27/07, Tom Johnson <tjhnson@...> wrote:
> > On 9/27/07, Darren Dale <dd55@...> wrote:
> > > On Thursday 27 September 2007 01:28:46 am Tom Johnson wrote:
> > > > Actually, the problem exists as early as the dvi file.
> > >
> > > The dvi looks fine here, and so does my pdf.
> > Hmm...I have:
> > ESP Ghostscript 8.15.04 (2007-03-14)
> > pdftops version 3.01 (coming from libpoppler1 version 0.5.4-0ubuntu8)
> > pdfeTeX 3.141592-1.21a-2.2 (tetex-3.0.dfsg.3-4)
> After doing some upgrades, I think I have more information about this
> issue. In summary, the problem is fixed, but I think there are still
> some questions as to the cause of the earlier problem. Currently, I
> GPL Ghostscript 8.61
> pdftops version 3.02
> pdfTeX 3.141592-1.40.3-2.2
> If I use the scripts in the original email, then there is no problem.
> That is, with facecolor='white', the resulting eps, dvi, ps, and pdf
> all have a figure with a white facecolor.
> Strangely, if I use an EPS from before my upgrades, the problem still
> exists. This has the fortunate effect that I do not need to
> regenerate all my images. In this situation, as described previously,
> the eps file looks fine using gv (has a white facecolor). However,
> the resulting dvi, ps, and pdf all have a figure with no
> facecolor---and this behavior not consistent with edgecolor.
> I am using the same version of matplotlib (before and after the
> upgrade)... SVN Revision 3709...and python 2.5 as well. Since the
> problem still occurs with particular EPS files....the problem
> definitely must be with the EPS.
> I don't know how the EPS file is constructed in matplotlib...does it
> make use of external programs like gs (and thus, points the reason
> back at EPS Ghostscript)? In case someone is interested in searching
> for the source of the problem, I have attached:
It was a problem introduced by one of the external dependencies during the
distillation process, that's why your old eps files still look the way they
do. It was not a problem with the viewer. It looks like the problem was fixed
in a recent ghostscript release, and I don't think the matplotlib mailing
lists are an appropriate forum for discussing problems with ghostscript.