public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Gustavo Costa <gusbemacbe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Will markdown_github be removed from future versions of pandoc?
Date: Tue, 27 Sep 2022 21:01:35 -0700 (PDT)	[thread overview]
Message-ID: <5f04deb1-8f16-4bf8-90e9-b0f7ceffd269n@googlegroups.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1271 bytes --]



Hello everybody!

I want to always use markdown_github because it works for everything, 
including beautified and linted HTML code. It supports many and many 
extensions that gfm doesn’t support, like grid_tables and startrum.

I know you would recommend to use markdown_mmd, but it is bad for the 
beautified and linted HTM code. I find the unlinted HTM code ugly. It also 
is bad for Markdown image syntax, with or without a backslash, with enabled 
extension implicit_figures.

Yes, I heard about markdown_phpextra, it almost worked for everything, but 
it doesn’t support the fenced code with backticks, it supports only fenced 
code with tildes. It doesn’t support the Markdown image syntax, with or 
without a backslash, with enabled extension implicit_figures.

Thank you for your attention, help and understanding!
​

-- 
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/5f04deb1-8f16-4bf8-90e9-b0f7ceffd269n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 5518 bytes --]

                 reply	other threads:[~2022-09-28  4:01 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=5f04deb1-8f16-4bf8-90e9-b0f7ceffd269n@googlegroups.com \
    --to=gusbemacbe-re5jqeeqqe8avxtiumwx3w@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).