Opinions on in-band variation signaling

Michel Fortin michel.fortin at michelf.ca
Tue Nov 11 19:49:04 EST 2014

Before this discussion derails on a syntax bikeshedding, I think I should highlight the important part:

Sean Leonard wrote:

> Do any implementers have experience with picking the type of Markdown based on some info at the top of the Markdown content?

To my knowledge, no one is doing that. But it'd be interesting to hear about it if someone is doing it.

As for this:

> By in-band, I mean a Markdown file with content like this:
> !pandoc
> % This is a Title
> % Sean Leonard
> % November 2014
> Blah blah *blah*.
> <<< (fortin’s suggestion)

I suggested privately to you that using `!pandoc` would be better as a header than `Content-Type: text/markdown; variant="pandoc"` if you wished people to actually write something in a file. But for me this is an enclosure format for Markdown (similar to how mp4 is an enclosure format for many codecs.). The actual Markdown content starts after the metadata header. 

Also, lines prefixed by a `%` are ugly, I would never suggest such a thing.

Michel Fortin
michel.fortin at michelf.ca

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 4154 bytes
Desc: not available
URL: <https://pairlist6.pair.net/pipermail/markdown-discuss/attachments/20141111/7c2ae133/attachment-0001.bin>

More information about the Markdown-Discuss mailing list