public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
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.18
Date: Mon, 04 Apr 2022 11:36:12 -0700	[thread overview]
Message-ID: <m27d84elwj.fsf@MacBook-Pro-2.hsd1.ca.comcast.net> (raw)


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

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

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

In addition to the usual under-the-hood improvements
and bug fixes, there are some new features:

* New input formats: endnotexml and ris bibliographies.

* A RIS bibliography file may now be used with `--citeproc`.

* Citeproc now allows a formatted bibliography to be placed
  in a metadata field (and thus to be placed at an arbitrary
  position in a template).  To do this, include a metadata
  field (say, 'refs') whose content is an empty Div with id 'refs'.

* Metadata files specified with --metadata-file are now sought
  in $DATADIR/metadata if not found locally.

* --self-contained now issues a warning rather than failing with
  an error when a resource cannot be found.

* The LaTeX reader will now skip parts of local packages imported with
  \usepackage that it cannot parse.

* The Lua interface adds a new module pandoc.layout, allows any
  type of callable object as an argument to list functions
  filter, map, and find_if, and allows passing a Sources object
  to pandoc.read.

* wkhtmltopdf is again the default PDF engine for HTML.

* LaTeX and JATS templates have been revised, so take note if you
  use custom templates.

* A new compiler flag lua53 (false by default) will cause pandoc
  to be built with embedded Lua 5.3.  By default Lua 5.4 will be
  embedded.  pandoc --version will now tell you which version of
  Lua is embedded.

API changes:

* New exported module Text.Pandoc.Readers.RIS (readRIS).

* New exported module Text.Pandoc.Readers.EndNote (readEndNoteXML,
  readEndNoteXMLCitation).

* Text.Pandoc.Logging: Add CouldNotParseIncludeFile constructor for
  LogMessage.

* Text.Pandoc.Error: Export PandocCouldNotFindMetadataFileError
  constructor for PandocError.

* Text.Pandoc.Parsing: Change type of tableWith' and gridTableWith'
  so they return a structured TableComponents rather than a tuple.
  Export tableWith', TableComponents, TableNormalization,
  toTableComponents, toTableComponents'.

* Text.Pandoc.XML.Light: Export parseXMLElementWithEntities,
  parseXMLContentsWithEntities (these allow specifying a custom entity map).
  
* Text.Pandoc.Class: Export readMetadataFile.

Thanks to everyone who contributed, especially new contributers
Dmitris Apostolou, Guriy Samarin, Ivar de Bruin, Jaap de Jong,
Jonathan Dönszelmann, Lucas V. R, Mario Lang, Naveen, Ola Wolska,
damon-sava-stanley, mjfs.

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/m27d84elwj.fsf%40MacBook-Pro-2.hsd1.ca.comcast.net.


             reply	other threads:[~2022-04-04 18:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-04 18:36 John MacFarlane [this message]
     [not found] ` <m27d84elwj.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2022-04-06 20:47   ` 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=m27d84elwj.fsf@MacBook-Pro-2.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).