-
-
Notifications
You must be signed in to change notification settings - Fork 3.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LaTeX reader sometimes omits expressions containing square brackets [ #7512
Comments
The issue is shown a bit more clearly by:
|
I think what's happening here is that there's some code in the LaTeX reader's generic environment parser that skips over bracketed optional arguments that some environments have. This is obviously not wanted for the |
More workarounds:
|
I've modified the title because this isn't specific to HTML output or mathjax.
|
I would like to provide another example where this happens: In the following table the first entry in the second row (starts with \documentclass{article}
\begin{document}
\begin{table}[htb]
\centering
\begin{tabular}{|c|c|c|c|c|c|c|}
$W$ & $N_S$ & $L$ & $L$ & rel. err. & $L$ & rel. err. \\[0mm]
[$\mu$m] & [-] & [nH] & [nH] & [\%] & [nH] & [\%]\\
\hline\hline
1.00 & 32 & 0.2871 & 0.293 & 2.06 & 0.294 & 2.40 \\
2.00 & 32 & 0.2616 & 0.266 & 1.68 & 0.269 & 2.83 \\
\end{tabular}
\end{table}
\end{document} Note that the commands |
This is due to a pandoc bug, see jgm/pandoc#7512
In LaTeX, I have an expression
[d,\delta]=0
that I've placed in anequation*
environment. Upon converting to HTML, all I see is "=0" (see screenshot below), even if we were to get rid of MathJax. When placed in the\[ \]
environment, however, the expression converts correctly.The following is a working example:
resulting in
Interestingly, throwing a character
a[d,\delta]=0
in front of the opening square bracket in theequation*
environment solves the problem. Is this a bug or a feature that I should work around? Thanks!Version: I'm running pandoc version 2.14.1 on macOS Big Sur 11.4 on a Macbook Air (M1 2020).
The text was updated successfully, but these errors were encountered: