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

[Jonas Smedegaard]

Quoting Dmitry Shachnev (2015-07-13 13:58:49)
> Hi Jonas,
> 
> 2015-07-13 14:56 GMT+03:00 Jonas Smedegaard <dr at jones.dk>:
>> Would be nice if this issue could (also, separately) be filed as a
>> bugreport against pandoc, documenting what specifically fails.
>>
>> I fully understand if libffms2-dev package maintainers choose to avoid
>> pandoc, but great if the bug revealed by its usage till now could
>> benefit the development of pandoc anyway :-)
>
> 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

...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.

 - Jonas

-- 
 * Jonas Smedegaard - idealist & Internet-arkitekt
 * Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-multimedia-maintainers/attachments/20150713/7e2f4752/attachment.sig>