On Tuesday 10 July 2007 07:51:25 am Michael Droettboom wrote:
I was able to duplicate your bug on my Ubuntu Feisty box.
There is a bug against evince filed here:
http://bugzilla.gnome.org/show_bug.cgi?id=303365
It appears that evince always renders an entire page at a time. There
are some
On Monday 09 July 2007 11:25:57 am Michael Droettboom wrote:
An initial revision of TTF font subsetting has been committed to SVN.
Thank you for doing this.
[...]
ttconv supports outputting a Type 42 font (without subsetting), so
matplotlib's old Type 42 output has been replaced with
On 7/9/07, Darren Dale [EMAIL PROTECTED] wrote:
Could you be more specific about how to test your changes? I dont see anything
in matplotlibrc.template, or in rcsetup.py, concerning the valid settings of
ps.fonttype. (rc settings should be validated, have a default value, and have
a commented
On 7/9/07, Michael Droettboom [EMAIL PROTECTED] wrote:
Sorry about that. I didn't notice the SVN login error the first time.
It should be in SVN now.
The default is to output Type 3 fonts (i.e. the new way).
Darren: you mean rcdefaults.py, not rcsetup.py, right? I can't find an
Michael Droettboom wrote:
Sorry about that. I didn't notice the SVN login error the first time.
It should be in SVN now.
The default is to output Type 3 fonts (i.e. the new way).
Darren: you mean rcdefaults.py, not rcsetup.py, right? I can't find an
rcsetup.py.
Mike,
I renamed
Eric Firing wrote:
Michael Droettboom wrote:
Sorry about that. I didn't notice the SVN login error the first
time. It should be in SVN now.
The default is to output Type 3 fonts (i.e. the new way).
Darren: you mean rcdefaults.py, not rcsetup.py, right? I can't find
an rcsetup.py.
Michael Droettboom wrote:
[...]
All should be in SVN.
Mike,
Now it compiles and runs all the demos, and displays OK at normal
resolution; but when I try to show it with gv or evince at 400%, gs crashes:
[EMAIL PROTECTED]:~/programs/py/mpl/matplotlib_units/examples$ evince
simple_plot_ps.ps
Eric Firing wrote:
Michael Droettboom wrote:
Even if my Postscript is to spec, it's not terribly useful if it
crashes a very popular tool ;)
I'm curious -- does the file fail if you set ps.fonttype: 42 in
your matplotlibrc? That would at least rule out anything non-font in
the file.
I
Michael Droettboom wrote:
Here's simple_plot.ps generated with the old PS backend.
Crash! Again, with 400% magnification. So now you really are off the hook.
[EMAIL PROTECTED]:~/programs/py/mpl/tests$ evince simple_plot_ps.ps
ERROR: /unknownerror in --%op_show_continue--
Operand stack:
