You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The list of variants registered is woefully lacking but the registration mechanism allow formalize which mimetype variant parameter should be used to identify a flavor of markdown.
i.e. text/markdown;variant=MYST or text/markdown;variant=GFM
Even having an open draft RFC (probably for years) might allow us to establish and register the MYST parameter at least somewhat formally.
It is also worth noting that pandoc additionally provides for more parameters, that can specify which extensions/directives are loaded.
The text was updated successfully, but these errors were encountered:
Thanks for opening your first issue here! Engagement like this is essential for open source projects! 🤗
If you haven't done so already, check out EBP's Code of Conduct. Also, please try to follow the issue template as it helps other community members to contribute more effectively.
If your issue is a feature request, others may react to it, to raise its prominence (see Feature Voting).
IANA accepted an official registration for the
text/markdown
mimetype here: https://www.iana.org/assignments/media-types/text/markdownSection 6.1 of the RFC specified a IANA based registry for markdown variants that is established here: https://www.iana.org/assignments/markdown-variants/markdown-variants.xhtml
The list of variants registered is woefully lacking but the registration mechanism allow formalize which mimetype variant parameter should be used to identify a flavor of markdown.
i.e.
text/markdown;variant=MYST
ortext/markdown;variant=GFM
Even having an open draft RFC (probably for years) might allow us to establish and register the MYST parameter at least somewhat formally.
It is also worth noting that
pandoc
additionally provides for more parameters, that can specify which extensions/directives are loaded.The text was updated successfully, but these errors were encountered: