John Hunter wrote: > On 8/30/07, Michael Droettboom <[EMAIL PROTECTED]> wrote: > >>> ...but if we need to go into agg anyway, why not use Agg's font handling >>> capabilities directly? >> Perhaps historical reasons. I wonder if they're still relevant. > > Yes, that's it. agg did not have font support when the agg backend > was added. It was always easier to continue adding and extending what > we had (ft2font) than to port over to agg's support.
I think that's probably still the case -- while we could do rendering with agg at this point, agg doesn't provide a very complete interface to the font's metrics. We'd still have to maintain *some* sort of C code for that anyway. IMHO, I don't see any compelling reason to reduce the code in ft2font in favor of agg at this point. Cheers, Mike ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ Matplotlib-devel mailing list Matplotlib-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
