public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org,
	pandoc-announce-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: (unknown)
Date: Sun, 03 Mar 2019 12:11:29 -0800	[thread overview]
Message-ID: <m2d0n7u39q.fsf@johnmacfarlane.net> (raw)


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

Binary packages & changelog:
  https://github.com/jgm/pandoc/releases/tag/2.7
Source & API documentation:
  http://hackage.haskell.org/package/pandoc-2.7

Some noteworthy behavior changes:

- We now default to using the XDG data directory
  (by default, $HOME/.local/share/pandoc but
  overridable by setting XDG_DATA_HOME) instead of
  $HOME/.pandoc for the user data directory.  If
  this directory is not present, $HOME/.pandoc will
  be used, for backwards compatibility.  On Windows
  there are no changes.

- In slide shows, content under headers superordinate
  to slide level is no longer omitted; instead, it is
  included in the title slide for the section (in HTML
  slide formats) or in a slide after the section title
  (in beamer). This change facilitates 2D reveal.js
  slideshows with content in the top slide on each
  stack (#4317, #5237).  (Note that you'll still need
  to specify --slide-level=2 for this behavior.)

- There is a new command line option
  --ipynb-output, with possible values 'all', 'none',
  or 'best' (the default). Output cells in ipynb
  notebooks often contain several different versions
  of an output, with different MIME types, e.g. an
  HTML table and a plain-text fallback. Specifying 'best'
  ensures that the best version for the output format
  is used; 'all' includes all versions; and 'none'
  suppresses them all, leaving output cells empty.

- asciidoctor is now an output format separate from
  asciidoc, to accommodate some minor
  implementation-specific differences (currently just
  in the treatment of display math).  If you produce
  asciidoc that you plan to process using asciidoctor,
  use '-t asciidoctor'.

- latexmk can now be used as an option to
  --pdf-engine. latexmk has a number of options and
  can automatically run bibtex, biber, makeindex, and
  other auxiliary programs. Note that you can use
  --pdf-engine-opt=-outdir=bar to specify a persistent
  temp directory, which should speed up repeated
  builds.

API changes:

- Add writeAsciiDoctor to Text.Pandoc.Writers.AsciiDoc.
- Text.Pandoc.Readers.Markdown: add ReaderOptios
  parameter to yamlToMeta.
- Text.Pandoc.Shared: remove withTempDir, add
  defaultUserDataDirs and filterIpynbOutput.

Thanks to everyone who contributed, including
Mauro Bieg, Jesse Rosenthal, Alexander Krotov,
Albert Krewinkel, Tarik Graba, John KetzerX,
Agustín Martín Barbero, Arfon Smith, and Pascal Wagler.
Thanks also to those who suggested bug fixes and
new features.

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/m2d0n7u39q.fsf%40johnmacfarlane.net.
For more options, visit https://groups.google.com/d/optout.


             reply	other threads:[~2019-03-03 20:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-03 20:11 John MacFarlane [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-05-25 13:52 (unknown) BPJ
     [not found] ` <CADAJKhBggA8DZjkoC=m7GvWRK-PdG-eDByP03tE47znBY4qOiw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2023-05-25 22:19   ` (unknown) Rik
2021-06-08 20:31 (unknown) T. Kurt Bond
2019-04-25  1:09 (unknown) lcy1980.ly
2014-04-14  8:25 (unknown) floss-U/CwgbeeR7qv6jhOC1oHvg

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=m2d0n7u39q.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).