The new mathtext with an underlying TeX-like box model is passing all
unit tests for all backends. I'm now at a point where I'd like to merge
this back into the trunk, but I'd like some feedback as to how to best
deal with the backward-incompatible change wrt font changes.
(This was discussed in an earlier thread, but I don't believe a
conclusion was reached, so I'm summarizing again here.) In the existing
mathtext implementation, font style changes affect the following group.
For example, in $\cal{R} x$, only the R will be in calligraphic face.
In TeX, however, font style markers stay in effect until the next font
style marker or the end of the enclosing group. Therefore, the same
example would be rendered with both the R and the x in calligraphic
face. The new mathtext adds LaTeX-style font macros (\mathcal, \mathrm
etc.) that behave as the old mathtext ones. So the example expression
could be re-written $\mathcal{R} x$. It's difficult to trap the old
case and correct for it, since both are still valid.
Becoming more TeX-like is a good thing, but does breaking existing
matplotlib plots warrant some additional care here? Should this be
merged into trunk, or onto some other branch where we're going to be
breaking a lot of things. It is probably feasible to have a
"compatibility" mode for this, but is that (in this particular case)
worth the extra maintenance burden?
Cheers,
Mike
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
