A slight glitch though. I think John has changed the AFMPATH
> environmental variable to MATPLOTLIBDATA (which is a more
> appropriate name) so people installing matplotlib in
> non-default places will have to set it instead.
ps backend is setup to use both, the idea that you may have some AFM
files independent of matplotlib, and some that ship with matplotlib.
The MATPLOTLIBDATA is indeed for people installing in nonstandard
places. But if AFMPATH is not working for you, I need to know since
this is a bug.
Thanks!
John Hunter
John Hunter wrote:
"LUK" == LUK ShunTim <shuntim.luk@...34...> writes:
> A slight glitch though. I think John has changed the AFMPATH
> environmental variable to MATPLOTLIBDATA (which is a more
> appropriate name) so people installing matplotlib in
> non-default places will have to set it instead.
ps backend is setup to use both, the idea that you may have some AFM
files independent of matplotlib, and some that ship with matplotlib.
The MATPLOTLIBDATA is indeed for people installing in nonstandard
places. But if AFMPATH is not working for you, I need to know since
this is a bug.
Thanks!
John Hunter
I think that's an oversight of mine. I had AFMPATH set to point to the directory which holds the afm, xpm files etc before I upgrade. After upgrading I got the error described above and I found out that I have to set MATPLOTLIBDATA. I did not realize that AFMPATH is *still* used.
I have tex installed so I hope I can use quite a lot more fonts now. Is the path to the .afm files all that is needed? Do I have to set anything else, for example where to find the pfa/pfb files? I found that matplotlib spits out warnings like
** (log_demo.py:1264): WARNING **: Couldn't load font "Times 9.599609375"
falling back to "Sans 9.599609375"
Regards,
ST