Mathjax-v2.2-feature-discussion.md

@@ -106,5 +106,6 @@ Other topics
     * fred: Perhaps we could do the conversion Content MathML => Presentation MathML in the MathML input Jax processor (maybe making this optional) and not necessarily using the XSLT (not sure whether it is available to all browsers). 
     * peter: sure, I don't know where it fits best. From what I can google, all our supported browsers do xslt 1.0 but I have no idea how performance is anyway. 
     * fred: if they all support XSLT 1.0 then I think it would be very easy to add a configuration option in the MathML input Jax to call David Carlisle's stylesheet before processing them. Given that content MathML is not a top priority, that would just give a convenient option for authors that need it on their pages without impacting other users. And we don't have to worry too much about performance or imperfect content to presentation mapping, I guess. The idea would be to modify the DOM to have: <math><semantics>[presentation MathML ouput]<annotation-xml encoding="application/mathml-content+xml">[content MathML input]</annotation-xml></semantics></math> (no need to create a new semantics if it already exists).
-* Encourage use of <mrow>+<mo> construction instead of <mfenced>. See https://groups.google.com/forum/#!topic/mathjax-dev/GIvpWSNJrgA/discussion
+* Encourage use of &lt;mrow&gt;+&lt;mo&gt; construction instead of &lt;mfenced&gt;. See https://groups.google.com/forum/#!topic/mathjax-dev/GIvpWSNJrgA/discussion
     * needs to be fleshed out after dev meeting: focus is on native MathML support. Switching will make NativeMML on Opera worse, but Opera is not on our target list and nativeMML is not suggested on Opera anyway.
+    * We can also do this conversion in the NativeMML output for all browsers but Opera.
\ No newline at end of file