I have been having problems with postscript output from MPL
> on my various Macs that is just beyond the problem discussed
> in the tread here. But this seemed like the best place to
> bring it up. The basic problem is that Adobe products like
> Illustrator can't read MPL .eps output.
Are you sure you have set the font paths properly *and* flushed your
~/.matplotlib/ttffont.cache before regenerating your files. Use
--verbose-debug when creating your test EPS to make sure you are
getting bitstream fonts. If you still have trouble, post an errant
eps file somewhere and maybe someone can poke into it.
> I think that opening an EPS in Illustrator is the ultimate
> test of EPS format compliance, as those are the folks who
> made it.
I think this is debatable, as it is a closed source implementation of
an open document format specification. But I am willing to accept
that it is more likely that Illustrator is right than that mpl is
right.
> What can we do to make MPL output universally readable
> postscript?
Find the bug and fix it 
JDH
Well, the fonts are correct -- I checked in both the EPS source, and what Illustrator thinks the font is (after translation with pstopdf).
The definition of the fonts looks right in the EPS source (checked by comparing against a sample from illustrator).
If nobody else is having the same problem, typing pstopdf is really not a tremendous burden. I just thought I would raise this issue.
BTW, SVG files seem to do fine with fonts. However, it can take a very long time to save large files in MPL and import large files into Illustrator, which seems to want to translate them into some native format, and does so poorly.
If I ever figure out a better solution, I'll let you all know,
-Rob
···
On Sep 6, 2006, at 8:46 AM, John Hunter wrote:
> I have been having problems with postscript output from MPL
> on my various Macs that is just beyond the problem discussed
> in the tread here. But this seemed like the best place to
> bring it up. The basic problem is that Adobe products like
> Illustrator can't read MPL .eps output.
Are you sure you have set the font paths properly *and* flushed your
~/.matplotlib/ttffont.cache before regenerating your files. Use
--verbose-debug when creating your test EPS to make sure you are
getting bitstream fonts. If you still have trouble, post an errant
eps file somewhere and maybe someone can poke into it.
> I think that opening an EPS in Illustrator is the ultimate
> test of EPS format compliance, as those are the folks who
> made it.
I think this is debatable, as it is a closed source implementation of
an open document format specification. But I am willing to accept
that it is more likely that Illustrator is right than that mpl is
right.
> What can we do to make MPL output universally readable
> postscript?
Find the bug and fix it
JDH
----
Rob Hetland, Associate Professor
Dept. of Oceanography, Texas A&M University
http://pong.tamu.edu/~rob
phone: 979-458-0096, fax: 979-845-6331
One of these days, we'll have to figure out how to embed individual glyphs
rather than the entire font set.
···
On Wednesday 06 September 2006 11:04, Rob Hetland wrote:
Well, the fonts are correct -- I checked in both the EPS source, and
what Illustrator thinks the font is (after translation with pstopdf).
The definition of the fonts looks right in the EPS source (checked by
comparing against a sample from illustrator).
If nobody else is having the same problem, typing pstopdf is really
not a tremendous burden. I just thought I would raise this issue.
BTW, SVG files seem to do fine with fonts. However, it can take a
very long time to save large files in MPL and import large files into
Illustrator, which seems to want to translate them into some native
format, and does so poorly.
If I ever figure out a better solution, I'll let you all know,