Andrew,
I believe this bug was recently discussed on matplotlib-devel and is
likely related to recent changes in the font manager cache.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01531.html
I believe it's being looked into, but I haven't seen a resolution
(unless I missed it).
Cheers,
Michael Droettboom wrote:
Andrew,
I believe this bug was recently discussed on matplotlib-devel and is
likely related to recent changes in the font manager cache.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01531.html
I believe it's being looked into, but I haven't seen a
Andrew Jaffe wrote:
Michael Droettboom wrote:
Andrew,
I believe this bug was recently discussed on matplotlib-devel and is
likely related to recent changes in the font manager cache.
http://www.mail-archive.com/[EMAIL PROTECTED]/msg01531.html
I believe it's being looked into, but I
Eric Firing [EMAIL PROTECTED] writes:
My guess is that this problem has been lurking all along, but was only
triggered when I changed font_manager to look for *all* system fonts
instead of only truetype,
Another data point: a recent svn version of matplotlib segfaults on my
OS X system,
Jouni K. Seppänen [EMAIL PROTECTED] writes:
Another data point: a recent svn version of matplotlib segfaults on my
OS X system, and ktrace suggests it occurs while it is reading
CharcoalCY.dfont.
Looks like a freetype bug: the following code segfaults when linked
against libfreetype.6.3.10
Eric Firing [EMAIL PROTECTED] writes:
I think that the problem is occurring in the last line. This remains to
be verified. It looks like *.afm files are being found, but when
createFontDict tries to parse them it doesn't find what it expects.
The cause of the problem is a combination of
Andrew Jaffe [EMAIL PROTECTED] writes:
I admit I don't understand the problems or the speccific code involved,
but I *think* it may be that the OSX-specific code isn't restricted to
afm files. Hence I wonder if the following is a fix:
-for f in OSXInstalledFonts():
+
