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
Thank you very much for pandoc; it is great, esp. for interconverting markup.
Today, I discovered a small issue when starting to play with asciidoc translation:
markdown:
“*their*” problem
is translated to asciidoc:
“_their_” problem
, which confuses asciidoc. (The second underscore is ignored, and emphasis continues.) It should be:
“__their__” problem
I assume that this would need an implementation of the following rule from the asciidoc docs (emphasis mine):
When you want to quote text (e.g., place emphasis) somewhere other than at the boundaries of a word, you need to double up the punctuation. For instance, to emphasis [sic!] the first letter of a word, you need to surround it in double asterisks:
Four score and seven years ago...
(This also means that closing quotation marks do not count as word boundaries. Given the many different styles of quotation marks, where nearly any sign can be opening or closing, depending on language and personal preference, this seems reasonable.)
It would be great if this could be fixed.
The text was updated successfully, but these errors were encountered:
Thank you very much for pandoc; it is great, esp. for interconverting markup.
Today, I discovered a small issue when starting to play with asciidoc translation:
markdown:
is translated to asciidoc:
, which confuses asciidoc. (The second underscore is ignored, and emphasis continues.) It should be:
I assume that this would need an implementation of the following rule from the asciidoc docs (emphasis mine):
(This also means that closing quotation marks do not count as word boundaries. Given the many different styles of quotation marks, where nearly any sign can be opening or closing, depending on language and personal preference, this seems reasonable.)
It would be great if this could be fixed.
The text was updated successfully, but these errors were encountered: