git.iko.soy/typeable/pandoc
on master help sign in
Updated man page.
commit632d4347f49ce1d1de7e991a88325319d4ede0c8 authorJohn MacFarlane <jgm@berkeley.edu> dateSun 29 Jan 2017, 21:19 (10 years ago) parent484c91e
1 file changed+189−171
man/pandoc.1+189−171
man/pandoc.1+189−171
@@ -1,10 +1,10 @@
11.\"t
2−.TH PANDOC 1 "December 10, 2016" "pandoc 1.19.1"
2+.TH PANDOC 1 "January 29, 2017" "pandoc 1.19.2"
33.SH NAME
44pandoc - general markup converter
55.SH SYNOPSIS
66.PP
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[]]\&...
88.SH DESCRIPTION
99.PP
1010Pandoc 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.
2323It can also produce PDF output on systems where LaTeX, ConTeXt, or
2424\f[C]wkhtmltopdf\f[] is installed.
2525.PP
26−Pandoc\[aq]s enhanced version of Markdown includes syntax for footnotes,
26+Pandoc's enhanced version of Markdown includes syntax for footnotes,
2727tables, flexible ordered lists, definition lists, fenced code blocks,
2828superscripts and subscripts, strikeout, metadata blocks, automatic
2929tables of contents, embedded LaTeX math, citations, and Markdown inside
3030HTML block elements.
31−(These enhancements, described further under Pandoc\[aq]s Markdown, can
32−be disabled using the \f[C]markdown_strict\f[] input or output format.)
31+(These enhancements, described further under Pandoc's Markdown, can be
32+disabled using the \f[C]markdown_strict\f[] input or output format.)
3333.PP
3434In contrast to most existing tools for converting Markdown to HTML,
3535which use regex substitutions, pandoc has a modular design: it consists
@@ -39,16 +39,16 @@ convert this native representation into a target format.
3939Thus, adding an input or output format requires only adding a reader or
4040writer.
4141.PP
42−Because pandoc\[aq]s intermediate representation of a document is less
42+Because pandoc's intermediate representation of a document is less
4343expressive than many of the formats it converts between, one should not
4444expect perfect conversions between every format and every other.
4545Pandoc attempts to preserve the structural elements of a document, but
4646not formatting details such as margin size.
4747And some document elements, such as complex tables, may not fit into
48−pandoc\[aq]s simple document model.
49−While conversions from pandoc\[aq]s Markdown to all formats aspire to be
50−perfect, conversions from formats more expressive than pandoc\[aq]s
51−Markdown can be expected to be lossy.
48+pandoc's simple document model.
49+While conversions from pandoc's Markdown to all formats aspire to be
50+perfect, conversions from formats more expressive than pandoc's Markdown
51+can be expected to be lossy.
5252.SS Using \f[C]pandoc\f[]
5353.PP
5454If no \f[I]input\-file\f[] is specified, input is read from
@@ -137,11 +137,11 @@ pandoc\ \-o\ hello.tex\ hello.txt
137137.PP
138138will convert \f[C]hello.txt\f[] from Markdown to LaTeX.
139139If 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
141141default to HTML.
142142If 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
144−be assumed to be Markdown unless explicitly specified.
143+or if the input files' extensions are unknown, the input format will be
144+assumed to be Markdown unless explicitly specified.
145145.PP
146146Pandoc uses the UTF\-8 character encoding for both input and output.
147147If your local character encoding is not UTF\-8, you should pipe input
@@ -208,7 +208,7 @@ as will \f[C]\-\-css\f[].
208208.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[]
209209Specify input format.
210210\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
212212Markdown), \f[C]markdown_strict\f[] (original unextended Markdown),
213213\f[C]markdown_phpextra\f[] (PHP Markdown Extra),
214214\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
227227name.
228228So, for example, \f[C]markdown_strict+footnotes+definition_lists\f[] is
229229strict 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
231231without pipe tables and with hard line breaks.
232−See Pandoc\[aq]s Markdown, below, for a list of extensions and their
233−names.
232+See Pandoc's Markdown, below, for a list of extensions and their names.
234233See \f[C]\-\-list\-input\-formats\f[] and \f[C]\-\-list\-extensions\f[],
235234below.
236235.RS
@@ -240,10 +239,9 @@ below.
240239Specify output format.
241240\f[I]FORMAT\f[] can be \f[C]native\f[] (native Haskell), \f[C]json\f[]
242241(JSON version of native AST), \f[C]plain\f[] (plain text),
243−\f[C]markdown\f[] (pandoc\[aq]s extended Markdown),
244−\f[C]markdown_strict\f[] (original unextended Markdown),
245−\f[C]markdown_phpextra\f[] (PHP Markdown Extra),
246−\f[C]markdown_github\f[] (GitHub\-Flavored Markdown),
242+\f[C]markdown\f[] (pandoc's extended Markdown), \f[C]markdown_strict\f[]
243+(original unextended Markdown), \f[C]markdown_phpextra\f[] (PHP Markdown
244+Extra), \f[C]markdown_github\f[] (GitHub\-Flavored Markdown),
247245\f[C]markdown_mmd\f[] (MultiMarkdown), \f[C]commonmark\f[] (CommonMark
248246Markdown), \f[C]rst\f[] (reStructuredText), \f[C]html\f[] (XHTML),
249247\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
319317at the output of \f[C]pandoc\ \-\-version\f[].
320318A \f[C]reference.odt\f[], \f[C]reference.docx\f[], \f[C]epub.css\f[],
321319\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
323321defaults.
324322.RE
325323.TP
@@ -355,7 +353,7 @@ List supported output formats, one per line.
355353.B \f[C]\-\-list\-extensions\f[]
356354List supported Markdown extensions, one per line, followed by a
357355\f[C]+\f[] or \f[C]\-\f[] indicating whether it is enabled by default in
358−pandoc\[aq]s Markdown.
356+pandoc's Markdown.
359357.RS
360358.RE
361359.TP
@@ -401,8 +399,8 @@ Produce typographically correct output, converting straight quotes to
401399curly quotes, \f[C]\-\-\-\f[] to em\-dashes, \f[C]\-\-\f[] to
402400en\-dashes, and \f[C]\&...\f[] to ellipses.
403401Nonbreaking spaces are inserted after certain abbreviations, such as
404−"Mr." (Note: This option is selected automatically when the output
405−format is \f[C]latex\f[] or \f[C]context\f[], unless
402+\[lq]Mr.\[rq] (Note: This option is selected automatically when the
403+output format is \f[C]latex\f[] or \f[C]context\f[], unless
406404\f[C]\-\-no\-tex\-ligatures\f[] is used.
407405It has no effect for \f[C]latex\f[] input.)
408406.RS
@@ -422,7 +420,7 @@ Specify the base level for headers (defaults to 1).
422420.RE
423421.TP
424422.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,
426424\f[C]perl,numberLines\f[] or \f[C]haskell\f[].
427425Multiple classes may be separated by spaces or commas.
428426.RS
@@ -450,7 +448,7 @@ Reading binary files (docx, odt, epub) implies \f[C]\-\-file\-scope\f[].
450448Specify an executable to be used as a filter transforming the pandoc AST
451449after the input is parsed and before the output is written.
452450The 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.
454452The name of the output format will be passed to the filter as the first
455453argument.
456454Hence,
@@ -524,7 +522,7 @@ Specify the number of spaces per tab (default is 4).
524522.TP
525523.B \f[C]\-\-track\-changes=accept\f[]|\f[C]reject\f[]|\f[C]all\f[]
526524Specifies 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.
528526\f[C]accept\f[] (the default), inserts all insertions, and ignores all
529527deletions.
530528\f[C]reject\f[] inserts all deletions and ignores insertions.
@@ -550,8 +548,8 @@ This option only affects the docx and epub readers.
550548.SS General writer options
551549.TP
552550.B \f[C]\-s\f[], \f[C]\-\-standalone\f[]
553−Produce output with an appropriate header and footer (e.g.
554−a standalone HTML, LaTeX, TEI, or RTF file, not a fragment).
551+Produce output with an appropriate header and footer (e.g.\ a standalone
552+HTML, LaTeX, TEI, or RTF file, not a fragment).
555553This option is set automatically for \f[C]pdf\f[], \f[C]epub\f[],
556554\f[C]epub3\f[], \f[C]fb2\f[], \f[C]docx\f[], and \f[C]odt\f[] output.
557555.RS
@@ -609,12 +607,13 @@ Technically, the correct term would be ppi (pixels per inch).
609607Determine how text is wrapped in the output (the source code, not the
610608rendered version).
611609With \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).
613611With \f[C]none\f[], pandoc will not wrap lines at all.
614612With \f[C]preserve\f[], pandoc will attempt to preserve the wrapping
615613from the source document (that is, where there are nonsemantic newlines
616614in the source, there will be nonsemantic newlines in the output as
617615well).
616+Automatic wrapping does not currently work in HTML output.
618617.RS
619618.RE
620619.TP
@@ -659,8 +658,8 @@ language attribute is given.
659658.B \f[C]\-\-highlight\-style=\f[]\f[I]STYLE\f[]
660659Specifies the coloring style to be used in highlighted source code.
661660Options are \f[C]pygments\f[] (the default), \f[C]kate\f[],
662−\f[C]monochrome\f[], \f[C]espresso\f[], \f[C]zenburn\f[],
663−\f[C]haddock\f[], and \f[C]tango\f[].
661+\f[C]monochrome\f[], \f[C]breezeDark\f[], \f[C]espresso\f[],
662+\f[C]zenburn\f[], \f[C]haddock\f[], and \f[C]tango\f[].
664663For more information on syntax highlighting in pandoc, see Syntax
665664highlighting, below.
666665See also \f[C]\-\-list\-highlight\-styles\f[].
@@ -680,9 +679,8 @@ Implies \f[C]\-\-standalone\f[].
680679.TP
681680.B \f[C]\-B\f[] \f[I]FILE\f[], \f[C]\-\-include\-before\-body=\f[]\f[I]FILE\f[]
682681Include contents of \f[I]FILE\f[], verbatim, at the beginning of the
683−document body (e.g.
684−after the \f[C]<body>\f[] tag in HTML, or the \f[C]\\begin{document}\f[]
685−command in LaTeX).
682+document body (e.g.\ after the \f[C]<body>\f[] tag in HTML, or the
683+\f[C]\\begin{document}\f[] command in LaTeX).
686684This can be used to include navigation bars or banners in HTML
687685documents.
688686This option can be used repeatedly to include multiple files.
@@ -706,9 +704,9 @@ Implies \f[C]\-\-standalone\f[].
706704Produce a standalone HTML file with no external dependencies, using
707705\f[C]data:\f[] URIs to incorporate the contents of linked scripts,
708706stylesheets, images, and videos.
709−The resulting file should be "self\-contained," in the sense that it
710−needs no external files and no net access to be displayed properly by a
711−browser.
707+The resulting file should be \[lq]self\-contained,\[rq] in the sense
708+that it needs no external files and no net access to be displayed
709+properly by a browser.
712710This option works only with HTML output formats, including
713711\f[C]html\f[], \f[C]html5\f[], \f[C]html+lhs\f[], \f[C]html5+lhs\f[],
714712\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
719717first source file is remote).
720718Limitation: resources that are loaded dynamically through JavaScript
721719cannot 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.
723−zoom or speaker notes) may not work in an offline "self\-contained"
724−\f[C]reveal.js\f[] slide show.
720+not work with \f[C]\-\-mathjax\f[], and some advanced features
721+(e.g.\ zoom or speaker notes) may not work in an offline
722+\[lq]self\-contained\[rq] \f[C]reveal.js\f[] slide show.
725723.RS
726724.RE
727725.TP
@@ -792,15 +790,16 @@ Sections with class \f[C]unnumbered\f[] will never be numbered, even if
792790.RS
793791.RE
794792.TP
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[]]
796794Offset for section headings in HTML output (ignored in other output
797795formats).
798796The first number is added to the section number for top\-level headers,
799797the second for second\-level headers, and so on.
800798So, 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[].
802801If 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[].
804803Offsets are 0 by default.
805804Implies \f[C]\-\-number\-sections\f[].
806805.RS
@@ -1026,7 +1025,7 @@ body\ {\ font\-family:\ "DejaVuSans";\ }
10261025.TP
10271026.B \f[C]\-\-epub\-chapter\-level=\f[]\f[I]NUMBER\f[]
10281027Specify the header level at which to split the EPUB into separate
1029−"chapter" files.
1028+\[lq]chapter\[rq] files.
10301029The default is to split into chapters at level 1 headers.
10311030This option only affects the internal composition of the EPUB, not the
10321031way chapters and sections are displayed to users.
@@ -1055,7 +1054,7 @@ Note that no check for duplicate options is done.
10551054.SS Citation rendering
10561055.TP
10571056.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
10591058\f[I]FILE\f[], overriding any value set in the metadata, and process
10601059citations using \f[C]pandoc\-citeproc\f[].
10611060(This is equivalent to
@@ -1069,15 +1068,15 @@ added to bibliography.
10691068.RE
10701069.TP
10711070.B \f[C]\-\-csl=\f[]\f[I]FILE\f[]
1072−Set the \f[C]csl\f[] field in the document\[aq]s metadata to
1073−\f[I]FILE\f[], overriding any value set in the metadata.
1071+Set the \f[C]csl\f[] field in the document's metadata to \f[I]FILE\f[],
1072+overriding any value set in the metadata.
10741073(This is equivalent to \f[C]\-\-metadata\ csl=FILE\f[].) This option is
10751074only relevant with \f[C]pandoc\-citeproc\f[].
10761075.RS
10771076.RE
10781077.TP
10791078.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
10811080metadata to \f[I]FILE\f[], overriding any value set in the metadata.
10821081(This is equivalent to
10831082\f[C]\-\-metadata\ citation\-abbreviations=FILE\f[].) This option is
@@ -1164,7 +1163,7 @@ to images.
11641163The formula will be concatenated with the URL provided.
11651164If \f[I]URL\f[] is not specified, the CodeCogs will be used.
11661165Note: 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
11681167without native math support.
11691168.RS
11701169.RE
@@ -1345,7 +1344,7 @@ body of document
13451344.RE
13461345.TP
13471346.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
13491348.RS
13501349.RE
13511350.SS Language variables
@@ -1387,8 +1386,8 @@ For bidirectional documents, native pandoc \f[C]span\f[]s and
13871386\f[C]div\f[]s with the \f[C]dir\f[] attribute (value \f[C]rtl\f[] or
13881387\f[C]ltr\f[]) can be used to override the base direction in some output
13891388formats.
1390−This may not always be necessary if the final renderer (e.g.
1391−the browser, when generating HTML) supports the Unicode Bidirectional
1389+This may not always be necessary if the final renderer (e.g.\ the
1390+browser, when generating HTML) supports the Unicode Bidirectional
13921391Algorithm.
13931392.PP
13941393When 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
14381437.RE
14391438.TP
14401439.B \f[C]section\-titles\f[]
1441−enables on "title pages" for new sections in \f[C]beamer\f[] documents
1442−(default = true).
1440+enables on \[lq]title pages\[rq] for new sections in \f[C]beamer\f[]
1441+documents (default = true).
14431442.RS
14441443.RE
14451444.TP
@@ -1548,6 +1547,11 @@ font encodings)
15481547.RS
15491548.RE
15501549.TP
1550+.B \f[C]microtypeoptions\f[]
1551+options to pass to the microtype package
1552+.RS
1553+.RE
1554+.TP
15511555.B \f[C]colorlinks\f[]
15521556add color to link text; automatically enabled if any of
15531557\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
18141818modifying your custom templates accordingly.
18151819An easy way to do this is to fork the pandoc\-templates repository and
18161820merge in changes after each pandoc release.
1817−.SH PANDOC\[aq]S MARKDOWN
1821+.SH PANDOC'S MARKDOWN
18181822.PP
18191823Pandoc understands an extended and slightly revised version of John
1820−Gruber\[aq]s Markdown syntax.
1824+Gruber's Markdown syntax.
18211825This document explains the syntax, noting differences from standard
18221826Markdown.
18231827Except 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
18261830name and disabled by adding \f[C]\-EXTENSION\f[].
18271831For example, \f[C]markdown_strict+footnotes\f[] is strict Markdown with
18281832footnotes 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.
18301834.SS Philosophy
18311835.PP
18321836Markdown is designed to be easy to write, and, even more importantly,
@@ -1834,16 +1838,16 @@ easy to read:
18341838.RS
18351839.PP
18361840A Markdown\-formatted document should be publishable as\-is, as plain
1837−text, without looking like it\[aq]s been marked up with tags or
1838−formatting instructions.
1839−\-\- John Gruber
1841+text, without looking like it's been marked up with tags or formatting
1842+instructions.
1843+\[en] John Gruber
18401844.RE
18411845.PP
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
18431847tables, footnotes, and other extensions.
18441848.PP
1845−There is, however, one respect in which pandoc\[aq]s aims are different
1846−from the original aims of Markdown.
1849+There is, however, one respect in which pandoc's aims are different from
1850+the original aims of Markdown.
18471851Whereas Markdown was originally designed with HTML generation in mind,
18481852pandoc is designed for multiple output formats.
18491853Thus, 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.
18671871There are two kinds of headers: Setext and ATX.
18681872.SS Setext\-style headers
18691873.PP
1870−A setext\-style header is a line of text "underlined" with a row of
1871−\f[C]=\f[] signs (for a level one header) or \f[C]\-\f[] signs (for a
1874+A setext\-style header is a line of text \[lq]underlined\[rq] with a row
1875+of \f[C]=\f[] signs (for a level one header) or \f[C]\-\f[] signs (for a
18721876level two header):
18731877.IP
18741878.nf
@@ -1950,7 +1954,7 @@ My\ other\ header\ \ \ {#foo}
19501954(This syntax is compatible with PHP Markdown Extra.)
19511955.PP
19521956Note 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
19541958information.
19551959Identifiers, classes, and key/value attributes are used in HTML and
19561960HTML\-based formats such as EPUB and slidy.
@@ -2149,8 +2153,8 @@ indented more than three spaces.)
21492153\f[]
21502154.fi
21512155.PP
2152−A "lazy" form, which requires the \f[C]>\f[] character only on the first
2153−line of each block, is also allowed:
2156+A \[lq]lazy\[rq] form, which requires the \f[C]>\f[] character only on
2157+the first line of each block, is also allowed:
21542158.IP
21552159.nf
21562160\f[C]
@@ -2378,8 +2382,8 @@ Here is a simple example:
23782382\f[]
23792383.fi
23802384.PP
2381−This will produce a "compact" list.
2382−If you want a "loose" list, in which each item is formatted as a
2385+This will produce a \[lq]compact\[rq] list.
2386+If you want a \[lq]loose\[rq] list, in which each item is formatted as a
23832387paragraph, put spaces between the items:
23842388.IP
23852389.nf
@@ -2407,7 +2411,7 @@ List items look best if subsequent lines are flush with the first line
24072411\f[]
24082412.fi
24092413.PP
2410−But Markdown also allows a "lazy" format:
2414+But Markdown also allows a \[lq]lazy\[rq] format:
24112415.IP
24122416.nf
24132417\f[C]
@@ -2456,8 +2460,8 @@ The nested list must be indented four spaces or one tab:
24562460\f[]
24572461.fi
24582462.PP
2459−As noted above, Markdown allows you to write list items "lazily,"
2460−instead of indenting continuation lines.
2463+As noted above, Markdown allows you to write list items
2464+\[lq]lazily,\[rq] instead of indenting continuation lines.
24612465However, if there are multiple paragraphs or other blocks in a list
24622466item, the first line of each must be indented.
24632467.IP
@@ -2523,8 +2527,8 @@ They must be separated from the text that follows by at least one space,
25232527and, if the list marker is a capital letter with a period, by at least
25242528two spaces.
25252529.PP
2526−The \f[C]fancy_lists\f[] extension also allows \[aq]\f[C]#\f[]\[aq] to
2527−be used as an ordered list marker in place of a numeral:
2530+The \f[C]fancy_lists\f[] extension also allows `\f[C]#\f[]' to be used
2531+as an ordered list marker in place of a numeral:
25282532.IP
25292533.nf
25302534\f[C]
@@ -2606,8 +2610,9 @@ one or more block elements (paragraph, code block, list, etc.), each
26062610indented four spaces or one tab stop.
26072611The body of the definition (including the first line, aside from the
26082612colon or tilde) should be indented four spaces.
2609−However, as with other Markdown lists, you can "lazily" omit indentation
2610−except at the beginning of a paragraph or other block element:
2613+However, as with other Markdown lists, you can \[lq]lazily\[rq] omit
2614+indentation except at the beginning of a paragraph or other block
2615+element:
26112616.IP
26122617.nf
26132618\f[C]
@@ -2639,16 +2644,16 @@ Term\ 2
26392644.fi
26402645.PP
26412646Note that space between items in a definition list is required.
2642−(A variant that loosens this requirement, but disallows "lazy" hard
2643−wrapping, can be activated with \f[C]compact_definition_lists\f[]: see
2644−Non\-pandoc extensions, below.)
2647+(A variant that loosens this requirement, but disallows \[lq]lazy\[rq]
2648+hard wrapping, can be activated with \f[C]compact_definition_lists\f[]:
2649+see Non\-pandoc extensions, below.)
26452650.SS Numbered example lists
26462651.SS Extension: \f[C]example_lists\f[]
26472652.PP
26482653The special list marker \f[C]\@\f[] can be used for sequentially
26492654numbered examples.
2650−The first list item with a \f[C]\@\f[] marker will be numbered
2651−\[aq]1\[aq], the next \[aq]2\[aq], and so on, throughout the document.
2655+The first list item with a \f[C]\@\f[] marker will be numbered `1', the
2656+next `2', and so on, throughout the document.
26522657The numbered examples need not occur in a single list; each new list
26532658using \f[C]\@\f[] will take up where the last stopped.
26542659So, for example:
@@ -2679,8 +2684,8 @@ The label can be any string of alphanumeric characters, underscores, or
26792684hyphens.
26802685.SS Compact and loose lists
26812686.PP
2682−Pandoc behaves differently from \f[C]Markdown.pl\f[] on some "edge
2683−cases" involving lists.
2687+Pandoc behaves differently from \f[C]Markdown.pl\f[] on some \[lq]edge
2688+cases\[rq] involving lists.
26842689Consider this source:
26852690.IP
26862691.nf
@@ -2695,14 +2700,15 @@ Consider this source:
26952700\f[]
26962701.fi
26972702.PP
2698−Pandoc transforms this into a "compact list" (with no \f[C]<p>\f[] tags
2699−around "First", "Second", or "Third"), while Markdown puts \f[C]<p>\f[]
2700−tags around "Second" and "Third" (but not "First"), because of the blank
2701−space around "Third".
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
2705+\[lq]Third\[rq]), while Markdown puts \f[C]<p>\f[] tags around
2706+\[lq]Second\[rq] and \[lq]Third\[rq] (but not \[lq]First\[rq]), because
2707+of the blank space around \[lq]Third\[rq].
27022708Pandoc follows a simple rule: if the text is followed by a blank line,
27032709it is treated as a paragraph.
2704−Since "Second" is followed by a list, and not a blank line, it isn\[aq]t
2705−treated as a paragraph.
2710+Since \[lq]Second\[rq] is followed by a list, and not a blank line, it
2711+isn't treated as a paragraph.
27062712The fact that the list is followed by a blank line is irrelevant.
27072713(Note: Pandoc works this way even when the \f[C]markdown_strict\f[]
27082714format is specified.
@@ -2726,9 +2732,9 @@ Trouble! Here pandoc (like other Markdown implementations) will treat
27262732\f[C]{\ my\ code\ block\ }\f[] as the second paragraph of item two, and
27272733not as a code block.
27282734.PP
2729−To "cut off" the list after item two, you can insert some non\-indented
2730−content, like an HTML comment, which won\[aq]t produce visible output in
2731−any format:
2735+To \[lq]cut off\[rq] the list after item two, you can insert some
2736+non\-indented content, like an HTML comment, which won't produce visible
2737+output in any format:
27322738.IP
27332739.nf
27342740\f[C]
@@ -2992,7 +2998,7 @@ wrap, with the relative cell widths determined by the widths of the
29922998separator lines.
29932999.PP
29943000Note: 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:
29963002.IP
29973003.nf
29983004\f[C]
@@ -3005,8 +3011,8 @@ be produced by Emacs\[aq] orgtbl\-mode:
30053011.PP
30063012The difference is that \f[C]+\f[] is used instead of \f[C]|\f[].
30073013Other orgtbl features are not supported.
3008−In particular, to get non\-default column alignment, you\[aq]ll need to
3009−add colons as above.
3014+In particular, to get non\-default column alignment, you'll need to add
3015+colons as above.
30103016.SS Metadata blocks
30113017.SS Extension: \f[C]pandoc_title_block\f[]
30123018.PP
@@ -3071,13 +3077,13 @@ All three metadata fields may contain standard inline formatting
30713077.PP
30723078Title blocks will always be parsed, but they will affect the output only
30733079when 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 \-\-
3075−this is the title that will appear at the top of the window in a browser
3076−\-\- and once at the beginning of the document body.
3080+In HTML output, titles will appear twice: once in the document head
3081+\[en] this is the title that will appear at the top of the window in a
3082+browser \[en] and once at the beginning of the document body.
30773083The title in the document head can have an optional prefix attached
30783084(\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
3080−can be suppressed or reformatted with CSS.
3085+The title in the body appears as an H1 element with class
3086+\[lq]title\[rq], so it can be suppressed or reformatted with CSS.
30813087If a title prefix is specified with \f[C]\-T\f[] and no title block
30823088appears in the document, the title prefix will be used by itself as the
30833089HTML title.
@@ -3106,7 +3112,7 @@ will yield a man page with the title \f[C]PANDOC\f[] and section 1.
31063112\f[]
31073113.fi
31083114.PP
3109−will also have "Pandoc User Manuals" in the footer.
3115+will also have \[lq]Pandoc User Manuals\[rq] in the footer.
31103116.IP
31113117.nf
31123118\f[C]
@@ -3114,7 +3120,7 @@ will also have "Pandoc User Manuals" in the footer.
31143120\f[]
31153121.fi
31163122.PP
3117−will also have "Version 4.0" in the header.
3123+will also have \[lq]Version 4.0\[rq] in the header.
31183124.SS Extension: \f[C]yaml_metadata_block\f[]
31193125.PP
31203126A YAML metadata block is a valid YAML object, delimited by a line of
@@ -3253,7 +3259,7 @@ instead of
32533259\f[]
32543260.fi
32553261.PP
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
32573263allows only the following characters to be backslash\-escaped:
32583264.IP
32593265.nf
@@ -3269,12 +3275,11 @@ A backslash\-escaped space is parsed as a nonbreaking space.
32693275It will appear in TeX output as \f[C]~\f[] and in HTML and XML as
32703276\f[C]\\&#160;\f[] or \f[C]\\&nbsp;\f[].
32713277.PP
3272−A backslash\-escaped newline (i.e.
3273−a backslash occurring at the end of a line) is parsed as a hard line
3274−break.
3278+A backslash\-escaped newline (i.e.\ a backslash occurring at the end of
3279+a line) is parsed as a hard line break.
32753280It will appear in TeX output as \f[C]\\\\\f[] and in HTML as
32763281\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
32783283indicating hard line breaks using two trailing spaces on a line.
32793284.PP
32803285Backslash escapes do not work in verbatim contexts.
@@ -3286,7 +3291,7 @@ typographically correct output, converting straight quotes to curly
32863291quotes, \f[C]\-\-\-\f[] to em\-dashes, \f[C]\-\-\f[] to en\-dashes, and
32873292\f[C]\&...\f[] to ellipses.
32883293Nonbreaking spaces are inserted after certain abbreviations, such as
3289−"Mr."
3294+\[lq]Mr.\[rq]
32903295.PP
32913296Note: if your LaTeX template or any included header file call for the
32923297\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
33623367must be escaped with backslashes.
33633368(This is to prevent accidental superscripting and subscripting through
33643369the 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[],
3366−not \f[C]P~a\ cat~\f[].
3370+letter P with `a cat' in subscripts, use \f[C]P~a\\\ cat~\f[], not
3371+\f[C]P~a\ cat~\f[].
33673372.SS Verbatim
33683373.PP
33693374To 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
34353440its right, while the closing \f[C]$\f[] must have a non\-space character
34363441immediately to its left, and must not be followed immediately by a
34373442digit.
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.
34393444If 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
34413446delimiters.
34423447.PP
34433448TeX math will be printed in all output formats.
@@ -3464,7 +3469,7 @@ It will be rendered inside a \f[C]\@math\f[] command.
34643469.RE
34653470.TP
34663471.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.
34683473.RS
34693474.RE
34703475.TP
@@ -3578,9 +3583,9 @@ DZSlides, EPUB, Markdown, Emacs Org mode, and Textile output, and
35783583suppressed in other formats.
35793584.SS Extension: \f[C]markdown_in_html_blocks\f[]
35803585.PP
3581−Standard Markdown allows you to include HTML "blocks": blocks of HTML
3582−between balanced tags that are separated from the surrounding text with
3583−blank lines, and start and end at the left margin.
3586+Standard Markdown allows you to include HTML \[lq]blocks\[rq]: blocks of
3587+HTML between balanced tags that are separated from the surrounding text
3588+with blank lines, and start and end at the left margin.
35843589Within these blocks, everything is interpreted as HTML, not Markdown; so
35853590(for example), \f[C]*\f[] does not signify emphasis.
35863591.PP
@@ -3848,7 +3853,7 @@ slide shows and EPUB), LaTeX, and ConTeXt.
38483853.SS Images
38493854.PP
38503855A 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:
38523857.IP
38533858.nf
38543859\f[C]
@@ -3865,7 +3870,7 @@ An image occurring by itself in a paragraph will be rendered as a figure
38653870with a caption. (In LaTeX, a figure environment will be used; in HTML,
38663871the image will be placed in a \f[C]div\f[] with class \f[C]figure\f[],
38673872together 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.
38693874.IP
38703875.nf
38713876\f[C]
@@ -3952,7 +3957,7 @@ attributes:
39523957.SS Footnotes
39533958.SS Extension: \f[C]footnotes\f[]
39543959.PP
3955−Pandoc\[aq]s Markdown allows footnotes, using the following syntax:
3960+Pandoc's Markdown allows footnotes, using the following syntax:
39563961.IP
39573962.nf
39583963\f[C]
@@ -3984,6 +3989,8 @@ the note itself; in the output, footnotes will be numbered sequentially.
39843989The footnotes themselves need not be placed at the end of the document.
39853990They may appear anywhere except inside other block elements (lists,
39863991block quotes, tables, etc.).
3992+Each footnote should be separated from surrounding content (including
3993+other footnotes) by blank lines.
39873994.SS Extension: \f[C]inline_notes\f[]
39883995.PP
39893996Inline footnotes are also allowed (though, unlike regular notes, they
@@ -4134,7 +4141,7 @@ JSON and CSL YAML formats as far as possible.
41344141As an alternative to specifying a bibliography file using
41354142\f[C]\-\-bibliography\f[] or the YAML metadata field
41364143\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.
41384145The field should contain an array of YAML\-encoded references, for
41394146example:
41404147.IP
@@ -4184,7 +4191,7 @@ To make your citations hyperlinks to the corresponding bibliography
41844191entries, add \f[C]link\-citations:\ true\f[] to your YAML metadata.
41854192.PP
41864193Citations 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
41884195identifier from the database, and may optionally have a prefix, a
41894196locator, and a suffix.
41904197The 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[];
42194226\f[C]s.v.\f[]/\f[C]s.vv.\f[]; \f[C]verse\f[], \f[C]v.\f[]/\f[C]vv.\f[];
42204227\f[C]volume\f[], \f[C]vol.\f[]/\f[C]vols.\f[]; \f[C]¶\f[]/\f[C]¶¶\f[];
42214228\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.
42234230.PP
42244231A minus sign (\f[C]\-\f[]) before the \f[C]\@\f[] will suppress mention
42254232of the author in the citation.
@@ -4276,6 +4283,18 @@ In this example, the document will contain a citation for \f[C]item3\f[]
42764283only, but the bibliography will contain entries for \f[C]item1\f[],
42774284\f[C]item2\f[], and \f[C]item3\f[].
42784285.PP
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:
4288+.IP
4289+.nf
4290+\f[C]
4291+\-\-\-
4292+nocite:\ |
4293+\ \ \@*
4294+\&...
4295+\f[]
4296+.fi
4297+.PP
42794298For LaTeX or PDF output, you can also use \f[C]natbib\f[] or
42804299\f[C]biblatex\f[] to render bibliography.
42814300In order to do so, specify bibliography files as outlined above, and add
@@ -4296,7 +4315,7 @@ hard line breaks.
42964315.PP
42974316Allow \f[C]<\f[] and \f[C]>\f[] to be backslash\-escaped, as they can be
42984317in 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[].
43004319.SS Extension: \f[C]lists_without_preceding_blankline\f[]
43014320.PP
43024321Allow a list to occur right after a paragraph, with no intervening blank
@@ -4410,15 +4429,15 @@ in several respects:
44104429No blank line is required between consecutive items of the definition
44114430list.
44124431.IP \[bu] 2
4413−To get a "tight" or "compact" list, omit space between consecutive
4414−items; the space between a term and its definition does not affect
4415−anything.
4432+To get a \[lq]tight\[rq] or \[lq]compact\[rq] list, omit space between
4433+consecutive items; the space between a term and its definition does not
4434+affect anything.
44164435.IP \[bu] 2
44174436Lazy wrapping of paragraphs is not allowed: the entire definition must
44184437be indented four spaces.
44194438.SS Markdown variants
44204439.PP
4421−In addition to pandoc\[aq]s extended Markdown, the following Markdown
4440+In addition to pandoc's extended Markdown, the following Markdown
44224441variants are supported:
44234442.TP
44244443.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
44754494reveal.js.
44764495You can also produce a PDF slide show using LaTeX \f[C]beamer\f[].
44774496.PP
4478−Here\[aq]s the Markdown source for a simple slide show,
4479−\f[C]habits.txt\f[]:
4497+Here's the Markdown source for a simple slide show, \f[C]habits.txt\f[]:
44804498.IP
44814499.nf
44824500\f[C]
@@ -4571,17 +4589,17 @@ A header at the slide level always starts a new slide.
45714589Headers \f[I]below\f[] the slide level in the hierarchy create headers
45724590\f[I]within\f[] a slide.
45734591.IP \[bu] 2
4574−Headers \f[I]above\f[] the slide level in the hierarchy create "title
4575−slides," which just contain the section title and help to break the
4576−slide show into sections.
4592+Headers \f[I]above\f[] the slide level in the hierarchy create
4593+\[lq]title slides,\[rq] which just contain the section title and help to
4594+break the slide show into sections.
45774595.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
45794597block, if present.
45804598(In the case of beamer, this can be disabled by commenting out some
45814599lines in the default template.)
45824600.PP
45834601These 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
45854603subsections, you can just use level 1 headers for all each slide.
45864604(In that case, level 1 will be the slide level.) But you can also
45874605structure 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
45934611reveal.js.
45944612.SS Incremental lists
45954613.PP
4596−By default, these writers produce lists that display "all at once." If
4597−you want your lists to display incrementally (one item at a time), use
4598−the \f[C]\-i\f[] option.
4614+By default, these writers produce lists that display \[lq]all at
4615+once.\[rq] If you want your lists to display incrementally (one item at
4616+a time), use the \f[C]\-i\f[] option.
45994617If you want a particular list to depart from the default (that is, to
46004618display incrementally without the \f[C]\-i\f[] option and all at once
46014619with 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
46114629single document.
46124630.SS Inserting pauses
46134631.PP
4614−You can add "pauses" within a slide by including a paragraph containing
4615−three dots, separated by spaces:
4632+You can add \[lq]pauses\[rq] within a slide by including a paragraph
4633+containing three dots, separated by spaces:
46164634.IP
46174635.nf
46184636\f[C]
@@ -4632,8 +4650,8 @@ in \f[C]$DATADIR/s5/default\f[] (for S5), \f[C]$DATADIR/slidy\f[] (for
46324650Slidy), or \f[C]$DATADIR/slideous\f[] (for Slideous), where
46334651\f[C]$DATADIR\f[] is the user data directory (see
46344652\f[C]\-\-data\-dir\f[], above).
4635−The originals may be found in pandoc\[aq]s system data directory
4636−(generally \f[C]$CABALDIR/pandoc\-VERSION/s5/default\f[]).
4653+The originals may be found in pandoc's system data directory (generally
4654+\f[C]$CABALDIR/pandoc\-VERSION/s5/default\f[]).
46374655Pandoc will look there for any files it does not find in the user data
46384656directory.
46394657.PP
@@ -4712,7 +4730,7 @@ introducing the slide:
47124730.fi
47134731.PP
47144732All 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[],
47164734\f[C]allowframebreaks\f[], \f[C]b\f[], \f[C]c\f[], \f[C]t\f[],
47174735\f[C]environment\f[], \f[C]label\f[], \f[C]plain\f[], \f[C]shrink\f[].
47184736.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[],
47714789Either a string value, or an object with fields \f[C]role\f[],
47724790\f[C]file\-as\f[], and \f[C]text\f[], or a list of such objects.
47734791Valid values for \f[C]role\f[] are MARC relators, but pandoc will
4774−attempt to translate the human\-readable versions (like "author" and
4775−"editor") to the appropriate marc relators.
4792+attempt to translate the human\-readable versions (like \[lq]author\[rq]
4793+and \[lq]editor\[rq]) to the appropriate marc relators.
47764794.RS
47774795.RE
47784796.TP
@@ -4873,24 +4891,23 @@ output; \f[C]beamer\f[], \f[C]html\f[] or \f[C]html5\f[] for output
48734891only), pandoc will treat the document as literate Haskell source.
48744892This means that
48754893.IP \[bu] 2
4876−In Markdown input, "bird track" sections will be parsed as Haskell code
4877−rather than block quotations.
4894+In Markdown input, \[lq]bird track\[rq] sections will be parsed as
4895+Haskell code rather than block quotations.
48784896Text between \f[C]\\begin{code}\f[] and \f[C]\\end{code}\f[] will also
48794897be treated as Haskell code.
4880−For ATX\-style headers the character \[aq]=\[aq] will be used instead of
4881−\[aq]#\[aq].
4898+For ATX\-style headers the character `=' will be used instead of `#'.
48824899.IP \[bu] 2
48834900In Markdown output, code blocks with classes \f[C]haskell\f[] and
48844901\f[C]literate\f[] will be rendered using bird tracks, and block
48854902quotations will be indented one space, so they will not be treated as
48864903Haskell code.
48874904In addition, headers will be rendered setext\-style (with underlines)
4888−rather than ATX\-style (with \[aq]#\[aq] characters).
4889−(This is because ghc treats \[aq]#\[aq] characters in column 1 as
4890−introducing line numbers.)
4905+rather than ATX\-style (with `#' characters).
4906+(This is because ghc treats `#' characters in column 1 as introducing
4907+line numbers.)
48914908.IP \[bu] 2
4892−In restructured text input, "bird track" sections will be parsed as
4893−Haskell code.
4909+In restructured text input, \[lq]bird track\[rq] sections will be parsed
4910+as Haskell code.
48944911.IP \[bu] 2
48954912In restructured text output, code blocks with class \f[C]haskell\f[]
48964913will be rendered using bird tracks.
@@ -4943,8 +4960,8 @@ To see a list of highlight styles, type
49434960To disable highlighting, use the \f[C]\-\-no\-highlight\f[] option.
49444961.SH CUSTOM STYLES IN DOCX OUTPUT
49454962.PP
4946−By default, pandoc\[aq]s docx output applies a predefined set of styles
4947−for blocks such as paragraphs and block quotes, and uses largely default
4963+By default, pandoc's docx output applies a predefined set of styles for
4964+blocks such as paragraphs and block quotes, and uses largely default
49484965formatting (italics, bold) for inlines.
49494966This will work for most purposes, especially alongside a
49504967\f[C]reference.docx\f[] file.
@@ -4963,8 +4980,8 @@ So, for example,
49634980\f[]
49644981.fi
49654982.PP
4966−would produce a docx file with "Get out," styled with character style
4967−\f[C]Emphatically\f[].
4983+would produce a docx file with \[lq]Get out,\[rq] styled with character
4984+style \f[C]Emphatically\f[].
49684985Similarly,
49694986.IP
49704987.nf
@@ -5029,14 +5046,14 @@ This software carries no warranty of any kind.
50295046Contributors include Arata Mizuki, Aaron Wolen, Albert Krewinkel, Alex
50305047Ivkin, Alex Vong, Alexander Kondratskiy, Alexander Sulfrian, Alexander V
50315048Vershilov, 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.
50335050Scott Michel, Ben Gamari, Beni Cherniavsky\-Paskin, Benoit Schweblin,
5034−Bjorn Buckwalter, Bradley Kuhn, Brent Yorgey, Bryan O\[aq]Sullivan,
5035−Caleb McDaniel, Calvin Beck, Carlos Sosa, Chris Black, Christian Conkle,
5051+Bjorn Buckwalter, Bradley Kuhn, Brent Yorgey, Bryan O'Sullivan, Caleb
5052+McDaniel, Calvin Beck, Carlos Sosa, Chris Black, Christian Conkle,
50365053Christoffer Ackelman, Christoffer Sawicki, Clare Macrae, Clint Adams,
50375054Conal Elliott, Craig S.
50385055Bosma, 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
50405057Laxalde, Douglas Calvert, Emanuel Evans, Emily Eisenberg, Eric Kow, Eric
50415058Seidel, Felix Yan, Florian Eitel, François Gannaz, Freiric Barral,
50425059Freirich Raabe, Frerich Raabe, Fyodor Sheremetyev, Gabor Pali, Gavin
@@ -5047,9 +5064,9 @@ Portnov, Ivo Clarysse, J.
50475064Lewis Muir, Jaime Marquínez Ferrándiz, Jakob Voß, James Aspnes, Jamie F.
50485065Olson, Jan Larres, Jan Schulz, Jason Ronallo, Jeff Arnold, Jeff
50495066Runningen, Jens Petersen, Jesse Rosenthal, Joe Hillenbrand, John
5050−MacFarlane, Jonas Smedegaard, Jonathan Daugherty, Jose Luis Duran, Josef
5051−Svenningsson, Julien Cretel, Juliusz Gonera, Justin Bogner, Jérémy
5052−Bobbio, Kelsey Hightower, Kolen Cheung, KolenCheung, Konstantin Zudov,
5067+MacFarlane, John Muccigrosso, Jonas Smedegaard, Jonathan Daugherty, Jose
5068+Luis Duran, Josef Svenningsson, Julien Cretel, Juliusz Gonera, Justin
5069+Bogner, Jérémy Bobbio, Kelsey Hightower, Kolen Cheung, Konstantin Zudov,
50535070Kristof Bastiaensen, Lars\-Dominik Braun, Luke Plant, Mark Szepieniec,
50545071Mark Wright, Martin Linn, Masayoshi Takahashi, Matej Kollar, Mathias
50555072Schenner, Mathieu Duponchelle, Matthew Eddey, Matthew Pickering,
@@ -5065,10 +5082,11 @@ Silva, Recai Oktaş, RyanGlScott, Scott Morrison, Sergei Trofimovich,
50655082Sergey Astanin, Shahbaz Youssefi, Shaun Attfield, Sidarth Kapur,
50665083Sidharth Kapur, Simon Hengel, Sumit Sahrawat, Thomas Hodgson, Thomas
50675084Weiß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,
5069−Waldir Pimenta, Wikiwide, Xavier Olive, csforste, infinity0x, nkalvi,
5070−qerub, robabla, roblabla, rodja.trappe, rski, shreevatsa.public,
5071−takahashim, thsutton.
5085+Leese, Uli Köhler, Václav Zeman, Viktor Kronvall, Vincent, Václav
5086+Haisman, Václav Zeman, Wandmalfarbe, Waldir Pimenta, Wikiwide, Xavier
5087+Olive, bumper314, csforste, infinity0x, nkalvi, qerub, robabla,
5088+roblabla, rodja.trappe, rski, shreevatsa.public, takahashim, tgkokk,
5089+thsutton.
50725090.PP
50735091The Pandoc source code and all documentation may be downloaded
50745092from <http://pandoc.org>.