From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-announce-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: ANN: pandoc 2.5
Date: Tue, 27 Nov 2018 09:42:55 -0800 [thread overview]
Message-ID: <m2mupu4dsw.fsf@johnmacfarlane.net> (raw)
I'm pleased to announce the release of pandoc 2.5,
which is available in the usual places:
Binary packages & changelog:
https://github.com/jgm/pandoc/releases/tag/2.5
Source & API documentation:
http://hackage.haskell.org/package/pandoc-2.5
This version fixes a regression in the parsing of
citations, quotes, and underline emphasis after
symbols (#5099, #5053). I recommend that everyone
upgrade.
There is one API change, which necessitates the major
version number bump: A parameter for Extensions has
been added to uniqueIdent and inlineListToIdentifier
(#5057).
The rest of the changes are bug fixes and minor
improvements, which are documented in the changelog:
http://pandoc.org/releases.html#pandoc-2.5-27-november-2018
Thanks to everyone who contributed!
reply other threads:[~2018-11-27 17:42 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=m2mupu4dsw.fsf@johnmacfarlane.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).