Skip to content
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_mmd source option doesn't properly handle fenced code blocks #3637

Closed
jonBoone opened this issue May 4, 2017 · 2 comments
Closed

Comments

@jonBoone
Copy link

jonBoone commented May 4, 2017

$ pandoc --version
pandoc 1.19.2.1
Compiled with pandoc-types 1.17.0.5, texmath 0.9, skylighting 0.1.1.4


~~~~~json
{
  "test" : "testing"
}
~~~~~

when converting to pdf via latex using the following command:
pandoc -o test.pdf --read=markdown --latex-engine=xelatex test.md
everything works as expected

however, when using this command:
pandoc -o test.pdf --read=markdown_mmd --latex-engine=xelatex test.md
the output is rendered incorrectly

@jgm jgm closed this as completed in 1668998 May 4, 2017
@jgm
Copy link
Owner

jgm commented May 4, 2017 via email

@ickc
Copy link
Contributor

ickc commented Oct 27, 2017

Just realized this change when reading the changelog.

This is strange, because I remembered that MultiMarkdown has long (don't know how long though) been able to parse the

```yaml
testing
```

style codeblock with optional language attribute.

And then I recalled I once checked all relevant pandoc markdown extensions is enabled in the markdown_mmd variant. But apparently I missed this.

To @jonBoone, markdown variants like markdown_mmd in pandoc is not perfect, and you may call it an "emulation mode". So be aware of this if you use it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants