On Aug 22, 2013, at 10:28 PM, James Boyle wrote:
> I built MPL 1.3 from source, all seem to go OK but I ran into the problem of
> not finding libfreetype.6.dylib when importing.
>
> On the web, I found references to this problem for builds on OS X. The
> solutions refer to a file README.osx,
>
> > with/without third party X
> I'm not quite sure what you mean by with/without third party X. If you
> are referring to Tck/Tk:
>
I had an issue where MPL found the headers to freetype in /opt/local, but
library in /usr/X11. Hilarity ensues. I *think* /usr/X11 showed up when I
installed XQu
I built MPL 1.3 from source, all seem to go OK but I ran into the problem of
not finding libfreetype.6.dylib when importing.
On the web, I found references to this problem for builds on OS X. The
solutions refer to a file README.osx, which is not
present in the 1.3 distribution. The documentatio
Thanks for these tips. It looks like some programs (like illustrator, and
pdf2ps) are semi-smart about handling transparency when converting to ps.
Both have their quirks (illustrator seems to mess up the bounding box,
pdf2ps makes the text look worse/fuzzy).
Is this the recommended/best strategy?
Chris Beaumont :
>
> I have a semitransparent plot that I rather like:
...
> I'd like to publish something like this in a journal which requires
> EPS figures. Unfortunately, EPS doesn't support transparency.
>
> How hard would it be to coax matplotlib (or another tool) to convert
> this semi-tra
Hi,
I have a semitransparent plot that I rather like:
[image: Inline image 1]
I'd like to publish something like this in a journal which requires EPS
figures. Unfortunately, EPS doesn't support transparency.
How hard would it be to coax matplotlib (or another tool) to convert this
semi-transpare
