matplotlib-devel Mailing List for matplotlib

in backend_agg lines 194 and 211, my application was passing unicodes
which were generating a CXX type error ( expecting a string ). I put
in a str( .. ) around the 's' arg in these 2 lines and everything
worked. 
i.e.
font.set_text( s, 0.0) 
changed to..
font.set_text( str( s ), 0.0) 
Just a note that unicodes cause a problem going through CXX when a
string is expected.
S
		
__________________________________ 
Do you Yahoo!? 
Check out the new Yahoo! Front Page. 
www.yahoo.com 
 

On Oct 28, 2004, at 4:58 PM, Robert Kern wrote:
> gary ruben wrote:
>> True, I didn't pay much attention to licencing. In light of it 
>> though, here
>> are a couple more links to a couple of gentlemen who may be worth
>> grovelling to should the need arise. No specific licencing is 
>> mentioned.
>> <http://mahi.ucsd.edu/parker/Software/>
>
> Actually, having seen this code and the gist code, I'd recommend 
> waiting for the gist-derived prototype.
>
> To muddy the waters a bit, the gist contouring algorithm looks to my 
> eye like Paul Bourke's CONREC algorithm, which may or may not be 
> patented.
>
Which gist contouring routine are you referring to? It appears to use 
two separate
implementations for different contour functions. We are using the code 
in gcntr.c.
If that is based on Bourke's routine, there shouldn't be a problem. 
None of the code
that uses it makes any reference to a patent; there appear to be a 
number of other
implementations, none of which appear to have been challenged. As far 
as patent
rights go, aren't they only good for 17 years? It was published in July 
1987
(though I suppose it may derive from when it was granted, not 
published).
Then there is copyright, but that doesn't guard against 
reimplementation so
long as code isn't copied (But I am not a lawy...).
Perry

>>>>> "Jochen" == Jochen Voss <vo...@se...> writes:
 Jochen> Hello John,
 Jochen> On Sun, Oct 31, 2004 at 10:54:04AM -0600, John Hunter wrote:
 >> One other PS quasi-bug you may want to be aware of is the way
 >> truetype fonts are embedded. The basic problem is that Paul
 >> couldn't find a way to access the individual glyph information
 >> so ended up having to embed the entire font. ...
 Jochen> Yes, I know about this. Let's see whether I can do
 Jochen> anything ...
 Jochen> It would also be nice if I could find a way to use the
 Jochen> printer's built-in fonts if the user wants to. This
 Jochen> should lead to really small PostScript files and really
 Jochen> high quality printed glyphs.
This is effectively what we were doing before we started embedding PS
fonts in matplotlib (0.61 I believe). So you can check out a CVS
version prior to that and take a look. It might be nice to support
this as an rc option, to use afm fonts. matplotlib has an afm parser
and ships with the standard afm files.
JDH

Hello John,
On Sun, Oct 31, 2004 at 10:54:04AM -0600, John Hunter wrote:
> One other PS quasi-bug you may want to be aware of is the way truetype
> fonts are embedded. The basic problem is that Paul couldn't find a
> way to access the individual glyph information so ended up having to
> embed the entire font. ...
Yes, I know about this. Let's see whether I can do anything ...
It would also be nice if I could find a way to use the printer's built-in
fonts if the user wants to. This should lead to really small PostScript
files and really high quality printed glyphs.
All the best,
Jochen
--=20
http://seehuhn.de/