From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Dan Shearer <dan-QNUrB6Xd9YFAfugRpC6u6w@public.gmane.org>,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Pikchr in Pandoc
Date: Mon, 01 Feb 2021 09:40:18 -0800 [thread overview]
Message-ID: <m21rdz3cvx.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <YBeGoc/cMhn7sLG8-2yWpFc3xKUBM656bX5wj8A@public.gmane.org>
We wouldn't embed this directly in pandoc (trying to avoid
C dependencies), but it would be easy to create a filter
to intercept specially marked code blocks and convert them
to pictures. (There are examples of this kind of thing in the
pandoc/lua-filters repository.)
Dan Shearer <dan-QNUrB6Xd9YFAfugRpC6u6w@public.gmane.org> writes:
> I have not noticed mention of Pikchr here, and I think it is relevant to
> recent discussion of diagrams and also GSoC.
>
> https://pikchr.org/ is a simple plain-text markup language for diagrams
> that produces SVG. It is a slightly modified version of Brian
> Kernighan's PIC language from 40 years ago, updated to make it safe to
> use on the web.
>
> Pikchr is ideal for use in Markdown - see the examples at
> https://pikchr.org/home/skn_default/doc/trunk/doc/examples.md , or the
> same examples in darkmode:
> https://pikchr.org/home/skn_ardoise/doc/trunk/doc/examples.md . Click on
> each diagram to see the plain text source code.
>
> Pikchr is implemented in a single C source file with no dependencies,
> intended for embedding within as many tools as possible.
>
> --
> Dan Shearer
> dan-QNUrB6Xd9YFAfugRpC6u6w@public.gmane.org
>
> --
> 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/YBeGoc/cMhn7sLG8%40mx.shearer.org.
next prev parent reply other threads:[~2021-02-01 17:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-01 4:42 Dan Shearer
[not found] ` <YBeGoc/cMhn7sLG8-2yWpFc3xKUBM656bX5wj8A@public.gmane.org>
2021-02-01 16:43 ` ChrisD
[not found] ` <0f250ab3-fbea-cc8f-dd4c-c9ff234b8c98-4SSc53hpTiu9TMao6EloiEEOCMrvLtNR@public.gmane.org>
2021-02-02 14:46 ` 'Dan Shearer' via pandoc-discuss
2021-02-01 17:40 ` John MacFarlane [this message]
[not found] ` <m21rdz3cvx.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2021-02-02 14:32 ` 'Dan Shearer' via pandoc-discuss
[not found] ` <f194310d-8b68-41d5-a13e-28f83fd7b512n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-02-02 17:29 ` John MacFarlane
[not found] ` <m2czxigyzn.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2022-01-10 21:16 ` 'Dan Shearer' via pandoc-discuss
2021-02-02 14:55 ` 'Dan Shearer' via pandoc-discuss
2021-11-25 9:19 ` 'Dan Shearer' via pandoc-discuss
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=m21rdz3cvx.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
--cc=dan-QNUrB6Xd9YFAfugRpC6u6w@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).