## MathJax best practices for publishers

### Publishers that use MathML

MathJax understands MathML (indeed, MathML is MathJax's "internal" language). Publishers that already provide Euclid with MathML-coded metadata (in titles and abstracts) should not do anything differently. Your submissions will work as they are, just for more browsers. If you provide TeX source for reference list processing, then see the next section.

### Publishers that use TeX

MathJax understands a very large (and growing) subset of TeX, including AMS math and symbols. What MathJax does not understand (unless instructed) are user macros. So, for example, if an abstract contains $\rtwo$ as a shortcut for $\mathbf{R}^2$, then MathJax will not be able to render this expression. Publishers should use only standard LaTeX and AMSLaTeX macros in titles, abstracts, and reference lists. If you are not sure whether a certain expression will work with MathJax, contact us, and we will be able to tell you. Pay careful attention to article titles in reference lists, which can sometimes contain non-standard macros defined in the original BibTeX database files.

Also, since < and > are reserved characters in HTML and XML, one cannot use them for inequalities in math expressions. Instead, you should use the predefined TeX commands (built into MathJax) \gt for "greater than" and \lt for "less than."

Please note: Only TeX code in math mode will be processed, which means that $\bf N$ will be rendered as "N", but {\bf N} will not be processed at all and be rendered as "{\bf N}". If you want bold characters in your non-math abstract text, use the HTML code <b>12</b> to give "12".

Likewise, since TeX coding of accented characters outside of math mode will not be processed by MathJax, the name H\"older will appear as "H\"older", not "Hölder". Please use UTF-8 encoding or character entities (ö or &#x00F6;, in this case) for special characters.

### Euclid back content

Every effort will be made to "teach" MathJax about non-standard macros used in journal back content metadata. If you notice TeX code that is not rendering properly, contact us and we'll address it. Be aware that you might have to make modifications to the metadata.