From: David Nebauer <david@nebauer.id.au>
To: "Saša Janiška" <gour@atmarama.com>, ntg-context@ntg.nl
Subject: Re: Typesetting Markdown -- Part 2
Date: Fri, 31 May 2019 06:34:23 +0930 [thread overview]
Message-ID: <1559249839.4jpsjo1zt2.astroid@hezmana.none> (raw)
In-Reply-To: <87muj4dz45.fsf@atmarama.com>
https://github.com/Witiko/markdown is forked from https://github.com/jgm/lunamark. Github user "jgm" is John MacFarlane, the creator of pandoc, and pandoc itself is hosted on github under "jgm" as well: https://github.com/jgm/pandoc.
So, it seems a good bet that https://github.com/Witiko/markdown supports pandoc markdown.
Regards,
David.
Excerpts from Saša Janiška's message of May 30, 2019 7:48 pm:
> Hans Hagen <j.hagen@xs4all.nl> writes:
>
>> just test it and tell me what needs to be fixed / added
>
> I'm looking at https://github.com/Witiko/markdown and wondering which
> flavour of Markdown this package does support?
>
> By reading https://github.com/Witiko/markdown/issues/25 it could mean it
> could be Pandoc's one, but not sure?
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2019-05-30 21:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-29 21:54 Thangalin
2019-05-30 9:01 ` Hans Hagen
2019-05-30 10:18 ` Saša Janiška
2019-05-30 13:00 ` Hans Hagen
2019-05-31 1:28 ` Thangalin
2019-05-30 21:04 ` David Nebauer [this message]
2019-05-31 10:08 ` Saša Janiška
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=1559249839.4jpsjo1zt2.astroid@hezmana.none \
--to=david@nebauer.id.au \
--cc=gour@atmarama.com \
--cc=ntg-context@ntg.nl \
/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).