public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: "'John MacFarlane' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-announce-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: ANN: pandoc 3.1.9
Date: Fri, 27 Oct 2023 18:14:40 -0700	[thread overview]
Message-ID: <5BF3F118-59C2-4664-B986-A5A57B7D9F9E@berkeley.edu> (raw)

I'm pleased to announce the release of pandoc 3.1.9,
available in the usual places:

Binary packages & changelog:
https://github.com/jgm/pandoc/releases/tag/3.1.9

Source & API documentation:
http://hackage.haskell.org/package/pandoc-3.1.9

This release includes a number of small bug fixes and new features.
Most notably:

- Pandoc can now read the BITS dialect of JATS (bits is a new input
  format).
- A new extension tex_math_gfm supports math formats that are specific
  to GFM (inline math with $`..`$ delimiters and display math in a code
  block marked 'math').  It is enabled by default for gfm.

API changes:

- In Text.Pandoc.Extensions Ext_tex_math_gfm is a new constructor
  for Extensions.
- Text.Pandoc.Shared now exports addPandocAttributes.

See the changelog for full details

Thanks to all who contributed or submitted bug reports, especially
Julia Diaz for improvements to the JATS reader, and new contributors
James J Balamuta, John Purnell, Michael McClurg, Seth Speaks,
Stephan Daus, Tim Stewart, 3w36zj6, piq9117, priiduon, and samuel-weinhardt.


                 reply	other threads:[~2023-10-28  1:14 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=5BF3F118-59C2-4664-B986-A5A57B7D9F9E@berkeley.edu \
    --to=pandoc-discuss-/jypxa39uh5tlh3mbocffw@public.gmane.org \
    --cc=pandoc-announce-/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).