From: Albert Krewinkel <albert+pandoc-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: GitHub now supports MermaidJS
Date: Fri, 14 Jan 2022 16:33:20 +0100 [thread overview]
Message-ID: <87tue6uxxy.fsf@zeitkraut.de> (raw)
In-Reply-To: <6a978c09-0b8d-4199-862a-0a0b78955a41n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
"dave....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org" <dave.jarvis-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:
> Some food for thought on simple code block namespaces.
>
> Re: https://github.com/github/markup/issues/533
>
> [...] It's encouraging to see that
> Mermaid diagrams are being supported in GitHub.
I'm not sure I understand: The linked issue was closed with the author
being referred to GitHub support. Is Mermaid actually supported on
GitHub?
> My feature request is to add support for Kroki and the diagram- prefix
> syntax. That is:
I believe that this is mostly out-of-scope for pandoc. But the
`diagram-` prefix could be implemented in the `diagram-generator` Lua
filter available here:
https://github.com/pandoc/lua-filters/tree/master/diagram-generator
A PR would be very welcome.
Thanks for bringing this up.
Cheers,
Albert
--
Albert Krewinkel
GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
next prev parent reply other threads:[~2022-01-14 15:33 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 [this message]
[not found] ` <87tue6uxxy.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2022-01-14 16:59 ` dave....-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
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=87tue6uxxy.fsf@zeitkraut.de \
--to=albert+pandoc-9eawchwdxg8hfhg+jk9f0w@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).