From: Connor Patrick Jackson <cpjackson-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Markdown -> CommonMark extensions tracker
Date: Wed, 21 Jul 2021 08:26:19 -0700 (PDT) [thread overview]
Message-ID: <11d4e07a-6151-42f1-8a2f-56ce4bb2ae1bn@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 2363 bytes --]
As pandoc moves toward commonmark_x as the default processor, I was
thinking it might be nice to have a table of extensions and their current
status with each processor, so users can see the status of the extensions
they need, easing the decision of whether/when they can switch to using
commonmark_x. Perhaps this could live on the GitHub wiki?
I was imagining each extension could have one of several possible values,
for markdown and for commonmark:
- enabled by default
- disabled by default
- required by the spec (cannot be disabled)
- Not allowed by the spec (cannot be enabled)
- Not available (under development)
and any other statuses that might be informative. I have put together a
framework table from the result of pandoc --list-extensions, but that only
lets me see whether they are disabled or enabled by default, or
whether they do not appear as extensions (which could be for any of the
latter three reasons). Rough vision:
-----------------------------------------------------------------------------------
commonmark
markdown
--------------------------------------- ---------------------
---------------------
**abbreviations** NA disabled by
default
**all_symbols_escapable** NA enabled by
default
**angle_brackets_escapable** NA disabled by
default
**ascii_identifiers** disabled by default disabled by
default
**attributes** enabled by default NA
**auto_identifiers** NA enabled by
default
Would this be useful, and if so, could others more knowledgable than I help
fill in the NAs with the other three possible values? I can post the
framework table onto the Wiki if others will then help fill it in.
Connor
--
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/11d4e07a-6151-42f1-8a2f-56ce4bb2ae1bn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4324 bytes --]
next reply other threads:[~2021-07-21 15:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-21 15:26 Connor Patrick Jackson [this message]
[not found] ` <11d4e07a-6151-42f1-8a2f-56ce4bb2ae1bn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-21 17:17 ` John MacFarlane
[not found] ` <m2a6mf4mdz.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-07-21 17:41 ` Connor Patrick Jackson
[not found] ` <ec4a5de6-77a4-4a48-86cc-e3d2610f5257n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-21 18:00 ` BPJ
[not found] ` <CADAJKhA3VdyosoGi+C_AjgK2hZLM+56ju8sHvd9yzMYqb=40QQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-07-21 18:09 ` Connor Patrick Jackson
2021-07-21 18:52 ` John MacFarlane
[not found] ` <yh480ktukn5wj8.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-07-22 1:01 ` Connor Patrick Jackson
[not found] ` <abf704be-12e2-4952-98a1-4ca4660db027n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-07-22 18:43 ` John MacFarlane
[not found] ` <yh480kbl6u42bq.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-09-04 15:23 ` Connor Patrick Jackson
[not found] ` <97ef942c-42de-413f-aacc-18792d3c9c6fn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-09-04 17:01 ` John MacFarlane
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=11d4e07a-6151-42f1-8a2f-56ce4bb2ae1bn@googlegroups.com \
--to=cpjackson-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).