public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'Dan Shearer' via pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pikchr in Pandoc
Date: Tue, 02 Feb 2021 09:29:00 -0800	[thread overview]
Message-ID: <m2czxigyzn.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
In-Reply-To: <f194310d-8b68-41d5-a13e-28f83fd7b512n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

"'Dan Shearer' via pandoc-discuss"
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> writes:

> Le lundi 1 février 2021 à 17:40:33 UTC, John MacFarlane a écrit :
>
>>
>> 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.) 
>>
>
> John, what is needed to help make a Pikchr filter happen? 

You can learn about how to write pandoc filters from the
documentation

https://pandoc.org/filters.html
https://pandoc.org/lua-filters.html

You could, in principle, write the whole filter in C (using
the pikchr liibrary and a JSON-parsing and generating library).
Or you could use any other language.

-- 
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/m2czxigyzn.fsf%40MacBook-Pro.hsd1.ca.comcast.net.


  parent reply	other threads:[~2021-02-02 17:29 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
     [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 [this message]
     [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=m2czxigyzn.fsf@MacBook-Pro.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).