Jae-Joon Lee wrote:
> John,
>
> Would you do me a favor and open a ticket for this? So that other
> developers can take a look in the future.
Have done:
https://sourceforge.net/tracker/?func=detail&aid=2931430&group_id=80706&atid=560720
--
John,
Would you do me a favor and open a ticket for this? So that other
developers can take a look in the future.
http://sourceforge.net/tracker/?atid=560720&group_id=80706&func=browse
Please specify the options you're using, e.g., distiller, usetex,
ghostscript version, etc.
Regards,
-JJ
On
Jae-Joon Lee wrote:
> I'm afraid that there is not much I can help anymore.
>
> Just in case, does the same error occur when my patch is not applied?
>
> Is it an error or just a warning? If it is an error, can you post a
> full traceback? I just want to know what step causes that.
>
> Also, a
I'm afraid that there is not much I can help anymore.
Just in case, does the same error occur when my patch is not applied?
Is it an error or just a warning? If it is an error, can you post a
full traceback? I just want to know what step causes that.
Also, are you using the usetex mode? See if t
Jae-Joon Lee wrote:
> When you check out the svn, please try to apply the patch attached.
>
> patch -p1 < ps_distiller.patch
>
> I hope this solves your problem.
>
Thanks again for quick response. I've got the svn version and applied
the patch. Now I get this error (with ps.usedistiller : xp
When you check out the svn, please try to apply the patch attached.
patch -p1 < ps_distiller.patch
I hope this solves your problem.
Regards,
-JJ
On Mon, Jan 11, 2010 at 7:25 PM, Jae-Joon Lee wrote:
> On Mon, Jan 11, 2010 at 6:49 PM, John Reid
> wrote:
>> Thanks for help so far. Any more id
On Mon, Jan 11, 2010 at 6:49 PM, John Reid wrote:
> Thanks for help so far. Any more ideas? I'll try the svn if it is just a
> case of checking it out and compiling.
>
Please try.
I don't think the current svn version will make any difference. But,
at least I can send you a patch that I think fi
Jae-Joon Lee wrote:
> My guess is that somehow the output format of bbox device in the
> recent ghostscript has changed.
>
> What kind of output do you get when you run
>
>> gs -dBATCH -dNOPAUSE -sDEVICE=bbox test.eps
>
> in your shell (replace "test.eps" with any eps file you have)
>
> I get
>
My guess is that somehow the output format of bbox device in the
recent ghostscript has changed.
What kind of output do you get when you run
> gs -dBATCH -dNOPAUSE -sDEVICE=bbox test.eps
in your shell (replace "test.eps" with any eps file you have)
I get
GPL Ghostscript 8.61 (2007-11-21)
Copyr
Thanks for looking at this. I upgraded to 99.1.1 (although the tar file
was named 99.1.2) and I got the same error message. When I played with
the ps.usedistiller option I found it only doesn't work when I set
ps.usedistiller to xpdf. With False or ghostscript it works ok but gives
me output wi
You code works okay with the current svn.
See if changing the distiller option makes any difference
("ps.usedistiller" in the rc file).
The best would be for you to upgrade to the recent release of
matplotlib if possible.
Regards,
-JJ
On Mon, Jan 11, 2010 at 8:35 AM, John Reid wrote:
> Hi,
>
Hi,
I'm using matplotlib 0.98.5.2 on Ubuntu with Ghostscript 8.70. The
following code produces the following error. Can anyone verify whether
this a problem with my installation or with matplotlib?
import pylab as P
P.figure()
width=.4
x1 = [-0.4, 0.6, 1.6, 2.6, 3.6, 4.6, 5.6]
y1 = [1.0,
12 matches
Mail list logo
