John Hunter writes: > Just to summarize then to make sure we're all on the same page > > * family lists will be moved to matplotlibrc and so will be user > configurable. This list can be overriden on a per-script basis > using the method in > http://matplotlib.sourceforge.net/faq.html#CUSTOM > > * text.fontname and the other text.font* attributes in the config > file and in matplotlib.__init__ are deprecated and should warn. > The warning should point to the appropriate web page for > instruction. You should use family lists rather than fontnames for > general/global preferences. However, Text.set_fontname is > preserved and moves the named font to the head of the list > appropriate list using some kind of dictionary that maps names to > families. > > This should satisfy Perry's concern about specifying a specific > font for use in a specific place. If the font is in your system > path and the finder algorithm is working properly this font will be > used. There is one significant caveat to this, which is that it > may be difficult or impossible to specify a complete dictionary > from names to families. Or, are you reasonably certain you can > build this on the fly Paul using font properties from FT2Font? > > * font.family must be one of sans-serif, serif, monospace, cursive or > fantasy. Anything else should raise > > * Paul, I think when you do the documentation, some discussion of > what the different families look like, what the classic examples of > each are Eg "Courier is an example of Monospace", and a text > screenshot along the lines of examples/alignment_test.py showing an > example from each of the families would be very helpful to users. > All of this could go into htdocs/fonts.html.template and/or > tutorial.html.template. > All the above sounds good to me. Perry