From: Sam Liddicott <sam-zQGKLn5Wc3Lby3iVrkZq2A@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Pandoc markdown support for ASCII drawings as SVG using GOAT or ASCIITOSVG ?
Date: Thu, 3 Aug 2017 08:56:53 -0700 (PDT) [thread overview]
Message-ID: <12d588a3-8bc4-4659-a6d9-d872d63e2e3b@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1126 bytes --]
What are the thoughts on calling GOAT (https://github.com/blampe/goat)
or ASCIITOSVG (https://github.com/dhobsd/asciitosvg) from pandoc?
I think it would make a good further enhancement to pandoc's enhanced
markdown.
GOAT is the better tool, and will take ASCII diagrams and produce SVG
output.
ASCIITOSVG does the same but handles more basic diagrams (but the output is
prettier).
It may work similar to diagrams-pandoc
(http://hackage.haskell.org/package/diagrams-pandoc)
or the mermaid filter (https://github.com/raghur/mermaid-filter)
Sam
--
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/12d588a3-8bc4-4659-a6d9-d872d63e2e3b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 1699 bytes --]
next reply other threads:[~2017-08-03 15:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-03 15:56 Sam Liddicott [this message]
[not found] ` <12d588a3-8bc4-4659-a6d9-d872d63e2e3b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-08-03 16:22 ` 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=12d588a3-8bc4-4659-a6d9-d872d63e2e3b@googlegroups.com \
--to=sam-zqgkln5wc3lby3ivrkzq2a@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).