You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I expect "Wow![@legras_michel_2010]" to be parsed as the string "Wow!" followed by a normal citation, but pandoc 2.19.2 unexpectedly parses the citation as an AuthorInText in square brackets, and drops the exclamation point.
II was bitten by this again, so here's another case. From the lack of comment, I gather that it is considered reasonable to expect users to escape the exclamation point. If this is what should be done, then pandoc's Markdown output is wrong, because it fails to escape the exclamation point, causing it to be incorrectly parsed by pandoc.
The first pandoc invocation outputs Not so![]{.a}[i]{.b}: as in the case of a citation, the exclamation mark prevents the span from being recognized, and is not represented in the AST.
This is not exactly the same case as above, because it's a span that is parsed incorrectly rather than a citation, but I suspect it's the same issue with the Markdown parsing.
I expect "Wow![@legras_michel_2010]" to be parsed as the string "Wow!" followed by a normal citation, but pandoc 2.19.2 unexpectedly parses the citation as an AuthorInText in square brackets, and drops the exclamation point.
MWE:
Workaroud: If the exclamation mark is escaped, it works as expected.
This is pandoc 2.19.2 on macOS 12.5.1.
The text was updated successfully, but these errors were encountered: