OK, I've got it. Previously, I checked the quality of the output image
by two means: by visual inspection in gv and by checking the size of the
output eps images.
I was puzzled by the different sizes of the images at magnification 1.
Also, convert produces much larger eps files.
When the size
In fact, the dpi option does change the resulting PS file, but the
quality is still very poor - see the example
http://www.ucl.cas.cz/~petr/matplotlib-test.tgz
pd
On Fri, 2007-08-24 at 20:03, Jouni K. Seppänen wrote:
I just tried with current svn, and the following script produces two
Petr Danecek [EMAIL PROTECTED] writes:
On Fri, 2007-08-24 at 20:03, Jouni K. Seppänen wrote:
savefig('foo10.ps', dpi=10)
savefig('foo100.ps', dpi=100)
In fact, the dpi option does change the resulting PS file, but the
quality is still very poor - see the example
Petr Danecek wrote:
Hi,
I'd like to open a high-quality image (600dpi) in matplotlib, add some
plots and save it as a postscript file.
It seems that whatever I do, the input image gets scaled down
:-(
I'm sorry I don't know enough about MPL's handling of images to help, but...
Looking in
On 8/24/07, Christopher Barker [EMAIL PROTECTED] wrote:
This may not be what it seems. The native coordinate system for
PostScript is in points, which are 1/72 if an inch, so it's common to
force that as a dpi. Postscript supports fractional (is it floating
point or fixed -- I'm not sure)
John Hunter [EMAIL PROTECTED] writes:
On 8/24/07, Christopher Barker [EMAIL PROTECTED] wrote:
This may not be what it seems. The native coordinate system for
PostScript is in points, which are 1/72 if an inch, so it's common to
force that as a dpi. [...]
Yes, this is exactly right and the
