Re: [matplotlib-devel] pdf output

2007-09-11 Thread Paul Kienzle
On Tue, Sep 11, 2007 at 12:31:25PM -0400, Michael Droettboom wrote: > Did r3829 not work for you? (Or did you miss that in my earlier post?) > > I don't think anything related to Lengths has changed recently, and it > did work at one point... The current svn works --- I must have missed a build

Re: [matplotlib-devel] pdf output

2007-09-11 Thread william ratcliff
Has anyone worked with postscript files on windows? I don't know if this is related, but when I do a savefig('foo.ps',dpi=150) on plot generated by pcolormesh, I find that ghostview gives the error: " DSC Error at line 518: %%Page: 1 1 This %%Page: line occured in the trailer, which is not legal.

Re: [matplotlib-devel] pdf output

2007-09-11 Thread Jouni K . Seppänen
Paul Kienzle <[EMAIL PROTECTED]> writes: > I'm not sure yet how to fix the problem, but in the sample I sent > earlier if I change: > > 5 0 obj > << /Length 11 0 R >> > endobj > > to > > 5 0 obj > << /Length 1239 >> > endobj > > then both gv and acroread can process the file without error.

Re: [matplotlib-devel] pdf output

2007-09-11 Thread Jouni K . Seppänen
Michael Droettboom <[EMAIL PROTECTED]> writes: > There was a small typo in the recently added support for non-rectangular > clip paths. Fixed in r3829. > > (Jouni -- you may want to review this and verify that my change is > correct.) Yes, your change fixes a bug; thanks. Strangely enough, Appl

Re: [matplotlib-devel] pdf output

2007-09-11 Thread Michael Droettboom
Did r3829 not work for you? (Or did you miss that in my earlier post?) I don't think anything related to Lengths has changed recently, and it did work at one point... Cheers, Mike Paul Kienzle wrote: > On Tue, Sep 11, 2007 at 10:57:18AM -0400, Paul Kienzle wrote: >> I'm not sure yet how to fix

Re: [matplotlib-devel] pdf output

2007-09-11 Thread Paul Kienzle
On Tue, Sep 11, 2007 at 10:57:18AM -0400, Paul Kienzle wrote: > I'm not sure yet how to fix the problem, but in the sample I sent > earlier if I change: > > 5 0 obj > << /Length 11 0 R >> > endobj > > to > > 5 0 obj > << /Length 1239 >> > endobj > > then both gv and acroread can process

Re: [matplotlib-devel] pdf output

2007-09-11 Thread Paul Kienzle
I'm not sure yet how to fix the problem, but in the sample I sent earlier if I change: 5 0 obj << /Length 11 0 R >> endobj to 5 0 obj << /Length 1239 >> endobj then both gv and acroread can process the file without error. - Paul On Tue, Sep 11, 2007 at 08:49:05AM -0400, Michae

Re: [matplotlib-devel] pdf output

2007-09-11 Thread Michael Droettboom
This seems to be a cross platform bug and unrelated to fonts -- at least I am able to reproduce it on Linux. There was a small typo in the recently added support for non-rectangular clip paths. Fixed in r3829. (Jouni -- you may want to review this and verify that my change is correct.) Cheers

Re: [matplotlib-devel] pdf output

2007-09-10 Thread Michael Droettboom
Paul Kienzle wrote: > A further comment on the windows PDF problems. > > PDF output generated by matplotlib on Windows and on OS X is readable > in Preview.app on OS X but is not readable in Acrobat 8.1.0 or 7.0.5 > on Windows. > > Adobe 7.0.5 produces the message "There were too many argument

[matplotlib-devel] pdf output

2007-09-10 Thread Paul Kienzle
A further comment on the windows PDF problems. PDF output generated by matplotlib on Windows and on OS X is readable in Preview.app on OS X but is not readable in Acrobat 8.1.0 or 7.0.5 on Windows. Adobe 7.0.5 produces the message "There were too many arguments". At this point I have no idea