From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
pandoc-announce-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: ANN: pandoc 2.11.1
Date: Tue, 03 Nov 2020 14:45:39 -0800 [thread overview]
Message-ID: <m2zh3yjbzg.fsf@MacBook-Pro.hsd1.ca.comcast.net> (raw)
I'm pleased to announce the release of pandoc 2.11.1,
available in the usual places:
Binary packages & changelog:
https://github.com/jgm/pandoc/releases/tag/2.11.1
Source & API documentation:
http://hackage.haskell.org/package/pandoc-2.11.1
This is another minor release to fix some regressions (and help
deal with election anxiety).
Minor API change:
Add `PandocBibliographyError` constructor for `PandocError`.
(This will help us give more informative error messages
when pandoc can't parse a bibliography.)
Some other improvements of note:
- Fixed overlong lines in some bibliography styles (e.g., ieee.csl).
- Fixed bug in commonmark with footnote extension, whereby
nested block-level elements inside a footnote would be rendered
in reverse order.
- Fixed regression in JATS output when using `--citeproc`.
- Improved calculation of table column widths in the LaTeX writer.
- Improved treatment of author-in-text citations inside footnotes,
in note styles. Rather than putting the bibliographic data
in paretheses after the author's name, we now separate it using
a comma.
- Fixed improper capitalization of "Ibid." and other labels
generated by `--citeproc`.
- Better handling of inline SVG in HTML.
- Refined default CSS for HTML.
- Added documentation for pandoc's JATS handling.
Thanks to Albert Krewinkel, Mauro Bieg, Nils Carlson, and Andy
Morris for contributions.
next reply other threads:[~2020-11-03 22:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-03 22:45 John MacFarlane [this message]
[not found] ` <m2zh3yjbzg.fsf-jF64zX8BO08an7k8zZ43ob9bIa4KchGshsV+eolpW18@public.gmane.org>
2020-11-06 7:39 ` Geoff Russell
[not found] ` <27ecca51-7881-411b-8f31-02af125e65bfn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-11-06 8:21 ` 'Denis Maier' via pandoc-discuss
[not found] ` <4242b24f-9a1d-9a6e-c052-e8c63b3df65d-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-11-06 9:52 ` Geoff Russell
2020-11-10 8:32 ` Math blocks with specified environment [generic directives / attributes] Gabriel Nützi
[not found] ` <d9796bc9-ce29-c607-8a0f-79d0834f4286-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2020-11-10 16:49 ` John MacFarlane
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=m2zh3yjbzg.fsf@MacBook-Pro.hsd1.ca.comcast.net \
--to=jgm-tvlzxgkolnx2fbvcvol8/a@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).