Michael Droettboom <mdroe-PfB3aINIHTeHXe+LvDLADg@...1455...> writes:
For some reason, my matplotlib isn't able to print percent signs ('%')
properly:
It's a known bug, fixed since 1.1.1.
PDF renderer draws strange artifacts on '%' character in 1.1.1 · Issue #1211 · matplotlib/matplotlib · GitHub
Indeed. Luckily 1.2.0~rc2-1 is in experimental, and upgrading fixed the
problem. Thanks!
Now the only question that remains is: why doesn't github find this
issue when I search for '%'?
BTW: If you're running the Debian package, how come the version is a
release candidate? (1.1.1rc2)
Not sure what you mean, why shouldn't it?
Best,
-Nikolaus
···
--
»Time flies like an arrow, fruit flies like a Banana.«
PGP fingerprint: 5B93 61F8 4EA2 E279 ABF6 02CF A9AD B7F8 AE4E 425C
Michael Droettboom <mdroe-PfB3aINIHTeHXe+LvDLADg@...1455...> writes:
For some reason, my matplotlib isn't able to print percent signs ('%')
properly:
It's a known bug, fixed since 1.1.1.
PDF renderer draws strange artifacts on '%' character in 1.1.1 · Issue #1211 · matplotlib/matplotlib · GitHub
Indeed. Luckily 1.2.0~rc2-1 is in experimental, and upgrading fixed the
problem. Thanks!
Now the only question that remains is: why doesn't github find this
issue when I search for '%'?
Indeed - we should file a bug with github. I was able to find it because I knew the bug had to do with ttconv -- but there's no reason a user should have to know that.
BTW: If you're running the Debian package, how come the version is a
release candidate? (1.1.1rc2)
Not sure what you mean, why shouldn't it?
I had just forgotten that Debian went with a release candidate -- ideally it would have been a final release, but the schedule didn't work out that way.
Mike
···
On 10/10/2012 09:45 AM, Nikolaus Rath wrote: