On 13 Jan 2011, at 5:50 AM, Michael Droettboom wrote:
> Can you provide a simple LaTeX document that illustrates the problem
> with psfrag? This is still compliant Postscript, AFAICT.
It is not a postscript compliance issue, but rather a requirement of
the psfrag package which relys on searc
The change in behavior was to fix this bug:
http://sourceforge.net/tracker/?func=detail&aid=3062773&group_id=80706&atid=560720
It seems it may be impossible to produce Postscript that works across
all fonts and all readers at the same time.
Can you provide a simple LaTeX document that illustr
On Tue, Jan 11, 2011 at 8:45 AM, Lebostein wrote:
>
> I have compared the new and old output. For example the "0.0" in a diagram:
>
> old eps (1.0.0):
>
> 35.223 19.934 m
> 0 0.141 rmoveto
> (0.0) show
> [1 2] 0 setdash
> 0.502 setgray
>
> new eps (1.0.1):
>
> 35.222810 19.933563 translate
> 0.00
I have compared the new and old output. For example the "0.0" in a diagram:
old eps (1.0.0):
35.223 19.934 m
0 0.141 rmoveto
(0.0) show
[1 2] 0 setdash
0.502 setgray
new eps (1.0.1):
35.222810 19.933563 translate
0.00 rotate
0.00 0.140625 m /zero glyphshow
6.362305 0.140625 m /period g
Hi,
the eps output of matplotlib 1.0.1 don't work with the LaTeX macro PSfrag
(http://en.wikipedia.org/wiki/PSfrag). In the release notes
(RELEASE_NOTES-1.0.1.txt) I can not find any changes to the eps output. What
have you done?
--
View this message in context:
http://old.nabble.com/Problem-w
