Hi All-
FYI, I am seeing the same problem on intel OSX 10.4.10
Andrew
Eric Firing wrote:
> Rob, Mike,
>
> What this implies to me is that either there is a problem with the code
> that is generating afmdict (and I did not change that code, I just
> caused it to be invoked when the fontMan
Rob, Mike,
What this implies to me is that either there is a problem with the code
that is generating afmdict (and I did not change that code, I just
caused it to be invoked when the fontManager instance is created.), or
there is a problem with some .afm files on Rob's machine.
I really don't
On Aug 14, 2007, at 1:55 PM, Eric Firing wrote:
> rcParams['pdf.use14corefonts']
Indeed, reversing this value fixes the problem.
My value had been set to False.
pdf.use14corefonts : True
in the mplrc file works with the latest revision.
-r
Rob Hetland, Associate Professor
Dept.
Mike, Rob,
One of the changes I made was to cause the afmdict to be generated
automatically at the start rather than on demand. The problem you are
having seems related to afm fonts, so I suspect this is it.
What is your rcParams['pdf.use14corefonts'] setting? Please try
reversing it, and se
> What are you setting in matplotlibrc (or in your plot?)
>
> Also, if you delete the font cache (which is now
> ~/.matplotlib/fontManager.cache), does that help? (Might be a useful
> data point -- not suggesting it as a solution.)
Well, I've been trying out the Arev fonts, as you know, so I chan
Hmm... I'm not readily able to reproduce this here.
What are you setting in matplotlibrc (or in your plot?)
Also, if you delete the font cache (which is now
~/.matplotlib/fontManager.cache), does that help? (Might be a useful
data point -- not suggesting it as a solution.)
Cheers,
Mike
Rob
> Done and committed.
It seems a recent commit has severely broken my font loading. When I
start MPL now, I get an infinite stream of messages similar to:
Found an unknown keyword in AFM header (was )
Found an unknown keyword in AFM header (was !"%
#*3*9*:*<[EMAIL PROTECTED]@";;"C#C)*=>A&B879
Michael Droettboom wrote:
> My suspicion from looking at the code was that a great deal of time
was spent statting all the font files at start up. FontManager.__init__
goes through all the files in the cache to determine if they still exist
and refreshes the cache if it finds one missing. Your patc
Michael Droettboom wrote:
Just wanted to link up this thread with a question I posed on the cairo
mailing list.
http://lists.cairographics.org/archives/cairo/2007-August/011201.html
Cheers,
Mike
Eric Firing wrote:
Michael Droettboom wrote:
[...]
One middle ground I thought of since my first
Quick status update --
I've committed code to font_manager that will retrieve the list of all
installed fonts from fontconfig if available (using making a shell call
to fc-list). This will handle the cases where users want to use fonts
that have been installed in non-standard places or their d
Just wanted to link up this thread with a question I posed on the cairo
mailing list.
http://lists.cairographics.org/archives/cairo/2007-August/011201.html
Cheers,
Mike
Eric Firing wrote:
> Michael Droettboom wrote:
> [...]
>> One middle ground I thought of since my first message is to use
>>
Michael Droettboom wrote:
[...]
> All this raises a much larger question of whether we want to replace
> font_manager.py with something like fontconfig. There don't appear to
> be Python wrappers for it, but it would eliminate a number of issues
> with font_manager.py : a) it would look up fonts i
I just finished writing code to support scalable mathtext with the Cairo
backend. (The old version rendered the mathtext to bitmaps first).
Mostly straightforward, but I ran into one small snag. It *seems* that
pycairo requires that the fonts it uses are installed and accessible
through fontconf
13 matches
Mail list logo
