From: "dave....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <dave.jarvis-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: GitHub now supports MermaidJS
Date: Fri, 14 Jan 2022 08:59:03 -0800 (PST) [thread overview]
Message-ID: <414214a7-8d59-49ca-aefd-e617130b6d7en@googlegroups.com> (raw)
In-Reply-To: <87tue6uxxy.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 1325 bytes --]
There's a bigger issue here that isn't about whether pandoc supports Kroki
diagrams.
We're seeing a small-scale repeat of Browser Wars regarding *de facto*
standards being ushered in without due process, which inevitably leads to
splintering and incompatibilities. That was my main point, sorry that I did
not state it directly.
To be clear, I think it'd be worthwhile to have a discussion about
introducing simple namespaces regarding diagrams, syntax highlighting, and
other possible ways to mark up diagrams. Without such a discussion, we'll
see proliferation of Markdown documents that are specific to different
implementations.
Or maybe having different flavours of Markdown is fine and any software
that wants to support Markdown can optionally support as many flavours is
people request: GitHub Markdown, GitLab Markdown, Pandoc Markdown,
KeenWrite Markdown, Markdown-Writer-FX Markdown, etc.
--
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/414214a7-8d59-49ca-aefd-e617130b6d7en%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 1706 bytes --]
prev parent reply other threads:[~2022-01-14 16:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-14 5:51 dave....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
[not found] ` <6a978c09-0b8d-4199-862a-0a0b78955a41n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-01-14 15:33 ` Albert Krewinkel
[not found] ` <87tue6uxxy.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-01-14 16:59 ` dave....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org [this message]
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=414214a7-8d59-49ca-aefd-e617130b6d7en@googlegroups.com \
--to=dave.jarvis-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).