aboutsummaryrefslogtreecommitdiffhomepage
path: root/pandoc-citeproc-preamble.1.pod
diff options
context:
space:
mode:
authorSean Whitton <spwhitton@spwhitton.name>2017-02-04 13:23:28 -0700
committerSean Whitton <spwhitton@spwhitton.name>2017-02-04 13:23:28 -0700
commitd66301d8aca7be2821a083dd7cbefb20bdf164ad (patch)
tree83316e5557cdc095f4a463cd19cddaac0935fbe7 /pandoc-citeproc-preamble.1.pod
parent8819e8fe1d3a56c80d7613f829ef70f43ec41eb5 (diff)
downloadpandoc-citeproc-preamble-d66301d8aca7be2821a083dd7cbefb20bdf164ad.tar.gz
add manpage
Diffstat (limited to 'pandoc-citeproc-preamble.1.pod')
-rw-r--r--pandoc-citeproc-preamble.1.pod76
1 files changed, 76 insertions, 0 deletions
diff --git a/pandoc-citeproc-preamble.1.pod b/pandoc-citeproc-preamble.1.pod
new file mode 100644
index 0000000..521988e
--- /dev/null
+++ b/pandoc-citeproc-preamble.1.pod
@@ -0,0 +1,76 @@
+=head1 NAME
+
+pandoc-citeproc-preamble - insert a preamble before pandoc-citeproc's bibliography
+
+=head1 SYNOPSIS
+
+B<pandoc-citeproc-preamble>
+
+=head1 DESCRIPTION
+
+B<pandoc-citeproc-preamble> is a JSON filter for pandoc(1) which
+inserts a preamble before the output that the pandoc-citeproc(1)
+filter appends to the document. This preamble might include a heading
+(e.g. "Bibliography") and/or raw markup to format the bibliography for
+the output format.
+
+=head1 USAGE
+
+Add B<--filter pandoc-citeproc-preamble> somewhere after B<--filter
+pandoc-citeproc>, e.g.
+
+=over 4
+
+ % pandoc -s --filter pandoc-citeproc --bibliography=~/doc/mine.bib \
+ --filter pandoc-citeproc-preamble \
+ ~/doc/my_essay.mdwn -o ~/my_essay.pdf
+
+=back
+
+=head1 FILES
+
+=over 4
+
+=item ~/.pandoc/citeproc-preamble/default.I<FORMAT>
+
+Default citeproc preamble for Pandoc output format I<FORMAT>
+(e.g. "latex").
+
+=back
+
+To override this, you can set document metadata like this:
+
+=over 4
+
+ % pandoc ... --filter pandoc-citeprocpreamble \
+ -M citeproc-preamble=~/mypreamble.tex ...
+
+=back
+
+=head1 RATIONALE
+
+One motivation for authoring with Pandoc is that one's input files are
+agnostic with regard to the output format to which they will
+eventually be compiled. For example, it should not be necessary to
+include LaTeX code in one's input file in order to format the
+bibliography. The input file might also be compiled to HTML.
+
+However, when compiling to PDF, formatting code is usually required in
+order to have the entries of pandoc-citeproc's bibliography line up
+with each other; by default, all entries except the first will be
+indented. Another common customisation is to set up a hanging indent
+for bibliography entries.
+
+Since pandoc-citeproc(1) doesn't provide any facility to add
+formatting control code to its output, B<pandoc-citeproc-preamble> is
+necessary to avoid the user being forced to add their control code to
+the end of their input files, thereby losing the input file's
+agnosticity with regard to output format.
+
+=head1 AUTHOR
+
+Sean Whitton <spwhitton@spwhitton.name>
+
+=head1 SEE ALSO
+
+pandoc(1), pandoc-citeproc(1)