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
Subject: Re: ANN: pandoc 1.14.1
Date: Wed, 1 Jul 2015 10:20:06 -0700	[thread overview]
Message-ID: <20150701172006.GA61328@localhost.hsd1.ca.comcast.net> (raw)
In-Reply-To: <20150701164457.GD61054-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>

Actually, looking at the man page situation, I'm tempted
to change to using one big man page (pandoc.1) instead of
pandoc.1 and pandoc_markdown.5.

Currently these are carved out of the README.  But parts
of pandoc.1 actually refer to sections that end up
in pandoc_markdown.5.

If we did this, we'd be closer to being able to generate
the man page using a straightforward pandoc command with
README and a custom template.  We'd also need custom
filters for the other transformations we do (remove links,
capitalize headers).

Man page generation would then be something like:

    pandoc README -t man -s --template man/man_template.1 \
      --filter man/removeLinks.hs \
      --filter man/capitalizeHeaders.hs \
      -o pandoc.1

I like that better than including `--man1` and `--man5`
in pandoc itself, and I don't know why I didn't think of
doing it this way.


  parent reply	other threads:[~2015-07-01 17:20 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-01  5:54 John MacFarlane
     [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 [this message]
     [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=20150701172006.GA61328@localhost.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).