From: John MacFarlane <fiddlosopher-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-announce-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: ANN: pandoc 3.1
Date: Thu, 9 Feb 2023 22:45:06 -0800 [thread overview]
Message-ID: <25FF7685-B3A2-4E54-818F-79A84449D292@gmail.com> (raw)
I'm pleased to announce the release of pandoc 3.1,
available in the usual places:
Binary packages & changelog:
https://github.com/jgm/pandoc/releases/tag/3.1
Source & API documentation:
http://hackage.haskell.org/package/pandoc-3.1
This version adds a new option --chunk-template, giving the user more
control over the filenames in chunked HTML output.
There are several other bug fixes and minor improvements.
API changes:
* Text.Pandoc.App: Add optChunkTemplate constructor to Opt.
* Text.Pandoc.Options: add writerChunkTemplate constructor to WriterOptions.
* Text.Pandoc.Chunks: add Data, Typeable, Generic, ToJSON, FromJSON
instances for PathTemplate.
Thanks to all who contributed, especially new contributors
Daniel Kessler, Martin Joerg, and Stephen Altamirano.
reply other threads:[~2023-02-10 6:45 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=25FF7685-B3A2-4E54-818F-79A84449D292@gmail.com \
--to=fiddlosopher-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=pandoc-announce-/JYPxA39Uh5TLH3MbocFFw@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).