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
If a footnote text includes right brackets - ] - the first one will match with the "footnote:[" markup of asciidoc, provoking an early interruption of the footnote, and pushing back the end of the footnote text in the main text.
Example, using test.docx, and running: pandoc -f docx -t asciidoc test.docx
produces the following output: textfootnote:[[…] footnote]
Escaping the inner right brackets should fix the issue (cf. asciidoctor/asciidoctor#2495 (comment)), producing this output instead: textfootnote:[[…\] footnote]
I used Pandoc v2.5 for the test, but it should still apply to the latest version from my understanding of the AsciiDoc writer code.
The text was updated successfully, but these errors were encountered:
<attrlist> is a list of attributes enclosed in square brackets.
] characters inside attribute lists must be escaped with a backslash.
Outside of macros, ] has no particular meaning and \] will be rendered as \]. So if that's what you mean by always, I'm afraid you won't get away with that.
If the attribute value contains the same quote character being used to enclose the value, escape the quote character in the value by prefixing it with a backslash (e.g., title="\"Dark Horse\" is a song by George Harrison").
If a footnote text includes right brackets - ] - the first one will match with the "footnote:[" markup of asciidoc, provoking an early interruption of the footnote, and pushing back the end of the footnote text in the main text.
Example, using test.docx, and running:
pandoc -f docx -t asciidoc test.docx
produces the following output:
textfootnote:[[…] footnote]
Escaping the inner right brackets should fix the issue (cf. asciidoctor/asciidoctor#2495 (comment)), producing this output instead:
textfootnote:[[…\] footnote]
I used Pandoc v2.5 for the test, but it should still apply to the latest version from my understanding of the AsciiDoc writer code.
The text was updated successfully, but these errors were encountered: