From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: Including DJOT reader and writer in compiled Pandoc
Date: Wed, 28 Dec 2022 18:28:58 -0800 [thread overview]
Message-ID: <2F735960-5659-4780-AF0E-BB0AF842084B@gmail.com> (raw)
In-Reply-To: <3441BD7B-5172-41F6-874F-950BA63FA704-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org>
Djot is pretty experimental; I think I want to wait til it settles down a bit (and see if people actually want to use it) before I include it as a regular reader/writer. So for now you need to use the lua scripts.
> On Dec 28, 2022, at 10:02 AM, Thomas Byskov Dalgaard <tbdlist@coolfortheblind.dk> wrote:
>
> Hi!
>
> I have followed the development of DJOT since it started. There are custom reader and writer for Pandoc. I understand it has not ben easy to create these in the first place, and now it can be quite complicated to install packages and fetching GitHub content.
>
> Is it possible to include the DJOT reader and writer like other readers and writers in pandoc so one can type
> pandoc -f djot -t html -o filename.html filename.dt
> Is this already in the roadmap or should a GitHub issue be created for this?
>
> Best regards Thomas
>
> --
> 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/3441BD7B-5172-41F6-874F-950BA63FA704%40coolfortheblind.dk.
--
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/2F735960-5659-4780-AF0E-BB0AF842084B%40gmail.com.
next prev parent reply other threads:[~2022-12-29 2:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 18:02 Thomas Byskov Dalgaard
[not found] ` <3441BD7B-5172-41F6-874F-950BA63FA704-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org>
2022-12-29 2:28 ` John MacFarlane [this message]
[not found] ` <2F735960-5659-4780-AF0E-BB0AF842084B-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-12-29 12:02 ` Thomas Byskov Dalgaard
[not found] ` <AE561250-2C85-463D-877B-145C25F4715E-AHfMSizzl90sTMJHDOTzqX9LOBIZ5rWg@public.gmane.org>
2022-12-29 12:16 ` Bastien DUMONT
2022-12-29 17:12 ` John MacFarlane
[not found] ` <3ECA20A2-4D59-483D-97E2-02DE05586369-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2022-12-29 19:18 ` Thomas Byskov Dalgaard
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=2F735960-5659-4780-AF0E-BB0AF842084B@gmail.com \
--to=fiddlosopher-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).