-
Notifications
You must be signed in to change notification settings - Fork 76
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
Using math mode within mbox mismatches $
#313
Comments
As you suspected this is an edge case that will be rather tricky to fix. In case you cannot change the old file you can use a functionality added a few weeks ago (not yet in a release version):
in the new file you can suppress the markup inside the enclosed region. This means, the resulting output should be at least compilable but changes in the equation will not be shown. |
I assigned "Low" priority to a fix as it would be relatively complicated for what I feel is a niche case, and it can be avoided by also using the other options for marking inline maths. (I did not test but if you change both inner and outer symbols you might get into trouble again. |
Thanks! Agreed that this is a niche case and can reasonably be considered low priority. The I haven't tested it with the development version, but I should mention that applying It's may be a low priority for me, but if I manage to come up with a minimal example that reproduces the |
I was referring to a new way of marking a block where markup should be suppressed, which has only been introduced recently, which uses special comments ( |
If I have a line of text that uses math mode via pairs of
$$
, and an\mbox
within that block, which contains its own$$
math mode block within the\mbox
, then latexdiff's parsing seems to match the opening$
outside of the\mbox
with the opening$
within the\mbox
.I'm not sure if there's an easy workaround, but if there is then I didn't manage to find it (I ended up removing the entire
\mbox
and using\text
to make the diff work for my immediate use case, but that's kind of a tedious process).What I ran:
What I expected:
What I got:
This leads to the error:
The text was updated successfully, but these errors were encountered: