Bug#792259: ffms2: pandoc does not render Markdown properly

Dmitry Shachnev mitya57 at ubuntu.com
Mon Jul 13 19:40:30 UTC 2015

Hi Jonas,

2015-07-13 15:15 GMT+03:00 Jonas Smedegaard <dr at jones.dk>:
>> GitHub-style (```) code blocks are not standardized, so Pandoc has the
>> full rights to not support it.
>> Python-Markdown supports it via a non-default extension.
> Seems indeed it is standardized:
> http://spec.commonmark.org/0.20/#fenced-code-blocks

CommonMark ≠ Markdown (i.e. John Gruber even asked them to change the name).

> ...so perhaps (if interested in keep using pandoc) simply a matter of
> choosing the correct flavor of Markdown parsing?
> Even if it wasn't standardized, pandoc aims to cover a rich variety of
> Markdown parsing, including several non-standard but popular extensions
> - so I would expect upstream to be interested in fixing also this one if
> needed.  Please do consider filing a bug against pandoc, even if you do
> not want to use pandoc yourself in the future.

Apparently pandoc has an extension to support such code blocks [1], so
no bug needed.

[1]: http://pandoc.org/demo/example19/Extension-fenced_005fcode_005fattributes.html

Anyway, because of #792287 the switch to Python-Markdown is better anyway.

Sebastian, thanks for taking care of this so quickly!

Dmitry Shachnev

More information about the pkg-multimedia-maintainers mailing list