From: "'John MacFarlane' via pandoc-announce" <pandoc-announce@googlegroups.com>
To: pandoc-announce@googlegroups.com, pandoc-discuss@googlegroups.com
Subject: ANN: pandoc 3.1.11
Date: Fri, 15 Dec 2023 19:56:11 -0800 [thread overview]
Message-ID: <E5D716B2-37FB-4442-887B-FE5860B71849@berkeley.edu> (raw)
I'm pleased to announce the release of pandoc 3.1.11,
available in the usual places:
Binary packages & changelog:
https://github.com/jgm/pandoc/releases/tag/3.1.11
Source & API documentation:
http://hackage.haskell.org/package/pandoc-3.1.11
Typst support has been improved, and in producing PDFs via LaTeX,
pandoc now tries to determine the proper number of runs by parsing
the log file. This should fix issues some users of custom templates have had
after upgrading to 3.1.10, which reduced the number of runs.
--
You received this message because you are subscribed to the Google Groups "pandoc-announce" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-announce+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-announce/E5D716B2-37FB-4442-887B-FE5860B71849%40berkeley.edu.
reply other threads:[~2023-12-16 3:56 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=E5D716B2-37FB-4442-887B-FE5860B71849@berkeley.edu \
--to=pandoc-announce@googlegroups.com \
--cc=pandoc-discuss@googlegroups.com \
/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).