Carl Worth wrote:
don't think it is supported in cairo. So I am not sure where these
rasters are coming from, unless cairo is converting all text to
rasters.
Definitely not converting all text to raster, (unless someone's using
an ancient version of cairo).
I don't know the root
On 7/6/07, Michael Droettboom [EMAIL PROTECTED] wrote:
I don't know the root cause, but FYI I'm definitely getting rasterized
text with the Cairo backend for mathtext_demo.py. (I'm using
cairo-1.4.10, which I believe is the latest stable release).
And you are pretty sure it is all the text,
On Friday 06 July 2007 08:35:31 am John Hunter wrote:
On 7/6/07, Michael Droettboom [EMAIL PROTECTED] wrote:
I don't know the root cause, but FYI I'm definitely getting rasterized
text with the Cairo backend for mathtext_demo.py. (I'm using
cairo-1.4.10, which I believe is the latest
On 7/5/07, Carl Worth [EMAIL PROTECTED] wrote:
Thanks, John, for sharing this essay. Please allow me to respond to a
few points:
Hey Carl -- thanks for the response. You have definitely made me
reconsider some of my arguments, though my conclusion mostly remains
intact. At the end of the
John Hunter wrote:
What about simple_demo.py -- do you get rasters there too?
No. I get vectors there.
I noticed that using the backend GtkCairo seems to use backend_ps.py
for Postscript output. Using backend Cairo uses cairo. Maybe
probably explains the difference between Darren and my
On Fri, 6 Jul 2007 08:20:59 -0500, John Hunter wrote:
On 7/5/07, Carl Worth [EMAIL PROTECTED] wrote:
Hey Carl -- thanks for the response.
You're quite welcome. Thank you for receiving it as intended---as an
alternate viewpoint based on my experience.
I think LGPL is a perfectly good license
On 7/5/07, Eric Firing [EMAIL PROTECTED] wrote:
The plan is to make the choice of the existing or new behavior be an
option, with the default TBD.
Is there any reason *not* to do the subsetting?
There was some original confusion in a potential loss of quality in
truetype/type2 conversions,
On 7/5/07, Carl Worth [EMAIL PROTECTED] wrote:
You might take a look at what kind of PostScript and PDF output you
get from cairo right now, (since cairo has many different kinds of
font subsetting, (type3, type42 and others), and it's regularly being
tested on as many PostScript and PDF
Carl Worth wrote:
You might take a look at what kind of PostScript and PDF output you
get from cairo right now, (since cairo has many different kinds of
font subsetting, (type3, type42 and others), and it's regularly being
tested on as many PostScript and PDF viewers as possible).
Thanks
Michael Droettboom wrote:
Carl Worth wrote:
You might take a look at what kind of PostScript and PDF output you
get from cairo right now, (since cairo has many different kinds of
font subsetting, (type3, type42 and others), and it's regularly being
tested on as many PostScript and PDF
On 7/5/07, Michael Droettboom [EMAIL PROTECTED] wrote:
It may be worthwhile to look at Cairo's font subsetting code if it's
determined that the Python Postscript backend has other advantages. I'm
sure people who've been here longer than I have can better speak to
those pros and cons.
On 7/5/07, Michael Droettboom [EMAIL PROTECTED] wrote:
Do you agree that it is still an open question whether it's better to
spend time improving the matplotib PS backend, or to fix (if possible)
the issues with matplotlib's Cairo integration? It does ultimately come
down to a tradeoff: an
John Hunter wrote:
On 7/5/07, Michael Droettboom [EMAIL PROTECTED] wrote:
Do you agree that it is still an open question whether it's better to
spend time improving the matplotib PS backend, or to fix (if possible)
the issues with matplotlib's Cairo integration? It does ultimately come
On Thursday 05 July 2007 03:46:13 pm John Hunter wrote:
On 7/5/07, Michael Droettboom [EMAIL PROTECTED] wrote:
Do you agree that it is still an open question whether it's better to
spend time improving the matplotib PS backend, or to fix (if possible)
the issues with matplotlib's Cairo
On Thu, 5 Jul 2007 14:46:13 -0500, John Hunter wrote:
The postscript backend as it stands is in good shape, and is full
featured (Darren can tell you how much work he has put into supporting
and enhancing the latex support). The last major issue with it is the
font size issue, and with your
Carl,
I have made a few changes in svn to facilitate testing cairo with
backend_driver (and to fix a bug that turned up), and I will do a bit
more on this later today or tomorrow. The result of a quick pass
through the backend_driver test with png output is quite encouraging,
though. There
On Thu, 05 Jul 2007 13:22:11 -1000, Eric Firing wrote:
I have made a few changes in svn to facilitate testing cairo with
backend_driver (and to fix a bug that turned up), and I will do a bit
more on this later today or tomorrow.
Cool. I've started downloading all the matplotlib source history
Carl Worth wrote:
On Thu, 05 Jul 2007 13:22:11 -1000, Eric Firing wrote:
[...]
My suggestion would be to make it default to .png if no additional
information is provided, and then to also add some sort of pseudo
backends so that the other cairo-supported file types could easily be
obtained
18 matches
Mail list logo
