public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Connor Patrick Jackson
	<cpjackson-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Markdown -> CommonMark extensions tracker
Date: Wed, 21 Jul 2021 11:52:59 -0700	[thread overview]
Message-ID: <yh480ktukn5wj8.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <ec4a5de6-77a4-4a48-86cc-e3d2610f5257n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Note: at this point, we're talking about commonmark extensions
provided by pandoc. None of this is going into the commonmark
spec, which currently just focuses on the core. (Maybe at
some point.)

abbreviations - maybe?

all_symbols_escapable - this is already in core commonmark, so not an extension

angle_brackets_escapable - already in core commonmark

auto_identifiers - we have gfm_auto_identifiers, no plans to
support the old auto_identifiers, since I think it's best to
standardize on one system

backtick_code_blocks - part of core commonmark

blank_before_blockquote - incompatible with core commonmark,
won't be implemented as an extension

blank_before_header -  incompatible with core commonmark,
won't be implemented as an extension

citations - I plan to support this but it's not an easy one to implement

compact_definition_lists - I'd prefer not to support this, for
sake of standardization - it's here for legacy reasons

escaped_line_breaks - part of core commonmark

example_lists - plan to support

fenced_code_attributes - this is provided as part of the
attributes extension, don't plan to implement separately

fenced_code_blocks - part of core commonmark

four_space_rule - don't plan to implement, incompatible with core
commonmark

grid_tables - plan to implement, probably

gutenberg - this only really affects plain output

header_attributes - provided by attributes extension, don't plan
to implement separately

ignore_line_breaks - might make sense to implement, but this
would be a bit tricky to do as a commonmark-hs extension; we
might need a few changes to the core commonmark processor to
enable this.  I'd be curious how many people use it.

inline_code_attributes - provided by attributes, don't plan to
implement separately

inline_notes - will probably implement as an extension

intraword_underscores - part of core commonmark, won't be an extension

latex_macros - not sure, maybe

line_blocks - plan to implement as extensions

link_attributes - provided by attributes extension

lists_without_preceding_blankline - part of core commonmark,
don't plan to implement

literate_haskell - maybe

markdown_attribute - probably not, because commonmark has a
different way of doing this and I'd like to keep it simple

markdown_in_html_blocks - no, because commonmark has a different
way of doing this

mmd_header_identifiers - maybe

mmd_link_attributes - maybe

mmd_title_block - maybe

multiline_tables - plan to implement

native_divs - probably not; I'd prefer to just support the fenced divs

native_spans - ditto, bracketed_spans

old_dashes - probably not, a legacy feature

pandoc_title_block - probably?

shortcut_reference_links - part of core commonmark

simple_tables - plan to support

space_in_atx_header - part of core commonmark, won't be an extension

spaced_reference_links - incompatible with core spec, don't plan
to support

startnum - part of core commonmark

table_captions - plan to support but maybe as part of table extensions

tex_math_double_backslash - not sure; might support

tex_math_single_backslash - incompat with core commonmark
escaping, probably not


  parent reply	other threads:[~2021-07-21 18:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-21 15:26 Connor Patrick Jackson
     [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 [this message]
     [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=yh480ktukn5wj8.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=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).