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 1.14.1
Date: Tue, 30 Jun 2015 22:54:19 -0700 [thread overview]
Message-ID: <20150701055418.GA60820@localhost.hsd1.ca.comcast.net> (raw)
I'm pleased to announce the release of pandoc 1.14.1.
A changelog and binary downloads can be found here:
https://github.com/jgm/pandoc/releases/1.14.1
If you use cabal to install pandoc, just
cabal update && cabal install --reinstall pandoc
In general this release just cleans up a few problems
with the 1.14.0.x series.
You can once again put a reference.docx in your ~/.pandoc
directory, and it will override defaults. You can also
once again do `pandoc --print-default-data-file
reference.docx`.
`--self-contained` should also work better with complex
CSS files.
Packagers take note: the man pages are no longer built
during the Cabal build process. Instead, pandoc can now
generate its own man pages:
pandoc --man1 > pandoc.1
pandoc --man5 > pandoc_markdown.5
next reply other threads:[~2015-07-01 5:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-01 5:54 John MacFarlane [this message]
[not found] ` <20150701055418.GA60820-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-07-01 7:14 ` Magnus Therning
2015-07-01 16:44 ` John MacFarlane
[not found] ` <20150701164457.GD61054-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-07-01 17:20 ` John MacFarlane
[not found] ` <20150701172006.GA61328-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-07-01 23:06 ` Magnus Therning
2015-07-01 23:42 ` John MacFarlane
2015-07-01 23:03 ` Magnus Therning
2015-07-01 14:32 ` Manolo Martínez
2015-07-01 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=20150701055418.GA60820@localhost.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).