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 lic
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
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 stable release).
>
> And you are
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 late
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 te
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
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
> obta
Carl Worth wrote:
> 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 t
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 histor
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 a
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 y
On Thu, 5 Jul 2007 13:26:22 -0500, "John Hunter" wrote:
> On 7/5/07, Carl Worth <[EMAIL PROTECTED]> wrote:
> > I don't know if there's anything special about the PostScript output
> > you're currently producing that wouldn't make it acceptable to use
> > cairo's PostScript output directly. But even
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 Ca
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
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
John Hunter wrote:
> 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
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.
U
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 an
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).
>
Than
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
On Thu, 05 Jul 2007 07:37:21 -1000, Eric Firing wrote:
> > 2. Convert the Truetype font to a Type 3 font (which is basically a set
> > of standard Postscript commands). There is a small C application
> > (http://www.this.net/~frank/ttconv.tar.gz) that converts TTF to Type 3
> > that looks to work
Will this (whichever method is chosen) work for PDF too?
Just wondering,
-Chris
--
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R(206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main re
Eric Firing wrote:
> Michael Droettboom wrote:
>> 1. Subset the Truetype font into another Truetype font and embed it
>> as we do now. This could theoretically be done with fonttools/ttx.
>> Writing out .ttf files looks to be rather complex, and there's a lot
>> of griping about the format its
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 conve
Michael Droettboom wrote:
> [I've been discussing this off-list with John Hunter, and I thought I'd
> summarize that conversation in case anyone else on this list has any
> thoughts or suggestions.]
>
> I've started working on the problem of reducing Postscript output file
> sizes by saving out
26 matches
Mail list logo
