matplotlib-devel Mailing List for matplotlib

Hello,
the file examples/matplotlib_icon.py lacks the magic python
line at the beginning. This can be corrected with the following
patch:
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
diff -u -r1.5 matplotlib_icon.py
--- matplotlib_icon.py 10 Aug 2004 15:04:27 -0000 1.5
+++ matplotlib_icon.py 19 Oct 2004 17:48:33 -0000
@@ -1,3 +1,4 @@
+#!/usr/bin/env python
 """
 make the matplotlib svg minimization icon
 """
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
I hope this helps,
Jochen
--=20
http://seehuhn.de/

Hello John,
On Tue, Oct 19, 2004 at 10:00:48AM -0500, John Hunter wrote:
> >>>>> "Jochen" =3D=3D Jochen Voss <vo...@se...> writes:
>=20
> Jochen> None, I looked at the generated PS file out of curiosity
> Jochen> and noticed that it does not follow the DSC conventions
> Jochen> very well. As this is just shuffling around comments it
> Jochen> will probably not affect many applications.
>=20
> Are there other noncompliant things in the matplotlib ps output that
> you are aware of, other than those you already fixed?
I think the horrible ones are fixed by now.
Minor issues:
The DSC spec states (at page 18): "If there is a section in
the document that corresponds to a particular comment, that comment
*must* be used to identify that section of the document."
=46rom reading this I would guess that all the "/something { ... } bind
def" statements and the included fonts should be inside a
 %%BeginPrologue
 %%EndPrologue
block. But I didn't check this properly.
Then page 19 "strongly suggests" to use some headers like
"%%CreationDate" and "%%Title".
Page 70 of the SDC specification states that "%%BeginFont" and
"%%EndFont" are outdated and should be replaced by "%%BeginResource"
and "%%EndResource" statements.
All the best,
Jochen
--=20
http://seehuhn.de/

>>>>> "Jochen" == Jochen Voss <vo...@se...> writes:
 Jochen> None, I looked at the generated PS file out of curiosity
 Jochen> and noticed that it does not follow the DSC conventions
 Jochen> very well. As this is just shuffling around comments it
 Jochen> will probably not affect many applications.
Are there other noncompliant things in the matplotlib ps output that
you are aware of, other than those you already fixed?
JDH

Hello John,
On Tue, Oct 19, 2004 at 09:37:37AM -0500, John Hunter wrote:
> For my information, what ps viewers/printers were giving you trouble.
None, I looked at the generated PS file out of curiosity and
noticed that it does not follow the DSC conventions very well.
As this is just shuffling around comments it will probably
not affect many applications.
> Finally, by changing the version information to
>=20
> pstype =3D 'PS-Adobe-3.0 EPSF-3.0'
>=20
> will we break devices that only support PS level II?
I do not think so. It is only a change to comments and not to the
actual PostScript code. It will only affect applications which try to
parse the DSC comments and do not understand DSC version 3.
I changed this because the document at
 http://partners.adobe.com/asn/developer/pdfs/tn/5001.DSC_Spec.pdf
which defines DSC version 3 is dated "25 September 1992", which seems
quite old to me. If you feel more comfortable using DSC version 2 we
could either try to reverse engineer the version 2 specification using
the "Changes Since Earlier Versions" chapter in above document or try
to find a DSC 2 specification somewhere.
All the best,
Jochen
--=20
http://seehuhn.de/

I submitted the site request we discussed a couple of days ago to move
the users_guide and htdocs into the matplotlib CVS root. This makes
'cvs co matplotlib' much faster. I suggest you get fresh checkouts.
The three modules are
 cvs co matplotlib
 cvs co htdocs
 cvs co users_guide
I had asked them to rename htdocs and users_guide to mpl_htdocs and
mpl_users_guide but they overlooked this and I can live with it.
On a mildly related note, I just noticed that when I submitted the
site-request to have the matplotlib python tree moved into a lib
directory, all version history was lost. Damned cvs.
JDH

>>>>> "Jochen" == Jochen Voss <vo...@se...> writes:
 Jochen> Hello,
 Jochen> On Mon, Oct 18, 2004 at 10:19:33PM +0100, Jochen Voss wrote:
 >> -%%BeginProlog +%%%%BeginProlog /inch {72 mul} def
 >> %%%%EndProlog """
 Jochen> does anybody know: is the "inch" thing actually used
 Jochen> anywhere? Maybe it should just be removed.
No it is apparently not used anywhere. It was a def that appeared in
my postscript book and several examples I looked at, so I threw it in
for good measure. I just applied you PS patch, removed this, and
checked the changes into CVS.
For my information, what ps viewers/printers were giving you trouble.
We've occasionally had reports of some viewers having trouble with
matplotlib output and I would like to gather some anecdotal
information.
Finally, by changing the version information to
 pstype = 'PS-Adobe-3.0 EPSF-3.0'
will we break devices that only support PS level II?
JDH

Hello,
On Mon, Oct 18, 2004 at 10:19:33PM +0100, Jochen Voss wrote:
> -%%BeginProlog
> +%%%%BeginProlog
> /inch {72 mul} def
> %%%%EndProlog
> """
does anybody know: is the "inch" thing actually used anywhere?
Maybe it should just be removed.
All the best,
Jochen
--=20
http://seehuhn.de/