Specific to Pandoc, it seems.

It is a behavior in Pandoc that is not specified in MarkDown dialects 
generally, or supported in other software currently.  

It is implemented in Pandoc as an extension, meaning that the behavior can 
be toggled.  Actually, I am confused about which extensions are enabled or 
disabled by default, but this one appears to work on a basic invocation of 
Pandoc.

While it seems ideally suited to your requirements as long as you are using 
Pandoc, you do ask the right question, and should be aware that results 
might be unpredictable with editors, readers, or other MarkDown 
converters.  

Yet, it seems to be one of the more useful features not part of common 
MarkDown dialects.

In a pinch you can use Pandoc to convert from a document using these 
extensions into a common dialect of MarkDown, suitable for ingestion by 
another converter.


On Wednesday, September 18, 2019 at 10:46:51 AM UTC-4, Craig Parker wrote:
>
>
> Is this something specific to pandoc, github markdown, or what? 
>
>

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/c18b9c78-2262-4f63-b995-0698dc795132%40googlegroups.com.