-
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
Markdown math rendering fails on multiple subscripts with curly brackets #1575
Comments
In the meantime, a workaround is to use trailing spaces after underscore symbols: |
Same issue, thanks for the workaround tho! |
In some cases also without curly brackets don't work. |
If the two subscripts are in two expressions but in the same line, render is broken as well.
will be rendered as "Range of $\mathbf{d}{ij}$ and $\mathbf{d}{ij} \cdot \Delta E$", but the workaround also work for this case "Range of |
To give more strange examples (but thanks a lot for the workaround), if I put a single expression it works, if I copy/paste it it fails:
Gives But
Gives $V^{a}{x} V^{a}{x}$ My bet is that github confuses it with emphasis (like in |
Also something similar happens with stars (I guess again because it thinks it's bold, so the same work around also works):
Gives
Gives $V^{} V^{}$ (bad!)
Gives |
I suspect this happens because So $$ |
For non-inline math, as an alternative, we can use
to replace I have more experiments at ImpleLee/c4w#1 . |
Inline math expression: Block math expression: Summation superscript is okay! Any workarounds? |
See e.g. ${\boldsymbol{x}1, ..., \boldsymbol{x}{i-1}, \boldsymbol{x}_{i+1}, ..., \boldsymbol{x}_n}$, which fails to render. |
@prasanth-ntu I was looking for the same and found a workaround on a github gist of some repo. One of the solutions described there was the following |
Today, we learned that GitHub's math rendering engine has some problem relating to subscripts/superscripts and curly brackets. See github/markup#1575. I have applied a workaround.
See Github bug here: github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... trying workaround from github/markup#1575
most SeQuant LaTeX output will not render correctly in GitHub markdown (seemingly due to GH issues, since MacDown renders it correctly) ... workaround from github/markup#1575 seems to work, but still need to break up overly long lines
Stale issue message |
Multiple subscripts in combination with curly brackets in LaTeX-based math expressions don't render as expected.
Single underscore with curly brackets works fine:$\mathbf{x}_{i,j} = \mathbf{y}$ .
\mathbf{x}_{i,j} = \mathbf{y}
renders asMultiple underscores without curly brackets work fine:$x_i = y_i$ .
x_i = y_i
renders asMultiple underscores with curly brackets fail:
\mathbf{x}_{i,j} = \mathbf{y}_{i,j}
renders as $\mathbf{x}{i,j} = \mathbf{y}{i,j}$.The text was updated successfully, but these errors were encountered: