@@ -1,10 +1,10 @@
2−.TH PANDOC 1 "December 10, 2016" "pandoc 1.19.1"
2+.TH PANDOC 1 "January 29, 2017" "pandoc 1.19.2"
4pandoc - general markup converter
4pandoc - general markup converter
5.SH SYNOPSIS
5.SH SYNOPSIS
7−\f[C]pandoc\f[] [\f[I]options\f[]] [\f[I]input\-file\f[]]...
7+\f[C]pandoc\f[] [\f[I]options\f[]] [\f[I]input\-file\f[]]\&...
8.SH DESCRIPTION
8.SH DESCRIPTION
10Pandoc is a Haskell library for converting from one markup format to
10Pandoc is a Haskell library for converting from one markup format to
@@ -23,13 +23,13 @@ Simple, and Slidy, Slideous, DZSlides, reveal.js or S5 HTML slide shows.
23It can also produce PDF output on systems where LaTeX, ConTeXt, or
23It can also produce PDF output on systems where LaTeX, ConTeXt, or
24\f[C]wkhtmltopdf\f[] is installed.
24\f[C]wkhtmltopdf\f[] is installed.
26−Pandoc\[aq]s enhanced version of Markdown includes syntax for footnotes,
26+Pandoc's enhanced version of Markdown includes syntax for footnotes,
27tables, flexible ordered lists, definition lists, fenced code blocks,
27tables, flexible ordered lists, definition lists, fenced code blocks,
28superscripts and subscripts, strikeout, metadata blocks, automatic
28superscripts and subscripts, strikeout, metadata blocks, automatic
29tables of contents, embedded LaTeX math, citations, and Markdown inside
29tables of contents, embedded LaTeX math, citations, and Markdown inside
30HTML block elements.
30HTML block elements.
31−(These enhancements, described further under Pandoc\[aq]s Markdown, can
31+(These enhancements, described further under Pandoc's Markdown, can be
32−be disabled using the \f[C]markdown_strict\f[] input or output format.)
32+disabled using the \f[C]markdown_strict\f[] input or output format.)
34In contrast to most existing tools for converting Markdown to HTML,
34In contrast to most existing tools for converting Markdown to HTML,
35which use regex substitutions, pandoc has a modular design: it consists
35which use regex substitutions, pandoc has a modular design: it consists
@@ -39,16 +39,16 @@ convert this native representation into a target format.
39Thus, adding an input or output format requires only adding a reader or
39Thus, adding an input or output format requires only adding a reader or
42−Because pandoc\[aq]s intermediate representation of a document is less
42+Because pandoc's intermediate representation of a document is less
43expressive than many of the formats it converts between, one should not
43expressive than many of the formats it converts between, one should not
44expect perfect conversions between every format and every other.
44expect perfect conversions between every format and every other.
45Pandoc attempts to preserve the structural elements of a document, but
45Pandoc attempts to preserve the structural elements of a document, but
46not formatting details such as margin size.
46not formatting details such as margin size.
47And some document elements, such as complex tables, may not fit into
47And some document elements, such as complex tables, may not fit into
48−pandoc\[aq]s simple document model.
48+pandoc's simple document model.
49−While conversions from pandoc\[aq]s Markdown to all formats aspire to be
49+While conversions from pandoc's Markdown to all formats aspire to be
50−perfect, conversions from formats more expressive than pandoc\[aq]s
50+perfect, conversions from formats more expressive than pandoc's Markdown
51−Markdown can be expected to be lossy.
51+can be expected to be lossy.
52.SS Using \f[C]pandoc\f[]
52.SS Using \f[C]pandoc\f[]
54If no \f[I]input\-file\f[] is specified, input is read from
54If no \f[I]input\-file\f[] is specified, input is read from
@@ -137,11 +137,11 @@ pandoc\ \-o\ hello.tex\ hello.txt
138will convert \f[C]hello.txt\f[] from Markdown to LaTeX.
138will convert \f[C]hello.txt\f[] from Markdown to LaTeX.
139If no output file is specified (so that output goes to \f[I]stdout\f[]),
139If no output file is specified (so that output goes to \f[I]stdout\f[]),
140−or if the output file\[aq]s extension is unknown, the output format will
140+or if the output file's extension is unknown, the output format will
141default to HTML.
141default to HTML.
142If no input file is specified (so that input comes from \f[I]stdin\f[]),
142If no input file is specified (so that input comes from \f[I]stdin\f[]),
143−or if the input files\[aq] extensions are unknown, the input format will
143+or if the input files' extensions are unknown, the input format will be
144−be assumed to be Markdown unless explicitly specified.
144+assumed to be Markdown unless explicitly specified.
146Pandoc uses the UTF\-8 character encoding for both input and output.
146Pandoc uses the UTF\-8 character encoding for both input and output.
147If your local character encoding is not UTF\-8, you should pipe input
147If your local character encoding is not UTF\-8, you should pipe input
@@ -208,7 +208,7 @@ as will \f[C]\-\-css\f[].
208.B \f[C]\-f\f[] \f[I]FORMAT\f[], \f[C]\-r\f[] \f[I]FORMAT\f[], \f[C]\-\-from=\f[]\f[I]FORMAT\f[], \f[C]\-\-read=\f[]\f[I]FORMAT\f[]
208.B \f[C]\-f\f[] \f[I]FORMAT\f[], \f[C]\-r\f[] \f[I]FORMAT\f[], \f[C]\-\-from=\f[]\f[I]FORMAT\f[], \f[C]\-\-read=\f[]\f[I]FORMAT\f[]
209Specify input format.
209Specify input format.
210\f[I]FORMAT\f[] can be \f[C]native\f[] (native Haskell), \f[C]json\f[]
210\f[I]FORMAT\f[] can be \f[C]native\f[] (native Haskell), \f[C]json\f[]
211−(JSON version of native AST), \f[C]markdown\f[] (pandoc\[aq]s extended
211+(JSON version of native AST), \f[C]markdown\f[] (pandoc's extended
212Markdown), \f[C]markdown_strict\f[] (original unextended Markdown),
212Markdown), \f[C]markdown_strict\f[] (original unextended Markdown),
213\f[C]markdown_phpextra\f[] (PHP Markdown Extra),
213\f[C]markdown_phpextra\f[] (PHP Markdown Extra),
214\f[C]markdown_github\f[] (GitHub\-Flavored Markdown),
214\f[C]markdown_github\f[] (GitHub\-Flavored Markdown),
@@ -227,10 +227,9 @@ appending \f[C]+EXTENSION\f[] or \f[C]\-EXTENSION\f[] to the format
228So, for example, \f[C]markdown_strict+footnotes+definition_lists\f[] is
228So, for example, \f[C]markdown_strict+footnotes+definition_lists\f[] is
229strict Markdown with footnotes and definition lists enabled, and
229strict Markdown with footnotes and definition lists enabled, and
230−\f[C]markdown\-pipe_tables+hard_line_breaks\f[] is pandoc\[aq]s Markdown
230+\f[C]markdown\-pipe_tables+hard_line_breaks\f[] is pandoc's Markdown
231without pipe tables and with hard line breaks.
231without pipe tables and with hard line breaks.
232−See Pandoc\[aq]s Markdown, below, for a list of extensions and their
232+See Pandoc's Markdown, below, for a list of extensions and their names.
234See \f[C]\-\-list\-input\-formats\f[] and \f[C]\-\-list\-extensions\f[],
233See \f[C]\-\-list\-input\-formats\f[] and \f[C]\-\-list\-extensions\f[],
@@ -240,10 +239,9 @@ below.
240Specify output format.
239Specify output format.
241\f[I]FORMAT\f[] can be \f[C]native\f[] (native Haskell), \f[C]json\f[]
240\f[I]FORMAT\f[] can be \f[C]native\f[] (native Haskell), \f[C]json\f[]
242(JSON version of native AST), \f[C]plain\f[] (plain text),
241(JSON version of native AST), \f[C]plain\f[] (plain text),
243−\f[C]markdown\f[] (pandoc\[aq]s extended Markdown),
242+\f[C]markdown\f[] (pandoc's extended Markdown), \f[C]markdown_strict\f[]
244−\f[C]markdown_strict\f[] (original unextended Markdown),
245−\f[C]markdown_phpextra\f[] (PHP Markdown Extra),
243+(original unextended Markdown), \f[C]markdown_phpextra\f[] (PHP Markdown
246−\f[C]markdown_github\f[] (GitHub\-Flavored Markdown),
244+Extra), \f[C]markdown_github\f[] (GitHub\-Flavored Markdown),
247\f[C]markdown_mmd\f[] (MultiMarkdown), \f[C]commonmark\f[] (CommonMark
245\f[C]markdown_mmd\f[] (MultiMarkdown), \f[C]commonmark\f[] (CommonMark
248Markdown), \f[C]rst\f[] (reStructuredText), \f[C]html\f[] (XHTML),
246Markdown), \f[C]rst\f[] (reStructuredText), \f[C]html\f[] (XHTML),
249\f[C]html5\f[] (HTML5), \f[C]latex\f[] (LaTeX), \f[C]beamer\f[] (LaTeX
247\f[C]html5\f[] (HTML5), \f[C]latex\f[] (LaTeX), \f[C]beamer\f[] (LaTeX
@@ -319,7 +317,7 @@ You can find the default user data directory on your system by looking
319at the output of \f[C]pandoc\ \-\-version\f[].
317at the output of \f[C]pandoc\ \-\-version\f[].
320A \f[C]reference.odt\f[], \f[C]reference.docx\f[], \f[C]epub.css\f[],
318A \f[C]reference.odt\f[], \f[C]reference.docx\f[], \f[C]epub.css\f[],
321\f[C]templates\f[], \f[C]slidy\f[], \f[C]slideous\f[], or \f[C]s5\f[]
319\f[C]templates\f[], \f[C]slidy\f[], \f[C]slideous\f[], or \f[C]s5\f[]
322−directory placed in this directory will override pandoc\[aq]s normal
320+directory placed in this directory will override pandoc's normal
@@ -355,7 +353,7 @@ List supported output formats, one per line.
355.B \f[C]\-\-list\-extensions\f[]
353.B \f[C]\-\-list\-extensions\f[]
356List supported Markdown extensions, one per line, followed by a
354List supported Markdown extensions, one per line, followed by a
357\f[C]+\f[] or \f[C]\-\f[] indicating whether it is enabled by default in
355\f[C]+\f[] or \f[C]\-\f[] indicating whether it is enabled by default in
358−pandoc\[aq]s Markdown.
356+pandoc's Markdown.
@@ -401,8 +399,8 @@ Produce typographically correct output, converting straight quotes to
401curly quotes, \f[C]\-\-\-\f[] to em\-dashes, \f[C]\-\-\f[] to
399curly quotes, \f[C]\-\-\-\f[] to em\-dashes, \f[C]\-\-\f[] to
402en\-dashes, and \f[C]\&...\f[] to ellipses.
400en\-dashes, and \f[C]\&...\f[] to ellipses.
403Nonbreaking spaces are inserted after certain abbreviations, such as
401Nonbreaking spaces are inserted after certain abbreviations, such as
404−"Mr." (Note: This option is selected automatically when the output
402+\[lq]Mr.\[rq] (Note: This option is selected automatically when the
405−format is \f[C]latex\f[] or \f[C]context\f[], unless
403+output format is \f[C]latex\f[] or \f[C]context\f[], unless
406\f[C]\-\-no\-tex\-ligatures\f[] is used.
404\f[C]\-\-no\-tex\-ligatures\f[] is used.
407It has no effect for \f[C]latex\f[] input.)
405It has no effect for \f[C]latex\f[] input.)
@@ -422,7 +420,7 @@ Specify the base level for headers (defaults to 1).
424.B \f[C]\-\-indented\-code\-classes=\f[]\f[I]CLASSES\f[]
422.B \f[C]\-\-indented\-code\-classes=\f[]\f[I]CLASSES\f[]
425−Specify classes to use for indented code blocks\-\-for example,
423+Specify classes to use for indented code blocks\[en]for example,
426\f[C]perl,numberLines\f[] or \f[C]haskell\f[].
424\f[C]perl,numberLines\f[] or \f[C]haskell\f[].
427Multiple classes may be separated by spaces or commas.
425Multiple classes may be separated by spaces or commas.
@@ -450,7 +448,7 @@ Reading binary files (docx, odt, epub) implies \f[C]\-\-file\-scope\f[].
450Specify an executable to be used as a filter transforming the pandoc AST
448Specify an executable to be used as a filter transforming the pandoc AST
451after the input is parsed and before the output is written.
449after the input is parsed and before the output is written.
452The executable should read JSON from stdin and write JSON to stdout.
450The executable should read JSON from stdin and write JSON to stdout.
453−The JSON must be formatted like pandoc\[aq]s own JSON input and output.
451+The JSON must be formatted like pandoc's own JSON input and output.
454The name of the output format will be passed to the filter as the first
452The name of the output format will be passed to the filter as the first
@@ -524,7 +522,7 @@ Specify the number of spaces per tab (default is 4).
525.B \f[C]\-\-track\-changes=accept\f[]|\f[C]reject\f[]|\f[C]all\f[]
523.B \f[C]\-\-track\-changes=accept\f[]|\f[C]reject\f[]|\f[C]all\f[]
526Specifies what to do with insertions, deletions, and comments produced
524Specifies what to do with insertions, deletions, and comments produced
527−by the MS Word "Track Changes" feature.
525+by the MS Word \[lq]Track Changes\[rq] feature.
528\f[C]accept\f[] (the default), inserts all insertions, and ignores all
526\f[C]accept\f[] (the default), inserts all insertions, and ignores all
529deletions.
527deletions.
530\f[C]reject\f[] inserts all deletions and ignores insertions.
528\f[C]reject\f[] inserts all deletions and ignores insertions.
@@ -550,8 +548,8 @@ This option only affects the docx and epub readers.
550.SS General writer options
548.SS General writer options
552.B \f[C]\-s\f[], \f[C]\-\-standalone\f[]
550.B \f[C]\-s\f[], \f[C]\-\-standalone\f[]
553−Produce output with an appropriate header and footer (e.g.
551+Produce output with an appropriate header and footer (e.g.\ a standalone
554−a standalone HTML, LaTeX, TEI, or RTF file, not a fragment).
552+HTML, LaTeX, TEI, or RTF file, not a fragment).
555This option is set automatically for \f[C]pdf\f[], \f[C]epub\f[],
553This option is set automatically for \f[C]pdf\f[], \f[C]epub\f[],
556\f[C]epub3\f[], \f[C]fb2\f[], \f[C]docx\f[], and \f[C]odt\f[] output.
554\f[C]epub3\f[], \f[C]fb2\f[], \f[C]docx\f[], and \f[C]odt\f[] output.
@@ -609,12 +607,13 @@ Technically, the correct term would be ppi (pixels per inch).
609Determine how text is wrapped in the output (the source code, not the
607Determine how text is wrapped in the output (the source code, not the
610rendered version).
608rendered version).
611With \f[C]auto\f[] (the default), pandoc will attempt to wrap lines to
609With \f[C]auto\f[] (the default), pandoc will attempt to wrap lines to
612−the column width specified by \f[C]\-\-columns\f[] (default 80).
610+the column width specified by \f[C]\-\-columns\f[] (default 72).
613With \f[C]none\f[], pandoc will not wrap lines at all.
611With \f[C]none\f[], pandoc will not wrap lines at all.
614With \f[C]preserve\f[], pandoc will attempt to preserve the wrapping
612With \f[C]preserve\f[], pandoc will attempt to preserve the wrapping
615from the source document (that is, where there are nonsemantic newlines
613from the source document (that is, where there are nonsemantic newlines
616in the source, there will be nonsemantic newlines in the output as
614in the source, there will be nonsemantic newlines in the output as
616+Automatic wrapping does not currently work in HTML output.
@@ -659,8 +658,8 @@ language attribute is given.
659.B \f[C]\-\-highlight\-style=\f[]\f[I]STYLE\f[]
658.B \f[C]\-\-highlight\-style=\f[]\f[I]STYLE\f[]
660Specifies the coloring style to be used in highlighted source code.
659Specifies the coloring style to be used in highlighted source code.
661Options are \f[C]pygments\f[] (the default), \f[C]kate\f[],
660Options are \f[C]pygments\f[] (the default), \f[C]kate\f[],
662−\f[C]monochrome\f[], \f[C]espresso\f[], \f[C]zenburn\f[],
661+\f[C]monochrome\f[], \f[C]breezeDark\f[], \f[C]espresso\f[],
663−\f[C]haddock\f[], and \f[C]tango\f[].
662+\f[C]zenburn\f[], \f[C]haddock\f[], and \f[C]tango\f[].
664For more information on syntax highlighting in pandoc, see Syntax
663For more information on syntax highlighting in pandoc, see Syntax
665highlighting, below.
664highlighting, below.
666See also \f[C]\-\-list\-highlight\-styles\f[].
665See also \f[C]\-\-list\-highlight\-styles\f[].
@@ -680,9 +679,8 @@ Implies \f[C]\-\-standalone\f[].
681.B \f[C]\-B\f[] \f[I]FILE\f[], \f[C]\-\-include\-before\-body=\f[]\f[I]FILE\f[]
680.B \f[C]\-B\f[] \f[I]FILE\f[], \f[C]\-\-include\-before\-body=\f[]\f[I]FILE\f[]
682Include contents of \f[I]FILE\f[], verbatim, at the beginning of the
681Include contents of \f[I]FILE\f[], verbatim, at the beginning of the
684−after the \f[C]<body>\f[] tag in HTML, or the \f[C]\\begin{document}\f[]
682+document body (e.g.\ after the \f[C]<body>\f[] tag in HTML, or the
685−command in LaTeX).
683+\f[C]\\begin{document}\f[] command in LaTeX).
686This can be used to include navigation bars or banners in HTML
684This can be used to include navigation bars or banners in HTML
687documents.
685documents.
688This option can be used repeatedly to include multiple files.
686This option can be used repeatedly to include multiple files.
@@ -706,9 +704,9 @@ Implies \f[C]\-\-standalone\f[].
706Produce a standalone HTML file with no external dependencies, using
704Produce a standalone HTML file with no external dependencies, using
707\f[C]data:\f[] URIs to incorporate the contents of linked scripts,
705\f[C]data:\f[] URIs to incorporate the contents of linked scripts,
708stylesheets, images, and videos.
706stylesheets, images, and videos.
709−The resulting file should be "self\-contained," in the sense that it
707+The resulting file should be \[lq]self\-contained,\[rq] in the sense
710−needs no external files and no net access to be displayed properly by a
708+that it needs no external files and no net access to be displayed
711−browser.
709+properly by a browser.
712This option works only with HTML output formats, including
710This option works only with HTML output formats, including
713\f[C]html\f[], \f[C]html5\f[], \f[C]html+lhs\f[], \f[C]html5+lhs\f[],
711\f[C]html\f[], \f[C]html5\f[], \f[C]html+lhs\f[], \f[C]html5+lhs\f[],
714\f[C]s5\f[], \f[C]slidy\f[], \f[C]slideous\f[], \f[C]dzslides\f[], and
712\f[C]s5\f[], \f[C]slidy\f[], \f[C]slideous\f[], \f[C]dzslides\f[], and
@@ -719,9 +717,9 @@ those at relative URLs will be sought relative to the working directory
719first source file is remote).
717first source file is remote).
720Limitation: resources that are loaded dynamically through JavaScript
718Limitation: resources that are loaded dynamically through JavaScript
721cannot be incorporated; as a result, \f[C]\-\-self\-contained\f[] does
719cannot be incorporated; as a result, \f[C]\-\-self\-contained\f[] does
722−not work with \f[C]\-\-mathjax\f[], and some advanced features (e.g.
720+not work with \f[C]\-\-mathjax\f[], and some advanced features
723−zoom or speaker notes) may not work in an offline "self\-contained"
721+(e.g.\ zoom or speaker notes) may not work in an offline
724−\f[C]reveal.js\f[] slide show.
722+\[lq]self\-contained\[rq] \f[C]reveal.js\f[] slide show.
@@ -792,15 +790,16 @@ Sections with class \f[C]unnumbered\f[] will never be numbered, even if
795−.B \f[C]\-\-number\-offset=\f[]\f[I]NUMBER\f[][\f[C],\f[]\f[I]NUMBER\f[]\f[C],\f[]\f[I]...\f[]]
793+.B \f[C]\-\-number\-offset=\f[]\f[I]NUMBER\f[][\f[C],\f[]\f[I]NUMBER\f[]\f[C],\f[]\f[I]\&...\f[]]
796Offset for section headings in HTML output (ignored in other output
794Offset for section headings in HTML output (ignored in other output
798The first number is added to the section number for top\-level headers,
796The first number is added to the section number for top\-level headers,
799the second for second\-level headers, and so on.
797the second for second\-level headers, and so on.
800So, for example, if you want the first top\-level header in your
798So, for example, if you want the first top\-level header in your
801−document to be numbered "6", specify \f[C]\-\-number\-offset=5\f[].
799+document to be numbered \[lq]6\[rq], specify
800+\f[C]\-\-number\-offset=5\f[].
802If your document starts with a level\-2 header which you want to be
801If your document starts with a level\-2 header which you want to be
803−numbered "1.5", specify \f[C]\-\-number\-offset=1,4\f[].
802+numbered \[lq]1.5\[rq], specify \f[C]\-\-number\-offset=1,4\f[].
804Offsets are 0 by default.
803Offsets are 0 by default.
805Implies \f[C]\-\-number\-sections\f[].
804Implies \f[C]\-\-number\-sections\f[].
@@ -1026,7 +1025,7 @@ body\ {\ font\-family:\ "DejaVuSans";\ }
1027.B \f[C]\-\-epub\-chapter\-level=\f[]\f[I]NUMBER\f[]
1026.B \f[C]\-\-epub\-chapter\-level=\f[]\f[I]NUMBER\f[]
1028Specify the header level at which to split the EPUB into separate
1027Specify the header level at which to split the EPUB into separate
1029−"chapter" files.
1028+\[lq]chapter\[rq] files.
1030The default is to split into chapters at level 1 headers.
1029The default is to split into chapters at level 1 headers.
1031This option only affects the internal composition of the EPUB, not the
1030This option only affects the internal composition of the EPUB, not the
1032way chapters and sections are displayed to users.
1031way chapters and sections are displayed to users.
@@ -1055,7 +1054,7 @@ Note that no check for duplicate options is done.
1055.SS Citation rendering
1054.SS Citation rendering
1057.B \f[C]\-\-bibliography=\f[]\f[I]FILE\f[]
1056.B \f[C]\-\-bibliography=\f[]\f[I]FILE\f[]
1058−Set the \f[C]bibliography\f[] field in the document\[aq]s metadata to
1057+Set the \f[C]bibliography\f[] field in the document's metadata to
1059\f[I]FILE\f[], overriding any value set in the metadata, and process
1058\f[I]FILE\f[], overriding any value set in the metadata, and process
1060citations using \f[C]pandoc\-citeproc\f[].
1059citations using \f[C]pandoc\-citeproc\f[].
1061(This is equivalent to
1060(This is equivalent to
@@ -1069,15 +1068,15 @@ added to bibliography.
1071.B \f[C]\-\-csl=\f[]\f[I]FILE\f[]
1070.B \f[C]\-\-csl=\f[]\f[I]FILE\f[]
1072−Set the \f[C]csl\f[] field in the document\[aq]s metadata to
1071+Set the \f[C]csl\f[] field in the document's metadata to \f[I]FILE\f[],
1073−\f[I]FILE\f[], overriding any value set in the metadata.
1072+overriding any value set in the metadata.
1074(This is equivalent to \f[C]\-\-metadata\ csl=FILE\f[].) This option is
1073(This is equivalent to \f[C]\-\-metadata\ csl=FILE\f[].) This option is
1075only relevant with \f[C]pandoc\-citeproc\f[].
1074only relevant with \f[C]pandoc\-citeproc\f[].
1079.B \f[C]\-\-citation\-abbreviations=\f[]\f[I]FILE\f[]
1078.B \f[C]\-\-citation\-abbreviations=\f[]\f[I]FILE\f[]
1080−Set the \f[C]citation\-abbreviations\f[] field in the document\[aq]s
1079+Set the \f[C]citation\-abbreviations\f[] field in the document's
1081metadata to \f[I]FILE\f[], overriding any value set in the metadata.
1080metadata to \f[I]FILE\f[], overriding any value set in the metadata.
1082(This is equivalent to
1081(This is equivalent to
1083\f[C]\-\-metadata\ citation\-abbreviations=FILE\f[].) This option is
1082\f[C]\-\-metadata\ citation\-abbreviations=FILE\f[].) This option is
@@ -1164,7 +1163,7 @@ to images.
1164The formula will be concatenated with the URL provided.
1163The formula will be concatenated with the URL provided.
1165If \f[I]URL\f[] is not specified, the CodeCogs will be used.
1164If \f[I]URL\f[] is not specified, the CodeCogs will be used.
1166Note: the \f[C]\-\-webtex\f[] option will affect Markdown output as well
1165Note: the \f[C]\-\-webtex\f[] option will affect Markdown output as well
1167−as HTML, which is useful if you\[aq]re targeting a version of Markdown
1166+as HTML, which is useful if you're targeting a version of Markdown
1168without native math support.
1167without native math support.
@@ -1345,7 +1344,7 @@ body of document
1347.B \f[C]meta\-json\f[]
1346.B \f[C]meta\-json\f[]
1348−JSON representation of all of the document\[aq]s metadata
1347+JSON representation of all of the document's metadata
1351.SS Language variables
1350.SS Language variables
@@ -1387,8 +1386,8 @@ For bidirectional documents, native pandoc \f[C]span\f[]s and
1387\f[C]div\f[]s with the \f[C]dir\f[] attribute (value \f[C]rtl\f[] or
1386\f[C]div\f[]s with the \f[C]dir\f[] attribute (value \f[C]rtl\f[] or
1388\f[C]ltr\f[]) can be used to override the base direction in some output
1387\f[C]ltr\f[]) can be used to override the base direction in some output
1390−This may not always be necessary if the final renderer (e.g.
1389+This may not always be necessary if the final renderer (e.g.\ the
1391−the browser, when generating HTML) supports the Unicode Bidirectional
1390+browser, when generating HTML) supports the Unicode Bidirectional
1392Algorithm.
1391Algorithm.
1394When using LaTeX for bidirectional documents, only the \f[C]xelatex\f[]
1393When using LaTeX for bidirectional documents, only the \f[C]xelatex\f[]
@@ -1438,8 +1437,8 @@ controls navigation symbols in \f[C]beamer\f[] documents (default is
1440.B \f[C]section\-titles\f[]
1439.B \f[C]section\-titles\f[]
1441−enables on "title pages" for new sections in \f[C]beamer\f[] documents
1440+enables on \[lq]title pages\[rq] for new sections in \f[C]beamer\f[]
1442−(default = true).
1441+documents (default = true).
@@ -1548,6 +1547,11 @@ font encodings)
1550+.B \f[C]microtypeoptions\f[]
1551+options to pass to the microtype package
1551.B \f[C]colorlinks\f[]
1555.B \f[C]colorlinks\f[]
1552add color to link text; automatically enabled if any of
1556add color to link text; automatically enabled if any of
1553\f[C]linkcolor\f[], \f[C]citecolor\f[], \f[C]urlcolor\f[], or
1557\f[C]linkcolor\f[], \f[C]citecolor\f[], \f[C]urlcolor\f[], or
@@ -1814,10 +1818,10 @@ We recommend tracking the changes in the default templates, and
1814modifying your custom templates accordingly.
1818modifying your custom templates accordingly.
1815An easy way to do this is to fork the pandoc\-templates repository and
1819An easy way to do this is to fork the pandoc\-templates repository and
1816merge in changes after each pandoc release.
1820merge in changes after each pandoc release.
1817−.SH PANDOC\[aq]S MARKDOWN
1821+.SH PANDOC'S MARKDOWN
1819Pandoc understands an extended and slightly revised version of John
1823Pandoc understands an extended and slightly revised version of John
1820−Gruber\[aq]s Markdown syntax.
1824+Gruber's Markdown syntax.
1821This document explains the syntax, noting differences from standard
1825This document explains the syntax, noting differences from standard
1822Markdown.
1826Markdown.
1823Except where noted, these differences can be suppressed by using the
1827Except where noted, these differences can be suppressed by using the
@@ -1826,7 +1830,7 @@ An extensions can be enabled by adding \f[C]+EXTENSION\f[] to the format
1826name and disabled by adding \f[C]\-EXTENSION\f[].
1830name and disabled by adding \f[C]\-EXTENSION\f[].
1827For example, \f[C]markdown_strict+footnotes\f[] is strict Markdown with
1831For example, \f[C]markdown_strict+footnotes\f[] is strict Markdown with
1828footnotes enabled, while \f[C]markdown\-footnotes\-pipe_tables\f[] is
1832footnotes enabled, while \f[C]markdown\-footnotes\-pipe_tables\f[] is
1829−pandoc\[aq]s Markdown without footnotes or pipe tables.
1833+pandoc's Markdown without footnotes or pipe tables.
1830.SS Philosophy
1834.SS Philosophy
1832Markdown is designed to be easy to write, and, even more importantly,
1836Markdown is designed to be easy to write, and, even more importantly,
@@ -1834,16 +1838,16 @@ easy to read:
1836A Markdown\-formatted document should be publishable as\-is, as plain
1840A Markdown\-formatted document should be publishable as\-is, as plain
1837−text, without looking like it\[aq]s been marked up with tags or
1841+text, without looking like it's been marked up with tags or formatting
1838−formatting instructions.
1842+instructions.
1839−\-\- John Gruber
1843+\[en] John Gruber
1842−This principle has guided pandoc\[aq]s decisions in finding syntax for
1846+This principle has guided pandoc's decisions in finding syntax for
1843tables, footnotes, and other extensions.
1847tables, footnotes, and other extensions.
1845−There is, however, one respect in which pandoc\[aq]s aims are different
1849+There is, however, one respect in which pandoc's aims are different from
1846−from the original aims of Markdown.
1850+the original aims of Markdown.
1847Whereas Markdown was originally designed with HTML generation in mind,
1851Whereas Markdown was originally designed with HTML generation in mind,
1848pandoc is designed for multiple output formats.
1852pandoc is designed for multiple output formats.
1849Thus, while pandoc allows the embedding of raw HTML, it discourages it,
1853Thus, while pandoc allows the embedding of raw HTML, it discourages it,
@@ -1867,8 +1871,8 @@ a hard line break, since trailing spaces in the cells are ignored.
1867There are two kinds of headers: Setext and ATX.
1871There are two kinds of headers: Setext and ATX.
1868.SS Setext\-style headers
1872.SS Setext\-style headers
1870−A setext\-style header is a line of text "underlined" with a row of
1874+A setext\-style header is a line of text \[lq]underlined\[rq] with a row
1871−\f[C]=\f[] signs (for a level one header) or \f[C]\-\f[] signs (for a
1875+of \f[C]=\f[] signs (for a level one header) or \f[C]\-\f[] signs (for a
1872level two header):
1876level two header):
@@ -1950,7 +1954,7 @@ My\ other\ header\ \ \ {#foo}
1950(This syntax is compatible with PHP Markdown Extra.)
1954(This syntax is compatible with PHP Markdown Extra.)
1952Note that although this syntax allows assignment of classes and
1956Note that although this syntax allows assignment of classes and
1953−key/value attributes, writers generally don\[aq]t use all of this
1957+key/value attributes, writers generally don't use all of this
1954information.
1958information.
1955Identifiers, classes, and key/value attributes are used in HTML and
1959Identifiers, classes, and key/value attributes are used in HTML and
1956HTML\-based formats such as EPUB and slidy.
1960HTML\-based formats such as EPUB and slidy.
@@ -2149,8 +2153,8 @@ indented more than three spaces.)
2152−A "lazy" form, which requires the \f[C]>\f[] character only on the first
2156+A \[lq]lazy\[rq] form, which requires the \f[C]>\f[] character only on
2153−line of each block, is also allowed:
2157+the first line of each block, is also allowed:
@@ -2378,8 +2382,8 @@ Here is a simple example:
2381−This will produce a "compact" list.
2385+This will produce a \[lq]compact\[rq] list.
2382−If you want a "loose" list, in which each item is formatted as a
2386+If you want a \[lq]loose\[rq] list, in which each item is formatted as a
2383paragraph, put spaces between the items:
2387paragraph, put spaces between the items:
@@ -2407,7 +2411,7 @@ List items look best if subsequent lines are flush with the first line
2410−But Markdown also allows a "lazy" format:
2414+But Markdown also allows a \[lq]lazy\[rq] format:
@@ -2456,8 +2460,8 @@ The nested list must be indented four spaces or one tab:
2459−As noted above, Markdown allows you to write list items "lazily,"
2463+As noted above, Markdown allows you to write list items
2460−instead of indenting continuation lines.
2464+\[lq]lazily,\[rq] instead of indenting continuation lines.
2461However, if there are multiple paragraphs or other blocks in a list
2465However, if there are multiple paragraphs or other blocks in a list
2462item, the first line of each must be indented.
2466item, the first line of each must be indented.
@@ -2523,8 +2527,8 @@ They must be separated from the text that follows by at least one space,
2523and, if the list marker is a capital letter with a period, by at least
2527and, if the list marker is a capital letter with a period, by at least
2524two spaces.
2528two spaces.
2526−The \f[C]fancy_lists\f[] extension also allows \[aq]\f[C]#\f[]\[aq] to
2530+The \f[C]fancy_lists\f[] extension also allows `\f[C]#\f[]' to be used
2527−be used as an ordered list marker in place of a numeral:
2531+as an ordered list marker in place of a numeral:
@@ -2606,8 +2610,9 @@ one or more block elements (paragraph, code block, list, etc.), each
2606indented four spaces or one tab stop.
2610indented four spaces or one tab stop.
2607The body of the definition (including the first line, aside from the
2611The body of the definition (including the first line, aside from the
2608colon or tilde) should be indented four spaces.
2612colon or tilde) should be indented four spaces.
2609−However, as with other Markdown lists, you can "lazily" omit indentation
2613+However, as with other Markdown lists, you can \[lq]lazily\[rq] omit
2610−except at the beginning of a paragraph or other block element:
2614+indentation except at the beginning of a paragraph or other block
@@ -2639,16 +2644,16 @@ Term\ 2
2641Note that space between items in a definition list is required.
2646Note that space between items in a definition list is required.
2642−(A variant that loosens this requirement, but disallows "lazy" hard
2647+(A variant that loosens this requirement, but disallows \[lq]lazy\[rq]
2643−wrapping, can be activated with \f[C]compact_definition_lists\f[]: see
2648+hard wrapping, can be activated with \f[C]compact_definition_lists\f[]:
2644−Non\-pandoc extensions, below.)
2649+see Non\-pandoc extensions, below.)
2645.SS Numbered example lists
2650.SS Numbered example lists
2646.SS Extension: \f[C]example_lists\f[]
2651.SS Extension: \f[C]example_lists\f[]
2648The special list marker \f[C]\@\f[] can be used for sequentially
2653The special list marker \f[C]\@\f[] can be used for sequentially
2649numbered examples.
2654numbered examples.
2650−The first list item with a \f[C]\@\f[] marker will be numbered
2655+The first list item with a \f[C]\@\f[] marker will be numbered `1', the
2651−\[aq]1\[aq], the next \[aq]2\[aq], and so on, throughout the document.
2656+next `2', and so on, throughout the document.
2652The numbered examples need not occur in a single list; each new list
2657The numbered examples need not occur in a single list; each new list
2653using \f[C]\@\f[] will take up where the last stopped.
2658using \f[C]\@\f[] will take up where the last stopped.
2654So, for example:
2659So, for example:
@@ -2679,8 +2684,8 @@ The label can be any string of alphanumeric characters, underscores, or
2680.SS Compact and loose lists
2685.SS Compact and loose lists
2682−Pandoc behaves differently from \f[C]Markdown.pl\f[] on some "edge
2687+Pandoc behaves differently from \f[C]Markdown.pl\f[] on some \[lq]edge
2683−cases" involving lists.
2688+cases\[rq] involving lists.
2684Consider this source:
2689Consider this source:
@@ -2695,14 +2700,15 @@ Consider this source:
2698−Pandoc transforms this into a "compact list" (with no \f[C]<p>\f[] tags
2703+Pandoc transforms this into a \[lq]compact list\[rq] (with no
2704+\f[C]<p>\f[] tags around \[lq]First\[rq], \[lq]Second\[rq], or
2699−around "First", "Second", or "Third"), while Markdown puts \f[C]<p>\f[]
2705+\[lq]Third\[rq]), while Markdown puts \f[C]<p>\f[] tags around
2700−tags around "Second" and "Third" (but not "First"), because of the blank
2706+\[lq]Second\[rq] and \[lq]Third\[rq] (but not \[lq]First\[rq]), because
2701−space around "Third".
2707+of the blank space around \[lq]Third\[rq].
2702Pandoc follows a simple rule: if the text is followed by a blank line,
2708Pandoc follows a simple rule: if the text is followed by a blank line,
2703it is treated as a paragraph.
2709it is treated as a paragraph.
2704−Since "Second" is followed by a list, and not a blank line, it isn\[aq]t
2710+Since \[lq]Second\[rq] is followed by a list, and not a blank line, it
2705−treated as a paragraph.
2711+isn't treated as a paragraph.
2706The fact that the list is followed by a blank line is irrelevant.
2712The fact that the list is followed by a blank line is irrelevant.
2707(Note: Pandoc works this way even when the \f[C]markdown_strict\f[]
2713(Note: Pandoc works this way even when the \f[C]markdown_strict\f[]
2708format is specified.
2714format is specified.
@@ -2726,9 +2732,9 @@ Trouble! Here pandoc (like other Markdown implementations) will treat
2726\f[C]{\ my\ code\ block\ }\f[] as the second paragraph of item two, and
2732\f[C]{\ my\ code\ block\ }\f[] as the second paragraph of item two, and
2727not as a code block.
2733not as a code block.
2729−To "cut off" the list after item two, you can insert some non\-indented
2735+To \[lq]cut off\[rq] the list after item two, you can insert some
2730−content, like an HTML comment, which won\[aq]t produce visible output in
2736+non\-indented content, like an HTML comment, which won't produce visible
2731−any format:
2737+output in any format:
@@ -2992,7 +2998,7 @@ wrap, with the relative cell widths determined by the widths of the
2992separator lines.
2998separator lines.
2994Note: pandoc also recognizes pipe tables of the following form, as can
3000Note: pandoc also recognizes pipe tables of the following form, as can
2995−be produced by Emacs\[aq] orgtbl\-mode:
3001+be produced by Emacs' orgtbl\-mode:
@@ -3005,8 +3011,8 @@ be produced by Emacs\[aq] orgtbl\-mode:
3006The difference is that \f[C]+\f[] is used instead of \f[C]|\f[].
3012The difference is that \f[C]+\f[] is used instead of \f[C]|\f[].
3007Other orgtbl features are not supported.
3013Other orgtbl features are not supported.
3008−In particular, to get non\-default column alignment, you\[aq]ll need to
3014+In particular, to get non\-default column alignment, you'll need to add
3009−add colons as above.
3015+colons as above.
3010.SS Metadata blocks
3016.SS Metadata blocks
3011.SS Extension: \f[C]pandoc_title_block\f[]
3017.SS Extension: \f[C]pandoc_title_block\f[]
@@ -3071,13 +3077,13 @@ All three metadata fields may contain standard inline formatting
3072Title blocks will always be parsed, but they will affect the output only
3078Title blocks will always be parsed, but they will affect the output only
3073when the \f[C]\-\-standalone\f[] (\f[C]\-s\f[]) option is chosen.
3079when the \f[C]\-\-standalone\f[] (\f[C]\-s\f[]) option is chosen.
3074−In HTML output, titles will appear twice: once in the document head \-\-
3080+In HTML output, titles will appear twice: once in the document head
3075−this is the title that will appear at the top of the window in a browser
3081+\[en] this is the title that will appear at the top of the window in a
3076−\-\- and once at the beginning of the document body.
3082+browser \[en] and once at the beginning of the document body.
3077The title in the document head can have an optional prefix attached
3083The title in the document head can have an optional prefix attached
3078(\f[C]\-\-title\-prefix\f[] or \f[C]\-T\f[] option).
3084(\f[C]\-\-title\-prefix\f[] or \f[C]\-T\f[] option).
3079−The title in the body appears as an H1 element with class "title", so it
3085+The title in the body appears as an H1 element with class
3080−can be suppressed or reformatted with CSS.
3086+\[lq]title\[rq], so it can be suppressed or reformatted with CSS.
3081If a title prefix is specified with \f[C]\-T\f[] and no title block
3087If a title prefix is specified with \f[C]\-T\f[] and no title block
3082appears in the document, the title prefix will be used by itself as the
3088appears in the document, the title prefix will be used by itself as the
3083HTML title.
3089HTML title.
@@ -3106,7 +3112,7 @@ will yield a man page with the title \f[C]PANDOC\f[] and section 1.
3109−will also have "Pandoc User Manuals" in the footer.
3115+will also have \[lq]Pandoc User Manuals\[rq] in the footer.
@@ -3114,7 +3120,7 @@ will also have "Pandoc User Manuals" in the footer.
3117−will also have "Version 4.0" in the header.
3123+will also have \[lq]Version 4.0\[rq] in the header.
3118.SS Extension: \f[C]yaml_metadata_block\f[]
3124.SS Extension: \f[C]yaml_metadata_block\f[]
3120A YAML metadata block is a valid YAML object, delimited by a line of
3126A YAML metadata block is a valid YAML object, delimited by a line of
@@ -3253,7 +3259,7 @@ instead of
3256−This rule is easier to remember than standard Markdown\[aq]s rule, which
3262+This rule is easier to remember than standard Markdown's rule, which
3257allows only the following characters to be backslash\-escaped:
3263allows only the following characters to be backslash\-escaped:
@@ -3269,12 +3275,11 @@ A backslash\-escaped space is parsed as a nonbreaking space.
3269It will appear in TeX output as \f[C]~\f[] and in HTML and XML as
3275It will appear in TeX output as \f[C]~\f[] and in HTML and XML as
3270\f[C]\\ \f[] or \f[C]\\ \f[].
3276\f[C]\\ \f[] or \f[C]\\ \f[].
3272−A backslash\-escaped newline (i.e.
3278+A backslash\-escaped newline (i.e.\ a backslash occurring at the end of
3273−a backslash occurring at the end of a line) is parsed as a hard line
3279+a line) is parsed as a hard line break.
3275It will appear in TeX output as \f[C]\\\\\f[] and in HTML as
3280It will appear in TeX output as \f[C]\\\\\f[] and in HTML as
3276\f[C]<br\ />\f[].
3281\f[C]<br\ />\f[].
3277−This is a nice alternative to Markdown\[aq]s "invisible" way of
3282+This is a nice alternative to Markdown's \[lq]invisible\[rq] way of
3278indicating hard line breaks using two trailing spaces on a line.
3283indicating hard line breaks using two trailing spaces on a line.
3280Backslash escapes do not work in verbatim contexts.
3285Backslash escapes do not work in verbatim contexts.
@@ -3286,7 +3291,7 @@ typographically correct output, converting straight quotes to curly
3286quotes, \f[C]\-\-\-\f[] to em\-dashes, \f[C]\-\-\f[] to en\-dashes, and
3291quotes, \f[C]\-\-\-\f[] to em\-dashes, \f[C]\-\-\f[] to en\-dashes, and
3287\f[C]\&...\f[] to ellipses.
3292\f[C]\&...\f[] to ellipses.
3288Nonbreaking spaces are inserted after certain abbreviations, such as
3293Nonbreaking spaces are inserted after certain abbreviations, such as
3289−"Mr."
3294+\[lq]Mr.\[rq]
3291Note: if your LaTeX template or any included header file call for the
3296Note: if your LaTeX template or any included header file call for the
3292\f[C]csquotes\f[] package, pandoc will detect this automatically and use
3297\f[C]csquotes\f[] package, pandoc will detect this automatically and use
@@ -3362,8 +3367,8 @@ If the superscripted or subscripted text contains spaces, these spaces
3362must be escaped with backslashes.
3367must be escaped with backslashes.
3363(This is to prevent accidental superscripting and subscripting through
3368(This is to prevent accidental superscripting and subscripting through
3364the ordinary use of \f[C]~\f[] and \f[C]^\f[].) Thus, if you want the
3369the ordinary use of \f[C]~\f[] and \f[C]^\f[].) Thus, if you want the
3365−letter P with \[aq]a cat\[aq] in subscripts, use \f[C]P~a\\\ cat~\f[],
3370+letter P with `a cat' in subscripts, use \f[C]P~a\\\ cat~\f[], not
3366−not \f[C]P~a\ cat~\f[].
3371+\f[C]P~a\ cat~\f[].
3367.SS Verbatim
3372.SS Verbatim
3369To make a short span of text verbatim, put it inside backticks:
3374To make a short span of text verbatim, put it inside backticks:
@@ -3435,9 +3440,9 @@ The opening \f[C]$\f[] must have a non\-space character immediately to
3435its right, while the closing \f[C]$\f[] must have a non\-space character
3440its right, while the closing \f[C]$\f[] must have a non\-space character
3436immediately to its left, and must not be followed immediately by a
3441immediately to its left, and must not be followed immediately by a
3438−Thus, \f[C]$20,000\ and\ $30,000\f[] won\[aq]t parse as math.
3443+Thus, \f[C]$20,000\ and\ $30,000\f[] won't parse as math.
3439If for some reason you need to enclose text in literal \f[C]$\f[]
3444If for some reason you need to enclose text in literal \f[C]$\f[]
3440−characters, backslash\-escape them and they won\[aq]t be treated as math
3445+characters, backslash\-escape them and they won't be treated as math
3441delimiters.
3446delimiters.
3443TeX math will be printed in all output formats.
3448TeX math will be printed in all output formats.
@@ -3464,7 +3469,7 @@ It will be rendered inside a \f[C]\@math\f[] command.
3466.B groff man
3471.B groff man
3467−It will be rendered verbatim without \f[C]$\f[]\[aq]s.
3472+It will be rendered verbatim without \f[C]$\f[]'s.
@@ -3578,9 +3583,9 @@ DZSlides, EPUB, Markdown, Emacs Org mode, and Textile output, and
3578suppressed in other formats.
3583suppressed in other formats.
3579.SS Extension: \f[C]markdown_in_html_blocks\f[]
3584.SS Extension: \f[C]markdown_in_html_blocks\f[]
3581−Standard Markdown allows you to include HTML "blocks": blocks of HTML
3586+Standard Markdown allows you to include HTML \[lq]blocks\[rq]: blocks of
3582−between balanced tags that are separated from the surrounding text with
3587+HTML between balanced tags that are separated from the surrounding text
3583−blank lines, and start and end at the left margin.
3588+with blank lines, and start and end at the left margin.
3584Within these blocks, everything is interpreted as HTML, not Markdown; so
3589Within these blocks, everything is interpreted as HTML, not Markdown; so
3585(for example), \f[C]*\f[] does not signify emphasis.
3590(for example), \f[C]*\f[] does not signify emphasis.
@@ -3848,7 +3853,7 @@ slide shows and EPUB), LaTeX, and ConTeXt.
3848.SS Images
3853.SS Images
3850A link immediately preceded by a \f[C]!\f[] will be treated as an image.
3855A link immediately preceded by a \f[C]!\f[] will be treated as an image.
3851−The link text will be used as the image\[aq]s alt text:
3856+The link text will be used as the image's alt text:
@@ -3865,7 +3870,7 @@ An image occurring by itself in a paragraph will be rendered as a figure
3865with a caption. (In LaTeX, a figure environment will be used; in HTML,
3870with a caption. (In LaTeX, a figure environment will be used; in HTML,
3866the image will be placed in a \f[C]div\f[] with class \f[C]figure\f[],
3871the image will be placed in a \f[C]div\f[] with class \f[C]figure\f[],
3867together with a caption in a \f[C]p\f[] with class \f[C]caption\f[].)
3872together with a caption in a \f[C]p\f[] with class \f[C]caption\f[].)
3868−The image\[aq]s alt text will be used as the caption.
3873+The image's alt text will be used as the caption.
@@ -3952,7 +3957,7 @@ attributes:
3952.SS Footnotes
3957.SS Footnotes
3953.SS Extension: \f[C]footnotes\f[]
3958.SS Extension: \f[C]footnotes\f[]
3955−Pandoc\[aq]s Markdown allows footnotes, using the following syntax:
3960+Pandoc's Markdown allows footnotes, using the following syntax:
@@ -3984,6 +3989,8 @@ the note itself; in the output, footnotes will be numbered sequentially.
3984The footnotes themselves need not be placed at the end of the document.
3989The footnotes themselves need not be placed at the end of the document.
3985They may appear anywhere except inside other block elements (lists,
3990They may appear anywhere except inside other block elements (lists,
3986block quotes, tables, etc.).
3991block quotes, tables, etc.).
3992+Each footnote should be separated from surrounding content (including
3993+other footnotes) by blank lines.
3987.SS Extension: \f[C]inline_notes\f[]
3994.SS Extension: \f[C]inline_notes\f[]
3989Inline footnotes are also allowed (though, unlike regular notes, they
3996Inline footnotes are also allowed (though, unlike regular notes, they
@@ -4134,7 +4141,7 @@ JSON and CSL YAML formats as far as possible.
4134As an alternative to specifying a bibliography file using
4141As an alternative to specifying a bibliography file using
4135\f[C]\-\-bibliography\f[] or the YAML metadata field
4142\f[C]\-\-bibliography\f[] or the YAML metadata field
4136\f[C]bibliography\f[], you can include the citation data directly in the
4143\f[C]bibliography\f[], you can include the citation data directly in the
4137−\f[C]references\f[] field of the document\[aq]s YAML metadata.
4144+\f[C]references\f[] field of the document's YAML metadata.
4138The field should contain an array of YAML\-encoded references, for
4145The field should contain an array of YAML\-encoded references, for
@@ -4184,7 +4191,7 @@ To make your citations hyperlinks to the corresponding bibliography
4184entries, add \f[C]link\-citations:\ true\f[] to your YAML metadata.
4191entries, add \f[C]link\-citations:\ true\f[] to your YAML metadata.
4186Citations go inside square brackets and are separated by semicolons.
4193Citations go inside square brackets and are separated by semicolons.
4187−Each citation must have a key, composed of \[aq]\@\[aq] + the citation
4194+Each citation must have a key, composed of `\@' + the citation
4188identifier from the database, and may optionally have a prefix, a
4195identifier from the database, and may optionally have a prefix, a
4189locator, and a suffix.
4196locator, and a suffix.
4190The citation key must begin with a letter, digit, or \f[C]_\f[], and may
4197The citation key must begin with a letter, digit, or \f[C]_\f[], and may
@@ -4219,7 +4226,7 @@ singular or plural forms, as \f[C]book\f[], \f[C]bk.\f[]/\f[C]bks.\f[];
4219\f[C]s.v.\f[]/\f[C]s.vv.\f[]; \f[C]verse\f[], \f[C]v.\f[]/\f[C]vv.\f[];
4226\f[C]s.v.\f[]/\f[C]s.vv.\f[]; \f[C]verse\f[], \f[C]v.\f[]/\f[C]vv.\f[];
4220\f[C]volume\f[], \f[C]vol.\f[]/\f[C]vols.\f[]; \f[C]¶\f[]/\f[C]¶¶\f[];
4227\f[C]volume\f[], \f[C]vol.\f[]/\f[C]vols.\f[]; \f[C]¶\f[]/\f[C]¶¶\f[];
4221\f[C]§\f[]/\f[C]§§\f[].
4228\f[C]§\f[]/\f[C]§§\f[].
4222−If no locator term is used, "page" is assumed.
4229+If no locator term is used, \[lq]page\[rq] is assumed.
4224A minus sign (\f[C]\-\f[]) before the \f[C]\@\f[] will suppress mention
4231A minus sign (\f[C]\-\f[]) before the \f[C]\@\f[] will suppress mention
4225of the author in the citation.
4232of the author in the citation.
@@ -4276,6 +4283,18 @@ In this example, the document will contain a citation for \f[C]item3\f[]
4276only, but the bibliography will contain entries for \f[C]item1\f[],
4283only, but the bibliography will contain entries for \f[C]item1\f[],
4277\f[C]item2\f[], and \f[C]item3\f[].
4284\f[C]item2\f[], and \f[C]item3\f[].
4286+It is possible to create a bibliography with all the citations, whether
4287+or not they appear in the document, by using a wildcard:
4279For LaTeX or PDF output, you can also use \f[C]natbib\f[] or
4298For LaTeX or PDF output, you can also use \f[C]natbib\f[] or
4280\f[C]biblatex\f[] to render bibliography.
4299\f[C]biblatex\f[] to render bibliography.
4281In order to do so, specify bibliography files as outlined above, and add
4300In order to do so, specify bibliography files as outlined above, and add
@@ -4296,7 +4315,7 @@ hard line breaks.
4297Allow \f[C]<\f[] and \f[C]>\f[] to be backslash\-escaped, as they can be
4316Allow \f[C]<\f[] and \f[C]>\f[] to be backslash\-escaped, as they can be
4298in GitHub flavored Markdown but not original Markdown.
4317in GitHub flavored Markdown but not original Markdown.
4299−This is implied by pandoc\[aq]s default \f[C]all_symbols_escapable\f[].
4318+This is implied by pandoc's default \f[C]all_symbols_escapable\f[].
4300.SS Extension: \f[C]lists_without_preceding_blankline\f[]
4319.SS Extension: \f[C]lists_without_preceding_blankline\f[]
4302Allow a list to occur right after a paragraph, with no intervening blank
4321Allow a list to occur right after a paragraph, with no intervening blank
@@ -4410,15 +4429,15 @@ in several respects:
4410No blank line is required between consecutive items of the definition
4429No blank line is required between consecutive items of the definition
4412.IP \[bu] 2
4431.IP \[bu] 2
4413−To get a "tight" or "compact" list, omit space between consecutive
4432+To get a \[lq]tight\[rq] or \[lq]compact\[rq] list, omit space between
4414−items; the space between a term and its definition does not affect
4433+consecutive items; the space between a term and its definition does not
4415−anything.
4434+affect anything.
4416.IP \[bu] 2
4435.IP \[bu] 2
4417Lazy wrapping of paragraphs is not allowed: the entire definition must
4436Lazy wrapping of paragraphs is not allowed: the entire definition must
4418be indented four spaces.
4437be indented four spaces.
4419.SS Markdown variants
4438.SS Markdown variants
4421−In addition to pandoc\[aq]s extended Markdown, the following Markdown
4440+In addition to pandoc's extended Markdown, the following Markdown
4422variants are supported:
4441variants are supported:
4424.B \f[C]markdown_phpextra\f[] (PHP Markdown Extra)
4443.B \f[C]markdown_phpextra\f[] (PHP Markdown Extra)
@@ -4475,8 +4494,7 @@ There are five ways to do this, using S5, DZSlides, Slidy, Slideous, or
4475reveal.js.
4494reveal.js.
4476You can also produce a PDF slide show using LaTeX \f[C]beamer\f[].
4495You can also produce a PDF slide show using LaTeX \f[C]beamer\f[].
4478−Here\[aq]s the Markdown source for a simple slide show,
4497+Here's the Markdown source for a simple slide show, \f[C]habits.txt\f[]:
4479−\f[C]habits.txt\f[]:
@@ -4571,17 +4589,17 @@ A header at the slide level always starts a new slide.
4571Headers \f[I]below\f[] the slide level in the hierarchy create headers
4589Headers \f[I]below\f[] the slide level in the hierarchy create headers
4572\f[I]within\f[] a slide.
4590\f[I]within\f[] a slide.
4573.IP \[bu] 2
4591.IP \[bu] 2
4574−Headers \f[I]above\f[] the slide level in the hierarchy create "title
4592+Headers \f[I]above\f[] the slide level in the hierarchy create
4575−slides," which just contain the section title and help to break the
4593+\[lq]title slides,\[rq] which just contain the section title and help to
4576−slide show into sections.
4594+break the slide show into sections.
4577.IP \[bu] 2
4595.IP \[bu] 2
4578−A title page is constructed automatically from the document\[aq]s title
4596+A title page is constructed automatically from the document's title
4579block, if present.
4597block, if present.
4580(In the case of beamer, this can be disabled by commenting out some
4598(In the case of beamer, this can be disabled by commenting out some
4581lines in the default template.)
4599lines in the default template.)
4583These rules are designed to support many different styles of slide show.
4601These rules are designed to support many different styles of slide show.
4584−If you don\[aq]t care about structuring your slides into sections and
4602+If you don't care about structuring your slides into sections and
4585subsections, you can just use level 1 headers for all each slide.
4603subsections, you can just use level 1 headers for all each slide.
4586(In that case, level 1 will be the slide level.) But you can also
4604(In that case, level 1 will be the slide level.) But you can also
4587structure the slide show into sections, as in the example above.
4605structure the slide show into sections, as in the example above.
@@ -4593,9 +4611,9 @@ It is not recommended that you use deeper nesting of section levels with
4593reveal.js.
4611reveal.js.
4594.SS Incremental lists
4612.SS Incremental lists
4596−By default, these writers produce lists that display "all at once." If
4614+By default, these writers produce lists that display \[lq]all at
4597−you want your lists to display incrementally (one item at a time), use
4615+once.\[rq] If you want your lists to display incrementally (one item at
4598−the \f[C]\-i\f[] option.
4616+a time), use the \f[C]\-i\f[] option.
4599If you want a particular list to depart from the default (that is, to
4617If you want a particular list to depart from the default (that is, to
4600display incrementally without the \f[C]\-i\f[] option and all at once
4618display incrementally without the \f[C]\-i\f[] option and all at once
4601with the \f[C]\-i\f[] option), put it in a block quote:
4619with the \f[C]\-i\f[] option), put it in a block quote:
@@ -4611,8 +4629,8 @@ In this way incremental and nonincremental lists can be mixed in a
4611single document.
4629single document.
4612.SS Inserting pauses
4630.SS Inserting pauses
4614−You can add "pauses" within a slide by including a paragraph containing
4632+You can add \[lq]pauses\[rq] within a slide by including a paragraph
4615−three dots, separated by spaces:
4633+containing three dots, separated by spaces:
@@ -4632,8 +4650,8 @@ in \f[C]$DATADIR/s5/default\f[] (for S5), \f[C]$DATADIR/slidy\f[] (for
4632Slidy), or \f[C]$DATADIR/slideous\f[] (for Slideous), where
4650Slidy), or \f[C]$DATADIR/slideous\f[] (for Slideous), where
4633\f[C]$DATADIR\f[] is the user data directory (see
4651\f[C]$DATADIR\f[] is the user data directory (see
4634\f[C]\-\-data\-dir\f[], above).
4652\f[C]\-\-data\-dir\f[], above).
4635−The originals may be found in pandoc\[aq]s system data directory
4653+The originals may be found in pandoc's system data directory (generally
4636−(generally \f[C]$CABALDIR/pandoc\-VERSION/s5/default\f[]).
4654+\f[C]$CABALDIR/pandoc\-VERSION/s5/default\f[]).
4637Pandoc will look there for any files it does not find in the user data
4655Pandoc will look there for any files it does not find in the user data
4638directory.
4656directory.
@@ -4712,7 +4730,7 @@ introducing the slide:
4714All of the other frame attributes described in Section 8.1 of the Beamer
4732All of the other frame attributes described in Section 8.1 of the Beamer
4715−User\[aq]s Guide may also be used: \f[C]allowdisplaybreaks\f[],
4733+User's Guide may also be used: \f[C]allowdisplaybreaks\f[],
4716\f[C]allowframebreaks\f[], \f[C]b\f[], \f[C]c\f[], \f[C]t\f[],
4734\f[C]allowframebreaks\f[], \f[C]b\f[], \f[C]c\f[], \f[C]t\f[],
4717\f[C]environment\f[], \f[C]label\f[], \f[C]plain\f[], \f[C]shrink\f[].
4735\f[C]environment\f[], \f[C]label\f[], \f[C]plain\f[], \f[C]shrink\f[].
4718.SH CREATING EPUBS WITH PANDOC
4736.SH CREATING EPUBS WITH PANDOC
@@ -4771,8 +4789,8 @@ Valid values for \f[C]type\f[] are \f[C]main\f[], \f[C]subtitle\f[],
4771Either a string value, or an object with fields \f[C]role\f[],
4789Either a string value, or an object with fields \f[C]role\f[],
4772\f[C]file\-as\f[], and \f[C]text\f[], or a list of such objects.
4790\f[C]file\-as\f[], and \f[C]text\f[], or a list of such objects.
4773Valid values for \f[C]role\f[] are MARC relators, but pandoc will
4791Valid values for \f[C]role\f[] are MARC relators, but pandoc will
4774−attempt to translate the human\-readable versions (like "author" and
4792+attempt to translate the human\-readable versions (like \[lq]author\[rq]
4775−"editor") to the appropriate marc relators.
4793+and \[lq]editor\[rq]) to the appropriate marc relators.
@@ -4873,24 +4891,23 @@ output; \f[C]beamer\f[], \f[C]html\f[] or \f[C]html5\f[] for output
4873only), pandoc will treat the document as literate Haskell source.
4891only), pandoc will treat the document as literate Haskell source.
4874This means that
4892This means that
4875.IP \[bu] 2
4893.IP \[bu] 2
4876−In Markdown input, "bird track" sections will be parsed as Haskell code
4894+In Markdown input, \[lq]bird track\[rq] sections will be parsed as
4877−rather than block quotations.
4895+Haskell code rather than block quotations.
4878Text between \f[C]\\begin{code}\f[] and \f[C]\\end{code}\f[] will also
4896Text between \f[C]\\begin{code}\f[] and \f[C]\\end{code}\f[] will also
4879be treated as Haskell code.
4897be treated as Haskell code.
4880−For ATX\-style headers the character \[aq]=\[aq] will be used instead of
4898+For ATX\-style headers the character `=' will be used instead of `#'.
4882.IP \[bu] 2
4899.IP \[bu] 2
4883In Markdown output, code blocks with classes \f[C]haskell\f[] and
4900In Markdown output, code blocks with classes \f[C]haskell\f[] and
4884\f[C]literate\f[] will be rendered using bird tracks, and block
4901\f[C]literate\f[] will be rendered using bird tracks, and block
4885quotations will be indented one space, so they will not be treated as
4902quotations will be indented one space, so they will not be treated as
4886Haskell code.
4903Haskell code.
4887In addition, headers will be rendered setext\-style (with underlines)
4904In addition, headers will be rendered setext\-style (with underlines)
4888−rather than ATX\-style (with \[aq]#\[aq] characters).
4905+rather than ATX\-style (with `#' characters).
4889−(This is because ghc treats \[aq]#\[aq] characters in column 1 as
4906+(This is because ghc treats `#' characters in column 1 as introducing
4890−introducing line numbers.)
4907+line numbers.)
4891.IP \[bu] 2
4908.IP \[bu] 2
4892−In restructured text input, "bird track" sections will be parsed as
4909+In restructured text input, \[lq]bird track\[rq] sections will be parsed
4893−Haskell code.
4910+as Haskell code.
4894.IP \[bu] 2
4911.IP \[bu] 2
4895In restructured text output, code blocks with class \f[C]haskell\f[]
4912In restructured text output, code blocks with class \f[C]haskell\f[]
4896will be rendered using bird tracks.
4913will be rendered using bird tracks.
@@ -4943,8 +4960,8 @@ To see a list of highlight styles, type
4943To disable highlighting, use the \f[C]\-\-no\-highlight\f[] option.
4960To disable highlighting, use the \f[C]\-\-no\-highlight\f[] option.
4944.SH CUSTOM STYLES IN DOCX OUTPUT
4961.SH CUSTOM STYLES IN DOCX OUTPUT
4946−By default, pandoc\[aq]s docx output applies a predefined set of styles
4963+By default, pandoc's docx output applies a predefined set of styles for
4947−for blocks such as paragraphs and block quotes, and uses largely default
4964+blocks such as paragraphs and block quotes, and uses largely default
4948formatting (italics, bold) for inlines.
4965formatting (italics, bold) for inlines.
4949This will work for most purposes, especially alongside a
4966This will work for most purposes, especially alongside a
4950\f[C]reference.docx\f[] file.
4967\f[C]reference.docx\f[] file.
@@ -4963,8 +4980,8 @@ So, for example,
4966−would produce a docx file with "Get out," styled with character style
4983+would produce a docx file with \[lq]Get out,\[rq] styled with character
4967−\f[C]Emphatically\f[].
4984+style \f[C]Emphatically\f[].
4968Similarly,
4985Similarly,
@@ -5029,14 +5046,14 @@ This software carries no warranty of any kind.
5029Contributors include Arata Mizuki, Aaron Wolen, Albert Krewinkel, Alex
5046Contributors include Arata Mizuki, Aaron Wolen, Albert Krewinkel, Alex
5030Ivkin, Alex Vong, Alexander Kondratskiy, Alexander Sulfrian, Alexander V
5047Ivkin, Alex Vong, Alexander Kondratskiy, Alexander Sulfrian, Alexander V
5031Vershilov, Alfred Wechselberger, Andreas Lööw, Andrew Dunning, Antoine
5048Vershilov, Alfred Wechselberger, Andreas Lööw, Andrew Dunning, Antoine
5032−Latter, Arata Mizuki, Arlo O\[aq]Keeffe, Artyom Kazak, B.
5049+Latter, Arata Mizuki, Arlo O'Keeffe, Artyom Kazak, B.
5033Scott Michel, Ben Gamari, Beni Cherniavsky\-Paskin, Benoit Schweblin,
5050Scott Michel, Ben Gamari, Beni Cherniavsky\-Paskin, Benoit Schweblin,
5034−Bjorn Buckwalter, Bradley Kuhn, Brent Yorgey, Bryan O\[aq]Sullivan,
5051+Bjorn Buckwalter, Bradley Kuhn, Brent Yorgey, Bryan O'Sullivan, Caleb
5035−Caleb McDaniel, Calvin Beck, Carlos Sosa, Chris Black, Christian Conkle,
5052+McDaniel, Calvin Beck, Carlos Sosa, Chris Black, Christian Conkle,
5036Christoffer Ackelman, Christoffer Sawicki, Clare Macrae, Clint Adams,
5053Christoffer Ackelman, Christoffer Sawicki, Clare Macrae, Clint Adams,
5037Conal Elliott, Craig S.
5054Conal Elliott, Craig S.
5038Bosma, Daniel Bergey, Daniel T.
5055Bosma, Daniel Bergey, Daniel T.
5039−Staal, Daniele D\[aq]Orazio, David Lazar, David Röthlisberger, Denis
5056+Staal, Daniele D'Orazio, David Lazar, David Röthlisberger, Denis
5040Laxalde, Douglas Calvert, Emanuel Evans, Emily Eisenberg, Eric Kow, Eric
5057Laxalde, Douglas Calvert, Emanuel Evans, Emily Eisenberg, Eric Kow, Eric
5041Seidel, Felix Yan, Florian Eitel, François Gannaz, Freiric Barral,
5058Seidel, Felix Yan, Florian Eitel, François Gannaz, Freiric Barral,
5042Freirich Raabe, Frerich Raabe, Fyodor Sheremetyev, Gabor Pali, Gavin
5059Freirich Raabe, Frerich Raabe, Fyodor Sheremetyev, Gabor Pali, Gavin
@@ -5047,9 +5064,9 @@ Portnov, Ivo Clarysse, J.
5047Lewis Muir, Jaime Marquínez Ferrándiz, Jakob Voß, James Aspnes, Jamie F.
5064Lewis Muir, Jaime Marquínez Ferrándiz, Jakob Voß, James Aspnes, Jamie F.
5048Olson, Jan Larres, Jan Schulz, Jason Ronallo, Jeff Arnold, Jeff
5065Olson, Jan Larres, Jan Schulz, Jason Ronallo, Jeff Arnold, Jeff
5049Runningen, Jens Petersen, Jesse Rosenthal, Joe Hillenbrand, John
5066Runningen, Jens Petersen, Jesse Rosenthal, Joe Hillenbrand, John
5050−MacFarlane, Jonas Smedegaard, Jonathan Daugherty, Jose Luis Duran, Josef
5067+MacFarlane, John Muccigrosso, Jonas Smedegaard, Jonathan Daugherty, Jose
5051−Svenningsson, Julien Cretel, Juliusz Gonera, Justin Bogner, Jérémy
5068+Luis Duran, Josef Svenningsson, Julien Cretel, Juliusz Gonera, Justin
5052−Bobbio, Kelsey Hightower, Kolen Cheung, KolenCheung, Konstantin Zudov,
5069+Bogner, Jérémy Bobbio, Kelsey Hightower, Kolen Cheung, Konstantin Zudov,
5053Kristof Bastiaensen, Lars\-Dominik Braun, Luke Plant, Mark Szepieniec,
5070Kristof Bastiaensen, Lars\-Dominik Braun, Luke Plant, Mark Szepieniec,
5054Mark Wright, Martin Linn, Masayoshi Takahashi, Matej Kollar, Mathias
5071Mark Wright, Martin Linn, Masayoshi Takahashi, Matej Kollar, Mathias
5055Schenner, Mathieu Duponchelle, Matthew Eddey, Matthew Pickering,
5072Schenner, Mathieu Duponchelle, Matthew Eddey, Matthew Pickering,
@@ -5065,10 +5082,11 @@ Silva, Recai Oktaş, RyanGlScott, Scott Morrison, Sergei Trofimovich,
5065Sergey Astanin, Shahbaz Youssefi, Shaun Attfield, Sidarth Kapur,
5082Sergey Astanin, Shahbaz Youssefi, Shaun Attfield, Sidarth Kapur,
5066Sidharth Kapur, Simon Hengel, Sumit Sahrawat, Thomas Hodgson, Thomas
5083Sidharth Kapur, Simon Hengel, Sumit Sahrawat, Thomas Hodgson, Thomas
5067Weißschuh, Tim Lin, Timothy Humphries, Tiziano Müller, Todd Sifleet, Tom
5084Weißschuh, Tim Lin, Timothy Humphries, Tiziano Müller, Todd Sifleet, Tom
5068−Leese, Uli Köhler, Václav Zeman, Viktor Kronvall, Vincent, Václav Zeman,
5085+Leese, Uli Köhler, Václav Zeman, Viktor Kronvall, Vincent, Václav
5086+Haisman, Václav Zeman, Wandmalfarbe, Waldir Pimenta, Wikiwide, Xavier
5069−Waldir Pimenta, Wikiwide, Xavier Olive, csforste, infinity0x, nkalvi,
5087+Olive, bumper314, csforste, infinity0x, nkalvi, qerub, robabla,
5070−qerub, robabla, roblabla, rodja.trappe, rski, shreevatsa.public,
5088+roblabla, rodja.trappe, rski, shreevatsa.public, takahashim, tgkokk,
5071−takahashim, thsutton.
5089+thsutton.
5073The Pandoc source code and all documentation may be downloaded
5091The Pandoc source code and all documentation may be downloaded
5074from <http://pandoc.org>.
5092from <http://pandoc.org>.