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
> a
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 reports that are very similar to yours -- but on the other
hand,
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:
Execu
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
>>
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.
Aha! You may be
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 just built my own ESP Ghostscript 815.04 and am abl
Oh dear. It works for me with my fairly old version of GNU ghostscript
(7.07) and a couple different Postscript HP laser printers I tried. The
file position where the error occurs at least seems plausible -- it's
where the first text is shown.
I'll have to look into this further. More data p
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
ER
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 rcset
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 renam
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
> rc
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.
Cheers,
Mike
John Hunter wrote:
> On 7/9/07, Darren D
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 comm
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 ttconv
An initial revision of TTF font subsetting has been committed to SVN.
It seems to work for all tests run by backend_driver.py (with the
exception quiver_demo, which didn't seem to work without my changes either).
Some key results:
fonts_demo_kq_ps.py: 633518 -> 45232
mathtext_demo.py: 366268 -
15 matches
Mail list logo
