> For the complete documentation index, see [llms.txt](https://docs.openreview.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openreview.net/v1/reference/openreview-tex/common-issues-with-latex-code-display.md).

# Common Issues with LaTeX Code Display

If your TeX notation is not rendering the way you expect, work through the following:

* **The macro may not be supported by MathJax.** If this is the case then macro will appear as plain red text in with the rendered TeX. MathJax implements only math-mode macros, so text-mode macros and environments such as `\emph` or `\begin{enumerate}...\end{enumerate}` will not render. See [Math-mode macros only](/v1/reference/openreview-tex/openreview-tex-support.md#math-mode-macros-only).
* **The command may be restricted.** MathJax runs with its `safe` extension enabled, so commands that set arbitrary links, styles, font sizes, or element classes and ids are filtered out even when MathJax implements them. See [Some commands are restricted](/v1/reference/openreview-tex/openreview-tex-support.md#some-commands-are-restricted).
* **The backslashes may not be escaped.** If the field has Markdown enabled, but not all the backslashes in the TeX notation were escaped, Markdown strips them before the TeX is parsed. This can lead to some layout problems, such as all the elements of a matrix appearing in 1 row instead of many. Similarly, underscores should also be escaped with a backslash when they are used at the beginning or the end of a word: '\\\_'. See [TeX in a Markdown-enabled field](/v1/reference/openreview-tex/openreview-tex-support.md#tex-in-a-markdown-enabled-field).
* **The delimiters may be missing.** Text is only rendered as TeX when it sits inside `$...$` for inline math or `$$...$$` for displayed math. See [Delimiters](/v1/reference/openreview-tex/openreview-tex-support.md#delimiters).
* **An HTML tag may be interfering.** Do not mix HTML tags with TeX: text that begins with `<` is treated as an HTML block, and the whole field can lose its Markdown formatting. Where a `<` or `>` has to appear inside the math delimiters, add spaces around it so it is not read as an open tag. See [TeX inside an HTML document](/v1/reference/openreview-tex/openreview-tex-support.md#tex-inside-an-html-document).

For the full picture of how OpenReview's TeX support differs from other systems, see [OpenReview TeX support](/v1/reference/openreview-tex/openreview-tex-support.md).


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openreview.net/v1/reference/openreview-tex/common-issues-with-latex-code-display.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `build a script that syncs our docs to a CMS` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.