@@ -1,10 +1,10 @@
11.\"t
2−.TH PANDOC 1 "September 27, 2018" "pandoc 2.3.1"
2+.TH PANDOC 1 "September 27, 2018" "pandoc 2.4"
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[R] [\f[I]options\f[R]] [\f[I]input\-file\f[R]]...
88.SH DESCRIPTION
99.PP
1010Pandoc is a Haskell library for converting from one markup format to
@@ -14,7 +14,7 @@ Pandoc can convert between numerous markup and word processing formats,
1414including, but not limited to, various flavors of Markdown, HTML, LaTeX
1515and Word docx.
1616For the full lists of input and output formats, see the
17−\f[C]\-\-from\f[] and \f[C]\-\-to\f[] options below.
17+\f[C]\-\-from\f[R] and \f[C]\-\-to\f[R] options below.
1818Pandoc can also produce PDF output: see creating a PDF, below.
1919.PP
2020Pandoc\[aq]s enhanced version of Markdown includes syntax for tables,
@@ -24,7 +24,7 @@ See below under Pandoc\[aq]s Markdown.
2424.PP
2525Pandoc has a modular design: it consists of a set of readers, which
2626parse text in a given format and produce a native representation of the
27−document (an \f[I]abstract syntax tree\f[] or AST), and a set of
27+document (an \f[I]abstract syntax tree\f[R] or AST), and a set of
2828writers, which convert this native representation into a target format.
2929Thus, adding an input or output format requires only adding a reader or
3030writer.
@@ -40,158 +40,160 @@ pandoc\[aq]s simple document model.
4040While conversions from pandoc\[aq]s Markdown to all formats aspire to be
4141perfect, conversions from formats more expressive than pandoc\[aq]s
4242Markdown can be expected to be lossy.
43−.SS Using \f[C]pandoc\f[]
43+.SS Using \f[C]pandoc\f[R]
4444.PP
45−If no \f[I]input\-files\f[] are specified, input is read from
46−\f[I]stdin\f[].
47−Output goes to \f[I]stdout\f[] by default.
48−For output to a file, use the \f[C]\-o\f[] option:
45+If no \f[I]input\-files\f[R] are specified, input is read from
46+\f[I]stdin\f[R].
47+Output goes to \f[I]stdout\f[R] by default.
48+For output to a file, use the \f[C]\-o\f[R] option:
4949.IP
5050.nf
5151\f[C]
5252pandoc\ \-o\ output.html\ input.txt
53−\f[]
53+\f[R]
5454.fi
5555.PP
5656By default, pandoc produces a document fragment.
5757To produce a standalone document (e.g.
58−a valid HTML file including \f[C]<head>\f[] and \f[C]<body>\f[]), use
59−the \f[C]\-s\f[] or \f[C]\-\-standalone\f[] flag:
58+a valid HTML file including \f[C]<head>\f[R] and \f[C]<body>\f[R]), use
59+the \f[C]\-s\f[R] or \f[C]\-\-standalone\f[R] flag:
6060.IP
6161.nf
6262\f[C]
6363pandoc\ \-s\ \-o\ output.html\ input.txt
64−\f[]
64+\f[R]
6565.fi
6666.PP
6767For more information on how standalone documents are produced, see
6868Templates below.
6969.PP
70−If multiple input files are given, \f[C]pandoc\f[] will concatenate them
71−all (with blank lines between them) before parsing.
72−(Use \f[C]\-\-file\-scope\f[] to parse files individually.)
70+If multiple input files are given, \f[C]pandoc\f[R] will concatenate
71+them all (with blank lines between them) before parsing.
72+(Use \f[C]\-\-file\-scope\f[R] to parse files individually.)
7373.SS Specifying formats
7474.PP
7575The format of the input and output can be specified explicitly using
7676command\-line options.
77−The input format can be specified using the \f[C]\-f/\-\-from\f[]
78−option, the output format using the \f[C]\-t/\-\-to\f[] option.
79−Thus, to convert \f[C]hello.txt\f[] from Markdown to LaTeX, you could
77+The input format can be specified using the \f[C]\-f/\-\-from\f[R]
78+option, the output format using the \f[C]\-t/\-\-to\f[R] option.
79+Thus, to convert \f[C]hello.txt\f[R] from Markdown to LaTeX, you could
8080type:
8181.IP
8282.nf
8383\f[C]
8484pandoc\ \-f\ markdown\ \-t\ latex\ hello.txt
85−\f[]
85+\f[R]
8686.fi
8787.PP
88−To convert \f[C]hello.html\f[] from HTML to Markdown:
88+To convert \f[C]hello.html\f[R] from HTML to Markdown:
8989.IP
9090.nf
9191\f[C]
9292pandoc\ \-f\ html\ \-t\ markdown\ hello.html
93−\f[]
93+\f[R]
9494.fi
9595.PP
9696Supported input and output formats are listed below under Options (see
97−\f[C]\-f\f[] for input formats and \f[C]\-t\f[] for output formats).
98−You can also use \f[C]pandoc\ \-\-list\-input\-formats\f[] and
99−\f[C]pandoc\ \-\-list\-output\-formats\f[] to print lists of supported
97+\f[C]\-f\f[R] for input formats and \f[C]\-t\f[R] for output formats).
98+You can also use \f[C]pandoc\ \-\-list\-input\-formats\f[R] and
99+\f[C]pandoc\ \-\-list\-output\-formats\f[R] to print lists of supported
100100formats.
101101.PP
102102If the input or output format is not specified explicitly,
103−\f[C]pandoc\f[] will attempt to guess it from the extensions of the
103+\f[C]pandoc\f[R] will attempt to guess it from the extensions of the
104104filenames.
105105Thus, for example,
106106.IP
107107.nf
108108\f[C]
109109pandoc\ \-o\ hello.tex\ hello.txt
110−\f[]
110+\f[R]
111111.fi
112112.PP
113−will convert \f[C]hello.txt\f[] from Markdown to LaTeX.
114−If no output file is specified (so that output goes to \f[I]stdout\f[]),
115−or if the output file\[aq]s extension is unknown, the output format will
116−default to HTML.
117−If no input file is specified (so that input comes from \f[I]stdin\f[]),
118−or if the input files\[aq] extensions are unknown, the input format will
119−be assumed to be Markdown.
113+will convert \f[C]hello.txt\f[R] from Markdown to LaTeX.
114+If no output file is specified (so that output goes to
115+\f[I]stdout\f[R]), or if the output file\[aq]s extension is unknown, the
116+output format will default to HTML.
117+If no input file is specified (so that input comes from
118+\f[I]stdin\f[R]), or if the input files\[aq] extensions are unknown, the
119+input format will be assumed to be Markdown.
120120.SS Character encoding
121121.PP
122122Pandoc uses the UTF\-8 character encoding for both input and output.
123123If your local character encoding is not UTF\-8, you should pipe input
124−and output through \f[C]iconv\f[]:
124+and output through \f[C]iconv\f[R]:
125125.IP
126126.nf
127127\f[C]
128128iconv\ \-t\ utf\-8\ input.txt\ |\ pandoc\ |\ iconv\ \-f\ utf\-8
129−\f[]
129+\f[R]
130130.fi
131131.PP
132132Note that in some output formats (such as HTML, LaTeX, ConTeXt, RTF,
133133OPML, DocBook, and Texinfo), information about the character encoding is
134134included in the document header, which will only be included if you use
135−the \f[C]\-s/\-\-standalone\f[] option.
135+the \f[C]\-s/\-\-standalone\f[R] option.
136136.SS Creating a PDF
137137.PP
138−To produce a PDF, specify an output file with a \f[C]\&.pdf\f[]
138+To produce a PDF, specify an output file with a \f[C]\&.pdf\f[R]
139139extension:
140140.IP
141141.nf
142142\f[C]
143143pandoc\ test.txt\ \-o\ test.pdf
144−\f[]
144+\f[R]
145145.fi
146146.PP
147147By default, pandoc will use LaTeX to create the PDF, which requires that
148−a LaTeX engine be installed (see \f[C]\-\-pdf\-engine\f[] below).
148+a LaTeX engine be installed (see \f[C]\-\-pdf\-engine\f[R] below).
149149.PP
150−Alternatively, pandoc can use ConTeXt, \f[C]pdfroff\f[], or any of the
150+Alternatively, pandoc can use ConTeXt, \f[C]pdfroff\f[R], or any of the
151151following HTML/CSS\-to\-PDF\-engines, to create a PDF:
152−\f[C]wkhtmltopdf\f[], \f[C]weasyprint\f[] or \f[C]prince\f[].
153−To do this, specify an output file with a \f[C]\&.pdf\f[] extension, as
154−before, but add the \f[C]\-\-pdf\-engine\f[] option or
155−\f[C]\-t\ context\f[], \f[C]\-t\ html\f[], or \f[C]\-t\ ms\f[] to the
156−command line (\f[C]\-t\ html\f[] defaults to
157−\f[C]\-\-pdf\-engine=wkhtmltopdf\f[]).
152+\f[C]wkhtmltopdf\f[R], \f[C]weasyprint\f[R] or \f[C]prince\f[R].
153+To do this, specify an output file with a \f[C]\&.pdf\f[R] extension, as
154+before, but add the \f[C]\-\-pdf\-engine\f[R] option or
155+\f[C]\-t\ context\f[R], \f[C]\-t\ html\f[R], or \f[C]\-t\ ms\f[R] to the
156+command line (\f[C]\-t\ html\f[R] defaults to
157+\f[C]\-\-pdf\-engine=wkhtmltopdf\f[R]).
158158.PP
159159PDF output can be controlled using variables for LaTeX (if LaTeX is
160160used) and variables for ConTeXt (if ConTeXt is used).
161−When using an HTML/CSS\-to\-PDF\-engine, \f[C]\-\-css\f[] affects the
161+When using an HTML/CSS\-to\-PDF\-engine, \f[C]\-\-css\f[R] affects the
162162output.
163−If \f[C]wkhtmltopdf\f[] is used, then the variables
164−\f[C]margin\-left\f[], \f[C]margin\-right\f[], \f[C]margin\-top\f[],
165−\f[C]margin\-bottom\f[], \f[C]footer\-html\f[], \f[C]header\-html\f[]
166−and \f[C]papersize\f[] will affect the output.
163+If \f[C]wkhtmltopdf\f[R] is used, then the variables
164+\f[C]margin\-left\f[R], \f[C]margin\-right\f[R], \f[C]margin\-top\f[R],
165+\f[C]margin\-bottom\f[R], \f[C]footer\-html\f[R], \f[C]header\-html\f[R]
166+and \f[C]papersize\f[R] will affect the output.
167167.PP
168168To debug the PDF creation, it can be useful to look at the intermediate
169−representation: instead of \f[C]\-o\ test.pdf\f[], use for example
170−\f[C]\-s\ \-o\ test.tex\f[] to output the generated LaTeX.
171−You can then test it with \f[C]pdflatex\ test.tex\f[].
169+representation: instead of \f[C]\-o\ test.pdf\f[R], use for example
170+\f[C]\-s\ \-o\ test.tex\f[R] to output the generated LaTeX.
171+You can then test it with \f[C]pdflatex\ test.tex\f[R].
172172.PP
173173When using LaTeX, the following packages need to be available (they are
174−included with all recent versions of TeX Live): \f[C]amsfonts\f[],
175−\f[C]amsmath\f[], \f[C]lm\f[], \f[C]unicode\-math\f[], \f[C]ifxetex\f[],
176−\f[C]ifluatex\f[], \f[C]listings\f[] (if the \f[C]\-\-listings\f[]
177−option is used), \f[C]fancyvrb\f[], \f[C]longtable\f[],
178−\f[C]booktabs\f[], \f[C]graphicx\f[] and \f[C]grffile\f[] (if the
179−document contains images), \f[C]hyperref\f[], \f[C]xcolor\f[] (with
180−\f[C]colorlinks\f[]), \f[C]ulem\f[], \f[C]geometry\f[] (with the
181−\f[C]geometry\f[] variable set), \f[C]setspace\f[] (with
182−\f[C]linestretch\f[]), and \f[C]babel\f[] (with \f[C]lang\f[]).
183−The use of \f[C]xelatex\f[] or \f[C]lualatex\f[] as the LaTeX engine
184−requires \f[C]fontspec\f[].
185−\f[C]xelatex\f[] uses \f[C]polyglossia\f[] (with \f[C]lang\f[]),
186−\f[C]xecjk\f[], and \f[C]bidi\f[] (with the \f[C]dir\f[] variable set).
187−If the \f[C]mathspec\f[] variable is set, \f[C]xelatex\f[] will use
188−\f[C]mathspec\f[] instead of \f[C]unicode\-math\f[].
189−The \f[C]upquote\f[] and \f[C]microtype\f[] packages are used if
190−available, and \f[C]csquotes\f[] will be used for typography if
191−\f[C]\\usepackage{csquotes}\f[] is present in the template or included
192−via \f[C]/H/\-\-include\-in\-header\f[].
193−The \f[C]natbib\f[], \f[C]biblatex\f[], \f[C]bibtex\f[], and
194−\f[C]biber\f[] packages can optionally be used for citation rendering.
174+included with all recent versions of TeX Live): \f[C]amsfonts\f[R],
175+\f[C]amsmath\f[R], \f[C]lm\f[R], \f[C]unicode\-math\f[R],
176+\f[C]ifxetex\f[R], \f[C]ifluatex\f[R], \f[C]listings\f[R] (if the
177+\f[C]\-\-listings\f[R] option is used), \f[C]fancyvrb\f[R],
178+\f[C]longtable\f[R], \f[C]booktabs\f[R], \f[C]graphicx\f[R] and
179+\f[C]grffile\f[R] (if the document contains images), \f[C]hyperref\f[R],
180+\f[C]xcolor\f[R] (with \f[C]colorlinks\f[R]), \f[C]ulem\f[R],
181+\f[C]geometry\f[R] (with the \f[C]geometry\f[R] variable set),
182+\f[C]setspace\f[R] (with \f[C]linestretch\f[R]), and \f[C]babel\f[R]
183+(with \f[C]lang\f[R]).
184+The use of \f[C]xelatex\f[R] or \f[C]lualatex\f[R] as the LaTeX engine
185+requires \f[C]fontspec\f[R].
186+\f[C]xelatex\f[R] uses \f[C]polyglossia\f[R] (with \f[C]lang\f[R]),
187+\f[C]xecjk\f[R], and \f[C]bidi\f[R] (with the \f[C]dir\f[R] variable
188+set).
189+If the \f[C]mathspec\f[R] variable is set, \f[C]xelatex\f[R] will use
190+\f[C]mathspec\f[R] instead of \f[C]unicode\-math\f[R].
191+The \f[C]upquote\f[R] and \f[C]microtype\f[R] packages are used if
192+available, and \f[C]csquotes\f[R] will be used for typography if
193+\f[C]\[rs]usepackage{csquotes}\f[R] is present in the template or
194+included via \f[C]/H/\-\-include\-in\-header\f[R].
195+The \f[C]natbib\f[R], \f[C]biblatex\f[R], \f[C]bibtex\f[R], and
196+\f[C]biber\f[R] packages can optionally be used for citation rendering.
195197.SS Reading from the Web
196198.PP
197199Instead of an input file, an absolute URI may be given.
@@ -200,7 +202,7 @@ In this case pandoc will fetch the content using HTTP:
200202.nf
201203\f[C]
202204pandoc\ \-f\ html\ \-t\ markdown\ http://www.fsf.org
203−\f[]
205+\f[R]
204206.fi
205207.PP
206208It is possible to supply a custom User\-Agent string or other header
@@ -208,202 +210,203 @@ when requesting a document from a URL:
208210.IP
209211.nf
210212\f[C]
211−pandoc\ \-f\ html\ \-t\ markdown\ \-\-request\-header\ User\-Agent:"Mozilla/5.0"\ \\
213+pandoc\ \-f\ html\ \-t\ markdown\ \-\-request\-header\ User\-Agent:\[dq]Mozilla/5.0\[dq]\ \[rs]
212214\ \ http://www.fsf.org
213−\f[]
215+\f[R]
214216.fi
215217.SH OPTIONS
216218.SS General options
217219.TP
218−.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[]
220+.B \f[C]\-f\f[R] \f[I]FORMAT\f[R], \f[C]\-r\f[R] \f[I]FORMAT\f[R], \f[C]\-\-from=\f[R]\f[I]FORMAT\f[R], \f[C]\-\-read=\f[R]\f[I]FORMAT\f[R]
219221Specify input format.
220−\f[I]FORMAT\f[] can be:
222+\f[I]FORMAT\f[R] can be:
221223.RS
222224.IP \[bu] 2
223−\f[C]commonmark\f[] (CommonMark Markdown)
225+\f[C]commonmark\f[R] (CommonMark Markdown)
224226.IP \[bu] 2
225−\f[C]creole\f[] (Creole 1.0)
227+\f[C]creole\f[R] (Creole 1.0)
226228.IP \[bu] 2
227−\f[C]docbook\f[] (DocBook)
229+\f[C]docbook\f[R] (DocBook)
228230.IP \[bu] 2
229−\f[C]docx\f[] (Word docx)
231+\f[C]docx\f[R] (Word docx)
230232.IP \[bu] 2
231−\f[C]epub\f[] (EPUB)
233+\f[C]epub\f[R] (EPUB)
232234.IP \[bu] 2
233−\f[C]fb2\f[] (FictionBook2 e\-book)
235+\f[C]fb2\f[R] (FictionBook2 e\-book)
234236.IP \[bu] 2
235−\f[C]gfm\f[] (GitHub\-Flavored Markdown), or the deprecated and less
236−accurate \f[C]markdown_github\f[]; use \f[C]markdown_github\f[] only if
237−you need extensions not supported in \f[C]gfm\f[].
237+\f[C]gfm\f[R] (GitHub\-Flavored Markdown), or the deprecated and less
238+accurate \f[C]markdown_github\f[R]; use \f[C]markdown_github\f[R] only
239+if you need extensions not supported in \f[C]gfm\f[R].
238240.IP \[bu] 2
239−\f[C]haddock\f[] (Haddock markup)
241+\f[C]haddock\f[R] (Haddock markup)
240242.IP \[bu] 2
241−\f[C]html\f[] (HTML)
243+\f[C]html\f[R] (HTML)
242244.IP \[bu] 2
243−\f[C]jats\f[] (JATS XML)
245+\f[C]jats\f[R] (JATS XML)
244246.IP \[bu] 2
245−\f[C]json\f[] (JSON version of native AST)
247+\f[C]json\f[R] (JSON version of native AST)
246248.IP \[bu] 2
247−\f[C]latex\f[] (LaTeX)
249+\f[C]latex\f[R] (LaTeX)
248250.IP \[bu] 2
249−\f[C]markdown\f[] (Pandoc\[aq]s Markdown)
251+\f[C]markdown\f[R] (Pandoc\[aq]s Markdown)
250252.IP \[bu] 2
251−\f[C]markdown_mmd\f[] (MultiMarkdown)
253+\f[C]markdown_mmd\f[R] (MultiMarkdown)
252254.IP \[bu] 2
253−\f[C]markdown_phpextra\f[] (PHP Markdown Extra)
255+\f[C]markdown_phpextra\f[R] (PHP Markdown Extra)
254256.IP \[bu] 2
255−\f[C]markdown_strict\f[] (original unextended Markdown)
257+\f[C]markdown_strict\f[R] (original unextended Markdown)
256258.IP \[bu] 2
257−\f[C]mediawiki\f[] (MediaWiki markup)
259+\f[C]mediawiki\f[R] (MediaWiki markup)
258260.IP \[bu] 2
259−\f[C]muse\f[] (Muse)
261+\f[C]muse\f[R] (Muse)
260262.IP \[bu] 2
261−\f[C]native\f[] (native Haskell)
263+\f[C]native\f[R] (native Haskell)
262264.IP \[bu] 2
263−\f[C]odt\f[] (ODT)
265+\f[C]odt\f[R] (ODT)
264266.IP \[bu] 2
265−\f[C]opml\f[] (OPML)
267+\f[C]opml\f[R] (OPML)
266268.IP \[bu] 2
267−\f[C]org\f[] (Emacs Org mode)
269+\f[C]org\f[R] (Emacs Org mode)
268270.IP \[bu] 2
269−\f[C]rst\f[] (reStructuredText)
271+\f[C]rst\f[R] (reStructuredText)
270272.IP \[bu] 2
271−\f[C]t2t\f[] (txt2tags)
273+\f[C]t2t\f[R] (txt2tags)
272274.IP \[bu] 2
273−\f[C]textile\f[] (Textile)
275+\f[C]textile\f[R] (Textile)
274276.IP \[bu] 2
275−\f[C]tikiwiki\f[] (TikiWiki markup)
277+\f[C]tikiwiki\f[R] (TikiWiki markup)
276278.IP \[bu] 2
277−\f[C]twiki\f[] (TWiki markup)
279+\f[C]twiki\f[R] (TWiki markup)
278280.IP \[bu] 2
279−\f[C]vimwiki\f[] (Vimwiki)
281+\f[C]vimwiki\f[R] (Vimwiki)
280282.PP
281283Extensions can be individually enabled or disabled by appending
282−\f[C]+EXTENSION\f[] or \f[C]\-EXTENSION\f[] to the format name.
284+\f[C]+EXTENSION\f[R] or \f[C]\-EXTENSION\f[R] to the format name.
283285See Extensions below, for a list of extensions and their names.
284−See \f[C]\-\-list\-input\-formats\f[] and \f[C]\-\-list\-extensions\f[],
285−below.
286+See \f[C]\-\-list\-input\-formats\f[R] and
287+\f[C]\-\-list\-extensions\f[R], below.
286288.RE
287289.TP
288−.B \f[C]\-t\f[] \f[I]FORMAT\f[], \f[C]\-w\f[] \f[I]FORMAT\f[], \f[C]\-\-to=\f[]\f[I]FORMAT\f[], \f[C]\-\-write=\f[]\f[I]FORMAT\f[]
290+.B \f[C]\-t\f[R] \f[I]FORMAT\f[R], \f[C]\-w\f[R] \f[I]FORMAT\f[R], \f[C]\-\-to=\f[R]\f[I]FORMAT\f[R], \f[C]\-\-write=\f[R]\f[I]FORMAT\f[R]
289291Specify output format.
290−\f[I]FORMAT\f[] can be:
292+\f[I]FORMAT\f[R] can be:
291293.RS
292294.IP \[bu] 2
293−\f[C]asciidoc\f[] (AsciiDoc)
295+\f[C]asciidoc\f[R] (AsciiDoc)
294296.IP \[bu] 2
295−\f[C]beamer\f[] (LaTeX beamer slide show)
297+\f[C]beamer\f[R] (LaTeX beamer slide show)
296298.IP \[bu] 2
297−\f[C]commonmark\f[] (CommonMark Markdown)
299+\f[C]commonmark\f[R] (CommonMark Markdown)
298300.IP \[bu] 2
299−\f[C]context\f[] (ConTeXt)
301+\f[C]context\f[R] (ConTeXt)
300302.IP \[bu] 2
301−\f[C]docbook\f[] or \f[C]docbook4\f[] (DocBook 4)
303+\f[C]docbook\f[R] or \f[C]docbook4\f[R] (DocBook 4)
302304.IP \[bu] 2
303−\f[C]docbook5\f[] (DocBook 5)
305+\f[C]docbook5\f[R] (DocBook 5)
304306.IP \[bu] 2
305−\f[C]docx\f[] (Word docx)
307+\f[C]docx\f[R] (Word docx)
306308.IP \[bu] 2
307−\f[C]dokuwiki\f[] (DokuWiki markup)
309+\f[C]dokuwiki\f[R] (DokuWiki markup)
308310.IP \[bu] 2
309−\f[C]epub\f[] or \f[C]epub3\f[] (EPUB v3 book)
311+\f[C]epub\f[R] or \f[C]epub3\f[R] (EPUB v3 book)
310312.IP \[bu] 2
311−\f[C]epub2\f[] (EPUB v2)
313+\f[C]epub2\f[R] (EPUB v2)
312314.IP \[bu] 2
313−\f[C]fb2\f[] (FictionBook2 e\-book)
315+\f[C]fb2\f[R] (FictionBook2 e\-book)
314316.IP \[bu] 2
315−\f[C]gfm\f[] (GitHub\-Flavored Markdown), or the deprecated and less
316−accurate \f[C]markdown_github\f[]; use \f[C]markdown_github\f[] only if
317−you need extensions not supported in \f[C]gfm\f[].
317+\f[C]gfm\f[R] (GitHub\-Flavored Markdown), or the deprecated and less
318+accurate \f[C]markdown_github\f[R]; use \f[C]markdown_github\f[R] only
319+if you need extensions not supported in \f[C]gfm\f[R].
318320.IP \[bu] 2
319−\f[C]haddock\f[] (Haddock markup)
321+\f[C]haddock\f[R] (Haddock markup)
320322.IP \[bu] 2
321−\f[C]html\f[] or \f[C]html5\f[] (HTML, i.e.
323+\f[C]html\f[R] or \f[C]html5\f[R] (HTML, i.e.
322324HTML5/XHTML polyglot markup)
323325.IP \[bu] 2
324−\f[C]html4\f[] (XHTML 1.0 Transitional)
326+\f[C]html4\f[R] (XHTML 1.0 Transitional)
325327.IP \[bu] 2
326−\f[C]icml\f[] (InDesign ICML)
328+\f[C]icml\f[R] (InDesign ICML)
327329.IP \[bu] 2
328−\f[C]jats\f[] (JATS XML)
330+\f[C]jats\f[R] (JATS XML)
329331.IP \[bu] 2
330−\f[C]json\f[] (JSON version of native AST)
332+\f[C]json\f[R] (JSON version of native AST)
331333.IP \[bu] 2
332−\f[C]latex\f[] (LaTeX)
334+\f[C]latex\f[R] (LaTeX)
333335.IP \[bu] 2
334−\f[C]man\f[] (groff man)
336+\f[C]man\f[R] (groff man)
335337.IP \[bu] 2
336−\f[C]markdown\f[] (Pandoc\[aq]s Markdown)
338+\f[C]markdown\f[R] (Pandoc\[aq]s Markdown)
337339.IP \[bu] 2
338−\f[C]markdown_mmd\f[] (MultiMarkdown)
340+\f[C]markdown_mmd\f[R] (MultiMarkdown)
339341.IP \[bu] 2
340−\f[C]markdown_phpextra\f[] (PHP Markdown Extra)
342+\f[C]markdown_phpextra\f[R] (PHP Markdown Extra)
341343.IP \[bu] 2
342−\f[C]markdown_strict\f[] (original unextended Markdown)
344+\f[C]markdown_strict\f[R] (original unextended Markdown)
343345.IP \[bu] 2
344−\f[C]mediawiki\f[] (MediaWiki markup)
346+\f[C]mediawiki\f[R] (MediaWiki markup)
345347.IP \[bu] 2
346−\f[C]ms\f[] (groff ms)
348+\f[C]ms\f[R] (groff ms)
347349.IP \[bu] 2
348−\f[C]muse\f[] (Muse),
350+\f[C]muse\f[R] (Muse),
349351.IP \[bu] 2
350−\f[C]native\f[] (native Haskell),
352+\f[C]native\f[R] (native Haskell),
351353.IP \[bu] 2
352−\f[C]odt\f[] (OpenOffice text document)
354+\f[C]odt\f[R] (OpenOffice text document)
353355.IP \[bu] 2
354−\f[C]opml\f[] (OPML)
356+\f[C]opml\f[R] (OPML)
355357.IP \[bu] 2
356−\f[C]opendocument\f[] (OpenDocument)
358+\f[C]opendocument\f[R] (OpenDocument)
357359.IP \[bu] 2
358−\f[C]org\f[] (Emacs Org mode)
360+\f[C]org\f[R] (Emacs Org mode)
359361.IP \[bu] 2
360−\f[C]plain\f[] (plain text),
362+\f[C]plain\f[R] (plain text),
361363.IP \[bu] 2
362−\f[C]pptx\f[] (PowerPoint slide show)
364+\f[C]pptx\f[R] (PowerPoint slide show)
363365.IP \[bu] 2
364−\f[C]rst\f[] (reStructuredText)
366+\f[C]rst\f[R] (reStructuredText)
365367.IP \[bu] 2
366−\f[C]rtf\f[] (Rich Text Format)
368+\f[C]rtf\f[R] (Rich Text Format)
367369.IP \[bu] 2
368−\f[C]texinfo\f[] (GNU Texinfo)
370+\f[C]texinfo\f[R] (GNU Texinfo)
369371.IP \[bu] 2
370−\f[C]textile\f[] (Textile)
372+\f[C]textile\f[R] (Textile)
371373.IP \[bu] 2
372−\f[C]slideous\f[] (Slideous HTML and JavaScript slide show)
374+\f[C]slideous\f[R] (Slideous HTML and JavaScript slide show)
373375.IP \[bu] 2
374−\f[C]slidy\f[] (Slidy HTML and JavaScript slide show)
376+\f[C]slidy\f[R] (Slidy HTML and JavaScript slide show)
375377.IP \[bu] 2
376−\f[C]dzslides\f[] (DZSlides HTML5 + JavaScript slide show),
378+\f[C]dzslides\f[R] (DZSlides HTML5 + JavaScript slide show),
377379.IP \[bu] 2
378−\f[C]revealjs\f[] (reveal.js HTML5 + JavaScript slide show)
380+\f[C]revealjs\f[R] (reveal.js HTML5 + JavaScript slide show)
379381.IP \[bu] 2
380−\f[C]s5\f[] (S5 HTML and JavaScript slide show)
382+\f[C]s5\f[R] (S5 HTML and JavaScript slide show)
381383.IP \[bu] 2
382−\f[C]tei\f[] (TEI Simple)
384+\f[C]tei\f[R] (TEI Simple)
383385.IP \[bu] 2
384−\f[C]zimwiki\f[] (ZimWiki markup)
386+\f[C]zimwiki\f[R] (ZimWiki markup)
385387.IP \[bu] 2
386388the path of a custom lua writer, see Custom writers below
387389.PP
388−Note that \f[C]odt\f[], \f[C]docx\f[], and \f[C]epub\f[] output will not
389−be directed to \f[I]stdout\f[] unless forced with \f[C]\-o\ \-\f[].
390+Note that \f[C]odt\f[R], \f[C]docx\f[R], and \f[C]epub\f[R] output will
391+not be directed to \f[I]stdout\f[R] unless forced with
392+\f[C]\-o\ \-\f[R].
390393.PP
391394Extensions can be individually enabled or disabled by appending
392−\f[C]+EXTENSION\f[] or \f[C]\-EXTENSION\f[] to the format name.
395+\f[C]+EXTENSION\f[R] or \f[C]\-EXTENSION\f[R] to the format name.
393396See Extensions below, for a list of extensions and their names.
394−See \f[C]\-\-list\-output\-formats\f[] and
395−\f[C]\-\-list\-extensions\f[], below.
397+See \f[C]\-\-list\-output\-formats\f[R] and
398+\f[C]\-\-list\-extensions\f[R], below.
396399.RE
397400.TP
398−.B \f[C]\-o\f[] \f[I]FILE\f[], \f[C]\-\-output=\f[]\f[I]FILE\f[]
399−Write output to \f[I]FILE\f[] instead of \f[I]stdout\f[].
400−If \f[I]FILE\f[] is \f[C]\-\f[], output will go to \f[I]stdout\f[], even
401−if a non\-textual format (\f[C]docx\f[], \f[C]odt\f[], \f[C]epub2\f[],
402−\f[C]epub3\f[]) is specified.
401+.B \f[C]\-o\f[R] \f[I]FILE\f[R], \f[C]\-\-output=\f[R]\f[I]FILE\f[R]
402+Write output to \f[I]FILE\f[R] instead of \f[I]stdout\f[R].
403+If \f[I]FILE\f[R] is \f[C]\-\f[R], output will go to \f[I]stdout\f[R],
404+even if a non\-textual format (\f[C]docx\f[R], \f[C]odt\f[R],
405+\f[C]epub2\f[R], \f[C]epub3\f[R]) is specified.
403406.RS
404407.RE
405408.TP
406−.B \f[C]\-\-data\-dir=\f[]\f[I]DIRECTORY\f[]
409+.B \f[C]\-\-data\-dir=\f[R]\f[I]DIRECTORY\f[R]
407410Specify the user data directory to search for pandoc data files.
408411If this option is not specified, the default user data directory will be
409412used.
@@ -413,131 +416,131 @@ This is, in UNIX:
413416.nf
414417\f[C]
415418$HOME/.pandoc
416−\f[]
419+\f[R]
417420.fi
418421.PP
419422in Windows XP:
420423.IP
421424.nf
422425\f[C]
423−C:\\Documents\ And\ Settings\\USERNAME\\Application\ Data\\pandoc
424−\f[]
426+C:\[rs]Documents\ And\ Settings\[rs]USERNAME\[rs]Application\ Data\[rs]pandoc
427+\f[R]
425428.fi
426429.PP
427430and in Windows Vista or later:
428431.IP
429432.nf
430433\f[C]
431−C:\\Users\\USERNAME\\AppData\\Roaming\\pandoc
432−\f[]
434+C:\[rs]Users\[rs]USERNAME\[rs]AppData\[rs]Roaming\[rs]pandoc
435+\f[R]
433436.fi
434437.PP
435438You can find the default user data directory on your system by looking
436−at the output of \f[C]pandoc\ \-\-version\f[].
437−A \f[C]reference.odt\f[], \f[C]reference.docx\f[], \f[C]epub.css\f[],
438−\f[C]templates\f[], \f[C]slidy\f[], \f[C]slideous\f[], or \f[C]s5\f[]
439−directory placed in this directory will override pandoc\[aq]s normal
440−defaults.
439+at the output of \f[C]pandoc\ \-\-version\f[R].
440+A \f[C]reference.odt\f[R], \f[C]reference.docx\f[R], \f[C]epub.css\f[R],
441+\f[C]templates\f[R], \f[C]slidy\f[R], \f[C]slideous\f[R], or
442+\f[C]s5\f[R] directory placed in this directory will override
443+pandoc\[aq]s normal defaults.
441444.RE
442445.TP
443−.B \f[C]\-\-bash\-completion\f[]
446+.B \f[C]\-\-bash\-completion\f[R]
444447Generate a bash completion script.
445448To enable bash completion with pandoc, add this to your
446−\f[C]\&.bashrc\f[]:
449+\f[C]\&.bashrc\f[R]:
447450.RS
448451.IP
449452.nf
450453\f[C]
451−eval\ "$(pandoc\ \-\-bash\-completion)"
452−\f[]
454+eval\ \[dq]$(pandoc\ \-\-bash\-completion)\[dq]
455+\f[R]
453456.fi
454457.RE
455458.TP
456−.B \f[C]\-\-verbose\f[]
459+.B \f[C]\-\-verbose\f[R]
457460Give verbose debugging output.
458461Currently this only has an effect with PDF output.
459462.RS
460463.RE
461464.TP
462−.B \f[C]\-\-quiet\f[]
465+.B \f[C]\-\-quiet\f[R]
463466Suppress warning messages.
464467.RS
465468.RE
466469.TP
467−.B \f[C]\-\-fail\-if\-warnings\f[]
470+.B \f[C]\-\-fail\-if\-warnings\f[R]
468471Exit with error status if there are any warnings.
469472.RS
470473.RE
471474.TP
472−.B \f[C]\-\-log=\f[]\f[I]FILE\f[]
473−Write log messages in machine\-readable JSON format to \f[I]FILE\f[].
475+.B \f[C]\-\-log=\f[R]\f[I]FILE\f[R]
476+Write log messages in machine\-readable JSON format to \f[I]FILE\f[R].
474477All messages above DEBUG level will be written, regardless of verbosity
475−settings (\f[C]\-\-verbose\f[], \f[C]\-\-quiet\f[]).
478+settings (\f[C]\-\-verbose\f[R], \f[C]\-\-quiet\f[R]).
476479.RS
477480.RE
478481.TP
479−.B \f[C]\-\-list\-input\-formats\f[]
482+.B \f[C]\-\-list\-input\-formats\f[R]
480483List supported input formats, one per line.
481484.RS
482485.RE
483486.TP
484−.B \f[C]\-\-list\-output\-formats\f[]
487+.B \f[C]\-\-list\-output\-formats\f[R]
485488List supported output formats, one per line.
486489.RS
487490.RE
488491.TP
489−.B \f[C]\-\-list\-extensions\f[][\f[C]=\f[]\f[I]FORMAT\f[]]
490−List supported extensions, one per line, preceded by a \f[C]+\f[] or
491−\f[C]\-\f[] indicating whether it is enabled by default in
492−\f[I]FORMAT\f[].
493−If \f[I]FORMAT\f[] is not specified, defaults for pandoc\[aq]s Markdown
492+.B \f[C]\-\-list\-extensions\f[R][\f[C]=\f[R]\f[I]FORMAT\f[R]]
493+List supported extensions, one per line, preceded by a \f[C]+\f[R] or
494+\f[C]\-\f[R] indicating whether it is enabled by default in
495+\f[I]FORMAT\f[R].
496+If \f[I]FORMAT\f[R] is not specified, defaults for pandoc\[aq]s Markdown
494497are given.
495498.RS
496499.RE
497500.TP
498−.B \f[C]\-\-list\-highlight\-languages\f[]
501+.B \f[C]\-\-list\-highlight\-languages\f[R]
499502List supported languages for syntax highlighting, one per line.
500503.RS
501504.RE
502505.TP
503−.B \f[C]\-\-list\-highlight\-styles\f[]
506+.B \f[C]\-\-list\-highlight\-styles\f[R]
504507List supported styles for syntax highlighting, one per line.
505−See \f[C]\-\-highlight\-style\f[].
508+See \f[C]\-\-highlight\-style\f[R].
506509.RS
507510.RE
508511.TP
509−.B \f[C]\-v\f[], \f[C]\-\-version\f[]
512+.B \f[C]\-v\f[R], \f[C]\-\-version\f[R]
510513Print version.
511514.RS
512515.RE
513516.TP
514−.B \f[C]\-h\f[], \f[C]\-\-help\f[]
517+.B \f[C]\-h\f[R], \f[C]\-\-help\f[R]
515518Show usage message.
516519.RS
517520.RE
518521.SS Reader options
519522.TP
520−.B \f[C]\-\-base\-header\-level=\f[]\f[I]NUMBER\f[]
523+.B \f[C]\-\-base\-header\-level=\f[R]\f[I]NUMBER\f[R]
521524Specify the base level for headers (defaults to 1).
522525.RS
523526.RE
524527.TP
525−.B \f[C]\-\-strip\-empty\-paragraphs\f[]
528+.B \f[C]\-\-strip\-empty\-paragraphs\f[R]
526529\f[I]Deprecated. Use the \f[CI]+empty_paragraphs\f[I] extension
527−instead.\f[] Ignore paragraphs with no content.
530+instead.\f[R] Ignore paragraphs with no content.
528531This option is useful for converting word processing documents where
529532users have used empty paragraphs to create inter\-paragraph space.
530533.RS
531534.RE
532535.TP
533−.B \f[C]\-\-indented\-code\-classes=\f[]\f[I]CLASSES\f[]
536+.B \f[C]\-\-indented\-code\-classes=\f[R]\f[I]CLASSES\f[R]
534537Specify classes to use for indented code blocks\-\-for example,
535−\f[C]perl,numberLines\f[] or \f[C]haskell\f[].
538+\f[C]perl,numberLines\f[R] or \f[C]haskell\f[R].
536539Multiple classes may be separated by spaces or commas.
537540.RS
538541.RE
539542.TP
540−.B \f[C]\-\-default\-image\-extension=\f[]\f[I]EXTENSION\f[]
543+.B \f[C]\-\-default\-image\-extension=\f[R]\f[I]EXTENSION\f[R]
541544Specify a default extension to use when image paths/URLs have no
542545extension.
543546This allows you to use the same source for formats that require
@@ -546,16 +549,17 @@ Currently this option only affects the Markdown and LaTeX readers.
546549.RS
547550.RE
548551.TP
549−.B \f[C]\-\-file\-scope\f[]
552+.B \f[C]\-\-file\-scope\f[R]
550553Parse each file individually before combining for multifile documents.
551554This will allow footnotes in different files with the same identifiers
552555to work as expected.
553556If this option is set, footnotes and links will not work across files.
554−Reading binary files (docx, odt, epub) implies \f[C]\-\-file\-scope\f[].
557+Reading binary files (docx, odt, epub) implies
558+\f[C]\-\-file\-scope\f[R].
555559.RS
556560.RE
557561.TP
558−.B \f[C]\-F\f[] \f[I]PROGRAM\f[], \f[C]\-\-filter=\f[]\f[I]PROGRAM\f[]
562+.B \f[C]\-F\f[R] \f[I]PROGRAM\f[R], \f[C]\-\-filter=\f[R]\f[I]PROGRAM\f[R]
559563Specify an executable to be used as a filter transforming the pandoc AST
560564after the input is parsed and before the output is written.
561565The executable should read JSON from stdin and write JSON to stdout.
@@ -568,7 +572,7 @@ Hence,
568572.nf
569573\f[C]
570574pandoc\ \-\-filter\ ./caps.py\ \-t\ latex
571−\f[]
575+\f[R]
572576.fi
573577.PP
574578is equivalent to
@@ -576,16 +580,16 @@ is equivalent to
576580.nf
577581\f[C]
578582pandoc\ \-t\ json\ |\ ./caps.py\ latex\ |\ pandoc\ \-f\ json\ \-t\ latex
579−\f[]
583+\f[R]
580584.fi
581585.PP
582586The latter form may be useful for debugging filters.
583587.PP
584588Filters may be written in any language.
585−\f[C]Text.Pandoc.JSON\f[] exports \f[C]toJSONFilter\f[] to facilitate
589+\f[C]Text.Pandoc.JSON\f[R] exports \f[C]toJSONFilter\f[R] to facilitate
586590writing filters in Haskell.
587591Those who would prefer to write filters in python can use the module
588−\f[C]pandocfilters\f[], installable from PyPI.
592+\f[C]pandocfilters\f[R], installable from PyPI.
589593There are also pandoc filter libraries in PHP, perl, and
590594JavaScript/node.js.
591595.PP
@@ -593,19 +597,19 @@ In order of preference, pandoc will look for filters in
593597.IP "1." 3
594598a specified full or relative path (executable or non\-executable)
595599.IP "2." 3
596−\f[C]$DATADIR/filters\f[] (executable or non\-executable) where
597−\f[C]$DATADIR\f[] is the user data directory (see
598−\f[C]\-\-data\-dir\f[], above).
600+\f[C]$DATADIR/filters\f[R] (executable or non\-executable) where
601+\f[C]$DATADIR\f[R] is the user data directory (see
602+\f[C]\-\-data\-dir\f[R], above).
599603.IP "3." 3
600−\f[C]$PATH\f[] (executable only)
604+\f[C]$PATH\f[R] (executable only)
601605.PP
602606Filters and lua\-filters are applied in the order specified on the
603607command line.
604608.RE
605609.TP
606−.B \f[C]\-\-lua\-filter=\f[]\f[I]SCRIPT\f[]
610+.B \f[C]\-\-lua\-filter=\f[R]\f[I]SCRIPT\f[R]
607611Transform the document in a similar fashion as JSON filters (see
608−\f[C]\-\-filter\f[]), but use pandoc\[aq]s build\-in lua filtering
612+\f[C]\-\-filter\f[R]), but use pandoc\[aq]s build\-in lua filtering
609613system.
610614The given lua script is expected to return a list of lua filters which
611615will be applied in order.
@@ -614,7 +618,7 @@ the name of the AST element on which the filter function should be
614618applied.
615619.RS
616620.PP
617−The \f[C]pandoc\f[] lua module provides helper functions for element
621+The \f[C]pandoc\f[R] lua module provides helper functions for element
618622creation.
619623It is always loaded into the script\[aq]s lua environment.
620624.PP
@@ -624,88 +628,88 @@ The following is an example lua script for macro\-expansion:
624628\f[C]
625629function\ expand_hello_world(inline)
626630\ \ if\ inline.c\ ==\ \[aq]{{helloworld}}\[aq]\ then
627−\ \ \ \ return\ pandoc.Emph{\ pandoc.Str\ "Hello,\ World"\ }
631+\ \ \ \ return\ pandoc.Emph{\ pandoc.Str\ \[dq]Hello,\ World\[dq]\ }
628632\ \ else
629633\ \ \ \ return\ inline
630634\ \ end
631635end
632636
633637return\ {{Str\ =\ expand_hello_world}}
634−\f[]
638+\f[R]
635639.fi
636640.PP
637641In order of preference, pandoc will look for lua filters in
638642.IP "1." 3
639643a specified full or relative path (executable or non\-executable)
640644.IP "2." 3
641−\f[C]$DATADIR/filters\f[] (executable or non\-executable) where
642−\f[C]$DATADIR\f[] is the user data directory (see
643−\f[C]\-\-data\-dir\f[], above).
645+\f[C]$DATADIR/filters\f[R] (executable or non\-executable) where
646+\f[C]$DATADIR\f[R] is the user data directory (see
647+\f[C]\-\-data\-dir\f[R], above).
644648.RE
645649.TP
646−.B \f[C]\-M\f[] \f[I]KEY\f[][\f[C]=\f[]\f[I]VAL\f[]], \f[C]\-\-metadata=\f[]\f[I]KEY\f[][\f[C]:\f[]\f[I]VAL\f[]]
647−Set the metadata field \f[I]KEY\f[] to the value \f[I]VAL\f[].
650+.B \f[C]\-M\f[R] \f[I]KEY\f[R][\f[C]=\f[R]\f[I]VAL\f[R]], \f[C]\-\-metadata=\f[R]\f[I]KEY\f[R][\f[C]:\f[R]\f[I]VAL\f[R]]
651+Set the metadata field \f[I]KEY\f[R] to the value \f[I]VAL\f[R].
648652A value specified on the command line overrides a value specified in the
649653document using YAML metadata blocks.
650654Values will be parsed as YAML boolean or string values.
651655If no value is specified, the value will be treated as Boolean true.
652−Like \f[C]\-\-variable\f[], \f[C]\-\-metadata\f[] causes template
656+Like \f[C]\-\-variable\f[R], \f[C]\-\-metadata\f[R] causes template
653657variables to be set.
654−But unlike \f[C]\-\-variable\f[], \f[C]\-\-metadata\f[] affects the
658+But unlike \f[C]\-\-variable\f[R], \f[C]\-\-metadata\f[R] affects the
655659metadata of the underlying document (which is accessible from filters
656660and may be printed in some output formats) and metadata values will be
657661escaped when inserted into the template.
658662.RS
659663.RE
660664.TP
661−.B \f[C]\-\-metadata\-file=\f[]\f[I]FILE\f[]
665+.B \f[C]\-\-metadata\-file=\f[R]\f[I]FILE\f[R]
662666Read metadata from the supplied YAML (or JSON) file.
663667This option can be used with every input format, but string scalars in
664668the YAML file will always be parsed as Markdown.
665669Generally, the input will be handled the same as in YAML metadata
666670blocks.
667−Metadata values specified inside the document, or by using \f[C]\-M\f[],
668−overwrite values specified with this option.
671+Metadata values specified inside the document, or by using
672+\f[C]\-M\f[R], overwrite values specified with this option.
669673.RS
670674.RE
671675.TP
672−.B \f[C]\-p\f[], \f[C]\-\-preserve\-tabs\f[]
676+.B \f[C]\-p\f[R], \f[C]\-\-preserve\-tabs\f[R]
673677Preserve tabs instead of converting them to spaces (the default).
674678Note that this will only affect tabs in literal code spans and code
675679blocks; tabs in regular text will be treated as spaces.
676680.RS
677681.RE
678682.TP
679−.B \f[C]\-\-tab\-stop=\f[]\f[I]NUMBER\f[]
683+.B \f[C]\-\-tab\-stop=\f[R]\f[I]NUMBER\f[R]
680684Specify the number of spaces per tab (default is 4).
681685.RS
682686.RE
683687.TP
684−.B \f[C]\-\-track\-changes=accept\f[]|\f[C]reject\f[]|\f[C]all\f[]
688+.B \f[C]\-\-track\-changes=accept\f[R]|\f[C]reject\f[R]|\f[C]all\f[R]
685689Specifies what to do with insertions, deletions, and comments produced
686−by the MS Word "Track Changes" feature.
687−\f[C]accept\f[] (the default), inserts all insertions, and ignores all
690+by the MS Word \[dq]Track Changes\[dq] feature.
691+\f[C]accept\f[R] (the default), inserts all insertions, and ignores all
688692deletions.
689−\f[C]reject\f[] inserts all deletions and ignores insertions.
690−Both \f[C]accept\f[] and \f[C]reject\f[] ignore comments.
691−\f[C]all\f[] puts in insertions, deletions, and comments, wrapped in
692−spans with \f[C]insertion\f[], \f[C]deletion\f[],
693−\f[C]comment\-start\f[], and \f[C]comment\-end\f[] classes,
693+\f[C]reject\f[R] inserts all deletions and ignores insertions.
694+Both \f[C]accept\f[R] and \f[C]reject\f[R] ignore comments.
695+\f[C]all\f[R] puts in insertions, deletions, and comments, wrapped in
696+spans with \f[C]insertion\f[R], \f[C]deletion\f[R],
697+\f[C]comment\-start\f[R], and \f[C]comment\-end\f[R] classes,
694698respectively.
695699The author and time of change is included.
696−\f[C]all\f[] is useful for scripting: only accepting changes from a
700+\f[C]all\f[R] is useful for scripting: only accepting changes from a
697701certain reviewer, say, or before a certain date.
698−If a paragraph is inserted or deleted, \f[C]track\-changes=all\f[]
702+If a paragraph is inserted or deleted, \f[C]track\-changes=all\f[R]
699703produces a span with the class
700−\f[C]paragraph\-insertion\f[]/\f[C]paragraph\-deletion\f[] before the
704+\f[C]paragraph\-insertion\f[R]/\f[C]paragraph\-deletion\f[R] before the
701705affected paragraph break.
702706This option only affects the docx reader.
703707.RS
704708.RE
705709.TP
706−.B \f[C]\-\-extract\-media=\f[]\f[I]DIR\f[]
710+.B \f[C]\-\-extract\-media=\f[R]\f[I]DIR\f[R]
707711Extract images and other media contained in or linked from the source
708−document to the path \f[I]DIR\f[], creating it if necessary, and adjust
712+document to the path \f[I]DIR\f[R], creating it if necessary, and adjust
709713the images references in the document so they point to the extracted
710714files.
711715If the source format is a binary container (docx, epub, or odt), the
@@ -716,13 +720,13 @@ filenames are constructed based on SHA1 hashes of the contents.
716720.RS
717721.RE
718722.TP
719−.B \f[C]\-\-abbreviations=\f[]\f[I]FILE\f[]
723+.B \f[C]\-\-abbreviations=\f[R]\f[I]FILE\f[R]
720724Specifies a custom abbreviations file, with abbreviations one to a line.
721725If this option is not specified, pandoc will read the data file
722−\f[C]abbreviations\f[] from the user data directory or fall back on a
726+\f[C]abbreviations\f[R] from the user data directory or fall back on a
723727system default.
724728To see the system default, use
725−\f[C]pandoc\ \-\-print\-default\-data\-file=abbreviations\f[].
729+\f[C]pandoc\ \-\-print\-default\-data\-file=abbreviations\f[R].
726730The only use pandoc makes of this list is in the Markdown reader.
727731Strings ending in a period that are found in this list will be followed
728732by a nonbreaking space, so that the period will not produce
@@ -731,65 +735,66 @@ sentence\-ending space in formats like LaTeX.
731735.RE
732736.SS General writer options
733737.TP
734−.B \f[C]\-s\f[], \f[C]\-\-standalone\f[]
738+.B \f[C]\-s\f[R], \f[C]\-\-standalone\f[R]
735739Produce output with an appropriate header and footer (e.g.
736740a standalone HTML, LaTeX, TEI, or RTF file, not a fragment).
737−This option is set automatically for \f[C]pdf\f[], \f[C]epub\f[],
738−\f[C]epub3\f[], \f[C]fb2\f[], \f[C]docx\f[], and \f[C]odt\f[] output.
739−For \f[C]native\f[] output, this option causes metadata to be included;
741+This option is set automatically for \f[C]pdf\f[R], \f[C]epub\f[R],
742+\f[C]epub3\f[R], \f[C]fb2\f[R], \f[C]docx\f[R], and \f[C]odt\f[R]
743+output.
744+For \f[C]native\f[R] output, this option causes metadata to be included;
740745otherwise, metadata is suppressed.
741746.RS
742747.RE
743748.TP
744−.B \f[C]\-\-template=\f[]\f[I]FILE\f[]|\f[I]URL\f[]
749+.B \f[C]\-\-template=\f[R]\f[I]FILE\f[R]|\f[I]URL\f[R]
745750Use the specified file as a custom template for the generated document.
746−Implies \f[C]\-\-standalone\f[].
751+Implies \f[C]\-\-standalone\f[R].
747752See Templates, below, for a description of template syntax.
748753If no extension is specified, an extension corresponding to the writer
749−will be added, so that \f[C]\-\-template=special\f[] looks for
750−\f[C]special.html\f[] for HTML output.
754+will be added, so that \f[C]\-\-template=special\f[R] looks for
755+\f[C]special.html\f[R] for HTML output.
751756If the template is not found, pandoc will search for it in the
752−\f[C]templates\f[] subdirectory of the user data directory (see
753−\f[C]\-\-data\-dir\f[]).
757+\f[C]templates\f[R] subdirectory of the user data directory (see
758+\f[C]\-\-data\-dir\f[R]).
754759If this option is not used, a default template appropriate for the
755760output format will be used (see
756−\f[C]\-D/\-\-print\-default\-template\f[]).
761+\f[C]\-D/\-\-print\-default\-template\f[R]).
757762.RS
758763.RE
759764.TP
760−.B \f[C]\-V\f[] \f[I]KEY\f[][\f[C]=\f[]\f[I]VAL\f[]], \f[C]\-\-variable=\f[]\f[I]KEY\f[][\f[C]:\f[]\f[I]VAL\f[]]
761−Set the template variable \f[I]KEY\f[] to the value \f[I]VAL\f[] when
765+.B \f[C]\-V\f[R] \f[I]KEY\f[R][\f[C]=\f[R]\f[I]VAL\f[R]], \f[C]\-\-variable=\f[R]\f[I]KEY\f[R][\f[C]:\f[R]\f[I]VAL\f[R]]
766+Set the template variable \f[I]KEY\f[R] to the value \f[I]VAL\f[R] when
762767rendering the document in standalone mode.
763−This is generally only useful when the \f[C]\-\-template\f[] option is
768+This is generally only useful when the \f[C]\-\-template\f[R] option is
764769used to specify a custom template, since pandoc automatically sets the
765770variables used in the default templates.
766−If no \f[I]VAL\f[] is specified, the key will be given the value
767−\f[C]true\f[].
771+If no \f[I]VAL\f[R] is specified, the key will be given the value
772+\f[C]true\f[R].
768773.RS
769774.RE
770775.TP
771−.B \f[C]\-D\f[] \f[I]FORMAT\f[], \f[C]\-\-print\-default\-template=\f[]\f[I]FORMAT\f[]
772−Print the system default template for an output \f[I]FORMAT\f[].
773−(See \f[C]\-t\f[] for a list of possible \f[I]FORMAT\f[]s.) Templates in
774−the user data directory are ignored.
776+.B \f[C]\-D\f[R] \f[I]FORMAT\f[R], \f[C]\-\-print\-default\-template=\f[R]\f[I]FORMAT\f[R]
777+Print the system default template for an output \f[I]FORMAT\f[R].
778+(See \f[C]\-t\f[R] for a list of possible \f[I]FORMAT\f[R]s.) Templates
779+in the user data directory are ignored.
775780.RS
776781.RE
777782.TP
778−.B \f[C]\-\-print\-default\-data\-file=\f[]\f[I]FILE\f[]
783+.B \f[C]\-\-print\-default\-data\-file=\f[R]\f[I]FILE\f[R]
779784Print a system default data file.
780785Files in the user data directory are ignored.
781786.RS
782787.RE
783788.TP
784−.B \f[C]\-\-eol=crlf\f[]|\f[C]lf\f[]|\f[C]native\f[]
785−Manually specify line endings: \f[C]crlf\f[] (Windows), \f[C]lf\f[]
786−(macOS/Linux/UNIX), or \f[C]native\f[] (line endings appropriate to the
789+.B \f[C]\-\-eol=crlf\f[R]|\f[C]lf\f[R]|\f[C]native\f[R]
790+Manually specify line endings: \f[C]crlf\f[R] (Windows), \f[C]lf\f[R]
791+(macOS/Linux/UNIX), or \f[C]native\f[R] (line endings appropriate to the
787792OS on which pandoc is being run).
788−The default is \f[C]native\f[].
793+The default is \f[C]native\f[R].
789794.RS
790795.RE
791796.TP
792−.B \f[C]\-\-dpi\f[]=\f[I]NUMBER\f[]
797+.B \f[C]\-\-dpi\f[R]=\f[I]NUMBER\f[R]
793798Specify the dpi (dots per inch) value for conversion from pixels to
794799inch/centimeters and vice versa.
795800The default is 96dpi.
@@ -797,13 +802,13 @@ Technically, the correct term would be ppi (pixels per inch).
797802.RS
798803.RE
799804.TP
800−.B \f[C]\-\-wrap=auto\f[]|\f[C]none\f[]|\f[C]preserve\f[]
805+.B \f[C]\-\-wrap=auto\f[R]|\f[C]none\f[R]|\f[C]preserve\f[R]
801806Determine how text is wrapped in the output (the source code, not the
802807rendered version).
803−With \f[C]auto\f[] (the default), pandoc will attempt to wrap lines to
804−the column width specified by \f[C]\-\-columns\f[] (default 72).
805−With \f[C]none\f[], pandoc will not wrap lines at all.
806−With \f[C]preserve\f[], pandoc will attempt to preserve the wrapping
808+With \f[C]auto\f[R] (the default), pandoc will attempt to wrap lines to
809+the column width specified by \f[C]\-\-columns\f[R] (default 72).
810+With \f[C]none\f[R], pandoc will not wrap lines at all.
811+With \f[C]preserve\f[R], pandoc will attempt to preserve the wrapping
807812from the source document (that is, where there are nonsemantic newlines
808813in the source, there will be nonsemantic newlines in the output as
809814well).
@@ -811,27 +816,27 @@ Automatic wrapping does not currently work in HTML output.
811816.RS
812817.RE
813818.TP
814−.B \f[C]\-\-columns=\f[]\f[I]NUMBER\f[]
819+.B \f[C]\-\-columns=\f[R]\f[I]NUMBER\f[R]
815820Specify length of lines in characters.
816821This affects text wrapping in the generated source code (see
817−\f[C]\-\-wrap\f[]).
822+\f[C]\-\-wrap\f[R]).
818823It also affects calculation of column widths for plain text tables (see
819824Tables below).
820825.RS
821826.RE
822827.TP
823−.B \f[C]\-\-toc\f[], \f[C]\-\-table\-of\-contents\f[]
828+.B \f[C]\-\-toc\f[R], \f[C]\-\-table\-of\-contents\f[R]
824829Include an automatically generated table of contents (or, in the case of
825−\f[C]latex\f[], \f[C]context\f[], \f[C]docx\f[], \f[C]odt\f[],
826−\f[C]opendocument\f[], \f[C]rst\f[], or \f[C]ms\f[], an instruction to
827−create one) in the output document.
828−This option has no effect unless \f[C]\-s/\-\-standalone\f[] is used,
829−and it has no effect on \f[C]man\f[], \f[C]docbook4\f[],
830−\f[C]docbook5\f[], or \f[C]jats\f[] output.
830+\f[C]latex\f[R], \f[C]context\f[R], \f[C]docx\f[R], \f[C]odt\f[R],
831+\f[C]opendocument\f[R], \f[C]rst\f[R], or \f[C]ms\f[R], an instruction
832+to create one) in the output document.
833+This option has no effect unless \f[C]\-s/\-\-standalone\f[R] is used,
834+and it has no effect on \f[C]man\f[R], \f[C]docbook4\f[R],
835+\f[C]docbook5\f[R], or \f[C]jats\f[R] output.
831836.RS
832837.RE
833838.TP
834−.B \f[C]\-\-toc\-depth=\f[]\f[I]NUMBER\f[]
839+.B \f[C]\-\-toc\-depth=\f[R]\f[I]NUMBER\f[R]
835840Specify the number of section levels to include in the table of
836841contents.
837842The default is 3 (which means that level 1, 2, and 3 headers will be
@@ -839,47 +844,47 @@ listed in the contents).
839844.RS
840845.RE
841846.TP
842−.B \f[C]\-\-strip\-comments\f[]
847+.B \f[C]\-\-strip\-comments\f[R]
843848Strip out HTML comments in the Markdown or Textile source, rather than
844849passing them on to Markdown, Textile or HTML output as raw HTML.
845850This does not apply to HTML comments inside raw HTML blocks when the
846−\f[C]markdown_in_html_blocks\f[] extension is not set.
851+\f[C]markdown_in_html_blocks\f[R] extension is not set.
847852.RS
848853.RE
849854.TP
850−.B \f[C]\-\-no\-highlight\f[]
855+.B \f[C]\-\-no\-highlight\f[R]
851856Disables syntax highlighting for code blocks and inlines, even when a
852857language attribute is given.
853858.RS
854859.RE
855860.TP
856−.B \f[C]\-\-highlight\-style=\f[]\f[I]STYLE\f[]|\f[I]FILE\f[]
861+.B \f[C]\-\-highlight\-style=\f[R]\f[I]STYLE\f[R]|\f[I]FILE\f[R]
857862Specifies the coloring style to be used in highlighted source code.
858−Options are \f[C]pygments\f[] (the default), \f[C]kate\f[],
859−\f[C]monochrome\f[], \f[C]breezeDark\f[], \f[C]espresso\f[],
860−\f[C]zenburn\f[], \f[C]haddock\f[], and \f[C]tango\f[].
863+Options are \f[C]pygments\f[R] (the default), \f[C]kate\f[R],
864+\f[C]monochrome\f[R], \f[C]breezeDark\f[R], \f[C]espresso\f[R],
865+\f[C]zenburn\f[R], \f[C]haddock\f[R], and \f[C]tango\f[R].
861866For more information on syntax highlighting in pandoc, see Syntax
862867highlighting, below.
863−See also \f[C]\-\-list\-highlight\-styles\f[].
868+See also \f[C]\-\-list\-highlight\-styles\f[R].
864869.RS
865870.PP
866−Instead of a \f[I]STYLE\f[] name, a JSON file with extension
867−\f[C]\&.theme\f[] may be supplied.
871+Instead of a \f[I]STYLE\f[R] name, a JSON file with extension
872+\f[C]\&.theme\f[R] may be supplied.
868873This will be parsed as a KDE syntax highlighting theme and (if valid)
869874used as the highlighting style.
870875.PP
871876To generate the JSON version of an existing style, use
872−\f[C]\-\-print\-highlight\-style\f[].
877+\f[C]\-\-print\-highlight\-style\f[R].
873878.RE
874879.TP
875−.B \f[C]\-\-print\-highlight\-style=\f[]\f[I]STYLE\f[]|\f[I]FILE\f[]
880+.B \f[C]\-\-print\-highlight\-style=\f[R]\f[I]STYLE\f[R]|\f[I]FILE\f[R]
876881Prints a JSON version of a highlighting style, which can be modified,
877−saved with a \f[C]\&.theme\f[] extension, and used with
878−\f[C]\-\-highlight\-style\f[].
882+saved with a \f[C]\&.theme\f[R] extension, and used with
883+\f[C]\-\-highlight\-style\f[R].
879884.RS
880885.RE
881886.TP
882−.B \f[C]\-\-syntax\-definition=\f[]\f[I]FILE\f[]
887+.B \f[C]\-\-syntax\-definition=\f[R]\f[I]FILE\f[R]
883888Instructs pandoc to load a KDE XML syntax definition file, which will be
884889used for syntax highlighting of appropriately marked code blocks.
885890This can be used to add support for new languages or to use altered
@@ -887,175 +892,179 @@ syntax definitions for existing languages.
887892.RS
888893.RE
889894.TP
890−.B \f[C]\-H\f[] \f[I]FILE\f[], \f[C]\-\-include\-in\-header=\f[]\f[I]FILE\f[]
891−Include contents of \f[I]FILE\f[], verbatim, at the end of the header.
895+.B \f[C]\-H\f[R] \f[I]FILE\f[R], \f[C]\-\-include\-in\-header=\f[R]\f[I]FILE\f[R]
896+Include contents of \f[I]FILE\f[R], verbatim, at the end of the header.
892897This can be used, for example, to include special CSS or JavaScript in
893898HTML documents.
894899This option can be used repeatedly to include multiple files in the
895900header.
896901They will be included in the order specified.
897−Implies \f[C]\-\-standalone\f[].
902+Implies \f[C]\-\-standalone\f[R].
898903.RS
899904.RE
900905.TP
901−.B \f[C]\-B\f[] \f[I]FILE\f[], \f[C]\-\-include\-before\-body=\f[]\f[I]FILE\f[]
902−Include contents of \f[I]FILE\f[], verbatim, at the beginning of the
906+.B \f[C]\-B\f[R] \f[I]FILE\f[R], \f[C]\-\-include\-before\-body=\f[R]\f[I]FILE\f[R]
907+Include contents of \f[I]FILE\f[R], verbatim, at the beginning of the
903908document body (e.g.
904−after the \f[C]<body>\f[] tag in HTML, or the \f[C]\\begin{document}\f[]
905−command in LaTeX).
909+after the \f[C]<body>\f[R] tag in HTML, or the
910+\f[C]\[rs]begin{document}\f[R] command in LaTeX).
906911This can be used to include navigation bars or banners in HTML
907912documents.
908913This option can be used repeatedly to include multiple files.
909914They will be included in the order specified.
910−Implies \f[C]\-\-standalone\f[].
915+Implies \f[C]\-\-standalone\f[R].
911916.RS
912917.RE
913918.TP
914−.B \f[C]\-A\f[] \f[I]FILE\f[], \f[C]\-\-include\-after\-body=\f[]\f[I]FILE\f[]
915−Include contents of \f[I]FILE\f[], verbatim, at the end of the document
916−body (before the \f[C]</body>\f[] tag in HTML, or the
917−\f[C]\\end{document}\f[] command in LaTeX).
919+.B \f[C]\-A\f[R] \f[I]FILE\f[R], \f[C]\-\-include\-after\-body=\f[R]\f[I]FILE\f[R]
920+Include contents of \f[I]FILE\f[R], verbatim, at the end of the document
921+body (before the \f[C]</body>\f[R] tag in HTML, or the
922+\f[C]\[rs]end{document}\f[R] command in LaTeX).
918923This option can be used repeatedly to include multiple files.
919924They will be included in the order specified.
920−Implies \f[C]\-\-standalone\f[].
925+Implies \f[C]\-\-standalone\f[R].
921926.RS
922927.RE
923928.TP
924−.B \f[C]\-\-resource\-path=\f[]\f[I]SEARCHPATH\f[]
929+.B \f[C]\-\-resource\-path=\f[R]\f[I]SEARCHPATH\f[R]
925930List of paths to search for images and other resources.
926−The paths should be separated by \f[C]:\f[] on Linux, UNIX, and macOS
927−systems, and by \f[C];\f[] on Windows.
928−If \f[C]\-\-resource\-path\f[] is not specified, the default resource
931+The paths should be separated by \f[C]:\f[R] on Linux, UNIX, and macOS
932+systems, and by \f[C];\f[R] on Windows.
933+If \f[C]\-\-resource\-path\f[R] is not specified, the default resource
929934path is the working directory.
930−Note that, if \f[C]\-\-resource\-path\f[] is specified, the working
935+Note that, if \f[C]\-\-resource\-path\f[R] is specified, the working
931936directory must be explicitly listed or it will not be searched.
932−For example: \f[C]\-\-resource\-path=.:test\f[] will search the working
933−directory and the \f[C]test\f[] subdirectory, in that order.
937+For example: \f[C]\-\-resource\-path=.:test\f[R] will search the working
938+directory and the \f[C]test\f[R] subdirectory, in that order.
934939.RS
935940.PP
936−\f[C]\-\-resource\-path\f[] only has an effect if (a) the output format
937−embeds images (for example, \f[C]docx\f[], \f[C]pdf\f[], or
938−\f[C]html\f[] with \f[C]\-\-self\-contained\f[]) or (b) it is used
939−together with \f[C]\-\-extract\-media\f[].
941+\f[C]\-\-resource\-path\f[R] only has an effect if (a) the output format
942+embeds images (for example, \f[C]docx\f[R], \f[C]pdf\f[R], or
943+\f[C]html\f[R] with \f[C]\-\-self\-contained\f[R]) or (b) it is used
944+together with \f[C]\-\-extract\-media\f[R].
940945.RE
941946.TP
942−.B \f[C]\-\-request\-header=\f[]\f[I]NAME\f[]\f[C]:\f[]\f[I]VAL\f[]
943−Set the request header \f[I]NAME\f[] to the value \f[I]VAL\f[] when
947+.B \f[C]\-\-request\-header=\f[R]\f[I]NAME\f[R]\f[C]:\f[R]\f[I]VAL\f[R]
948+Set the request header \f[I]NAME\f[R] to the value \f[I]VAL\f[R] when
944949making HTTP requests (for example, when a URL is given on the command
945950line, or when resources used in a document must be downloaded).
946951If you\[aq]re behind a proxy, you also need to set the environment
947−variable \f[C]http_proxy\f[] to \f[C]http://...\f[].
952+variable \f[C]http_proxy\f[R] to \f[C]http://...\f[R].
948953.RS
949954.RE
950955.SS Options affecting specific writers
951956.TP
952−.B \f[C]\-\-self\-contained\f[]
957+.B \f[C]\-\-self\-contained\f[R]
953958Produce a standalone HTML file with no external dependencies, using
954−\f[C]data:\f[] URIs to incorporate the contents of linked scripts,
959+\f[C]data:\f[R] URIs to incorporate the contents of linked scripts,
955960stylesheets, images, and videos.
956−Implies \f[C]\-\-standalone\f[].
957−The resulting file should be "self\-contained," in the sense that it
958−needs no external files and no net access to be displayed properly by a
959−browser.
961+Implies \f[C]\-\-standalone\f[R].
962+The resulting file should be \[dq]self\-contained,\[dq] in the sense
963+that it needs no external files and no net access to be displayed
964+properly by a browser.
960965This option works only with HTML output formats, including
961−\f[C]html4\f[], \f[C]html5\f[], \f[C]html+lhs\f[], \f[C]html5+lhs\f[],
962−\f[C]s5\f[], \f[C]slidy\f[], \f[C]slideous\f[], \f[C]dzslides\f[], and
963−\f[C]revealjs\f[].
966+\f[C]html4\f[R], \f[C]html5\f[R], \f[C]html+lhs\f[R],
967+\f[C]html5+lhs\f[R], \f[C]s5\f[R], \f[C]slidy\f[R], \f[C]slideous\f[R],
968+\f[C]dzslides\f[R], and \f[C]revealjs\f[R].
964969Scripts, images, and stylesheets at absolute URLs will be downloaded;
965970those at relative URLs will be sought relative to the working directory
966971(if the first source file is local) or relative to the base URL (if the
967972first source file is remote).
968−Elements with the attribute \f[C]data\-external="1"\f[] will be left
969−alone; the documents they link to will not be incorporated in the
973+Elements with the attribute \f[C]data\-external=\[dq]1\[dq]\f[R] will be
974+left alone; the documents they link to will not be incorporated in the
970975document.
971976Limitation: resources that are loaded dynamically through JavaScript
972−cannot be incorporated; as a result, \f[C]\-\-self\-contained\f[] does
973−not work with \f[C]\-\-mathjax\f[], and some advanced features (e.g.
974−zoom or speaker notes) may not work in an offline "self\-contained"
975−\f[C]reveal.js\f[] slide show.
977+cannot be incorporated; as a result, \f[C]\-\-self\-contained\f[R] does
978+not work with \f[C]\-\-mathjax\f[R], and some advanced features (e.g.
979+zoom or speaker notes) may not work in an offline
980+\[dq]self\-contained\[dq] \f[C]reveal.js\f[R] slide show.
976981.RS
977982.RE
978983.TP
979−.B \f[C]\-\-html\-q\-tags\f[]
980−Use \f[C]<q>\f[] tags for quotes in HTML.
984+.B \f[C]\-\-html\-q\-tags\f[R]
985+Use \f[C]<q>\f[R] tags for quotes in HTML.
981986.RS
982987.RE
983988.TP
984−.B \f[C]\-\-ascii\f[]
989+.B \f[C]\-\-ascii\f[R]
985990Use only ASCII characters in output.
986991Currently supported for XML and HTML formats (which use numerical
987−entities instead of UTF\-8 when this option is selected) and for groff
988−ms and man (which use hexadecimal escapes).
992+entities instead of UTF\-8 when this option is selected), groff ms
993+(which use hexadecimal escapes), and to a limited degree LaTeX (which
994+uses standard commands for accented characters when possible).
995+Groff man output uses ASCII by default.
989996.RS
990997.RE
991998.TP
992−.B \f[C]\-\-reference\-links\f[]
999+.B \f[C]\-\-reference\-links\f[R]
9931000Use reference\-style links, rather than inline links, in writing
9941001Markdown or reStructuredText.
9951002By default inline links are used.
9961003The placement of link references is affected by the
997−\f[C]\-\-reference\-location\f[] option.
1004+\f[C]\-\-reference\-location\f[R] option.
9981005.RS
9991006.RE
10001007.TP
1001−.B \f[C]\-\-reference\-location\ =\ block\f[]|\f[C]section\f[]|\f[C]document\f[]
1002−Specify whether footnotes (and references, if \f[C]reference\-links\f[]
1008+.B \f[C]\-\-reference\-location\ =\ block\f[R]|\f[C]section\f[R]|\f[C]document\f[R]
1009+Specify whether footnotes (and references, if \f[C]reference\-links\f[R]
10031010is set) are placed at the end of the current (top\-level) block, the
10041011current section, or the document.
1005−The default is \f[C]document\f[].
1012+The default is \f[C]document\f[R].
10061013Currently only affects the markdown writer.
10071014.RS
10081015.RE
10091016.TP
1010−.B \f[C]\-\-atx\-headers\f[]
1017+.B \f[C]\-\-atx\-headers\f[R]
10111018Use ATX\-style headers in Markdown and AsciiDoc output.
10121019The default is to use setext\-style headers for levels 1\-2, and then
10131020ATX headers.
1014−(Note: for \f[C]gfm\f[] output, ATX headers are always used.)
1021+(Note: for \f[C]gfm\f[R] output, ATX headers are always used.)
10151022.RS
10161023.RE
10171024.TP
1018−.B \f[C]\-\-top\-level\-division=[default|section|chapter|part]\f[]
1025+.B \f[C]\-\-top\-level\-division=[default|section|chapter|part]\f[R]
10191026Treat top\-level headers as the given division type in LaTeX, ConTeXt,
10201027DocBook, and TEI output.
10211028The hierarchy order is part, chapter, then section; all headers are
10221029shifted such that the top\-level header becomes the specified type.
10231030The default behavior is to determine the best division type via
1024−heuristics: unless other conditions apply, \f[C]section\f[] is chosen.
1025−When the LaTeX document class is set to \f[C]report\f[], \f[C]book\f[],
1026−or \f[C]memoir\f[] (unless the \f[C]article\f[] option is specified),
1027−\f[C]chapter\f[] is implied as the setting for this option.
1028−If \f[C]beamer\f[] is the output format, specifying either
1029−\f[C]chapter\f[] or \f[C]part\f[] will cause top\-level headers to
1030−become \f[C]\\part{..}\f[], while second\-level headers remain as their
1031−default type.
1031+heuristics: unless other conditions apply, \f[C]section\f[R] is chosen.
1032+When the LaTeX document class is set to \f[C]report\f[R],
1033+\f[C]book\f[R], or \f[C]memoir\f[R] (unless the \f[C]article\f[R] option
1034+is specified), \f[C]chapter\f[R] is implied as the setting for this
1035+option.
1036+If \f[C]beamer\f[R] is the output format, specifying either
1037+\f[C]chapter\f[R] or \f[C]part\f[R] will cause top\-level headers to
1038+become \f[C]\[rs]part{..}\f[R], while second\-level headers remain as
1039+their default type.
10321040.RS
10331041.RE
10341042.TP
1035−.B \f[C]\-N\f[], \f[C]\-\-number\-sections\f[]
1043+.B \f[C]\-N\f[R], \f[C]\-\-number\-sections\f[R]
10361044Number section headings in LaTeX, ConTeXt, HTML, or EPUB output.
10371045By default, sections are not numbered.
1038−Sections with class \f[C]unnumbered\f[] will never be numbered, even if
1039−\f[C]\-\-number\-sections\f[] is specified.
1046+Sections with class \f[C]unnumbered\f[R] will never be numbered, even if
1047+\f[C]\-\-number\-sections\f[R] is specified.
10401048.RS
10411049.RE
10421050.TP
1043−.B \f[C]\-\-number\-offset=\f[]\f[I]NUMBER\f[][\f[C],\f[]\f[I]NUMBER\f[]\f[C],\f[]\f[I]...\f[]]
1051+.B \f[C]\-\-number\-offset=\f[R]\f[I]NUMBER\f[R][\f[C],\f[R]\f[I]NUMBER\f[R]\f[C],\f[R]\f[I]...\f[R]]
10441052Offset for section headings in HTML output (ignored in other output
10451053formats).
10461054The first number is added to the section number for top\-level headers,
10471055the second for second\-level headers, and so on.
10481056So, for example, if you want the first top\-level header in your
1049−document to be numbered "6", specify \f[C]\-\-number\-offset=5\f[].
1057+document to be numbered \[dq]6\[dq], specify
1058+\f[C]\-\-number\-offset=5\f[R].
10501059If your document starts with a level\-2 header which you want to be
1051−numbered "1.5", specify \f[C]\-\-number\-offset=1,4\f[].
1060+numbered \[dq]1.5\[dq], specify \f[C]\-\-number\-offset=1,4\f[R].
10521061Offsets are 0 by default.
1053−Implies \f[C]\-\-number\-sections\f[].
1062+Implies \f[C]\-\-number\-sections\f[R].
10541063.RS
10551064.RE
10561065.TP
1057−.B \f[C]\-\-listings\f[]
1058−Use the \f[C]listings\f[] package for LaTeX code blocks.
1066+.B \f[C]\-\-listings\f[R]
1067+Use the \f[C]listings\f[R] package for LaTeX code blocks.
10591068The package does not support multi\-byte encoding for source code.
10601069To handle UTF\-8 you would need to use a custom template.
10611070This issue is fully documented here: Encoding issue with the listings
@@ -1063,16 +1072,16 @@ package.
10631072.RS
10641073.RE
10651074.TP
1066−.B \f[C]\-i\f[], \f[C]\-\-incremental\f[]
1075+.B \f[C]\-i\f[R], \f[C]\-\-incremental\f[R]
10671076Make list items in slide shows display incrementally (one by one).
10681077The default is for lists to be displayed all at once.
10691078.RS
10701079.RE
10711080.TP
1072−.B \f[C]\-\-slide\-level=\f[]\f[I]NUMBER\f[]
1081+.B \f[C]\-\-slide\-level=\f[R]\f[I]NUMBER\f[R]
10731082Specifies that headers with the specified level create slides (for
1074−\f[C]beamer\f[], \f[C]s5\f[], \f[C]slidy\f[], \f[C]slideous\f[],
1075−\f[C]dzslides\f[]).
1083+\f[C]beamer\f[R], \f[C]s5\f[R], \f[C]slidy\f[R], \f[C]slideous\f[R],
1084+\f[C]dzslides\f[R]).
10761085Headers above this level in the hierarchy are used to divide the slide
10771086show into sections; headers below this level create subheads within a
10781087slide.
@@ -1083,26 +1092,26 @@ document; see Structuring the slide show.
10831092.RS
10841093.RE
10851094.TP
1086−.B \f[C]\-\-section\-divs\f[]
1087−Wrap sections in \f[C]<section>\f[] tags (or \f[C]<div>\f[] tags for
1088−\f[C]html4\f[]), and attach identifiers to the enclosing
1089−\f[C]<section>\f[] (or \f[C]<div>\f[]) rather than the header itself.
1095+.B \f[C]\-\-section\-divs\f[R]
1096+Wrap sections in \f[C]<section>\f[R] tags (or \f[C]<div>\f[R] tags for
1097+\f[C]html4\f[R]), and attach identifiers to the enclosing
1098+\f[C]<section>\f[R] (or \f[C]<div>\f[R]) rather than the header itself.
10901099See Header identifiers, below.
10911100.RS
10921101.RE
10931102.TP
1094−.B \f[C]\-\-email\-obfuscation=none\f[]|\f[C]javascript\f[]|\f[C]references\f[]
1095−Specify a method for obfuscating \f[C]mailto:\f[] links in HTML
1103+.B \f[C]\-\-email\-obfuscation=none\f[R]|\f[C]javascript\f[R]|\f[C]references\f[R]
1104+Specify a method for obfuscating \f[C]mailto:\f[R] links in HTML
10961105documents.
1097−\f[C]none\f[] leaves \f[C]mailto:\f[] links as they are.
1098−\f[C]javascript\f[] obfuscates them using JavaScript.
1099−\f[C]references\f[] obfuscates them by printing their letters as decimal
1100−or hexadecimal character references.
1101−The default is \f[C]none\f[].
1106+\f[C]none\f[R] leaves \f[C]mailto:\f[R] links as they are.
1107+\f[C]javascript\f[R] obfuscates them using JavaScript.
1108+\f[C]references\f[R] obfuscates them by printing their letters as
1109+decimal or hexadecimal character references.
1110+The default is \f[C]none\f[R].
11021111.RS
11031112.RE
11041113.TP
1105−.B \f[C]\-\-id\-prefix=\f[]\f[I]STRING\f[]
1114+.B \f[C]\-\-id\-prefix=\f[R]\f[I]STRING\f[R]
11061115Specify a prefix to be added to all identifiers and internal links in
11071116HTML and DocBook output, and to footnote numbers in Markdown and Haddock
11081117output.
@@ -1111,28 +1120,28 @@ fragments to be included in other pages.
11111120.RS
11121121.RE
11131122.TP
1114−.B \f[C]\-T\f[] \f[I]STRING\f[], \f[C]\-\-title\-prefix=\f[]\f[I]STRING\f[]
1115−Specify \f[I]STRING\f[] as a prefix at the beginning of the title that
1123+.B \f[C]\-T\f[R] \f[I]STRING\f[R], \f[C]\-\-title\-prefix=\f[R]\f[I]STRING\f[R]
1124+Specify \f[I]STRING\f[R] as a prefix at the beginning of the title that
11161125appears in the HTML header (but not in the title as it appears at the
11171126beginning of the HTML body).
1118−Implies \f[C]\-\-standalone\f[].
1127+Implies \f[C]\-\-standalone\f[R].
11191128.RS
11201129.RE
11211130.TP
1122−.B \f[C]\-c\f[] \f[I]URL\f[], \f[C]\-\-css=\f[]\f[I]URL\f[]
1131+.B \f[C]\-c\f[R] \f[I]URL\f[R], \f[C]\-\-css=\f[R]\f[I]URL\f[R]
11231132Link to a CSS style sheet.
11241133This option can be used repeatedly to include multiple files.
11251134They will be included in the order specified.
11261135.RS
11271136.PP
11281137A stylesheet is required for generating EPUB.
1129−If none is provided using this option (or the \f[C]stylesheet\f[]
1130−metadata field), pandoc will look for a file \f[C]epub.css\f[] in the
1131−user data directory (see \f[C]\-\-data\-dir\f[]).
1138+If none is provided using this option (or the \f[C]stylesheet\f[R]
1139+metadata field), pandoc will look for a file \f[C]epub.css\f[R] in the
1140+user data directory (see \f[C]\-\-data\-dir\f[R]).
11321141If it is not found there, sensible defaults will be used.
11331142.RE
11341143.TP
1135−.B \f[C]\-\-reference\-doc=\f[]\f[I]FILE\f[]
1144+.B \f[C]\-\-reference\-doc=\f[R]\f[I]FILE\f[R]
11361145Use the specified file as a style reference in producing a docx or ODT
11371146file.
11381147.RS
@@ -1144,15 +1153,15 @@ The contents of the reference docx are ignored, but its stylesheets and
11441153document properties (including margins, page size, header, and footer)
11451154are used in the new docx.
11461155If no reference docx is specified on the command line, pandoc will look
1147−for a file \f[C]reference.docx\f[] in the user data directory (see
1148−\f[C]\-\-data\-dir\f[]).
1156+for a file \f[C]reference.docx\f[R] in the user data directory (see
1157+\f[C]\-\-data\-dir\f[R]).
11491158If this is not found either, sensible defaults will be used.
11501159.RS
11511160.PP
1152−To produce a custom \f[C]reference.docx\f[], first get a copy of the
1153−default \f[C]reference.docx\f[]:
1154−\f[C]pandoc\ \-\-print\-default\-data\-file\ reference.docx\ >\ custom\-reference.docx\f[].
1155−Then open \f[C]custom\-reference.docx\f[] in Word, modify the styles as
1161+To produce a custom \f[C]reference.docx\f[R], first get a copy of the
1162+default \f[C]reference.docx\f[R]:
1163+\f[C]pandoc\ \-\-print\-default\-data\-file\ reference.docx\ >\ custom\-reference.docx\f[R].
1164+Then open \f[C]custom\-reference.docx\f[R] in Word, modify the styles as
11561165you wish, and save the file.
11571166For best results, do not make changes to this file other than modifying
11581167the styles used by pandoc: [paragraph] Normal, Body Text, First
@@ -1171,21 +1180,21 @@ ODT produced using pandoc.
11711180The contents of the reference ODT are ignored, but its stylesheets are
11721181used in the new ODT.
11731182If no reference ODT is specified on the command line, pandoc will look
1174−for a file \f[C]reference.odt\f[] in the user data directory (see
1175−\f[C]\-\-data\-dir\f[]).
1183+for a file \f[C]reference.odt\f[R] in the user data directory (see
1184+\f[C]\-\-data\-dir\f[R]).
11761185If this is not found either, sensible defaults will be used.
11771186.RS
11781187.PP
1179−To produce a custom \f[C]reference.odt\f[], first get a copy of the
1180−default \f[C]reference.odt\f[]:
1181−\f[C]pandoc\ \-\-print\-default\-data\-file\ reference.odt\ >\ custom\-reference.odt\f[].
1182−Then open \f[C]custom\-reference.odt\f[] in LibreOffice, modify the
1188+To produce a custom \f[C]reference.odt\f[R], first get a copy of the
1189+default \f[C]reference.odt\f[R]:
1190+\f[C]pandoc\ \-\-print\-default\-data\-file\ reference.odt\ >\ custom\-reference.odt\f[R].
1191+Then open \f[C]custom\-reference.odt\f[R] in LibreOffice, modify the
11831192styles as you wish, and save the file.
11841193.RE
11851194.TP
11861195.B PowerPoint
11871196Any template included with a recent install of Microsoft PowerPoint
1188−(either with \f[C]\&.pptx\f[] or \f[C]\&.potx\f[] extension) should
1197+(either with \f[C]\&.pptx\f[R] or \f[C]\&.potx\f[R] extension) should
11891198work, as will most templates derived from these.
11901199.RS
11911200.PP
@@ -1202,27 +1211,27 @@ Two Content
12021211.PP
12031212All templates included with a recent version of MS PowerPoint will fit
12041213these criteria.
1205−(You can click on \f[C]Layout\f[] under the \f[C]Home\f[] menu to
1214+(You can click on \f[C]Layout\f[R] under the \f[C]Home\f[R] menu to
12061215check.)
12071216.PP
1208−You can also modify the default \f[C]reference.pptx\f[]: first run
1209−\f[C]pandoc\ \-\-print\-default\-data\-file\ reference.pptx\ >\ custom\-reference.pptx\f[],
1210−and then modify \f[C]custom\-reference.pptx\f[] in MS PowerPoint (pandoc
1211−will use the first four layout slides, as mentioned above).
1217+You can also modify the default \f[C]reference.pptx\f[R]: first run
1218+\f[C]pandoc\ \-\-print\-default\-data\-file\ reference.pptx\ >\ custom\-reference.pptx\f[R],
1219+and then modify \f[C]custom\-reference.pptx\f[R] in MS PowerPoint
1220+(pandoc will use the first four layout slides, as mentioned above).
12121221.RE
12131222.RE
12141223.TP
1215−.B \f[C]\-\-epub\-cover\-image=\f[]\f[I]FILE\f[]
1224+.B \f[C]\-\-epub\-cover\-image=\f[R]\f[I]FILE\f[R]
12161225Use the specified image as the EPUB cover.
12171226It is recommended that the image be less than 1000px in width and
12181227height.
12191228Note that in a Markdown source document you can also specify
1220−\f[C]cover\-image\f[] in a YAML metadata block (see EPUB Metadata,
1229+\f[C]cover\-image\f[R] in a YAML metadata block (see EPUB Metadata,
12211230below).
12221231.RS
12231232.RE
12241233.TP
1225−.B \f[C]\-\-epub\-metadata=\f[]\f[I]FILE\f[]
1234+.B \f[C]\-\-epub\-metadata=\f[R]\f[I]FILE\f[R]
12261235Look in the specified XML file for metadata for the EPUB.
12271236The file should contain a series of Dublin Core elements.
12281237For example:
@@ -1232,15 +1241,16 @@ For example:
12321241\f[C]
12331242\ <dc:rights>Creative\ Commons</dc:rights>
12341243\ <dc:language>es\-AR</dc:language>
1235−\f[]
1244+\f[R]
12361245.fi
12371246.PP
12381247By default, pandoc will include the following metadata elements:
1239−\f[C]<dc:title>\f[] (from the document title), \f[C]<dc:creator>\f[]
1240−(from the document authors), \f[C]<dc:date>\f[] (from the document date,
1241−which should be in ISO 8601 format), \f[C]<dc:language>\f[] (from the
1242−\f[C]lang\f[] variable, or, if is not set, the locale), and
1243−\f[C]<dc:identifier\ id="BookId">\f[] (a randomly generated UUID).
1248+\f[C]<dc:title>\f[R] (from the document title), \f[C]<dc:creator>\f[R]
1249+(from the document authors), \f[C]<dc:date>\f[R] (from the document
1250+date, which should be in ISO 8601 format), \f[C]<dc:language>\f[R] (from
1251+the \f[C]lang\f[R] variable, or, if is not set, the locale), and
1252+\f[C]<dc:identifier\ id=\[dq]BookId\[dq]>\f[R] (a randomly generated
1253+UUID).
12441254Any of these may be overridden by elements in the metadata file.
12451255.PP
12461256Note: if the source document is Markdown, a YAML metadata block in the
@@ -1248,51 +1258,51 @@ document can be used instead.
12481258See below under EPUB Metadata.
12491259.RE
12501260.TP
1251−.B \f[C]\-\-epub\-embed\-font=\f[]\f[I]FILE\f[]
1261+.B \f[C]\-\-epub\-embed\-font=\f[R]\f[I]FILE\f[R]
12521262Embed the specified font in the EPUB.
12531263This option can be repeated to embed multiple fonts.
1254−Wildcards can also be used: for example, \f[C]DejaVuSans\-*.ttf\f[].
1264+Wildcards can also be used: for example, \f[C]DejaVuSans\-*.ttf\f[R].
12551265However, if you use wildcards on the command line, be sure to escape
12561266them or put the whole filename in single quotes, to prevent them from
12571267being interpreted by the shell.
12581268To use the embedded fonts, you will need to add declarations like the
1259−following to your CSS (see \f[C]\-\-css\f[]):
1269+following to your CSS (see \f[C]\-\-css\f[R]):
12601270.RS
12611271.IP
12621272.nf
12631273\f[C]
1264−\@font\-face\ {
1274+\[at]font\-face\ {
12651275font\-family:\ DejaVuSans;
12661276font\-style:\ normal;
12671277font\-weight:\ normal;
1268−src:url("DejaVuSans\-Regular.ttf");
1278+src:url(\[dq]DejaVuSans\-Regular.ttf\[dq]);
12691279}
1270−\@font\-face\ {
1280+\[at]font\-face\ {
12711281font\-family:\ DejaVuSans;
12721282font\-style:\ normal;
12731283font\-weight:\ bold;
1274−src:url("DejaVuSans\-Bold.ttf");
1284+src:url(\[dq]DejaVuSans\-Bold.ttf\[dq]);
12751285}
1276−\@font\-face\ {
1286+\[at]font\-face\ {
12771287font\-family:\ DejaVuSans;
12781288font\-style:\ italic;
12791289font\-weight:\ normal;
1280−src:url("DejaVuSans\-Oblique.ttf");
1290+src:url(\[dq]DejaVuSans\-Oblique.ttf\[dq]);
12811291}
1282−\@font\-face\ {
1292+\[at]font\-face\ {
12831293font\-family:\ DejaVuSans;
12841294font\-style:\ italic;
12851295font\-weight:\ bold;
1286−src:url("DejaVuSans\-BoldOblique.ttf");
1296+src:url(\[dq]DejaVuSans\-BoldOblique.ttf\[dq]);
12871297}
1288−body\ {\ font\-family:\ "DejaVuSans";\ }
1289−\f[]
1298+body\ {\ font\-family:\ \[dq]DejaVuSans\[dq];\ }
1299+\f[R]
12901300.fi
12911301.RE
12921302.TP
1293−.B \f[C]\-\-epub\-chapter\-level=\f[]\f[I]NUMBER\f[]
1303+.B \f[C]\-\-epub\-chapter\-level=\f[R]\f[I]NUMBER\f[R]
12941304Specify the header level at which to split the EPUB into separate
1295−"chapter" files.
1305+\[dq]chapter\[dq] files.
12961306The default is to split into chapters at level 1 headers.
12971307This option only affects the internal composition of the EPUB, not the
12981308way chapters and sections are displayed to users.
@@ -1302,25 +1312,25 @@ chapter level of 2 or 3.
13021312.RS
13031313.RE
13041314.TP
1305−.B \f[C]\-\-epub\-subdirectory=\f[]\f[I]DIRNAME\f[]
1315+.B \f[C]\-\-epub\-subdirectory=\f[R]\f[I]DIRNAME\f[R]
13061316Specify the subdirectory in the OCF container that is to hold the
13071317EPUB\-specific contents.
1308−The default is \f[C]EPUB\f[].
1318+The default is \f[C]EPUB\f[R].
13091319To put the EPUB contents in the top level, use an empty string.
13101320.RS
13111321.RE
13121322.TP
1313−.B \f[C]\-\-pdf\-engine=pdflatex\f[]|\f[C]lualatex\f[]|\f[C]xelatex\f[]|\f[C]wkhtmltopdf\f[]|\f[C]weasyprint\f[]|\f[C]prince\f[]|\f[C]context\f[]|\f[C]pdfroff\f[]
1323+.B \f[C]\-\-pdf\-engine=pdflatex\f[R]|\f[C]lualatex\f[R]|\f[C]xelatex\f[R]|\f[C]wkhtmltopdf\f[R]|\f[C]weasyprint\f[R]|\f[C]prince\f[R]|\f[C]context\f[R]|\f[C]pdfroff\f[R]
13141324Use the specified engine when producing PDF output.
1315−The default is \f[C]pdflatex\f[].
1325+The default is \f[C]pdflatex\f[R].
13161326If the engine is not in your PATH, the full path of the engine may be
13171327specified here.
13181328.RS
13191329.RE
13201330.TP
1321−.B \f[C]\-\-pdf\-engine\-opt=\f[]\f[I]STRING\f[]
1331+.B \f[C]\-\-pdf\-engine\-opt=\f[R]\f[I]STRING\f[R]
13221332Use the given string as a command\-line argument to the
1323−\f[C]pdf\-engine\f[].
1333+\f[C]pdf\-engine\f[R].
13241334If used multiple times, the arguments are provided with spaces between
13251335them.
13261336Note that no check for duplicate options is done.
@@ -1328,111 +1338,113 @@ Note that no check for duplicate options is done.
13281338.RE
13291339.SS Citation rendering
13301340.TP
1331−.B \f[C]\-\-bibliography=\f[]\f[I]FILE\f[]
1332−Set the \f[C]bibliography\f[] field in the document\[aq]s metadata to
1333−\f[I]FILE\f[], overriding any value set in the metadata, and process
1334−citations using \f[C]pandoc\-citeproc\f[].
1341+.B \f[C]\-\-bibliography=\f[R]\f[I]FILE\f[R]
1342+Set the \f[C]bibliography\f[R] field in the document\[aq]s metadata to
1343+\f[I]FILE\f[R], overriding any value set in the metadata, and process
1344+citations using \f[C]pandoc\-citeproc\f[R].
13351345(This is equivalent to
1336−\f[C]\-\-metadata\ bibliography=FILE\ \-\-filter\ pandoc\-citeproc\f[].)
1337−If \f[C]\-\-natbib\f[] or \f[C]\-\-biblatex\f[] is also supplied,
1338−\f[C]pandoc\-citeproc\f[] is not used, making this equivalent to
1339−\f[C]\-\-metadata\ bibliography=FILE\f[].
1340−If you supply this argument multiple times, each \f[I]FILE\f[] will be
1346+\f[C]\-\-metadata\ bibliography=FILE\ \-\-filter\ pandoc\-citeproc\f[R].)
1347+If \f[C]\-\-natbib\f[R] or \f[C]\-\-biblatex\f[R] is also supplied,
1348+\f[C]pandoc\-citeproc\f[R] is not used, making this equivalent to
1349+\f[C]\-\-metadata\ bibliography=FILE\f[R].
1350+If you supply this argument multiple times, each \f[I]FILE\f[R] will be
13411351added to bibliography.
13421352.RS
13431353.RE
13441354.TP
1345−.B \f[C]\-\-csl=\f[]\f[I]FILE\f[]
1346−Set the \f[C]csl\f[] field in the document\[aq]s metadata to
1347−\f[I]FILE\f[], overriding any value set in the metadata.
1348−(This is equivalent to \f[C]\-\-metadata\ csl=FILE\f[].) This option is
1349−only relevant with \f[C]pandoc\-citeproc\f[].
1355+.B \f[C]\-\-csl=\f[R]\f[I]FILE\f[R]
1356+Set the \f[C]csl\f[R] field in the document\[aq]s metadata to
1357+\f[I]FILE\f[R], overriding any value set in the metadata.
1358+(This is equivalent to \f[C]\-\-metadata\ csl=FILE\f[R].) This option is
1359+only relevant with \f[C]pandoc\-citeproc\f[R].
13501360.RS
13511361.RE
13521362.TP
1353−.B \f[C]\-\-citation\-abbreviations=\f[]\f[I]FILE\f[]
1354−Set the \f[C]citation\-abbreviations\f[] field in the document\[aq]s
1355−metadata to \f[I]FILE\f[], overriding any value set in the metadata.
1363+.B \f[C]\-\-citation\-abbreviations=\f[R]\f[I]FILE\f[R]
1364+Set the \f[C]citation\-abbreviations\f[R] field in the document\[aq]s
1365+metadata to \f[I]FILE\f[R], overriding any value set in the metadata.
13561366(This is equivalent to
1357−\f[C]\-\-metadata\ citation\-abbreviations=FILE\f[].) This option is
1358−only relevant with \f[C]pandoc\-citeproc\f[].
1367+\f[C]\-\-metadata\ citation\-abbreviations=FILE\f[R].) This option is
1368+only relevant with \f[C]pandoc\-citeproc\f[R].
13591369.RS
13601370.RE
13611371.TP
1362−.B \f[C]\-\-natbib\f[]
1363−Use \f[C]natbib\f[] for citations in LaTeX output.
1364−This option is not for use with the \f[C]pandoc\-citeproc\f[] filter or
1372+.B \f[C]\-\-natbib\f[R]
1373+Use \f[C]natbib\f[R] for citations in LaTeX output.
1374+This option is not for use with the \f[C]pandoc\-citeproc\f[R] filter or
13651375with PDF output.
13661376It is intended for use in producing a LaTeX file that can be processed
1367−with \f[C]bibtex\f[].
1377+with \f[C]bibtex\f[R].
13681378.RS
13691379.RE
13701380.TP
1371−.B \f[C]\-\-biblatex\f[]
1372−Use \f[C]biblatex\f[] for citations in LaTeX output.
1373−This option is not for use with the \f[C]pandoc\-citeproc\f[] filter or
1381+.B \f[C]\-\-biblatex\f[R]
1382+Use \f[C]biblatex\f[R] for citations in LaTeX output.
1383+This option is not for use with the \f[C]pandoc\-citeproc\f[R] filter or
13741384with PDF output.
13751385It is intended for use in producing a LaTeX file that can be processed
1376−with \f[C]bibtex\f[] or \f[C]biber\f[].
1386+with \f[C]bibtex\f[R] or \f[C]biber\f[R].
13771387.RS
13781388.RE
13791389.SS Math rendering in HTML
13801390.PP
13811391The default is to render TeX math as far as possible using Unicode
13821392characters.
1383−Formulas are put inside a \f[C]span\f[] with \f[C]class="math"\f[], so
1384−that they may be styled differently from the surrounding text if needed.
1393+Formulas are put inside a \f[C]span\f[R] with
1394+\f[C]class=\[dq]math\[dq]\f[R], so that they may be styled differently
1395+from the surrounding text if needed.
13851396However, this gives acceptable results only for basic math, usually you
1386−will want to use \f[C]\-\-mathjax\f[] or another of the following
1397+will want to use \f[C]\-\-mathjax\f[R] or another of the following
13871398options.
13881399.TP
1389−.B \f[C]\-\-mathjax\f[][\f[C]=\f[]\f[I]URL\f[]]
1400+.B \f[C]\-\-mathjax\f[R][\f[C]=\f[R]\f[I]URL\f[R]]
13901401Use MathJax to display embedded TeX math in HTML output.
1391−TeX math will be put between \f[C]\\(...\\)\f[] (for inline math) or
1392−\f[C]\\[...\\]\f[] (for display math) and wrapped in \f[C]<span>\f[]
1393−tags with class \f[C]math\f[].
1402+TeX math will be put between \f[C]\[rs](...\[rs])\f[R] (for inline math)
1403+or \f[C]\[rs][...\[rs]]\f[R] (for display math) and wrapped in
1404+\f[C]<span>\f[R] tags with class \f[C]math\f[R].
13941405Then the MathJax JavaScript will render it.
1395−The \f[I]URL\f[] should point to the \f[C]MathJax.js\f[] load script.
1396−If a \f[I]URL\f[] is not provided, a link to the Cloudflare CDN will be
1406+The \f[I]URL\f[R] should point to the \f[C]MathJax.js\f[R] load script.
1407+If a \f[I]URL\f[R] is not provided, a link to the Cloudflare CDN will be
13971408inserted.
13981409.RS
13991410.RE
14001411.TP
1401−.B \f[C]\-\-mathml\f[]
1402−Convert TeX math to MathML (in \f[C]epub3\f[], \f[C]docbook4\f[],
1403−\f[C]docbook5\f[], \f[C]jats\f[], \f[C]html4\f[] and \f[C]html5\f[]).
1404−This is the default in \f[C]odt\f[] output.
1412+.B \f[C]\-\-mathml\f[R]
1413+Convert TeX math to MathML (in \f[C]epub3\f[R], \f[C]docbook4\f[R],
1414+\f[C]docbook5\f[R], \f[C]jats\f[R], \f[C]html4\f[R] and
1415+\f[C]html5\f[R]).
1416+This is the default in \f[C]odt\f[R] output.
14051417Note that currently only Firefox and Safari (and select e\-book readers)
14061418natively support MathML.
14071419.RS
14081420.RE
14091421.TP
1410−.B \f[C]\-\-webtex\f[][\f[C]=\f[]\f[I]URL\f[]]
1411−Convert TeX formulas to \f[C]<img>\f[] tags that link to an external
1422+.B \f[C]\-\-webtex\f[R][\f[C]=\f[R]\f[I]URL\f[R]]
1423+Convert TeX formulas to \f[C]<img>\f[R] tags that link to an external
14121424script that converts formulas to images.
14131425The formula will be URL\-encoded and concatenated with the URL provided.
14141426For SVG images you can for example use
1415−\f[C]\-\-webtex\ https://latex.codecogs.com/svg.latex?\f[].
1427+\f[C]\-\-webtex\ https://latex.codecogs.com/svg.latex?\f[R].
14161428If no URL is specified, the CodeCogs URL generating PNGs will be used
1417−(\f[C]https://latex.codecogs.com/png.latex?\f[]).
1418−Note: the \f[C]\-\-webtex\f[] option will affect Markdown output as well
1419−as HTML, which is useful if you\[aq]re targeting a version of Markdown
1420−without native math support.
1429+(\f[C]https://latex.codecogs.com/png.latex?\f[R]).
1430+Note: the \f[C]\-\-webtex\f[R] option will affect Markdown output as
1431+well as HTML, which is useful if you\[aq]re targeting a version of
1432+Markdown without native math support.
14211433.RS
14221434.RE
14231435.TP
1424−.B \f[C]\-\-katex\f[][\f[C]=\f[]\f[I]URL\f[]]
1436+.B \f[C]\-\-katex\f[R][\f[C]=\f[R]\f[I]URL\f[R]]
14251437Use KaTeX to display embedded TeX math in HTML output.
1426−The \f[I]URL\f[] is the base URL for the KaTeX library.
1427−That directory should contain a \f[C]katex.min.js\f[] and a
1428−\f[C]katex.min.css\f[] file.
1429−If a \f[I]URL\f[] is not provided, a link to the KaTeX CDN will be
1438+The \f[I]URL\f[R] is the base URL for the KaTeX library.
1439+That directory should contain a \f[C]katex.min.js\f[R] and a
1440+\f[C]katex.min.css\f[R] file.
1441+If a \f[I]URL\f[R] is not provided, a link to the KaTeX CDN will be
14301442inserted.
14311443.RS
14321444.RE
14331445.TP
1434−.B \f[C]\-\-gladtex\f[]
1435−Enclose TeX math in \f[C]<eq>\f[] tags in HTML output.
1446+.B \f[C]\-\-gladtex\f[R]
1447+Enclose TeX math in \f[C]<eq>\f[R] tags in HTML output.
14361448The resulting HTML can then be processed by GladTeX to produce images of
14371449the typeset formulas and an HTML file with links to these images.
14381450So, the procedure is:
@@ -1443,27 +1455,27 @@ So, the procedure is:
14431455pandoc\ \-s\ \-\-gladtex\ input.md\ \-o\ myfile.htex
14441456gladtex\ \-d\ myfile\-images\ myfile.htex
14451457#\ produces\ myfile.html\ and\ images\ in\ myfile\-images
1446−\f[]
1458+\f[R]
14471459.fi
14481460.RE
14491461.SS Options for wrapper scripts
14501462.TP
1451−.B \f[C]\-\-dump\-args\f[]
1452−Print information about command\-line arguments to \f[I]stdout\f[], then
1453−exit.
1463+.B \f[C]\-\-dump\-args\f[R]
1464+Print information about command\-line arguments to \f[I]stdout\f[R],
1465+then exit.
14541466This option is intended primarily for use in wrapper scripts.
14551467The first line of output contains the name of the output file specified
1456−with the \f[C]\-o\f[] option, or \f[C]\-\f[] (for \f[I]stdout\f[]) if no
1457−output file was specified.
1468+with the \f[C]\-o\f[R] option, or \f[C]\-\f[R] (for \f[I]stdout\f[R]) if
1469+no output file was specified.
14581470The remaining lines contain the command\-line arguments, one per line,
14591471in the order they appear.
14601472These do not include regular pandoc options and their arguments, but do
1461−include any options appearing after a \f[C]\-\-\f[] separator at the end
1462−of the line.
1473+include any options appearing after a \f[C]\-\-\f[R] separator at the
1474+end of the line.
14631475.RS
14641476.RE
14651477.TP
1466−.B \f[C]\-\-ignore\-args\f[]
1478+.B \f[C]\-\-ignore\-args\f[R]
14671479Ignore command\-line arguments (for use in wrapper scripts).
14681480Regular pandoc options are not ignored.
14691481Thus, for example,
@@ -1472,7 +1484,7 @@ Thus, for example,
14721484.nf
14731485\f[C]
14741486pandoc\ \-\-ignore\-args\ \-o\ foo.html\ \-s\ foo.txt\ \-\-\ \-e\ latin1
1475−\f[]
1487+\f[R]
14761488.fi
14771489.PP
14781490is equivalent to
@@ -1480,12 +1492,12 @@ is equivalent to
14801492.nf
14811493\f[C]
14821494pandoc\ \-o\ foo.html\ \-s
1483−\f[]
1495+\f[R]
14841496.fi
14851497.RE
14861498.SH TEMPLATES
14871499.PP
1488−When the \f[C]\-s/\-\-standalone\f[] option is used, pandoc uses a
1500+When the \f[C]\-s/\-\-standalone\f[R] option is used, pandoc uses a
14891501template to add header and footer material that is needed for a
14901502self\-standing document.
14911503To see the default template that is used, just type
@@ -1493,46 +1505,46 @@ To see the default template that is used, just type
14931505.nf
14941506\f[C]
14951507pandoc\ \-D\ *FORMAT*
1496−\f[]
1508+\f[R]
14971509.fi
14981510.PP
1499−where \f[I]FORMAT\f[] is the name of the output format.
1500−A custom template can be specified using the \f[C]\-\-template\f[]
1511+where \f[I]FORMAT\f[R] is the name of the output format.
1512+A custom template can be specified using the \f[C]\-\-template\f[R]
15011513option.
15021514You can also override the system default templates for a given output
1503−format \f[I]FORMAT\f[] by putting a file
1504−\f[C]templates/default.*FORMAT*\f[] in the user data directory (see
1505−\f[C]\-\-data\-dir\f[], above).
1506−\f[I]Exceptions:\f[]
1515+format \f[I]FORMAT\f[R] by putting a file
1516+\f[C]templates/default.*FORMAT*\f[R] in the user data directory (see
1517+\f[C]\-\-data\-dir\f[R], above).
1518+\f[I]Exceptions:\f[R]
15071519.IP \[bu] 2
1508−For \f[C]odt\f[] output, customize the \f[C]default.opendocument\f[]
1520+For \f[C]odt\f[R] output, customize the \f[C]default.opendocument\f[R]
15091521template.
15101522.IP \[bu] 2
1511−For \f[C]pdf\f[] output, customize the \f[C]default.latex\f[] template
1512−(or the \f[C]default.context\f[] template, if you use
1513−\f[C]\-t\ context\f[], or the \f[C]default.ms\f[] template, if you use
1514−\f[C]\-t\ ms\f[], or the \f[C]default.html\f[] template, if you use
1515−\f[C]\-t\ html\f[]).
1523+For \f[C]pdf\f[R] output, customize the \f[C]default.latex\f[R] template
1524+(or the \f[C]default.context\f[R] template, if you use
1525+\f[C]\-t\ context\f[R], or the \f[C]default.ms\f[R] template, if you use
1526+\f[C]\-t\ ms\f[R], or the \f[C]default.html\f[R] template, if you use
1527+\f[C]\-t\ html\f[R]).
15161528.IP \[bu] 2
1517−\f[C]docx\f[] has no template (however, you can use
1518−\f[C]\-\-reference\-doc\f[] to customize the output).
1529+\f[C]docx\f[R] has no template (however, you can use
1530+\f[C]\-\-reference\-doc\f[R] to customize the output).
15191531.PP
1520−Templates contain \f[I]variables\f[], which allow for the inclusion of
1532+Templates contain \f[I]variables\f[R], which allow for the inclusion of
15211533arbitrary information at any point in the file.
1522−They may be set at the command line using the \f[C]\-V/\-\-variable\f[]
1534+They may be set at the command line using the \f[C]\-V/\-\-variable\f[R]
15231535option.
15241536If a variable is not set, pandoc will look for the key in the
15251537document\[aq]s metadata \[en] which can be set using either YAML
1526−metadata blocks or with the \f[C]\-\-metadata\f[] option.
1538+metadata blocks or with the \f[C]\-\-metadata\f[R] option.
15271539.SS Variables set by pandoc
15281540.PP
15291541Some variables are set automatically by pandoc.
15301542These vary somewhat depending on the output format, but include the
15311543following:
15321544.TP
1533−.B \f[C]sourcefile\f[], \f[C]outputfile\f[]
1545+.B \f[C]sourcefile\f[R], \f[C]outputfile\f[R]
15341546source and destination filenames, as given on the command line.
1535−\f[C]sourcefile\f[] can also be a list if input comes from multiple
1547+\f[C]sourcefile\f[R] can also be a list if input comes from multiple
15361548files, or empty if input is from stdin.
15371549You can use the following snippet in your template to distinguish them:
15381550.RS
@@ -1546,14 +1558,14 @@ $endfor$
15461558$else$
15471559(stdin)
15481560$endif$
1549−\f[]
1561+\f[R]
15501562.fi
15511563.PP
1552−Similarly, \f[C]outputfile\f[] can be \f[C]\-\f[] if output goes to the
1553−terminal.
1564+Similarly, \f[C]outputfile\f[R] can be \f[C]\-\f[R] if output goes to
1565+the terminal.
15541566.RE
15551567.TP
1556−.B \f[C]title\f[], \f[C]author\f[], \f[C]date\f[]
1568+.B \f[C]title\f[R], \f[C]author\f[R], \f[C]date\f[R]
15571569allow identification of basic aspects of the document.
15581570Included in PDF metadata through LaTeX and ConTeXt.
15591571These can be set through a pandoc title block, which allows for multiple
@@ -1567,366 +1579,367 @@ author:
15671579\-\ Aristotle
15681580\-\ Peter\ Abelard
15691581\&...
1570−\f[]
1582+\f[R]
15711583.fi
15721584.RE
15731585.TP
1574−.B \f[C]subtitle\f[]
1586+.B \f[C]subtitle\f[R]
15751587document subtitle, included in HTML, EPUB, LaTeX, ConTeXt, and Word
15761588docx; renders in LaTeX only when using a document class that supports
1577−\f[C]\\subtitle\f[], such as \f[C]beamer\f[] or the KOMA\-Script series
1578−(\f[C]scrartcl\f[], \f[C]scrreprt\f[], \f[C]scrbook\f[]).
1589+\f[C]\[rs]subtitle\f[R], such as \f[C]beamer\f[R] or the KOMA\-Script
1590+series (\f[C]scrartcl\f[R], \f[C]scrreprt\f[R], \f[C]scrbook\f[R]).
15791591.RS
15801592.RE
15811593.TP
1582−.B \f[C]institute\f[]
1594+.B \f[C]institute\f[R]
15831595author affiliations (in LaTeX and Beamer only).
15841596Can be a list, when there are multiple authors.
15851597.RS
15861598.RE
15871599.TP
1588−.B \f[C]abstract\f[]
1600+.B \f[C]abstract\f[R]
15891601document summary, included in LaTeX, ConTeXt, AsciiDoc, and Word docx
15901602.RS
15911603.RE
15921604.TP
1593−.B \f[C]keywords\f[]
1605+.B \f[C]keywords\f[R]
15941606list of keywords to be included in HTML, PDF, and AsciiDoc metadata; may
1595−be repeated as for \f[C]author\f[], above
1607+be repeated as for \f[C]author\f[R], above
15961608.RS
15971609.RE
15981610.TP
1599−.B \f[C]header\-includes\f[]
1600−contents specified by \f[C]\-H/\-\-include\-in\-header\f[] (may have
1611+.B \f[C]header\-includes\f[R]
1612+contents specified by \f[C]\-H/\-\-include\-in\-header\f[R] (may have
16011613multiple values)
16021614.RS
16031615.RE
16041616.TP
1605−.B \f[C]toc\f[]
1606−non\-null value if \f[C]\-\-toc/\-\-table\-of\-contents\f[] was
1617+.B \f[C]toc\f[R]
1618+non\-null value if \f[C]\-\-toc/\-\-table\-of\-contents\f[R] was
16071619specified
16081620.RS
16091621.RE
16101622.TP
1611−.B \f[C]toc\-title\f[]
1623+.B \f[C]toc\-title\f[R]
16121624title of table of contents (works only with EPUB, opendocument, odt,
16131625docx, pptx, beamer, LaTeX)
16141626.RS
16151627.RE
16161628.TP
1617−.B \f[C]include\-before\f[]
1618−contents specified by \f[C]\-B/\-\-include\-before\-body\f[] (may have
1629+.B \f[C]include\-before\f[R]
1630+contents specified by \f[C]\-B/\-\-include\-before\-body\f[R] (may have
16191631multiple values)
16201632.RS
16211633.RE
16221634.TP
1623−.B \f[C]include\-after\f[]
1624−contents specified by \f[C]\-A/\-\-include\-after\-body\f[] (may have
1635+.B \f[C]include\-after\f[R]
1636+contents specified by \f[C]\-A/\-\-include\-after\-body\f[R] (may have
16251637multiple values)
16261638.RS
16271639.RE
16281640.TP
1629−.B \f[C]body\f[]
1641+.B \f[C]body\f[R]
16301642body of document
16311643.RS
16321644.RE
16331645.TP
1634−.B \f[C]meta\-json\f[]
1646+.B \f[C]meta\-json\f[R]
16351647JSON representation of all of the document\[aq]s metadata.
16361648Field values are transformed to the selected output format.
16371649.RS
16381650.RE
16391651.SS Language variables
16401652.TP
1641−.B \f[C]lang\f[]
1653+.B \f[C]lang\f[R]
16421654identifies the main language of the document, using a code according to
16431655BCP 47 (e.g.
1644−\f[C]en\f[] or \f[C]en\-GB\f[]).
1656+\f[C]en\f[R] or \f[C]en\-GB\f[R]).
16451657For some output formats, pandoc will convert it to an appropriate format
1646−stored in the additional variables \f[C]babel\-lang\f[],
1647−\f[C]polyglossia\-lang\f[] (LaTeX) and \f[C]context\-lang\f[] (ConTeXt).
1658+stored in the additional variables \f[C]babel\-lang\f[R],
1659+\f[C]polyglossia\-lang\f[R] (LaTeX) and \f[C]context\-lang\f[R]
1660+(ConTeXt).
16481661.RS
16491662.PP
16501663Native pandoc Spans and Divs with the lang attribute (value in BCP 47)
16511664can be used to switch the language in that range.
1652−In LaTeX output, \f[C]babel\-otherlangs\f[] and
1653−\f[C]polyglossia\-otherlangs\f[] variables will be generated
1654−automatically based on the \f[C]lang\f[] attributes of Spans and Divs in
1655−the document.
1665+In LaTeX output, \f[C]babel\-otherlangs\f[R] and
1666+\f[C]polyglossia\-otherlangs\f[R] variables will be generated
1667+automatically based on the \f[C]lang\f[R] attributes of Spans and Divs
1668+in the document.
16561669.RE
16571670.TP
1658−.B \f[C]dir\f[]
1659−the base direction of the document, either \f[C]rtl\f[]
1660−(right\-to\-left) or \f[C]ltr\f[] (left\-to\-right).
1671+.B \f[C]dir\f[R]
1672+the base direction of the document, either \f[C]rtl\f[R]
1673+(right\-to\-left) or \f[C]ltr\f[R] (left\-to\-right).
16611674.RS
16621675.PP
1663−For bidirectional documents, native pandoc \f[C]span\f[]s and
1664−\f[C]div\f[]s with the \f[C]dir\f[] attribute (value \f[C]rtl\f[] or
1665−\f[C]ltr\f[]) can be used to override the base direction in some output
1676+For bidirectional documents, native pandoc \f[C]span\f[R]s and
1677+\f[C]div\f[R]s with the \f[C]dir\f[R] attribute (value \f[C]rtl\f[R] or
1678+\f[C]ltr\f[R]) can be used to override the base direction in some output
16661679formats.
16671680This may not always be necessary if the final renderer (e.g.
16681681the browser, when generating HTML) supports the Unicode Bidirectional
16691682Algorithm.
16701683.PP
1671−When using LaTeX for bidirectional documents, only the \f[C]xelatex\f[]
1672−engine is fully supported (use \f[C]\-\-pdf\-engine=xelatex\f[]).
1684+When using LaTeX for bidirectional documents, only the \f[C]xelatex\f[R]
1685+engine is fully supported (use \f[C]\-\-pdf\-engine=xelatex\f[R]).
16731686.RE
16741687.SS Variables for slides
16751688.PP
16761689Variables are available for producing slide shows with pandoc, including
16771690all reveal.js configuration options.
16781691.TP
1679−.B \f[C]titlegraphic\f[]
1692+.B \f[C]titlegraphic\f[R]
16801693title graphic for Beamer documents
16811694.RS
16821695.RE
16831696.TP
1684−.B \f[C]logo\f[]
1697+.B \f[C]logo\f[R]
16851698logo for Beamer documents
16861699.RS
16871700.RE
16881701.TP
1689−.B \f[C]slidy\-url\f[]
1702+.B \f[C]slidy\-url\f[R]
16901703base URL for Slidy documents (defaults to
1691−\f[C]https://www.w3.org/Talks/Tools/Slidy2\f[])
1704+\f[C]https://www.w3.org/Talks/Tools/Slidy2\f[R])
16921705.RS
16931706.RE
16941707.TP
1695−.B \f[C]slideous\-url\f[]
1696−base URL for Slideous documents (defaults to \f[C]slideous\f[])
1708+.B \f[C]slideous\-url\f[R]
1709+base URL for Slideous documents (defaults to \f[C]slideous\f[R])
16971710.RS
16981711.RE
16991712.TP
1700−.B \f[C]s5\-url\f[]
1701−base URL for S5 documents (defaults to \f[C]s5/default\f[])
1713+.B \f[C]s5\-url\f[R]
1714+base URL for S5 documents (defaults to \f[C]s5/default\f[R])
17021715.RS
17031716.RE
17041717.TP
1705−.B \f[C]revealjs\-url\f[]
1706−base URL for reveal.js documents (defaults to \f[C]reveal.js\f[])
1718+.B \f[C]revealjs\-url\f[R]
1719+base URL for reveal.js documents (defaults to \f[C]reveal.js\f[R])
17071720.RS
17081721.RE
17091722.TP
1710−.B \f[C]theme\f[], \f[C]colortheme\f[], \f[C]fonttheme\f[], \f[C]innertheme\f[], \f[C]outertheme\f[]
1711−themes for LaTeX \f[C]beamer\f[] documents
1723+.B \f[C]theme\f[R], \f[C]colortheme\f[R], \f[C]fonttheme\f[R], \f[C]innertheme\f[R], \f[C]outertheme\f[R]
1724+themes for LaTeX \f[C]beamer\f[R] documents
17121725.RS
17131726.RE
17141727.TP
1715−.B \f[C]themeoptions\f[]
1728+.B \f[C]themeoptions\f[R]
17161729options for LaTeX beamer themes (a list).
17171730.RS
17181731.RE
17191732.TP
1720−.B \f[C]navigation\f[]
1721−controls navigation symbols in \f[C]beamer\f[] documents (default is
1722−\f[C]empty\f[] for no navigation symbols; other valid values are
1723−\f[C]frame\f[], \f[C]vertical\f[], and \f[C]horizontal\f[]).
1733+.B \f[C]navigation\f[R]
1734+controls navigation symbols in \f[C]beamer\f[R] documents (default is
1735+\f[C]empty\f[R] for no navigation symbols; other valid values are
1736+\f[C]frame\f[R], \f[C]vertical\f[R], and \f[C]horizontal\f[R]).
17241737.RS
17251738.RE
17261739.TP
1727−.B \f[C]section\-titles\f[]
1728−enables on "title pages" for new sections in \f[C]beamer\f[] documents
1729−(default = true).
1740+.B \f[C]section\-titles\f[R]
1741+enables on \[dq]title pages\[dq] for new sections in \f[C]beamer\f[R]
1742+documents (default = true).
17301743.RS
17311744.RE
17321745.TP
1733−.B \f[C]beamerarticle\f[]
1734−when true, the \f[C]beamerarticle\f[] package is loaded (for producing
1746+.B \f[C]beamerarticle\f[R]
1747+when true, the \f[C]beamerarticle\f[R] package is loaded (for producing
17351748an article from beamer slides).
17361749.RS
17371750.RE
17381751.TP
1739−.B \f[C]aspectratio\f[]
1740−aspect ratio of slides (for beamer only, \f[C]1610\f[] for 16:10,
1741−\f[C]169\f[] for 16:9, \f[C]149\f[] for 14:9, \f[C]141\f[] for 1.41:1,
1742−\f[C]54\f[] for 5:4, \f[C]43\f[] for 4:3 which is the default, and
1743−\f[C]32\f[] for 3:2).
1752+.B \f[C]aspectratio\f[R]
1753+aspect ratio of slides (for beamer only, \f[C]1610\f[R] for 16:10,
1754+\f[C]169\f[R] for 16:9, \f[C]149\f[R] for 14:9, \f[C]141\f[R] for
1755+1.41:1, \f[C]54\f[R] for 5:4, \f[C]43\f[R] for 4:3 which is the default,
1756+and \f[C]32\f[R] for 3:2).
17441757.RS
17451758.RE
17461759.SS Variables for LaTeX
17471760.PP
17481761LaTeX variables are used when creating a PDF.
17491762.TP
1750−.B \f[C]papersize\f[]
1763+.B \f[C]papersize\f[R]
17511764paper size, e.g.
1752−\f[C]letter\f[], \f[C]a4\f[]
1765+\f[C]letter\f[R], \f[C]a4\f[R]
17531766.RS
17541767.RE
17551768.TP
1756−.B \f[C]fontsize\f[]
1769+.B \f[C]fontsize\f[R]
17571770font size for body text (e.g.
1758−\f[C]10pt\f[], \f[C]12pt\f[])
1771+\f[C]10pt\f[R], \f[C]12pt\f[R])
17591772.RS
17601773.RE
17611774.TP
1762−.B \f[C]documentclass\f[]
1775+.B \f[C]documentclass\f[R]
17631776document class, e.g.
1764−\f[C]article\f[], \f[C]report\f[], \f[C]book\f[], \f[C]memoir\f[]
1777+\f[C]article\f[R], \f[C]report\f[R], \f[C]book\f[R], \f[C]memoir\f[R]
17651778.RS
17661779.RE
17671780.TP
1768−.B \f[C]classoption\f[]
1781+.B \f[C]classoption\f[R]
17691782option for document class, e.g.
1770−\f[C]oneside\f[]; may be repeated for multiple options
1783+\f[C]oneside\f[R]; may be repeated for multiple options
17711784.RS
17721785.RE
17731786.TP
1774−.B \f[C]beameroption\f[]
1775−In beamer, add extra beamer option with \f[C]\\setbeameroption{}\f[]
1787+.B \f[C]beameroption\f[R]
1788+In beamer, add extra beamer option with \f[C]\[rs]setbeameroption{}\f[R]
17761789.RS
17771790.RE
17781791.TP
1779−.B \f[C]geometry\f[]
1780−option for \f[C]geometry\f[] package, e.g.
1781−\f[C]margin=1in\f[]; may be repeated for multiple options
1792+.B \f[C]geometry\f[R]
1793+option for \f[C]geometry\f[R] package, e.g.
1794+\f[C]margin=1in\f[R]; may be repeated for multiple options
17821795.RS
17831796.RE
17841797.TP
1785−.B \f[C]margin\-left\f[], \f[C]margin\-right\f[], \f[C]margin\-top\f[], \f[C]margin\-bottom\f[]
1786−sets margins, if \f[C]geometry\f[] is not used (otherwise
1787−\f[C]geometry\f[] overrides these)
1798+.B \f[C]margin\-left\f[R], \f[C]margin\-right\f[R], \f[C]margin\-top\f[R], \f[C]margin\-bottom\f[R]
1799+sets margins, if \f[C]geometry\f[R] is not used (otherwise
1800+\f[C]geometry\f[R] overrides these)
17881801.RS
17891802.RE
17901803.TP
1791−.B \f[C]linestretch\f[]
1792−adjusts line spacing using the \f[C]setspace\f[] package, e.g.
1793−\f[C]1.25\f[], \f[C]1.5\f[]
1804+.B \f[C]linestretch\f[R]
1805+adjusts line spacing using the \f[C]setspace\f[R] package, e.g.
1806+\f[C]1.25\f[R], \f[C]1.5\f[R]
17941807.RS
17951808.RE
17961809.TP
1797−.B \f[C]fontfamily\f[]
1798−font package for use with \f[C]pdflatex\f[]: TeX Live includes many
1810+.B \f[C]fontfamily\f[R]
1811+font package for use with \f[C]pdflatex\f[R]: TeX Live includes many
17991812options, documented in the LaTeX Font Catalogue.
18001813The default is Latin Modern.
18011814.RS
18021815.RE
18031816.TP
1804−.B \f[C]fontfamilyoptions\f[]
1805−options for package used as \f[C]fontfamily\f[]: e.g.
1806−\f[C]osf,sc\f[] with \f[C]fontfamily\f[] set to \f[C]mathpazo\f[]
1817+.B \f[C]fontfamilyoptions\f[R]
1818+options for package used as \f[C]fontfamily\f[R]: e.g.
1819+\f[C]osf,sc\f[R] with \f[C]fontfamily\f[R] set to \f[C]mathpazo\f[R]
18071820provides Palatino with old\-style figures and true small caps; may be
18081821repeated for multiple options
18091822.RS
18101823.RE
18111824.TP
1812−.B \f[C]mainfont\f[], \f[C]sansfont\f[], \f[C]monofont\f[], \f[C]mathfont\f[], \f[C]CJKmainfont\f[]
1813−font families for use with \f[C]xelatex\f[] or \f[C]lualatex\f[]: take
1814−the name of any system font, using the \f[C]fontspec\f[] package.
1815−Note that if \f[C]CJKmainfont\f[] is used, the \f[C]xecjk\f[] package
1825+.B \f[C]mainfont\f[R], \f[C]sansfont\f[R], \f[C]monofont\f[R], \f[C]mathfont\f[R], \f[C]CJKmainfont\f[R]
1826+font families for use with \f[C]xelatex\f[R] or \f[C]lualatex\f[R]: take
1827+the name of any system font, using the \f[C]fontspec\f[R] package.
1828+Note that if \f[C]CJKmainfont\f[R] is used, the \f[C]xecjk\f[R] package
18161829must be available.
18171830.RS
18181831.RE
18191832.TP
1820−.B \f[C]mainfontoptions\f[], \f[C]sansfontoptions\f[], \f[C]monofontoptions\f[], \f[C]mathfontoptions\f[], \f[C]CJKoptions\f[]
1821−options to use with \f[C]mainfont\f[], \f[C]sansfont\f[],
1822−\f[C]monofont\f[], \f[C]mathfont\f[], \f[C]CJKmainfont\f[] in
1823−\f[C]xelatex\f[] and \f[C]lualatex\f[].
1824−Allow for any choices available through \f[C]fontspec\f[], such as the
1825−OpenType features \f[C]Numbers=OldStyle,Numbers=Proportional\f[].
1833+.B \f[C]mainfontoptions\f[R], \f[C]sansfontoptions\f[R], \f[C]monofontoptions\f[R], \f[C]mathfontoptions\f[R], \f[C]CJKoptions\f[R]
1834+options to use with \f[C]mainfont\f[R], \f[C]sansfont\f[R],
1835+\f[C]monofont\f[R], \f[C]mathfont\f[R], \f[C]CJKmainfont\f[R] in
1836+\f[C]xelatex\f[R] and \f[C]lualatex\f[R].
1837+Allow for any choices available through \f[C]fontspec\f[R], such as the
1838+OpenType features \f[C]Numbers=OldStyle,Numbers=Proportional\f[R].
18261839May be repeated for multiple options.
18271840.RS
18281841.RE
18291842.TP
1830−.B \f[C]fontenc\f[]
1831−allows font encoding to be specified through \f[C]fontenc\f[] package
1832−(with \f[C]pdflatex\f[]); default is \f[C]T1\f[] (see guide to LaTeX
1843+.B \f[C]fontenc\f[R]
1844+allows font encoding to be specified through \f[C]fontenc\f[R] package
1845+(with \f[C]pdflatex\f[R]); default is \f[C]T1\f[R] (see guide to LaTeX
18331846font encodings)
18341847.RS
18351848.RE
18361849.TP
1837−.B \f[C]microtypeoptions\f[]
1850+.B \f[C]microtypeoptions\f[R]
18381851options to pass to the microtype package
18391852.RS
18401853.RE
18411854.TP
1842−.B \f[C]colorlinks\f[]
1855+.B \f[C]colorlinks\f[R]
18431856add color to link text; automatically enabled if any of
1844−\f[C]linkcolor\f[], \f[C]filecolor\f[], \f[C]citecolor\f[],
1845−\f[C]urlcolor\f[], or \f[C]toccolor\f[] are set
1857+\f[C]linkcolor\f[R], \f[C]filecolor\f[R], \f[C]citecolor\f[R],
1858+\f[C]urlcolor\f[R], or \f[C]toccolor\f[R] are set
18461859.RS
18471860.RE
18481861.TP
1849−.B \f[C]linkcolor\f[], \f[C]filecolor\f[], \f[C]citecolor\f[], \f[C]urlcolor\f[], \f[C]toccolor\f[]
1862+.B \f[C]linkcolor\f[R], \f[C]filecolor\f[R], \f[C]citecolor\f[R], \f[C]urlcolor\f[R], \f[C]toccolor\f[R]
18501863color for internal links, external links, citation links, linked URLs,
18511864and links in table of contents, respectively: uses options allowed by
1852−\f[C]xcolor\f[], including the \f[C]dvipsnames\f[], \f[C]svgnames\f[],
1853−and \f[C]x11names\f[] lists
1865+\f[C]xcolor\f[R], including the \f[C]dvipsnames\f[R],
1866+\f[C]svgnames\f[R], and \f[C]x11names\f[R] lists
18541867.RS
18551868.RE
18561869.TP
1857−.B \f[C]links\-as\-notes\f[]
1870+.B \f[C]links\-as\-notes\f[R]
18581871causes links to be printed as footnotes
18591872.RS
18601873.RE
18611874.TP
1862−.B \f[C]indent\f[]
1875+.B \f[C]indent\f[R]
18631876uses document class settings for indentation (the default LaTeX template
18641877otherwise removes indentation and adds space between paragraphs)
18651878.RS
18661879.RE
18671880.TP
1868−.B \f[C]subparagraph\f[]
1881+.B \f[C]subparagraph\f[R]
18691882disables default behavior of LaTeX template that redefines
18701883(sub)paragraphs as sections, changing the appearance of nested headings
18711884in some classes
18721885.RS
18731886.RE
18741887.TP
1875−.B \f[C]thanks\f[]
1888+.B \f[C]thanks\f[R]
18761889specifies contents of acknowledgments footnote after document title.
18771890.RS
18781891.RE
18791892.TP
1880−.B \f[C]toc\f[]
1893+.B \f[C]toc\f[R]
18811894include table of contents (can also be set using
1882−\f[C]\-\-toc/\-\-table\-of\-contents\f[])
1895+\f[C]\-\-toc/\-\-table\-of\-contents\f[R])
18831896.RS
18841897.RE
18851898.TP
1886−.B \f[C]toc\-depth\f[]
1899+.B \f[C]toc\-depth\f[R]
18871900level of section to include in table of contents
18881901.RS
18891902.RE
18901903.TP
1891−.B \f[C]secnumdepth\f[]
1904+.B \f[C]secnumdepth\f[R]
18921905numbering depth for sections, if sections are numbered
18931906.RS
18941907.RE
18951908.TP
1896−.B \f[C]lof\f[], \f[C]lot\f[]
1909+.B \f[C]lof\f[R], \f[C]lot\f[R]
18971910include list of figures, list of tables
18981911.RS
18991912.RE
19001913.TP
1901−.B \f[C]bibliography\f[]
1914+.B \f[C]bibliography\f[R]
19021915bibliography to use for resolving references
19031916.RS
19041917.RE
19051918.TP
1906−.B \f[C]biblio\-style\f[]
1907−bibliography style, when used with \f[C]\-\-natbib\f[] and
1908−\f[C]\-\-biblatex\f[].
1919+.B \f[C]biblio\-style\f[R]
1920+bibliography style, when used with \f[C]\-\-natbib\f[R] and
1921+\f[C]\-\-biblatex\f[R].
19091922.RS
19101923.RE
19111924.TP
1912−.B \f[C]biblio\-title\f[]
1913−bibliography title, when used with \f[C]\-\-natbib\f[] and
1914−\f[C]\-\-biblatex\f[].
1925+.B \f[C]biblio\-title\f[R]
1926+bibliography title, when used with \f[C]\-\-natbib\f[R] and
1927+\f[C]\-\-biblatex\f[R].
19151928.RS
19161929.RE
19171930.TP
1918−.B \f[C]biblatexoptions\f[]
1931+.B \f[C]biblatexoptions\f[R]
19191932list of options for biblatex.
19201933.RS
19211934.RE
19221935.TP
1923−.B \f[C]natbiboptions\f[]
1936+.B \f[C]natbiboptions\f[R]
19241937list of options for natbib.
19251938.RS
19261939.RE
19271940.TP
1928−.B \f[C]pagestyle\f[]
1929−An option for LaTeX\[aq]s \f[C]\\pagestyle{}\f[].
1941+.B \f[C]pagestyle\f[R]
1942+An option for LaTeX\[aq]s \f[C]\[rs]pagestyle{}\f[R].
19301943The default article class supports \[aq]plain\[aq] (default),
19311944\[aq]empty\[aq], and \[aq]headings\[aq]; headings puts section titles in
19321945the header.
@@ -1934,94 +1947,94 @@ the header.
19341947.RE
19351948.SS Variables for ConTeXt
19361949.TP
1937−.B \f[C]papersize\f[]
1950+.B \f[C]papersize\f[R]
19381951paper size, e.g.
1939−\f[C]letter\f[], \f[C]A4\f[], \f[C]landscape\f[] (see ConTeXt Paper
1952+\f[C]letter\f[R], \f[C]A4\f[R], \f[C]landscape\f[R] (see ConTeXt Paper
19401953Setup); may be repeated for multiple options
19411954.RS
19421955.RE
19431956.TP
1944−.B \f[C]layout\f[]
1957+.B \f[C]layout\f[R]
19451958options for page margins and text arrangement (see ConTeXt Layout); may
19461959be repeated for multiple options
19471960.RS
19481961.RE
19491962.TP
1950−.B \f[C]margin\-left\f[], \f[C]margin\-right\f[], \f[C]margin\-top\f[], \f[C]margin\-bottom\f[]
1951−sets margins, if \f[C]layout\f[] is not used (otherwise \f[C]layout\f[]
1952−overrides these)
1963+.B \f[C]margin\-left\f[R], \f[C]margin\-right\f[R], \f[C]margin\-top\f[R], \f[C]margin\-bottom\f[R]
1964+sets margins, if \f[C]layout\f[R] is not used (otherwise
1965+\f[C]layout\f[R] overrides these)
19531966.RS
19541967.RE
19551968.TP
1956−.B \f[C]fontsize\f[]
1969+.B \f[C]fontsize\f[R]
19571970font size for body text (e.g.
1958−\f[C]10pt\f[], \f[C]12pt\f[])
1971+\f[C]10pt\f[R], \f[C]12pt\f[R])
19591972.RS
19601973.RE
19611974.TP
1962−.B \f[C]mainfont\f[], \f[C]sansfont\f[], \f[C]monofont\f[], \f[C]mathfont\f[]
1975+.B \f[C]mainfont\f[R], \f[C]sansfont\f[R], \f[C]monofont\f[R], \f[C]mathfont\f[R]
19631976font families: take the name of any system font (see ConTeXt Font
19641977Switching)
19651978.RS
19661979.RE
19671980.TP
1968−.B \f[C]linkcolor\f[], \f[C]contrastcolor\f[]
1981+.B \f[C]linkcolor\f[R], \f[C]contrastcolor\f[R]
19691982color for links outside and inside a page, e.g.
1970−\f[C]red\f[], \f[C]blue\f[] (see ConTeXt Color)
1983+\f[C]red\f[R], \f[C]blue\f[R] (see ConTeXt Color)
19711984.RS
19721985.RE
19731986.TP
1974−.B \f[C]linkstyle\f[]
1987+.B \f[C]linkstyle\f[R]
19751988typeface style for links, e.g.
1976−\f[C]normal\f[], \f[C]bold\f[], \f[C]slanted\f[], \f[C]boldslanted\f[],
1977−\f[C]type\f[], \f[C]cap\f[], \f[C]small\f[]
1989+\f[C]normal\f[R], \f[C]bold\f[R], \f[C]slanted\f[R],
1990+\f[C]boldslanted\f[R], \f[C]type\f[R], \f[C]cap\f[R], \f[C]small\f[R]
19781991.RS
19791992.RE
19801993.TP
1981−.B \f[C]indenting\f[]
1994+.B \f[C]indenting\f[R]
19821995controls indentation of paragraphs, e.g.
1983−\f[C]yes,small,next\f[] (see ConTeXt Indentation); may be repeated for
1996+\f[C]yes,small,next\f[R] (see ConTeXt Indentation); may be repeated for
19841997multiple options
19851998.RS
19861999.RE
19872000.TP
1988−.B \f[C]whitespace\f[]
2001+.B \f[C]whitespace\f[R]
19892002spacing between paragraphs, e.g.
1990−\f[C]none\f[], \f[C]small\f[] (using \f[C]setupwhitespace\f[])
2003+\f[C]none\f[R], \f[C]small\f[R] (using \f[C]setupwhitespace\f[R])
19912004.RS
19922005.RE
19932006.TP
1994−.B \f[C]interlinespace\f[]
2007+.B \f[C]interlinespace\f[R]
19952008adjusts line spacing, e.g.
1996−\f[C]4ex\f[] (using \f[C]setupinterlinespace\f[]); may be repeated for
2009+\f[C]4ex\f[R] (using \f[C]setupinterlinespace\f[R]); may be repeated for
19972010multiple options
19982011.RS
19992012.RE
20002013.TP
2001−.B \f[C]headertext\f[], \f[C]footertext\f[]
2014+.B \f[C]headertext\f[R], \f[C]footertext\f[R]
20022015text to be placed in running header or footer (see ConTeXt Headers and
20032016Footers); may be repeated up to four times for different placement
20042017.RS
20052018.RE
20062019.TP
2007−.B \f[C]pagenumbering\f[]
2008−page number style and location (using \f[C]setuppagenumbering\f[]); may
2020+.B \f[C]pagenumbering\f[R]
2021+page number style and location (using \f[C]setuppagenumbering\f[R]); may
20092022be repeated for multiple options
20102023.RS
20112024.RE
20122025.TP
2013−.B \f[C]toc\f[]
2026+.B \f[C]toc\f[R]
20142027include table of contents (can also be set using
2015−\f[C]\-\-toc/\-\-table\-of\-contents\f[])
2028+\f[C]\-\-toc/\-\-table\-of\-contents\f[R])
20162029.RS
20172030.RE
20182031.TP
2019−.B \f[C]lof\f[], \f[C]lot\f[]
2032+.B \f[C]lof\f[R], \f[C]lot\f[R]
20202033include list of figures, list of tables
20212034.RS
20222035.RE
20232036.TP
2024−.B \f[C]pdfa\f[]
2037+.B \f[C]pdfa\f[R]
20252038adds to the preamble the setup necessary to generate PDF/A\-1b:2005.
20262039To successfully generate PDF/A the required ICC color profiles have to
20272040be available and the content and all included files (such as images)
@@ -2032,73 +2045,73 @@ See also ConTeXt PDFA for more details.
20322045.RE
20332046.SS Variables for man pages
20342047.TP
2035−.B \f[C]section\f[]
2048+.B \f[C]section\f[R]
20362049section number in man pages
20372050.RS
20382051.RE
20392052.TP
2040−.B \f[C]header\f[]
2053+.B \f[C]header\f[R]
20412054header in man pages
20422055.RS
20432056.RE
20442057.TP
2045−.B \f[C]footer\f[]
2058+.B \f[C]footer\f[R]
20462059footer in man pages
20472060.RS
20482061.RE
20492062.TP
2050−.B \f[C]adjusting\f[]
2051−adjusts text to left (\f[C]l\f[]), right (\f[C]r\f[]), center
2052−(\f[C]c\f[]), or both (\f[C]b\f[]) margins
2063+.B \f[C]adjusting\f[R]
2064+adjusts text to left (\f[C]l\f[R]), right (\f[C]r\f[R]), center
2065+(\f[C]c\f[R]), or both (\f[C]b\f[R]) margins
20532066.RS
20542067.RE
20552068.TP
2056−.B \f[C]hyphenate\f[]
2057−if \f[C]true\f[] (the default), hyphenation will be used
2069+.B \f[C]hyphenate\f[R]
2070+if \f[C]true\f[R] (the default), hyphenation will be used
20582071.RS
20592072.RE
20602073.SS Variables for ms
20612074.TP
2062−.B \f[C]pointsize\f[]
2075+.B \f[C]pointsize\f[R]
20632076point size (e.g.
2064−\f[C]10p\f[])
2077+\f[C]10p\f[R])
20652078.RS
20662079.RE
20672080.TP
2068−.B \f[C]lineheight\f[]
2081+.B \f[C]lineheight\f[R]
20692082line height (e.g.
2070−\f[C]12p\f[])
2083+\f[C]12p\f[R])
20712084.RS
20722085.RE
20732086.TP
2074−.B \f[C]fontfamily\f[]
2087+.B \f[C]fontfamily\f[R]
20752088font family (e.g.
2076−\f[C]T\f[] or \f[C]P\f[])
2089+\f[C]T\f[R] or \f[C]P\f[R])
20772090.RS
20782091.RE
20792092.TP
2080−.B \f[C]indent\f[]
2093+.B \f[C]indent\f[R]
20812094paragraph indent (e.g.
2082−\f[C]2m\f[])
2095+\f[C]2m\f[R])
20832096.RS
20842097.RE
20852098.SS Using variables in templates
20862099.PP
2087−Variable names are sequences of alphanumerics, \f[C]\-\f[], and
2088−\f[C]_\f[], starting with a letter.
2089−A variable name surrounded by \f[C]$\f[] signs will be replaced by its
2100+Variable names are sequences of alphanumerics, \f[C]\-\f[R], and
2101+\f[C]_\f[R], starting with a letter.
2102+A variable name surrounded by \f[C]$\f[R] signs will be replaced by its
20902103value.
2091−For example, the string \f[C]$title$\f[] in
2104+For example, the string \f[C]$title$\f[R] in
20922105.IP
20932106.nf
20942107\f[C]
20952108<title>$title$</title>
2096−\f[]
2109+\f[R]
20972110.fi
20982111.PP
20992112will be replaced by the document title.
21002113.PP
2101−To write a literal \f[C]$\f[] in a template, use \f[C]$$\f[].
2114+To write a literal \f[C]$\f[R] in a template, use \f[C]$$\f[R].
21022115.PP
21032116Templates may contain conditionals.
21042117The syntax is as follows:
@@ -2110,11 +2123,11 @@ X
21102123$else$
21112124Y
21122125$endif$
2113−\f[]
2126+\f[R]
21142127.fi
21152128.PP
2116−This will include \f[C]X\f[] in the template if \f[C]variable\f[] has a
2117−truthy value; otherwise it will include \f[C]Y\f[].
2129+This will include \f[C]X\f[R] in the template if \f[C]variable\f[R] has
2130+a truthy value; otherwise it will include \f[C]Y\f[R].
21182131Here a truthy value is any of the following:
21192132.IP \[bu] 2
21202133a string that is not entirely white space,
@@ -2125,25 +2138,25 @@ any number (including zero),
21252138.IP \[bu] 2
21262139any object,
21272140.IP \[bu] 2
2128−the boolean \f[C]true\f[] (to specify the boolean \f[C]true\f[] value
2129−using YAML metadata or the \f[C]\-\-metadata\f[] flag, use
2130−\f[C]true\f[], \f[C]True\f[], or \f[C]TRUE\f[]; with the
2131−\f[C]\-\-variable\f[] flag, simply omit a value for the variable, e.g.
2132−\f[C]\-\-variable\ draft\f[]).
2141+the boolean \f[C]true\f[R] (to specify the boolean \f[C]true\f[R] value
2142+using YAML metadata or the \f[C]\-\-metadata\f[R] flag, use
2143+\f[C]true\f[R], \f[C]True\f[R], or \f[C]TRUE\f[R]; with the
2144+\f[C]\-\-variable\f[R] flag, simply omit a value for the variable, e.g.
2145+\f[C]\-\-variable\ draft\f[R]).
21332146.PP
2134−\f[C]X\f[] and \f[C]Y\f[] are placeholders for any valid template text,
2135−and may include interpolated variables or other conditionals.
2136−The \f[C]$else$\f[] section may be omitted.
2147+\f[C]X\f[R] and \f[C]Y\f[R] are placeholders for any valid template
2148+text, and may include interpolated variables or other conditionals.
2149+The \f[C]$else$\f[R] section may be omitted.
21372150.PP
2138−When variables can have multiple values (for example, \f[C]author\f[] in
2139−a multi\-author document), you can use the \f[C]$for$\f[] keyword:
2151+When variables can have multiple values (for example, \f[C]author\f[R]
2152+in a multi\-author document), you can use the \f[C]$for$\f[R] keyword:
21402153.IP
21412154.nf
21422155\f[C]
21432156$for(author)$
2144−<meta\ name="author"\ content="$author$"\ />
2157+<meta\ name=\[dq]author\[dq]\ content=\[dq]$author$\[dq]\ />
21452158$endfor$
2146−\f[]
2159+\f[R]
21472160.fi
21482161.PP
21492162You can optionally specify a separator to be used between consecutive
@@ -2152,7 +2165,7 @@ items:
21522165.nf
21532166\f[C]
21542167$for(author)$$author$$sep$,\ $endfor$
2155−\f[]
2168+\f[R]
21562169.fi
21572170.PP
21582171A dot can be used to select a field of a variable that takes an object
@@ -2162,7 +2175,7 @@ So, for example:
21622175.nf
21632176\f[C]
21642177$author.name$\ ($author.affiliation$)
2165−\f[]
2178+\f[R]
21662179.fi
21672180.PP
21682181If you use custom templates, you may need to revise them as pandoc
@@ -2172,67 +2185,69 @@ modifying your custom templates accordingly.
21722185An easy way to do this is to fork the pandoc\-templates repository and
21732186merge in changes after each pandoc release.
21742187.PP
2175−Templates may contain comments: anything on a line after \f[C]$\-\-\f[]
2188+Templates may contain comments: anything on a line after \f[C]$\-\-\f[R]
21762189will be treated as a comment and ignored.
21772190.SH EXTENSIONS
21782191.PP
21792192The behavior of some of the readers and writers can be adjusted by
21802193enabling or disabling various extensions.
21812194.PP
2182−An extension can be enabled by adding \f[C]+EXTENSION\f[] to the format
2183−name and disabled by adding \f[C]\-EXTENSION\f[].
2184−For example, \f[C]\-\-from\ markdown_strict+footnotes\f[] is strict
2195+An extension can be enabled by adding \f[C]+EXTENSION\f[R] to the format
2196+name and disabled by adding \f[C]\-EXTENSION\f[R].
2197+For example, \f[C]\-\-from\ markdown_strict+footnotes\f[R] is strict
21852198Markdown with footnotes enabled, while
2186−\f[C]\-\-from\ markdown\-footnotes\-pipe_tables\f[] is pandoc\[aq]s
2199+\f[C]\-\-from\ markdown\-footnotes\-pipe_tables\f[R] is pandoc\[aq]s
21872200Markdown without footnotes or pipe tables.
21882201.PP
21892202The markdown reader and writer make by far the most use of extensions.
21902203Extensions only used by them are therefore covered in the section
21912204Pandoc\[aq]s Markdown below (See Markdown variants for
2192−\f[C]commonmark\f[] and \f[C]gfm\f[].) In the following, extensions that
2193−also work for other formats are covered.
2205+\f[C]commonmark\f[R] and \f[C]gfm\f[R].) In the following, extensions
2206+that also work for other formats are covered.
21942207.SS Typography
2195−.SS Extension: \f[C]smart\f[]
2208+.SS Extension: \f[C]smart\f[R]
21962209.PP
2197−Interpret straight quotes as curly quotes, \f[C]\-\-\-\f[] as
2198−em\-dashes, \f[C]\-\-\f[] as en\-dashes, and \f[C]\&...\f[] as ellipses.
2210+Interpret straight quotes as curly quotes, \f[C]\-\-\-\f[R] as
2211+em\-dashes, \f[C]\-\-\f[R] as en\-dashes, and \f[C]\&...\f[R] as
2212+ellipses.
21992213Nonbreaking spaces are inserted after certain abbreviations, such as
2200−"Mr."
2214+\[dq]Mr.\[dq]
22012215.PP
22022216This extension can be enabled/disabled for the following formats:
22032217.TP
22042218.B input formats
2205−\f[C]markdown\f[], \f[C]commonmark\f[], \f[C]latex\f[],
2206−\f[C]mediawiki\f[], \f[C]org\f[], \f[C]rst\f[], \f[C]twiki\f[]
2219+\f[C]markdown\f[R], \f[C]commonmark\f[R], \f[C]latex\f[R],
2220+\f[C]mediawiki\f[R], \f[C]org\f[R], \f[C]rst\f[R], \f[C]twiki\f[R]
22072221.RS
22082222.RE
22092223.TP
22102224.B output formats
2211−\f[C]markdown\f[], \f[C]latex\f[], \f[C]context\f[], \f[C]rst\f[]
2225+\f[C]markdown\f[R], \f[C]latex\f[R], \f[C]context\f[R], \f[C]rst\f[R]
22122226.RS
22132227.RE
22142228.TP
22152229.B enabled by default in
2216−\f[C]markdown\f[], \f[C]latex\f[], \f[C]context\f[] (both input and
2230+\f[C]markdown\f[R], \f[C]latex\f[R], \f[C]context\f[R] (both input and
22172231output)
22182232.RS
22192233.RE
22202234.PP
2221−Note: If you are \f[I]writing\f[] Markdown, then the \f[C]smart\f[]
2235+Note: If you are \f[I]writing\f[R] Markdown, then the \f[C]smart\f[R]
22222236extension has the reverse effect: what would have been curly quotes
22232237comes out straight.
22242238.PP
2225−In LaTeX, \f[C]smart\f[] means to use the standard TeX ligatures for
2226−quotation marks (\f[C]``\f[] and \f[C]\[aq]\[aq]\f[] for double quotes,
2227−\f[C]`\f[] and \f[C]\[aq]\f[] for single quotes) and dashes
2228−(\f[C]\-\-\f[] for en\-dash and \f[C]\-\-\-\f[] for em\-dash).
2229−If \f[C]smart\f[] is disabled, then in reading LaTeX pandoc will parse
2239+In LaTeX, \f[C]smart\f[R] means to use the standard TeX ligatures for
2240+quotation marks (\f[C]\[ga]\[ga]\f[R] and \f[C]\[aq]\[aq]\f[R] for
2241+double quotes, \f[C]\[ga]\f[R] and \f[C]\[aq]\f[R] for single quotes)
2242+and dashes (\f[C]\-\-\f[R] for en\-dash and \f[C]\-\-\-\f[R] for
2243+em\-dash).
2244+If \f[C]smart\f[R] is disabled, then in reading LaTeX pandoc will parse
22302245these characters literally.
2231−In writing LaTeX, enabling \f[C]smart\f[] tells pandoc to use the
2232−ligatures when possible; if \f[C]smart\f[] is disabled pandoc will use
2246+In writing LaTeX, enabling \f[C]smart\f[R] tells pandoc to use the
2247+ligatures when possible; if \f[C]smart\f[R] is disabled pandoc will use
22332248unicode quotation mark and dash characters.
22342249.SS Headers and sections
2235−.SS Extension: \f[C]auto_identifiers\f[]
2250+.SS Extension: \f[C]auto_identifiers\f[R]
22362251.PP
22372252A header without an explicitly specified identifier will be
22382253automatically assigned a unique identifier based on the header text.
@@ -2240,18 +2255,18 @@ automatically assigned a unique identifier based on the header text.
22402255This extension can be enabled/disabled for the following formats:
22412256.TP
22422257.B input formats
2243−\f[C]markdown\f[], \f[C]latex\f[], \f[C]rst\f[], \f[C]mediawiki\f[],
2244−\f[C]textile\f[]
2258+\f[C]markdown\f[R], \f[C]latex\f[R], \f[C]rst\f[R], \f[C]mediawiki\f[R],
2259+\f[C]textile\f[R]
22452260.RS
22462261.RE
22472262.TP
22482263.B output formats
2249−\f[C]markdown\f[], \f[C]muse\f[]
2264+\f[C]markdown\f[R], \f[C]muse\f[R]
22502265.RS
22512266.RE
22522267.TP
22532268.B enabled by default in
2254−\f[C]markdown\f[], \f[C]muse\f[]
2269+\f[C]markdown\f[R], \f[C]muse\f[R]
22552270.RS
22562271.RE
22572272.PP
@@ -2270,7 +2285,7 @@ Convert all alphabetic characters to lowercase.
22702285Remove everything up to the first letter (identifiers may not begin with
22712286a number or punctuation mark).
22722287.IP \[bu] 2
2273−If nothing is left after this, use the identifier \f[C]section\f[].
2288+If nothing is left after this, use the identifier \f[C]section\f[R].
22742289.PP
22752290Thus, for example,
22762291.PP
@@ -2284,29 +2299,29 @@ Identifier
22842299T}
22852300_
22862301T{
2287−\f[C]Header\ identifiers\ in\ HTML\f[]
2302+\f[C]Header\ identifiers\ in\ HTML\f[R]
22882303T}@T{
2289−\f[C]header\-identifiers\-in\-html\f[]
2304+\f[C]header\-identifiers\-in\-html\f[R]
22902305T}
22912306T{
2292−\f[C]*Dogs*?\-\-in\ *my*\ house?\f[]
2307+\f[C]*Dogs*?\-\-in\ *my*\ house?\f[R]
22932308T}@T{
2294−\f[C]dogs\-\-in\-my\-house\f[]
2309+\f[C]dogs\-\-in\-my\-house\f[R]
22952310T}
22962311T{
2297−\f[C][HTML],\ [S5],\ or\ [RTF]?\f[]
2312+\f[C][HTML],\ [S5],\ or\ [RTF]?\f[R]
22982313T}@T{
2299−\f[C]html\-s5\-or\-rtf\f[]
2314+\f[C]html\-s5\-or\-rtf\f[R]
23002315T}
23012316T{
2302−\f[C]3.\ Applications\f[]
2317+\f[C]3.\ Applications\f[R]
23032318T}@T{
2304−\f[C]applications\f[]
2319+\f[C]applications\f[R]
23052320T}
23062321T{
2307−\f[C]33\f[]
2322+\f[C]33\f[R]
23082323T}@T{
2309−\f[C]section\f[]
2324+\f[C]section\f[R]
23102325T}
23112326.TE
23122327.PP
@@ -2314,11 +2329,11 @@ These rules should, in most cases, allow one to determine the identifier
23142329from the header text.
23152330The exception is when several headers have the same text; in this case,
23162331the first will get an identifier as described above; the second will get
2317−the same identifier with \f[C]\-1\f[] appended; the third with
2318−\f[C]\-2\f[]; and so on.
2332+the same identifier with \f[C]\-1\f[R] appended; the third with
2333+\f[C]\-2\f[R]; and so on.
23192334.PP
23202335These identifiers are used to provide link targets in the table of
2321−contents generated by the \f[C]\-\-toc|\-\-table\-of\-contents\f[]
2336+contents generated by the \f[C]\-\-toc|\-\-table\-of\-contents\f[R]
23222337option.
23232338They also make it easy to provide links from one section of a document
23242339to another.
@@ -2328,30 +2343,30 @@ A link to this section, for example, might look like this:
23282343\f[C]
23292344See\ the\ section\ on
23302345[header\ identifiers](#header\-identifiers\-in\-html\-latex\-and\-context).
2331−\f[]
2346+\f[R]
23322347.fi
23332348.PP
23342349Note, however, that this method of providing links to sections works
23352350only in HTML, LaTeX, and ConTeXt formats.
23362351.PP
2337−If the \f[C]\-\-section\-divs\f[] option is specified, then each section
2338−will be wrapped in a \f[C]section\f[] (or a \f[C]div\f[], if
2339−\f[C]html4\f[] was specified), and the identifier will be attached to
2340−the enclosing \f[C]<section>\f[] (or \f[C]<div>\f[]) tag rather than the
2341−header itself.
2352+If the \f[C]\-\-section\-divs\f[R] option is specified, then each
2353+section will be wrapped in a \f[C]section\f[R] (or a \f[C]div\f[R], if
2354+\f[C]html4\f[R] was specified), and the identifier will be attached to
2355+the enclosing \f[C]<section>\f[R] (or \f[C]<div>\f[R]) tag rather than
2356+the header itself.
23422357This allows entire sections to be manipulated using JavaScript or
23432358treated differently in CSS.
2344−.SS Extension: \f[C]ascii_identifiers\f[]
2359+.SS Extension: \f[C]ascii_identifiers\f[R]
23452360.PP
2346−Causes the identifiers produced by \f[C]auto_identifiers\f[] to be pure
2361+Causes the identifiers produced by \f[C]auto_identifiers\f[R] to be pure
23472362ASCII.
23482363Accents are stripped off of accented Latin letters, and non\-Latin
23492364letters are omitted.
23502365.SS Math Input
23512366.PP
2352−The extensions \f[C]tex_math_dollars\f[],
2353−\f[C]tex_math_single_backslash\f[], and
2354−\f[C]tex_math_double_backslash\f[] are described in the section about
2367+The extensions \f[C]tex_math_dollars\f[R],
2368+\f[C]tex_math_single_backslash\f[R], and
2369+\f[C]tex_math_double_backslash\f[R] are described in the section about
23552370Pandoc\[aq]s Markdown.
23562371.PP
23572372However, they can also be used with HTML input.
@@ -2362,77 +2377,77 @@ example.
23622377The following extensions (especially how they affect Markdown
23632378input/output) are also described in more detail in their respective
23642379sections of Pandoc\[aq]s Markdown.
2365−.SS Extension: \f[C]raw_html\f[]
2380+.SS Extension: \f[C]raw_html\f[R]
23662381.PP
23672382When converting from HTML, parse elements to raw HTML which are not
23682383representable in pandoc\[aq]s AST.
23692384By default, this is disabled for HTML input.
2370−.SS Extension: \f[C]raw_tex\f[]
2385+.SS Extension: \f[C]raw_tex\f[R]
23712386.PP
23722387Allows raw LaTeX, TeX, and ConTeXt to be included in a document.
23732388.PP
23742389This extension can be enabled/disabled for the following formats (in
2375−addition to \f[C]markdown\f[]):
2390+addition to \f[C]markdown\f[R]):
23762391.TP
23772392.B input formats
2378−\f[C]latex\f[], \f[C]org\f[], \f[C]textile\f[], \f[C]html\f[]
2379−(environments, \f[C]\\ref\f[], and \f[C]\\eqref\f[] only)
2393+\f[C]latex\f[R], \f[C]org\f[R], \f[C]textile\f[R], \f[C]html\f[R]
2394+(environments, \f[C]\[rs]ref\f[R], and \f[C]\[rs]eqref\f[R] only)
23802395.RS
23812396.RE
23822397.TP
23832398.B output formats
2384−\f[C]textile\f[], \f[C]commonmark\f[]
2399+\f[C]textile\f[R], \f[C]commonmark\f[R]
23852400.RS
23862401.RE
2387−.SS Extension: \f[C]native_divs\f[]
2402+.SS Extension: \f[C]native_divs\f[R]
23882403.PP
23892404This extension is enabled by default for HTML input.
2390−This means that \f[C]div\f[]s are parsed to pandoc native elements.
2405+This means that \f[C]div\f[R]s are parsed to pandoc native elements.
23912406(Alternatively, you can parse them to raw HTML using
2392−\f[C]\-f\ html\-native_divs+raw_html\f[].)
2407+\f[C]\-f\ html\-native_divs+raw_html\f[R].)
23932408.PP
23942409When converting HTML to Markdown, for example, you may want to drop all
2395−\f[C]div\f[]s and \f[C]span\f[]s:
2410+\f[C]div\f[R]s and \f[C]span\f[R]s:
23962411.IP
23972412.nf
23982413\f[C]
23992414pandoc\ \-f\ html\-native_divs\-native_spans\ \-t\ markdown
2400−\f[]
2415+\f[R]
24012416.fi
2402−.SS Extension: \f[C]native_spans\f[]
2417+.SS Extension: \f[C]native_spans\f[R]
24032418.PP
2404−Analogous to \f[C]native_divs\f[] above.
2419+Analogous to \f[C]native_divs\f[R] above.
24052420.SS Literate Haskell support
2406−.SS Extension: \f[C]literate_haskell\f[]
2421+.SS Extension: \f[C]literate_haskell\f[R]
24072422.PP
24082423Treat the document as literate Haskell source.
24092424.PP
24102425This extension can be enabled/disabled for the following formats:
24112426.TP
24122427.B input formats
2413−\f[C]markdown\f[], \f[C]rst\f[], \f[C]latex\f[]
2428+\f[C]markdown\f[R], \f[C]rst\f[R], \f[C]latex\f[R]
24142429.RS
24152430.RE
24162431.TP
24172432.B output formats
2418−\f[C]markdown\f[], \f[C]rst\f[], \f[C]latex\f[], \f[C]html\f[]
2433+\f[C]markdown\f[R], \f[C]rst\f[R], \f[C]latex\f[R], \f[C]html\f[R]
24192434.RS
24202435.RE
24212436.PP
2422−If you append \f[C]+lhs\f[] (or \f[C]+literate_haskell\f[]) to one of
2437+If you append \f[C]+lhs\f[R] (or \f[C]+literate_haskell\f[R]) to one of
24232438the formats above, pandoc will treat the document as literate Haskell
24242439source.
24252440This means that
24262441.IP \[bu] 2
2427−In Markdown input, "bird track" sections will be parsed as Haskell code
2428−rather than block quotations.
2429−Text between \f[C]\\begin{code}\f[] and \f[C]\\end{code}\f[] will also
2430−be treated as Haskell code.
2442+In Markdown input, \[dq]bird track\[dq] sections will be parsed as
2443+Haskell code rather than block quotations.
2444+Text between \f[C]\[rs]begin{code}\f[R] and \f[C]\[rs]end{code}\f[R]
2445+will also be treated as Haskell code.
24312446For ATX\-style headers the character \[aq]=\[aq] will be used instead of
24322447\[aq]#\[aq].
24332448.IP \[bu] 2
2434−In Markdown output, code blocks with classes \f[C]haskell\f[] and
2435−\f[C]literate\f[] will be rendered using bird tracks, and block
2449+In Markdown output, code blocks with classes \f[C]haskell\f[R] and
2450+\f[C]literate\f[R] will be rendered using bird tracks, and block
24362451quotations will be indented one space, so they will not be treated as
24372452Haskell code.
24382453In addition, headers will be rendered setext\-style (with underlines)
@@ -2440,27 +2455,27 @@ rather than ATX\-style (with \[aq]#\[aq] characters).
24402455(This is because ghc treats \[aq]#\[aq] characters in column 1 as
24412456introducing line numbers.)
24422457.IP \[bu] 2
2443−In restructured text input, "bird track" sections will be parsed as
2444−Haskell code.
2458+In restructured text input, \[dq]bird track\[dq] sections will be parsed
2459+as Haskell code.
24452460.IP \[bu] 2
2446−In restructured text output, code blocks with class \f[C]haskell\f[]
2461+In restructured text output, code blocks with class \f[C]haskell\f[R]
24472462will be rendered using bird tracks.
24482463.IP \[bu] 2
2449−In LaTeX input, text in \f[C]code\f[] environments will be parsed as
2464+In LaTeX input, text in \f[C]code\f[R] environments will be parsed as
24502465Haskell code.
24512466.IP \[bu] 2
2452−In LaTeX output, code blocks with class \f[C]haskell\f[] will be
2453−rendered inside \f[C]code\f[] environments.
2467+In LaTeX output, code blocks with class \f[C]haskell\f[R] will be
2468+rendered inside \f[C]code\f[R] environments.
24542469.IP \[bu] 2
2455−In HTML output, code blocks with class \f[C]haskell\f[] will be rendered
2456−with class \f[C]literatehaskell\f[] and bird tracks.
2470+In HTML output, code blocks with class \f[C]haskell\f[R] will be
2471+rendered with class \f[C]literatehaskell\f[R] and bird tracks.
24572472.PP
24582473Examples:
24592474.IP
24602475.nf
24612476\f[C]
24622477pandoc\ \-f\ markdown+lhs\ \-t\ html
2463−\f[]
2478+\f[R]
24642479.fi
24652480.PP
24662481reads literate Haskell source formatted with Markdown conventions and
@@ -2469,7 +2484,7 @@ writes ordinary HTML (without bird tracks).
24692484.nf
24702485\f[C]
24712486pandoc\ \-f\ markdown+lhs\ \-t\ html+lhs
2472−\f[]
2487+\f[R]
24732488.fi
24742489.PP
24752490writes HTML with the Haskell code in bird tracks, so it can be copied
@@ -2480,7 +2495,7 @@ literate code blocks (e.g.
24802495inside an itemized environment) will not be picked up by the Haskell
24812496compiler.
24822497.SS Other extensions
2483−.SS Extension: \f[C]empty_paragraphs\f[]
2498+.SS Extension: \f[C]empty_paragraphs\f[R]
24842499.PP
24852500Allows empty paragraphs.
24862501By default empty paragraphs are omitted.
@@ -2488,15 +2503,15 @@ By default empty paragraphs are omitted.
24882503This extension can be enabled/disabled for the following formats:
24892504.TP
24902505.B input formats
2491−\f[C]docx\f[], \f[C]html\f[]
2506+\f[C]docx\f[R], \f[C]html\f[R]
24922507.RS
24932508.RE
24942509.TP
24952510.B output formats
2496−\f[C]docx\f[], \f[C]odt\f[], \f[C]opendocument\f[], \f[C]html\f[]
2511+\f[C]docx\f[R], \f[C]odt\f[R], \f[C]opendocument\f[R], \f[C]html\f[R]
24972512.RS
24982513.RE
2499−.SS Extension: \f[C]styles\f[]
2514+.SS Extension: \f[C]styles\f[R]
25002515.PP
25012516Read all docx styles as divs (for paragraph styles) and spans (for
25022517character styles) regardless of whether pandoc understands the meaning
@@ -2505,20 +2520,20 @@ This can be used with docx custom styles.
25052520Disabled by default.
25062521.TP
25072522.B input formats
2508−\f[C]docx\f[]
2523+\f[C]docx\f[R]
25092524.RS
25102525.RE
2511−.SS Extension: \f[C]amuse\f[]
2526+.SS Extension: \f[C]amuse\f[R]
25122527.PP
2513−In the \f[C]muse\f[] input format, this enables Text::Amuse extensions
2528+In the \f[C]muse\f[R] input format, this enables Text::Amuse extensions
25142529to Emacs Muse markup.
2515−.SS Extension: \f[C]citations\f[]
2530+.SS Extension: \f[C]citations\f[R]
25162531.PP
25172532Some aspects of Pandoc\[aq]s Markdown citation syntax are also accepted
2518−in \f[C]org\f[] input.
2519−.SS Extension: \f[C]ntb\f[]
2533+in \f[C]org\f[R] input.
2534+.SS Extension: \f[C]ntb\f[R]
25202535.PP
2521−In the \f[C]context\f[] output format this enables the use of Natural
2536+In the \f[C]context\f[R] output format this enables the use of Natural
25222537Tables (TABLE) instead of the default Extreme Tables (xtables).
25232538Natural tables allow more fine\-grained global customization but come at
25242539a performance penalty compared to extreme tables.
@@ -2529,7 +2544,7 @@ Gruber\[aq]s Markdown syntax.
25292544This document explains the syntax, noting differences from standard
25302545Markdown.
25312546Except where noted, these differences can be suppressed by using the
2532−\f[C]markdown_strict\f[] format instead of \f[C]markdown\f[].
2547+\f[C]markdown_strict\f[R] format instead of \f[C]markdown\f[R].
25332548Extensions can be enabled or disabled to specify the behavior more
25342549granularly.
25352550They are described in the following.
@@ -2565,7 +2580,7 @@ Newlines are treated as spaces, so you can reflow your paragraphs as you
25652580like.
25662581If you need a hard line break, put two or more spaces at the end of a
25672582line.
2568−.SS Extension: \f[C]escaped_line_breaks\f[]
2583+.SS Extension: \f[C]escaped_line_breaks\f[R]
25692584.PP
25702585A backslash followed by a newline is also a hard line break.
25712586Note: in multiline and grid table cells, this is the only way to create
@@ -2575,9 +2590,9 @@ a hard line break, since trailing spaces in the cells are ignored.
25752590There are two kinds of headers: Setext and ATX.
25762591.SS Setext\-style headers
25772592.PP
2578−A setext\-style header is a line of text "underlined" with a row of
2579−\f[C]=\f[] signs (for a level one header) or \f[C]\-\f[] signs (for a
2580−level two header):
2593+A setext\-style header is a line of text \[dq]underlined\[dq] with a row
2594+of \f[C]=\f[R] signs (for a level one header) or \f[C]\-\f[R] signs (for
2595+a level two header):
25812596.IP
25822597.nf
25832598\f[C]
@@ -2586,16 +2601,16 @@ A\ level\-one\ header
25862601
25872602A\ level\-two\ header
25882603\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
2589−\f[]
2604+\f[R]
25902605.fi
25912606.PP
25922607The header text can contain inline formatting, such as emphasis (see
25932608Inline formatting, below).
25942609.SS ATX\-style headers
25952610.PP
2596−An ATX\-style header consists of one to six \f[C]#\f[] signs and a line
2597−of text, optionally followed by any number of \f[C]#\f[] signs.
2598−The number of \f[C]#\f[] signs at the beginning of the line is the
2611+An ATX\-style header consists of one to six \f[C]#\f[R] signs and a line
2612+of text, optionally followed by any number of \f[C]#\f[R] signs.
2613+The number of \f[C]#\f[R] signs at the beginning of the line is the
25992614header level:
26002615.IP
26012616.nf
@@ -2603,7 +2618,7 @@ header level:
26032618##\ A\ level\-two\ header
26042619
26052620###\ A\ level\-three\ header\ ###
2606−\f[]
2621+\f[R]
26072622.fi
26082623.PP
26092624As with setext\-style headers, the header text can contain formatting:
@@ -2611,15 +2626,15 @@ As with setext\-style headers, the header text can contain formatting:
26112626.nf
26122627\f[C]
26132628#\ A\ level\-one\ header\ with\ a\ [link](/url)\ and\ *emphasis*
2614−\f[]
2629+\f[R]
26152630.fi
2616−.SS Extension: \f[C]blank_before_header\f[]
2631+.SS Extension: \f[C]blank_before_header\f[R]
26172632.PP
26182633Standard Markdown syntax does not require a blank line before a header.
26192634Pandoc does require this (except, of course, at the beginning of the
26202635document).
26212636The reason for the requirement is that it is all too easy for a
2622−\f[C]#\f[] to end up at the beginning of a line by accident (perhaps
2637+\f[C]#\f[R] to end up at the beginning of a line by accident (perhaps
26232638through line wrapping).
26242639Consider, for example:
26252640.IP
@@ -2627,18 +2642,18 @@ Consider, for example:
26272642\f[C]
26282643I\ like\ several\ of\ their\ flavors\ of\ ice\ cream:
26292644#22,\ for\ example,\ and\ #5.
2630−\f[]
2645+\f[R]
26312646.fi
2632−.SS Extension: \f[C]space_in_atx_header\f[]
2647+.SS Extension: \f[C]space_in_atx_header\f[R]
26332648.PP
26342649Many Markdown implementations do not require a space between the opening
2635−\f[C]#\f[]s of an ATX header and the header text, so that
2636−\f[C]#5\ bolt\f[] and \f[C]#hashtag\f[] count as headers.
2650+\f[C]#\f[R]s of an ATX header and the header text, so that
2651+\f[C]#5\ bolt\f[R] and \f[C]#hashtag\f[R] count as headers.
26372652With this extension, pandoc does require the space.
26382653.SS Header identifiers
26392654.PP
2640−See also the \f[C]auto_identifiers\f[] extension above.
2641−.SS Extension: \f[C]header_attributes\f[]
2655+See also the \f[C]auto_identifiers\f[R] extension above.
2656+.SS Extension: \f[C]header_attributes\f[R]
26422657.PP
26432658Headers can be assigned attributes using this syntax at the end of the
26442659line containing the header text:
@@ -2646,11 +2661,11 @@ line containing the header text:
26462661.nf
26472662\f[C]
26482663{#identifier\ .class\ .class\ key=value\ key=value}
2649−\f[]
2664+\f[R]
26502665.fi
26512666.PP
26522667Thus, for example, the following headers will all be assigned the
2653−identifier \f[C]foo\f[]:
2668+identifier \f[C]foo\f[R]:
26542669.IP
26552670.nf
26562671\f[C]
@@ -2660,7 +2675,7 @@ identifier \f[C]foo\f[]:
26602675
26612676My\ other\ header\ \ \ {#foo}
26622677\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
2663−\f[]
2678+\f[R]
26642679.fi
26652680.PP
26662681(This syntax is compatible with PHP Markdown Extra.)
@@ -2673,16 +2688,16 @@ HTML\-based formats such as EPUB and slidy.
26732688Identifiers are used for labels and link anchors in the LaTeX, ConTeXt,
26742689Textile, and AsciiDoc writers.
26752690.PP
2676−Headers with the class \f[C]unnumbered\f[] will not be numbered, even if
2677−\f[C]\-\-number\-sections\f[] is specified.
2678−A single hyphen (\f[C]\-\f[]) in an attribute context is equivalent to
2679−\f[C]\&.unnumbered\f[], and preferable in non\-English documents.
2691+Headers with the class \f[C]unnumbered\f[R] will not be numbered, even
2692+if \f[C]\-\-number\-sections\f[R] is specified.
2693+A single hyphen (\f[C]\-\f[R]) in an attribute context is equivalent to
2694+\f[C]\&.unnumbered\f[R], and preferable in non\-English documents.
26802695So,
26812696.IP
26822697.nf
26832698\f[C]
26842699#\ My\ header\ {\-}
2685−\f[]
2700+\f[R]
26862701.fi
26872702.PP
26882703is just the same as
@@ -2690,9 +2705,9 @@ is just the same as
26902705.nf
26912706\f[C]
26922707#\ My\ header\ {.unnumbered}
2693−\f[]
2708+\f[R]
26942709.fi
2695−.SS Extension: \f[C]implicit_header_references\f[]
2710+.SS Extension: \f[C]implicit_header_references\f[R]
26962711.PP
26972712Pandoc behaves as if reference links have been defined for each header.
26982713So, to link to a header
@@ -2700,7 +2715,7 @@ So, to link to a header
27002715.nf
27012716\f[C]
27022717#\ Header\ identifiers\ in\ HTML
2703−\f[]
2718+\f[R]
27042719.fi
27052720.PP
27062721you can simply write
@@ -2708,7 +2723,7 @@ you can simply write
27082723.nf
27092724\f[C]
27102725[Header\ identifiers\ in\ HTML]
2711−\f[]
2726+\f[R]
27122727.fi
27132728.PP
27142729or
@@ -2716,7 +2731,7 @@ or
27162731.nf
27172732\f[C]
27182733[Header\ identifiers\ in\ HTML][]
2719−\f[]
2734+\f[R]
27202735.fi
27212736.PP
27222737or
@@ -2725,7 +2740,7 @@ or
27252740\f[C]
27262741[the\ section\ on\ header\ identifiers][header\ identifiers\ in
27272742HTML]
2728−\f[]
2743+\f[R]
27292744.fi
27302745.PP
27312746instead of giving the identifier explicitly:
@@ -2733,7 +2748,7 @@ instead of giving the identifier explicitly:
27332748.nf
27342749\f[C]
27352750[Header\ identifiers\ in\ HTML](#header\-identifiers\-in\-html)
2736−\f[]
2751+\f[R]
27372752.fi
27382753.PP
27392754If there are multiple headers with identical text, the corresponding
@@ -2744,8 +2759,8 @@ Like regular reference links, these references are case\-insensitive.
27442759.PP
27452760Explicit link reference definitions always take priority over implicit
27462761header references.
2747−So, in the following example, the link will point to \f[C]bar\f[], not
2748−to \f[C]#foo\f[]:
2762+So, in the following example, the link will point to \f[C]bar\f[R], not
2763+to \f[C]#foo\f[R]:
27492764.IP
27502765.nf
27512766\f[C]
@@ -2754,15 +2769,15 @@ to \f[C]#foo\f[]:
27542769[foo]:\ bar
27552770
27562771See\ [foo]
2757−\f[]
2772+\f[R]
27582773.fi
27592774.SS Block quotations
27602775.PP
27612776Markdown uses email conventions for quoting blocks of text.
27622777A block quotation is one or more paragraphs or other block elements
2763−(such as lists or headers), with each line preceded by a \f[C]>\f[]
2778+(such as lists or headers), with each line preceded by a \f[C]>\f[R]
27642779character and an optional space.
2765−(The \f[C]>\f[] need not start at the left margin, but it should not be
2780+(The \f[C]>\f[R] need not start at the left margin, but it should not be
27662781indented more than three spaces.)
27672782.IP
27682783.nf
@@ -2772,11 +2787,11 @@ indented more than three spaces.)
27722787>
27732788>\ 1.\ This\ is\ a\ list\ inside\ a\ block\ quote.
27742789>\ 2.\ Second\ item.
2775−\f[]
2790+\f[R]
27762791.fi
27772792.PP
2778−A "lazy" form, which requires the \f[C]>\f[] character only on the first
2779−line of each block, is also allowed:
2793+A \[dq]lazy\[dq] form, which requires the \f[C]>\f[R] character only on
2794+the first line of each block, is also allowed:
27802795.IP
27812796.nf
27822797\f[C]
@@ -2785,7 +2800,7 @@ paragraph\ has\ two\ lines.
27852800
27862801>\ 1.\ This\ is\ a\ list\ inside\ a\ block\ quote.
278728022.\ Second\ item.
2788−\f[]
2803+\f[R]
27892804.fi
27902805.PP
27912806Among the block elements that can be contained in a block quote are
@@ -2797,37 +2812,37 @@ That is, block quotes can be nested:
27972812>\ This\ is\ a\ block\ quote.
27982813>
27992814>\ >\ A\ block\ quote\ within\ a\ block\ quote.
2800−\f[]
2815+\f[R]
28012816.fi
28022817.PP
2803−If the \f[C]>\f[] character is followed by an optional space, that space
2804−will be considered part of the block quote marker and not part of the
2805−indentation of the contents.
2818+If the \f[C]>\f[R] character is followed by an optional space, that
2819+space will be considered part of the block quote marker and not part of
2820+the indentation of the contents.
28062821Thus, to put an indented code block in a block quote, you need five
2807−spaces after the \f[C]>\f[]:
2822+spaces after the \f[C]>\f[R]:
28082823.IP
28092824.nf
28102825\f[C]
28112826>\ \ \ \ \ code
2812−\f[]
2827+\f[R]
28132828.fi
2814−.SS Extension: \f[C]blank_before_blockquote\f[]
2829+.SS Extension: \f[C]blank_before_blockquote\f[R]
28152830.PP
28162831Standard Markdown syntax does not require a blank line before a block
28172832quote.
28182833Pandoc does require this (except, of course, at the beginning of the
28192834document).
28202835The reason for the requirement is that it is all too easy for a
2821−\f[C]>\f[] to end up at the beginning of a line by accident (perhaps
2836+\f[C]>\f[R] to end up at the beginning of a line by accident (perhaps
28222837through line wrapping).
2823−So, unless the \f[C]markdown_strict\f[] format is used, the following
2838+So, unless the \f[C]markdown_strict\f[R] format is used, the following
28242839does not produce a nested block quote in pandoc:
28252840.IP
28262841.nf
28272842\f[C]
28282843>\ This\ is\ a\ block\ quote.
28292844>>\ Nested.
2830−\f[]
2845+\f[R]
28312846.fi
28322847.SS Verbatim (code) blocks
28332848.SS Indented code blocks
@@ -2842,7 +2857,7 @@ For example,
28422857\ \ \ \ if\ (a\ >\ 3)\ {
28432858\ \ \ \ \ \ moveShip(5\ *\ gravity,\ DOWN);
28442859\ \ \ \ }
2845−\f[]
2860+\f[R]
28462861.fi
28472862.PP
28482863The initial (four space or one tab) indentation is not considered part
@@ -2850,23 +2865,23 @@ of the verbatim text, and is removed in the output.
28502865.PP
28512866Note: blank lines in the verbatim text need not begin with four spaces.
28522867.SS Fenced code blocks
2853−.SS Extension: \f[C]fenced_code_blocks\f[]
2868+.SS Extension: \f[C]fenced_code_blocks\f[R]
28542869.PP
28552870In addition to standard indented code blocks, pandoc supports
2856−\f[I]fenced\f[] code blocks.
2857−These begin with a row of three or more tildes (\f[C]~\f[]) and end with
2858−a row of tildes that must be at least as long as the starting row.
2871+\f[I]fenced\f[R] code blocks.
2872+These begin with a row of three or more tildes (\f[C]\[ti]\f[R]) and end
2873+with a row of tildes that must be at least as long as the starting row.
28592874Everything between these lines is treated as code.
28602875No indentation is necessary:
28612876.IP
28622877.nf
28632878\f[C]
2864−~~~~~~~
2879+\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
28652880if\ (a\ >\ 3)\ {
28662881\ \ moveShip(5\ *\ gravity,\ DOWN);
28672882}
2868−~~~~~~~
2869−\f[]
2883+\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
2884+\f[R]
28702885.fi
28712886.PP
28722887Like regular code blocks, fenced code blocks must be separated from
@@ -2877,58 +2892,58 @@ longer row of tildes or backticks at the start and end:
28772892.IP
28782893.nf
28792894\f[C]
2880−~~~~~~~~~~~~~~~~
2881−~~~~~~~~~~
2895+\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
2896+\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
28822897code\ including\ tildes
2883−~~~~~~~~~~
2884−~~~~~~~~~~~~~~~~
2885−\f[]
2898+\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
2899+\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
2900+\f[R]
28862901.fi
2887−.SS Extension: \f[C]backtick_code_blocks\f[]
2902+.SS Extension: \f[C]backtick_code_blocks\f[R]
28882903.PP
2889−Same as \f[C]fenced_code_blocks\f[], but uses backticks (\f[C]`\f[])
2890−instead of tildes (\f[C]~\f[]).
2891−.SS Extension: \f[C]fenced_code_attributes\f[]
2904+Same as \f[C]fenced_code_blocks\f[R], but uses backticks
2905+(\f[C]\[ga]\f[R]) instead of tildes (\f[C]\[ti]\f[R]).
2906+.SS Extension: \f[C]fenced_code_attributes\f[R]
28922907.PP
28932908Optionally, you may attach attributes to fenced or backtick code block
28942909using this syntax:
28952910.IP
28962911.nf
28972912\f[C]
2898−~~~~\ {#mycode\ .haskell\ .numberLines\ startFrom="100"}
2913+\[ti]\[ti]\[ti]\[ti]\ {#mycode\ .haskell\ .numberLines\ startFrom=\[dq]100\[dq]}
28992914qsort\ []\ \ \ \ \ =\ []
29002915qsort\ (x:xs)\ =\ qsort\ (filter\ (<\ x)\ xs)\ ++\ [x]\ ++
29012916\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ qsort\ (filter\ (>=\ x)\ xs)
2902−~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
2903−\f[]
2917+\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
2918+\f[R]
29042919.fi
29052920.PP
2906−Here \f[C]mycode\f[] is an identifier, \f[C]haskell\f[] and
2907−\f[C]numberLines\f[] are classes, and \f[C]startFrom\f[] is an attribute
2908−with value \f[C]100\f[].
2921+Here \f[C]mycode\f[R] is an identifier, \f[C]haskell\f[R] and
2922+\f[C]numberLines\f[R] are classes, and \f[C]startFrom\f[R] is an
2923+attribute with value \f[C]100\f[R].
29092924Some output formats can use this information to do syntax highlighting.
29102925Currently, the only output formats that uses this information are HTML,
29112926LaTeX, Docx, Ms, and PowerPoint.
29122927If highlighting is supported for your output format and language, then
29132928the code block above will appear highlighted, with numbered lines.
29142929(To see which languages are supported, type
2915−\f[C]pandoc\ \-\-list\-highlight\-languages\f[].) Otherwise, the code
2930+\f[C]pandoc\ \-\-list\-highlight\-languages\f[R].) Otherwise, the code
29162931block above will appear as follows:
29172932.IP
29182933.nf
29192934\f[C]
2920−<pre\ id="mycode"\ class="haskell\ numberLines"\ startFrom="100">
2935+<pre\ id=\[dq]mycode\[dq]\ class=\[dq]haskell\ numberLines\[dq]\ startFrom=\[dq]100\[dq]>
29212936\ \ <code>
29222937\ \ ...
29232938\ \ </code>
29242939</pre>
2925−\f[]
2940+\f[R]
29262941.fi
29272942.PP
2928−The \f[C]numberLines\f[] (or \f[C]number\-lines\f[]) class will cause
2929−the lines of the code block to be numbered, starting with \f[C]1\f[] or
2930−the value of the \f[C]startFrom\f[] attribute.
2931−The \f[C]lineAnchors\f[] (or \f[C]line\-anchors\f[]) class will cause
2943+The \f[C]numberLines\f[R] (or \f[C]number\-lines\f[R]) class will cause
2944+the lines of the code block to be numbered, starting with \f[C]1\f[R] or
2945+the value of the \f[C]startFrom\f[R] attribute.
2946+The \f[C]lineAnchors\f[R] (or \f[C]line\-anchors\f[R]) class will cause
29322947the lines to be clickable anchors in HTML output.
29332948.PP
29342949A shortcut form can also be used for specifying the language of the code
@@ -2936,34 +2951,34 @@ block:
29362951.IP
29372952.nf
29382953\f[C]
2939−```haskell
2954+\[ga]\[ga]\[ga]haskell
29402955qsort\ []\ =\ []
2941−```
2942−\f[]
2956+\[ga]\[ga]\[ga]
2957+\f[R]
29432958.fi
29442959.PP
29452960This is equivalent to:
29462961.IP
29472962.nf
29482963\f[C]
2949−```\ {.haskell}
2964+\[ga]\[ga]\[ga]\ {.haskell}
29502965qsort\ []\ =\ []
2951−```
2952−\f[]
2966+\[ga]\[ga]\[ga]
2967+\f[R]
29532968.fi
29542969.PP
2955−If the \f[C]fenced_code_attributes\f[] extension is disabled, but input
2970+If the \f[C]fenced_code_attributes\f[R] extension is disabled, but input
29562971contains class attribute(s) for the code block, the first class
29572972attribute will be printed after the opening fence as a bare word.
29582973.PP
2959−To prevent all highlighting, use the \f[C]\-\-no\-highlight\f[] flag.
2960−To set the highlighting style, use \f[C]\-\-highlight\-style\f[].
2974+To prevent all highlighting, use the \f[C]\-\-no\-highlight\f[R] flag.
2975+To set the highlighting style, use \f[C]\-\-highlight\-style\f[R].
29612976For more information on highlighting, see Syntax highlighting, below.
29622977.SS Line blocks
2963−.SS Extension: \f[C]line_blocks\f[]
2978+.SS Extension: \f[C]line_blocks\f[R]
29642979.PP
29652980A line block is a sequence of lines beginning with a vertical bar
2966−(\f[C]|\f[]) followed by a space.
2981+(\f[C]|\f[R]) followed by a space.
29672982The division into lines will be preserved in the output, as will any
29682983leading spaces; otherwise, the lines will be formatted as Markdown.
29692984This is useful for verse and addresses:
@@ -2978,7 +2993,7 @@ This is useful for verse and addresses:
29782993
29792994|\ 200\ Main\ St.
29802995|\ Berkeley,\ CA\ 94718
2981−\f[]
2996+\f[R]
29822997.fi
29832998.PP
29842999The lines can be hard\-wrapped if needed, but the continuation line must
@@ -2990,7 +3005,7 @@ begin with a space.
29903005\ \ Constable,\ Jr.
29913006|\ 200\ Main\ St.
29923007|\ Berkeley,\ CA\ 94718
2993−\f[]
3008+\f[R]
29943009.fi
29953010.PP
29963011This syntax is borrowed from reStructuredText.
@@ -2998,8 +3013,8 @@ This syntax is borrowed from reStructuredText.
29983013.SS Bullet lists
29993014.PP
30003015A bullet list is a list of bulleted list items.
3001−A bulleted list item begins with a bullet (\f[C]*\f[], \f[C]+\f[], or
3002−\f[C]\-\f[]).
3016+A bulleted list item begins with a bullet (\f[C]*\f[R], \f[C]+\f[R], or
3017+\f[C]\-\f[R]).
30033018Here is a simple example:
30043019.IP
30053020.nf
@@ -3007,11 +3022,11 @@ Here is a simple example:
30073022*\ one
30083023*\ two
30093024*\ three
3010−\f[]
3025+\f[R]
30113026.fi
30123027.PP
3013−This will produce a "compact" list.
3014−If you want a "loose" list, in which each item is formatted as a
3028+This will produce a \[dq]compact\[dq] list.
3029+If you want a \[dq]loose\[dq] list, in which each item is formatted as a
30153030paragraph, put spaces between the items:
30163031.IP
30173032.nf
@@ -3021,7 +3036,7 @@ paragraph, put spaces between the items:
30213036*\ two
30223037
30233038*\ three
3024−\f[]
3039+\f[R]
30253040.fi
30263041.PP
30273042The bullets need not be flush with the left margin; they may be indented
@@ -3036,17 +3051,17 @@ List items look best if subsequent lines are flush with the first line
30363051*\ here\ is\ my\ first
30373052\ \ list\ item.
30383053*\ and\ my\ second.
3039−\f[]
3054+\f[R]
30403055.fi
30413056.PP
3042−But Markdown also allows a "lazy" format:
3057+But Markdown also allows a \[dq]lazy\[dq] format:
30433058.IP
30443059.nf
30453060\f[C]
30463061*\ here\ is\ my\ first
30473062list\ item.
30483063*\ and\ my\ second.
3049−\f[]
3064+\f[R]
30503065.fi
30513066.SS Block content in list items
30523067.PP
@@ -3066,7 +3081,7 @@ marker.
30663081\ \ \ \ eight\ spaces:
30673082
30683083\ \ \ \ \ \ \ \ {\ code\ }
3069−\f[]
3084+\f[R]
30703085.fi
30713086.PP
30723087Exception: if the list marker is followed by an indented code block,
@@ -3079,7 +3094,7 @@ marker:
30793094*\ \ \ \ \ code
30803095
30813096\ \ continuation\ paragraph
3082−\f[]
3097+\f[R]
30833098.fi
30843099.PP
30853100List items may include other lists.
@@ -3098,11 +3113,11 @@ character after the list marker of the containing list item.
30983113*\ vegetables
30993114\ \ +\ broccoli
31003115\ \ +\ chard
3101−\f[]
3116+\f[R]
31023117.fi
31033118.PP
3104−As noted above, Markdown allows you to write list items "lazily,"
3105−instead of indenting continuation lines.
3119+As noted above, Markdown allows you to write list items
3120+\[dq]lazily,\[dq] instead of indenting continuation lines.
31063121However, if there are multiple paragraphs or other blocks in a list
31073122item, the first line of each must be indented.
31083123.IP
@@ -3116,7 +3131,7 @@ bad\ but\ is\ legal.
31163131
31173132\ \ \ \ Second\ paragraph\ of\ second
31183133list\ item.
3119−\f[]
3134+\f[R]
31203135.fi
31213136.SS Ordered lists
31223137.PP
@@ -3133,7 +3148,7 @@ this list:
313331481.\ \ one
313431492.\ \ two
313531503.\ \ three
3136−\f[]
3151+\f[R]
31373152.fi
31383153.PP
31393154and this one:
@@ -3143,9 +3158,9 @@ and this one:
314331585.\ \ one
314431597.\ \ two
314531601.\ \ three
3146−\f[]
3161+\f[R]
31473162.fi
3148−.SS Extension: \f[C]fancy_lists\f[]
3163+.SS Extension: \f[C]fancy_lists\f[R]
31493164.PP
31503165Unlike standard Markdown, pandoc allows ordered list items to be marked
31513166with uppercase and lowercase letters and roman numerals, in addition to
@@ -3156,16 +3171,16 @@ They must be separated from the text that follows by at least one space,
31563171and, if the list marker is a capital letter with a period, by at least
31573172two spaces.
31583173.PP
3159−The \f[C]fancy_lists\f[] extension also allows \[aq]\f[C]#\f[]\[aq] to
3174+The \f[C]fancy_lists\f[R] extension also allows \[aq]\f[C]#\f[R]\[aq] to
31603175be used as an ordered list marker in place of a numeral:
31613176.IP
31623177.nf
31633178\f[C]
31643179#.\ one
31653180#.\ two
3166−\f[]
3181+\f[R]
31673182.fi
3168−.SS Extension: \f[C]startnum\f[]
3183+.SS Extension: \f[C]startnum\f[R]
31693184.PP
31703185Pandoc also pays attention to the type of list marker used, and to the
31713186starting number, and both of these are preserved where possible in the
@@ -3182,7 +3197,7 @@ numerals:
31823197\ \ \ \ \ \ \ i.\ subone
31833198\ \ \ \ \ \ ii.\ subtwo
31843199\ \ \ \ \ iii.\ subthree
3185−\f[]
3200+\f[R]
31863201.fi
31873202.PP
31883203Pandoc will start a new list each time a different type of list marker
@@ -3195,20 +3210,20 @@ So, the following will create three lists:
31953210(5)\ Three
319632111.\ \ Four
31973212*\ \ \ Five
3198−\f[]
3213+\f[R]
31993214.fi
32003215.PP
3201−If default list markers are desired, use \f[C]#.\f[]:
3216+If default list markers are desired, use \f[C]#.\f[R]:
32023217.IP
32033218.nf
32043219\f[C]
32053220#.\ \ one
32063221#.\ \ two
32073222#.\ \ three
3208−\f[]
3223+\f[R]
32093224.fi
32103225.SS Definition lists
3211−.SS Extension: \f[C]definition_lists\f[]
3226+.SS Extension: \f[C]definition_lists\f[R]
32123227.PP
32133228Pandoc supports definition lists, using the syntax of PHP Markdown Extra
32143229with some extensions.
@@ -3226,7 +3241,7 @@ Term\ 2\ with\ *inline\ markup*
32263241\ \ \ \ \ \ \ \ {\ some\ code,\ part\ of\ Definition\ 2\ }
32273242
32283243\ \ \ \ Third\ paragraph\ of\ definition\ 2.
3229−\f[]
3244+\f[R]
32303245.fi
32313246.PP
32323247Each term must fit on one line, which may optionally be followed by a
@@ -3239,8 +3254,9 @@ one or more block elements (paragraph, code block, list, etc.), each
32393254indented four spaces or one tab stop.
32403255The body of the definition (including the first line, aside from the
32413256colon or tilde) should be indented four spaces.
3242−However, as with other Markdown lists, you can "lazily" omit indentation
3243−except at the beginning of a paragraph or other block element:
3257+However, as with other Markdown lists, you can \[dq]lazily\[dq] omit
3258+indentation except at the beginning of a paragraph or other block
3259+element:
32443260.IP
32453261.nf
32463262\f[C]
@@ -3250,7 +3266,7 @@ Term\ 1
32503266with\ lazy\ continuation.
32513267
32523268\ \ \ \ Second\ paragraph\ of\ the\ definition.
3253−\f[]
3269+\f[R]
32543270.fi
32553271.PP
32563272If you leave space before the definition (as in the example above), the
@@ -3263,38 +3279,38 @@ definition:
32633279.nf
32643280\f[C]
32653281Term\ 1
3266−\ \ ~\ Definition\ 1
3282+\ \ \[ti]\ Definition\ 1
32673283
32683284Term\ 2
3269−\ \ ~\ Definition\ 2a
3270−\ \ ~\ Definition\ 2b
3271−\f[]
3285+\ \ \[ti]\ Definition\ 2a
3286+\ \ \[ti]\ Definition\ 2b
3287+\f[R]
32723288.fi
32733289.PP
32743290Note that space between items in a definition list is required.
3275−(A variant that loosens this requirement, but disallows "lazy" hard
3276−wrapping, can be activated with \f[C]compact_definition_lists\f[]: see
3277−Non\-pandoc extensions, below.)
3291+(A variant that loosens this requirement, but disallows \[dq]lazy\[dq]
3292+hard wrapping, can be activated with \f[C]compact_definition_lists\f[R]:
3293+see Non\-pandoc extensions, below.)
32783294.SS Numbered example lists
3279−.SS Extension: \f[C]example_lists\f[]
3295+.SS Extension: \f[C]example_lists\f[R]
32803296.PP
3281−The special list marker \f[C]\@\f[] can be used for sequentially
3297+The special list marker \f[C]\[at]\f[R] can be used for sequentially
32823298numbered examples.
3283−The first list item with a \f[C]\@\f[] marker will be numbered
3299+The first list item with a \f[C]\[at]\f[R] marker will be numbered
32843300\[aq]1\[aq], the next \[aq]2\[aq], and so on, throughout the document.
32853301The numbered examples need not occur in a single list; each new list
3286−using \f[C]\@\f[] will take up where the last stopped.
3302+using \f[C]\[at]\f[R] will take up where the last stopped.
32873303So, for example:
32883304.IP
32893305.nf
32903306\f[C]
3291−(\@)\ \ My\ first\ example\ will\ be\ numbered\ (1).
3292−(\@)\ \ My\ second\ example\ will\ be\ numbered\ (2).
3307+(\[at])\ \ My\ first\ example\ will\ be\ numbered\ (1).
3308+(\[at])\ \ My\ second\ example\ will\ be\ numbered\ (2).
32933309
32943310Explanation\ of\ examples.
32953311
3296−(\@)\ \ My\ third\ example\ will\ be\ numbered\ (3).
3297−\f[]
3312+(\[at])\ \ My\ third\ example\ will\ be\ numbered\ (3).
3313+\f[R]
32983314.fi
32993315.PP
33003316Numbered examples can be labeled and referred to elsewhere in the
@@ -3302,10 +3318,10 @@ document:
33023318.IP
33033319.nf
33043320\f[C]
3305−(\@good)\ \ This\ is\ a\ good\ example.
3321+(\[at]good)\ \ This\ is\ a\ good\ example.
33063322
3307−As\ (\@good)\ illustrates,\ ...
3308−\f[]
3323+As\ (\[at]good)\ illustrates,\ ...
3324+\f[R]
33093325.fi
33103326.PP
33113327The label can be any string of alphanumeric characters, underscores, or
@@ -3313,14 +3329,14 @@ hyphens.
33133329.PP
33143330Note: continuation paragraphs in example lists must always be indented
33153331four spaces, regardless of the length of the list marker.
3316−That is, example lists always behave as if the \f[C]four_space_rule\f[]
3332+That is, example lists always behave as if the \f[C]four_space_rule\f[R]
33173333extension is set.
33183334This is because example labels tend to be long, and indenting content to
33193335the first non\-space character after the label would be awkward.
33203336.SS Compact and loose lists
33213337.PP
3322−Pandoc behaves differently from \f[C]Markdown.pl\f[] on some "edge
3323−cases" involving lists.
3338+Pandoc behaves differently from \f[C]Markdown.pl\f[R] on some \[dq]edge
3339+cases\[dq] involving lists.
33243340Consider this source:
33253341.IP
33263342.nf
@@ -3332,23 +3348,24 @@ Consider this source:
33323348\ \ \ \ \-\ \ \ Foe
33333349
33343350+\ \ \ Third
3335−\f[]
3351+\f[R]
33363352.fi
33373353.PP
3338−Pandoc transforms this into a "compact list" (with no \f[C]<p>\f[] tags
3339−around "First", "Second", or "Third"), while Markdown puts \f[C]<p>\f[]
3340−tags around "Second" and "Third" (but not "First"), because of the blank
3341−space around "Third".
3354+Pandoc transforms this into a \[dq]compact list\[dq] (with no
3355+\f[C]<p>\f[R] tags around \[dq]First\[dq], \[dq]Second\[dq], or
3356+\[dq]Third\[dq]), while Markdown puts \f[C]<p>\f[R] tags around
3357+\[dq]Second\[dq] and \[dq]Third\[dq] (but not \[dq]First\[dq]), because
3358+of the blank space around \[dq]Third\[dq].
33423359Pandoc follows a simple rule: if the text is followed by a blank line,
33433360it is treated as a paragraph.
3344−Since "Second" is followed by a list, and not a blank line, it isn\[aq]t
3345−treated as a paragraph.
3361+Since \[dq]Second\[dq] is followed by a list, and not a blank line, it
3362+isn\[aq]t treated as a paragraph.
33463363The fact that the list is followed by a blank line is irrelevant.
3347−(Note: Pandoc works this way even when the \f[C]markdown_strict\f[]
3364+(Note: Pandoc works this way even when the \f[C]markdown_strict\f[R]
33483365format is specified.
33493366This behavior is consistent with the official Markdown syntax
33503367description, even though it is different from that of
3351−\f[C]Markdown.pl\f[].)
3368+\f[C]Markdown.pl\f[R].)
33523369.SS Ending a list
33533370.PP
33543371What if you want to put an indented code block after a list?
@@ -3359,16 +3376,16 @@ What if you want to put an indented code block after a list?
33593376\-\ \ \ item\ two
33603377
33613378\ \ \ \ {\ my\ code\ block\ }
3362−\f[]
3379+\f[R]
33633380.fi
33643381.PP
33653382Trouble! Here pandoc (like other Markdown implementations) will treat
3366−\f[C]{\ my\ code\ block\ }\f[] as the second paragraph of item two, and
3383+\f[C]{\ my\ code\ block\ }\f[R] as the second paragraph of item two, and
33673384not as a code block.
33683385.PP
3369−To "cut off" the list after item two, you can insert some non\-indented
3370−content, like an HTML comment, which won\[aq]t produce visible output in
3371−any format:
3386+To \[dq]cut off\[dq] the list after item two, you can insert some
3387+non\-indented content, like an HTML comment, which won\[aq]t produce
3388+visible output in any format:
33723389.IP
33733390.nf
33743391\f[C]
@@ -3378,7 +3395,7 @@ any format:
33783395<!\-\-\ end\ of\ list\ \-\->
33793396
33803397\ \ \ \ {\ my\ code\ block\ }
3381−\f[]
3398+\f[R]
33823399.fi
33833400.PP
33843401You can use the same trick if you want two consecutive lists instead of
@@ -3395,12 +3412,12 @@ one big list:
339534121.\ \ uno
339634132.\ \ dos
339734143.\ \ tres
3398−\f[]
3415+\f[R]
33993416.fi
34003417.SS Horizontal rules
34013418.PP
3402−A line containing a row of three or more \f[C]*\f[], \f[C]\-\f[], or
3403−\f[C]_\f[] characters (optionally separated by spaces) produces a
3419+A line containing a row of three or more \f[C]*\f[R], \f[C]\-\f[R], or
3420+\f[C]_\f[R] characters (optionally separated by spaces) produces a
34043421horizontal rule:
34053422.IP
34063423.nf
@@ -3408,7 +3425,7 @@ horizontal rule:
34083425*\ \ *\ \ *\ \ *
34093426
34103427\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
3411−\f[]
3428+\f[R]
34123429.fi
34133430.SS Tables
34143431.PP
@@ -3417,14 +3434,14 @@ The first three kinds presuppose the use of a fixed\-width font, such as
34173434Courier.
34183435The fourth kind can be used with proportionally spaced fonts, as it does
34193436not require lining up columns.
3420−.SS Extension: \f[C]table_captions\f[]
3437+.SS Extension: \f[C]table_captions\f[R]
34213438.PP
34223439A caption may optionally be provided with all 4 kinds of tables (as
34233440illustrated in the examples below).
3424−A caption is a paragraph beginning with the string \f[C]Table:\f[] (or
3425−just \f[C]:\f[]), which will be stripped off.
3441+A caption is a paragraph beginning with the string \f[C]Table:\f[R] (or
3442+just \f[C]:\f[R]), which will be stripped off.
34263443It may appear either before or after the table.
3427−.SS Extension: \f[C]simple_tables\f[]
3444+.SS Extension: \f[C]simple_tables\f[R]
34283445.PP
34293446Simple tables look like this:
34303447.IP
@@ -3437,7 +3454,7 @@ Simple tables look like this:
34373454\ \ \ \ \ \ 1\ \ \ \ \ 1\ \ \ \ \ \ \ \ \ \ 1\ \ \ \ \ \ \ \ \ \ \ \ \ 1
34383455
34393456Table:\ \ Demonstration\ of\ simple\ table\ syntax.
3440−\f[]
3457+\f[R]
34413458.fi
34423459.PP
34433460The headers and table rows must each fit on one line.
@@ -3470,14 +3487,14 @@ For example:
34703487\ \ \ \ 123\ \ \ \ \ 123\ \ \ \ \ \ \ 123\ \ \ \ \ \ \ \ \ \ \ 123
34713488\ \ \ \ \ \ 1\ \ \ \ \ 1\ \ \ \ \ \ \ \ \ \ 1\ \ \ \ \ \ \ \ \ \ \ \ \ \ 1
34723489\-\-\-\-\-\-\-\ \ \ \ \ \-\-\-\-\-\-\ \-\-\-\-\-\-\-\-\-\-\ \ \ \-\-\-\-\-\-\-
3473−\f[]
3490+\f[R]
34743491.fi
34753492.PP
34763493When headers are omitted, column alignments are determined on the basis
34773494of the first line of the table body.
34783495So, in the tables above, the columns would be right, left, center, and
34793496right aligned, respectively.
3480−.SS Extension: \f[C]multiline_tables\f[]
3497+.SS Extension: \f[C]multiline_tables\f[R]
34813498.PP
34823499Multiline tables allow headers and table rows to span multiple lines of
34833500text (but cells that span multiple columns or rows of the table are not
@@ -3500,7 +3517,7 @@ Here is an example:
35003517
35013518Table:\ Here\[aq]s\ the\ caption.\ It,\ too,\ may\ span
35023519multiple\ lines.
3503−\f[]
3520+\f[R]
35043521.fi
35053522.PP
35063523These work like simple tables, but with the following differences:
@@ -3532,13 +3549,13 @@ Headers may be omitted in multiline tables as well as simple tables:
35323549\-\-\-\-\-\-\-\-\-\-\-\ \-\-\-\-\-\-\-\ \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\ \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
35333550
35343551:\ Here\[aq]s\ a\ multiline\ table\ without\ headers.
3535−\f[]
3552+\f[R]
35363553.fi
35373554.PP
35383555It is possible for a multiline table to have just one row, but the row
35393556should be followed by a blank line (and then the row of dashes that ends
35403557the table), or the table may be interpreted as a simple table.
3541−.SS Extension: \f[C]grid_tables\f[]
3558+.SS Extension: \f[C]grid_tables\f[R]
35423559.PP
35433560Grid tables look like this:
35443561.IP
@@ -3555,11 +3572,11 @@ Grid tables look like this:
35553572|\ Oranges\ \ \ \ \ \ \ |\ $2.10\ \ \ \ \ \ \ \ \ |\ \-\ cures\ scurvy\ \ \ \ \ |
35563573|\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ |\ \ \ \ \ \ \ \ \ \ \ \ \ \ \ |\ \-\ tasty\ \ \ \ \ \ \ \ \ \ \ \ |
35573574+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
3558−\f[]
3575+\f[R]
35593576.fi
35603577.PP
3561−The row of \f[C]=\f[]s separates the header from the table body, and can
3562−be omitted for a headerless table.
3578+The row of \f[C]=\f[R]s separates the header from the table body, and
3579+can be omitted for a headerless table.
35633580The cells of grid tables may contain arbitrary block elements (multiple
35643581paragraphs, code blocks, lists, etc.).
35653582Cells that span multiple columns or rows are not supported.
@@ -3575,7 +3592,7 @@ the boundaries of the separator line after the header:
35753592+==============:+:==============+:==================:+
35763593|\ Bananas\ \ \ \ \ \ \ |\ $1.34\ \ \ \ \ \ \ \ \ |\ built\-in\ wrapper\ \ \ |
35773594+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
3578−\f[]
3595+\f[R]
35793596.fi
35803597.PP
35813598For headerless tables, the colons go on the top line instead:
@@ -3585,7 +3602,7 @@ For headerless tables, the colons go on the top line instead:
35853602+\-\-\-\-\-\-\-\-\-\-\-\-\-\-:+:\-\-\-\-\-\-\-\-\-\-\-\-\-\-+:\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-:+
35863603|\ Right\ \ \ \ \ \ \ \ \ |\ Left\ \ \ \ \ \ \ \ \ \ |\ Centered\ \ \ \ \ \ \ \ \ \ \ |
35873604+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-+
3588−\f[]
3605+\f[R]
35893606.fi
35903607.SS Grid Table Limitations
35913608.PP
@@ -3596,7 +3613,7 @@ All grid tables must have the same number of columns in each row, and
35963613the same number of rows in each column.
35973614For example, the Docutils sample grid tables will not render as expected
35983615with Pandoc.
3599−.SS Extension: \f[C]pipe_tables\f[]
3616+.SS Extension: \f[C]pipe_tables\f[R]
36003617.PP
36013618Pipe tables look like this:
36023619.IP
@@ -3609,7 +3626,7 @@ Pipe tables look like this:
36093626|\ \ \ \ 1\ \ |\ \ \ \ 1\ |\ \ \ \ \ 1\ \ \ |\ \ \ \ \ 1\ \ |
36103627
36113628\ \ :\ Demonstration\ of\ pipe\ table\ syntax.
3612−\f[]
3629+\f[R]
36133630.fi
36143631.PP
36153632The syntax is identical to PHP Markdown Extra tables.
@@ -3630,17 +3647,17 @@ fruit|\ price
36303647apple|2.05
36313648pear|1.37
36323649orange|3.09
3633−\f[]
3650+\f[R]
36343651.fi
36353652.PP
36363653The cells of pipe tables cannot contain block elements like paragraphs
36373654and lists, and cannot span multiple lines.
36383655If a pipe table contains a row whose printable content is wider than the
3639−column width (see \f[C]\-\-columns\f[]), then the table will take up the
3640−full text width and the cell contents will wrap, with the relative cell
3641−widths determined by the number of dashes in the line separating the
3642−table header from the table body.
3643−(For example \f[C]\-\-\-|\-\f[] would make the first column 3/4 and the
3656+column width (see \f[C]\-\-columns\f[R]), then the table will take up
3657+the full text width and the cell contents will wrap, with the relative
3658+cell widths determined by the number of dashes in the line separating
3659+the table header from the table body.
3660+(For example \f[C]\-\-\-|\-\f[R] would make the first column 3/4 and the
36443661second column 1/4 of the full text width.) On the other hand, if no
36453662lines are wider than column width, then cell contents will not be
36463663wrapped, and the cells will be sized to their contents.
@@ -3654,15 +3671,15 @@ be produced by Emacs\[aq] orgtbl\-mode:
36543671|\-\-\-\-\-+\-\-\-\-\-\-\-|
36553672|\ my\ \ |\ table\ |
36563673|\ is\ \ |\ nice\ \ |
3657−\f[]
3674+\f[R]
36583675.fi
36593676.PP
3660−The difference is that \f[C]+\f[] is used instead of \f[C]|\f[].
3677+The difference is that \f[C]+\f[R] is used instead of \f[C]|\f[R].
36613678Other orgtbl features are not supported.
36623679In particular, to get non\-default column alignment, you\[aq]ll need to
36633680add colons as above.
36643681.SS Metadata blocks
3665−.SS Extension: \f[C]pandoc_title_block\f[]
3682+.SS Extension: \f[C]pandoc_title_block\f[R]
36663683.PP
36673684If the file begins with a title block
36683685.IP
@@ -3671,7 +3688,7 @@ If the file begins with a title block
36713688%\ title
36723689%\ author(s)\ (separated\ by\ semicolons)
36733690%\ date
3674−\f[]
3691+\f[R]
36753692.fi
36763693.PP
36773694it will be parsed as bibliographic information, not regular text.
@@ -3689,7 +3706,7 @@ no author, you need a blank line:
36893706%\ My\ title
36903707%
36913708%\ June\ 15,\ 2006
3692−\f[]
3709+\f[R]
36933710.fi
36943711.PP
36953712The title may occupy multiple lines, but continuation lines must begin
@@ -3699,7 +3716,7 @@ with leading space, thus:
36993716\f[C]
37003717%\ My\ title
37013718\ \ on\ multiple\ lines
3702−\f[]
3719+\f[R]
37033720.fi
37043721.PP
37053722If a document has multiple authors, the authors may be put on separate
@@ -3715,7 +3732,7 @@ So, all of the following are equivalent:
37153732
37163733%\ Author\ One;
37173734\ \ Author\ Two
3718−\f[]
3735+\f[R]
37193736.fi
37203737.PP
37213738The date must fit on one line.
@@ -3724,15 +3741,15 @@ All three metadata fields may contain standard inline formatting
37243741(italics, links, footnotes, etc.).
37253742.PP
37263743Title blocks will always be parsed, but they will affect the output only
3727−when the \f[C]\-\-standalone\f[] (\f[C]\-s\f[]) option is chosen.
3744+when the \f[C]\-\-standalone\f[R] (\f[C]\-s\f[R]) option is chosen.
37283745In HTML output, titles will appear twice: once in the document head \-\-
37293746this is the title that will appear at the top of the window in a browser
37303747\-\- and once at the beginning of the document body.
37313748The title in the document head can have an optional prefix attached
3732−(\f[C]\-\-title\-prefix\f[] or \f[C]\-T\f[] option).
3733−The title in the body appears as an H1 element with class "title", so it
3734−can be suppressed or reformatted with CSS.
3735−If a title prefix is specified with \f[C]\-T\f[] and no title block
3749+(\f[C]\-\-title\-prefix\f[R] or \f[C]\-T\f[R] option).
3750+The title in the body appears as an H1 element with class
3751+\[dq]title\[dq], so it can be suppressed or reformatted with CSS.
3752+If a title prefix is specified with \f[C]\-T\f[R] and no title block
37363753appears in the document, the title prefix will be used by itself as the
37373754HTML title.
37383755.PP
@@ -3742,38 +3759,38 @@ The title is assumed to be the first word on the title line, which may
37423759optionally end with a (single\-digit) section number in parentheses.
37433760(There should be no space between the title and the parentheses.)
37443761Anything after this is assumed to be additional footer and header text.
3745−A single pipe character (\f[C]|\f[]) should be used to separate the
3762+A single pipe character (\f[C]|\f[R]) should be used to separate the
37463763footer text from the header text.
37473764Thus,
37483765.IP
37493766.nf
37503767\f[C]
37513768%\ PANDOC(1)
3752−\f[]
3769+\f[R]
37533770.fi
37543771.PP
3755−will yield a man page with the title \f[C]PANDOC\f[] and section 1.
3772+will yield a man page with the title \f[C]PANDOC\f[R] and section 1.
37563773.IP
37573774.nf
37583775\f[C]
37593776%\ PANDOC(1)\ Pandoc\ User\ Manuals
3760−\f[]
3777+\f[R]
37613778.fi
37623779.PP
3763−will also have "Pandoc User Manuals" in the footer.
3780+will also have \[dq]Pandoc User Manuals\[dq] in the footer.
37643781.IP
37653782.nf
37663783\f[C]
37673784%\ PANDOC(1)\ Pandoc\ User\ Manuals\ |\ Version\ 4.0
3768−\f[]
3785+\f[R]
37693786.fi
37703787.PP
3771−will also have "Version 4.0" in the header.
3772−.SS Extension: \f[C]yaml_metadata_block\f[]
3788+will also have \[dq]Version 4.0\[dq] in the header.
3789+.SS Extension: \f[C]yaml_metadata_block\f[R]
37733790.PP
37743791A YAML metadata block is a valid YAML object, delimited by a line of
3775−three hyphens (\f[C]\-\-\-\f[]) at the top and a line of three hyphens
3776−(\f[C]\-\-\-\f[]) or three dots (\f[C]\&...\f[]) at the bottom.
3792+three hyphens (\f[C]\-\-\-\f[R]) at the top and a line of three hyphens
3793+(\f[C]\-\-\-\f[R]) or three dots (\f[C]\&...\f[R]) at the bottom.
37773794A YAML metadata block may occur anywhere in the document, but if it is
37783795not at the beginning, it must be preceded by a blank line.
37793796(Note that, because of the way pandoc concatenates input files when
@@ -3784,12 +3801,12 @@ files:
37843801.nf
37853802\f[C]
37863803pandoc\ chap1.md\ chap2.md\ chap3.md\ metadata.yaml\ \-s\ \-o\ book.html
3787−\f[]
3804+\f[R]
37883805.fi
37893806.PP
3790−Just be sure that the YAML file begins with \f[C]\-\-\-\f[] and ends
3791−with \f[C]\-\-\-\f[] or \f[C]\&...\f[].) Alternatively, you can use the
3792−\f[C]\-\-metadata\-file\f[] option.
3807+Just be sure that the YAML file begins with \f[C]\-\-\-\f[R] and ends
3808+with \f[C]\-\-\-\f[R] or \f[C]\&...\f[R].) Alternatively, you can use
3809+the \f[C]\-\-metadata\-file\f[R] option.
37933810Using that approach however, you cannot reference content (like
37943811footnotes) from the main markdown input document.
37953812.PP
@@ -3800,23 +3817,23 @@ string scalars will be interpreted as Markdown.
38003817Fields with names ending in an underscore will be ignored by pandoc.
38013818(They may be given a role by external processors.) Field names must not
38023819be interpretable as YAML numbers or boolean values (so, for example,
3803−\f[C]yes\f[], \f[C]True\f[], and \f[C]15\f[] cannot be used as field
3820+\f[C]yes\f[R], \f[C]True\f[R], and \f[C]15\f[R] cannot be used as field
38043821names).
38053822.PP
38063823A document may contain multiple metadata blocks.
38073824The metadata fields will be combined through a \f[I]left\-biased
3808−union\f[]: if two metadata blocks attempt to set the same field, the
3825+union\f[R]: if two metadata blocks attempt to set the same field, the
38093826value from the first block will be taken.
38103827.PP
3811−When pandoc is used with \f[C]\-t\ markdown\f[] to create a Markdown
3828+When pandoc is used with \f[C]\-t\ markdown\f[R] to create a Markdown
38123829document, a YAML metadata block will be produced only if the
3813−\f[C]\-s/\-\-standalone\f[] option is used.
3830+\f[C]\-s/\-\-standalone\f[R] option is used.
38143831All of the metadata will appear in a single block at the beginning of
38153832the document.
38163833.PP
38173834Note that YAML escaping rules must be followed.
38183835Thus, for example, if a title contains a colon, it must be quoted.
3819−The pipe character (\f[C]|\f[]) can be used to begin an indented block
3836+The pipe character (\f[C]|\f[R]) can be used to begin an indented block
38203837that will be interpreted literally, without need for escaping.
38213838This form is necessary when the field contains blank lines or
38223839block\-level formatting:
@@ -3834,24 +3851,24 @@ abstract:\ |
38343851
38353852\ \ It\ consists\ of\ two\ paragraphs.
38363853\&...
3837−\f[]
3854+\f[R]
38383855.fi
38393856.PP
38403857Template variables will be set automatically from the metadata.
3841−Thus, for example, in writing HTML, the variable \f[C]abstract\f[] will
3842−be set to the HTML equivalent of the Markdown in the \f[C]abstract\f[]
3858+Thus, for example, in writing HTML, the variable \f[C]abstract\f[R] will
3859+be set to the HTML equivalent of the Markdown in the \f[C]abstract\f[R]
38433860field:
38443861.IP
38453862.nf
38463863\f[C]
38473864<p>This\ is\ the\ abstract.</p>
38483865<p>It\ consists\ of\ two\ paragraphs.</p>
3849−\f[]
3866+\f[R]
38503867.fi
38513868.PP
38523869Variables can contain arbitrary YAML structures, but the template must
38533870match this structure.
3854−The \f[C]author\f[] variable in the default templates expects a simple
3871+The \f[C]author\f[R] variable in the default templates expects a simple
38553872list or string, but can be changed to support more complicated
38563873structures.
38573874The following combination, for example, would add an affiliation to the
@@ -3867,7 +3884,7 @@ author:
38673884\-\ name:\ Author\ Two
38683885\ \ affiliation:\ University\ of\ Nowhere
38693886\&...
3870−\f[]
3887+\f[R]
38713888.fi
38723889.PP
38733890To use the structured authors in the example above, you would need a
@@ -3882,13 +3899,13 @@ $else$
38823899$author$
38833900$endif$
38843901$endfor$
3885−\f[]
3902+\f[R]
38863903.fi
38873904.PP
38883905Raw content to include in the document\[aq]s header may be specified
3889−using \f[C]header\-includes\f[]; however, it is important to mark up
3906+using \f[C]header\-includes\f[R]; however, it is important to mark up
38903907this content as raw code for a particular output format, using the
3891−\f[C]raw_attribute\f[] extension), or it will be interpreted as
3908+\f[C]raw_attribute\f[R] extension), or it will be interpreted as
38923909markdown.
38933910For example:
38943911.IP
@@ -3896,14 +3913,14 @@ For example:
38963913\f[C]
38973914header\-includes:
38983915\-\ |
3899−\ \ ```{=latex}
3900−\ \ \\let\\oldsection\\section
3901−\ \ \\renewcommand{\\section}[1]{\\clearpage\\oldsection{#1}}
3902−\ \ ```
3903−\f[]
3916+\ \ \[ga]\[ga]\[ga]{=latex}
3917+\ \ \[rs]let\[rs]oldsection\[rs]section
3918+\ \ \[rs]renewcommand{\[rs]section}[1]{\[rs]clearpage\[rs]oldsection{#1}}
3919+\ \ \[ga]\[ga]\[ga]
3920+\f[R]
39043921.fi
39053922.SS Backslash escapes
3906−.SS Extension: \f[C]all_symbols_escapable\f[]
3923+.SS Extension: \f[C]all_symbols_escapable\f[R]
39073924.PP
39083925Except inside a code block or inline code, any punctuation or space
39093926character preceded by a backslash will be treated literally, even if it
@@ -3912,8 +3929,8 @@ Thus, for example, if one writes
39123929.IP
39133930.nf
39143931\f[C]
3915−*\\*hello\\**
3916−\f[]
3932+*\[rs]*hello\[rs]**
3933+\f[R]
39173934.fi
39183935.PP
39193936one will get
@@ -3921,7 +3938,7 @@ one will get
39213938.nf
39223939\f[C]
39233940<em>*hello*</em>
3924−\f[]
3941+\f[R]
39253942.fi
39263943.PP
39273944instead of
@@ -3929,7 +3946,7 @@ instead of
39293946.nf
39303947\f[C]
39313948<strong>hello</strong>
3932−\f[]
3949+\f[R]
39333950.fi
39343951.PP
39353952This rule is easier to remember than standard Markdown\[aq]s rule, which
@@ -3937,115 +3954,115 @@ allows only the following characters to be backslash\-escaped:
39373954.IP
39383955.nf
39393956\f[C]
3940−\\`*_{}[]()>#+\-.!
3941−\f[]
3957+\[rs]\[ga]*_{}[]()>#+\-.!
3958+\f[R]
39423959.fi
39433960.PP
3944−(However, if the \f[C]markdown_strict\f[] format is used, the standard
3961+(However, if the \f[C]markdown_strict\f[R] format is used, the standard
39453962Markdown rule will be used.)
39463963.PP
39473964A backslash\-escaped space is parsed as a nonbreaking space.
3948−It will appear in TeX output as \f[C]~\f[] and in HTML and XML as
3949−\f[C]\\ \f[] or \f[C]\\ \f[].
3965+It will appear in TeX output as \f[C]\[ti]\f[R] and in HTML and XML as
3966+\f[C]\[rs] \f[R] or \f[C]\[rs] \f[R].
39503967.PP
39513968A backslash\-escaped newline (i.e.
39523969a backslash occurring at the end of a line) is parsed as a hard line
39533970break.
3954−It will appear in TeX output as \f[C]\\\\\f[] and in HTML as
3955−\f[C]<br\ />\f[].
3956−This is a nice alternative to Markdown\[aq]s "invisible" way of
3971+It will appear in TeX output as \f[C]\[rs]\[rs]\f[R] and in HTML as
3972+\f[C]<br\ />\f[R].
3973+This is a nice alternative to Markdown\[aq]s \[dq]invisible\[dq] way of
39573974indicating hard line breaks using two trailing spaces on a line.
39583975.PP
39593976Backslash escapes do not work in verbatim contexts.
39603977.SS Inline formatting
39613978.SS Emphasis
39623979.PP
3963−To \f[I]emphasize\f[] some text, surround it with \f[C]*\f[]s or
3964−\f[C]_\f[], like this:
3980+To \f[I]emphasize\f[R] some text, surround it with \f[C]*\f[R]s or
3981+\f[C]_\f[R], like this:
39653982.IP
39663983.nf
39673984\f[C]
39683985This\ text\ is\ _emphasized\ with\ underscores_,\ and\ this
39693986is\ *emphasized\ with\ asterisks*.
3970−\f[]
3987+\f[R]
39713988.fi
39723989.PP
3973−Double \f[C]*\f[] or \f[C]_\f[] produces \f[B]strong emphasis\f[]:
3990+Double \f[C]*\f[R] or \f[C]_\f[R] produces \f[B]strong emphasis\f[R]:
39743991.IP
39753992.nf
39763993\f[C]
39773994This\ is\ **strong\ emphasis**\ and\ __with\ underscores__.
3978−\f[]
3995+\f[R]
39793996.fi
39803997.PP
3981−A \f[C]*\f[] or \f[C]_\f[] character surrounded by spaces, or
3998+A \f[C]*\f[R] or \f[C]_\f[R] character surrounded by spaces, or
39823999backslash\-escaped, will not trigger emphasis:
39834000.IP
39844001.nf
39854002\f[C]
3986−This\ is\ *\ not\ emphasized\ *,\ and\ \\*neither\ is\ this\\*.
3987−\f[]
4003+This\ is\ *\ not\ emphasized\ *,\ and\ \[rs]*neither\ is\ this\[rs]*.
4004+\f[R]
39884005.fi
3989−.SS Extension: \f[C]intraword_underscores\f[]
4006+.SS Extension: \f[C]intraword_underscores\f[R]
39904007.PP
3991−Because \f[C]_\f[] is sometimes used inside words and identifiers,
3992−pandoc does not interpret a \f[C]_\f[] surrounded by alphanumeric
4008+Because \f[C]_\f[R] is sometimes used inside words and identifiers,
4009+pandoc does not interpret a \f[C]_\f[R] surrounded by alphanumeric
39934010characters as an emphasis marker.
3994−If you want to emphasize just part of a word, use \f[C]*\f[]:
4011+If you want to emphasize just part of a word, use \f[C]*\f[R]:
39954012.IP
39964013.nf
39974014\f[C]
39984015feas*ible*,\ not\ feas*able*.
3999−\f[]
4016+\f[R]
40004017.fi
40014018.SS Strikeout
4002−.SS Extension: \f[C]strikeout\f[]
4019+.SS Extension: \f[C]strikeout\f[R]
40034020.PP
40044021To strikeout a section of text with a horizontal line, begin and end it
4005−with \f[C]~~\f[].
4022+with \f[C]\[ti]\[ti]\f[R].
40064023Thus, for example,
40074024.IP
40084025.nf
40094026\f[C]
4010−This\ ~~is\ deleted\ text.~~
4011−\f[]
4027+This\ \[ti]\[ti]is\ deleted\ text.\[ti]\[ti]
4028+\f[R]
40124029.fi
40134030.SS Superscripts and subscripts
4014−.SS Extension: \f[C]superscript\f[], \f[C]subscript\f[]
4031+.SS Extension: \f[C]superscript\f[R], \f[C]subscript\f[R]
40154032.PP
40164033Superscripts may be written by surrounding the superscripted text by
4017−\f[C]^\f[] characters; subscripts may be written by surrounding the
4018−subscripted text by \f[C]~\f[] characters.
4034+\f[C]\[ha]\f[R] characters; subscripts may be written by surrounding the
4035+subscripted text by \f[C]\[ti]\f[R] characters.
40194036Thus, for example,
40204037.IP
40214038.nf
40224039\f[C]
4023−H~2~O\ is\ a\ liquid.\ \ 2^10^\ is\ 1024.
4024−\f[]
4040+H\[ti]2\[ti]O\ is\ a\ liquid.\ \ 2\[ha]10\[ha]\ is\ 1024.
4041+\f[R]
40254042.fi
40264043.PP
40274044If the superscripted or subscripted text contains spaces, these spaces
40284045must be escaped with backslashes.
40294046(This is to prevent accidental superscripting and subscripting through
4030−the ordinary use of \f[C]~\f[] and \f[C]^\f[].) Thus, if you want the
4031−letter P with \[aq]a cat\[aq] in subscripts, use \f[C]P~a\\\ cat~\f[],
4032−not \f[C]P~a\ cat~\f[].
4047+the ordinary use of \f[C]\[ti]\f[R] and \f[C]\[ha]\f[R].) Thus, if you
4048+want the letter P with \[aq]a cat\[aq] in subscripts, use
4049+\f[C]P\[ti]a\[rs]\ cat\[ti]\f[R], not \f[C]P\[ti]a\ cat\[ti]\f[R].
40334050.SS Verbatim
40344051.PP
40354052To make a short span of text verbatim, put it inside backticks:
40364053.IP
40374054.nf
40384055\f[C]
4039−What\ is\ the\ difference\ between\ `>>=`\ and\ `>>`?
4040−\f[]
4056+What\ is\ the\ difference\ between\ \[ga]>>=\[ga]\ and\ \[ga]>>\[ga]?
4057+\f[R]
40414058.fi
40424059.PP
40434060If the verbatim text includes a backtick, use double backticks:
40444061.IP
40454062.nf
40464063\f[C]
4047−Here\ is\ a\ literal\ backtick\ ``\ `\ ``.
4048−\f[]
4064+Here\ is\ a\ literal\ backtick\ \[ga]\[ga]\ \[ga]\ \[ga]\[ga].
4065+\f[R]
40494066.fi
40504067.PP
40514068(The spaces after the opening backticks and before the closing backticks
@@ -4060,56 +4077,56 @@ in verbatim contexts:
40604077.IP
40614078.nf
40624079\f[C]
4063−This\ is\ a\ backslash\ followed\ by\ an\ asterisk:\ `\\*`.
4064−\f[]
4080+This\ is\ a\ backslash\ followed\ by\ an\ asterisk:\ \[ga]\[rs]*\[ga].
4081+\f[R]
40654082.fi
4066−.SS Extension: \f[C]inline_code_attributes\f[]
4083+.SS Extension: \f[C]inline_code_attributes\f[R]
40674084.PP
40684085Attributes can be attached to verbatim text, just as with fenced code
40694086blocks:
40704087.IP
40714088.nf
40724089\f[C]
4073−`<$>`{.haskell}
4074−\f[]
4090+\[ga]<$>\[ga]{.haskell}
4091+\f[R]
40754092.fi
40764093.SS Small caps
40774094.PP
4078−To write small caps, use the \f[C]smallcaps\f[] class:
4095+To write small caps, use the \f[C]smallcaps\f[R] class:
40794096.IP
40804097.nf
40814098\f[C]
40824099[Small\ caps]{.smallcaps}
4083−\f[]
4100+\f[R]
40844101.fi
40854102.PP
4086−Or, without the \f[C]bracketed_spans\f[] extension:
4103+Or, without the \f[C]bracketed_spans\f[R] extension:
40874104.IP
40884105.nf
40894106\f[C]
4090−<span\ class="smallcaps">Small\ caps</span>
4091−\f[]
4107+<span\ class=\[dq]smallcaps\[dq]>Small\ caps</span>
4108+\f[R]
40924109.fi
40934110.PP
40944111For compatibility with other Markdown flavors, CSS is also supported:
40954112.IP
40964113.nf
40974114\f[C]
4098−<span\ style="font\-variant:small\-caps;">Small\ caps</span>
4099−\f[]
4115+<span\ style=\[dq]font\-variant:small\-caps;\[dq]>Small\ caps</span>
4116+\f[R]
41004117.fi
41014118.PP
41024119This will work in all output formats that support small caps.
41034120.SS Math
4104−.SS Extension: \f[C]tex_math_dollars\f[]
4105−.PP
4106−Anything between two \f[C]$\f[] characters will be treated as TeX math.
4107−The opening \f[C]$\f[] must have a non\-space character immediately to
4108−its right, while the closing \f[C]$\f[] must have a non\-space character
4109−immediately to its left, and must not be followed immediately by a
4110−digit.
4111−Thus, \f[C]$20,000\ and\ $30,000\f[] won\[aq]t parse as math.
4112−If for some reason you need to enclose text in literal \f[C]$\f[]
4121+.SS Extension: \f[C]tex_math_dollars\f[R]
4122+.PP
4123+Anything between two \f[C]$\f[R] characters will be treated as TeX math.
4124+The opening \f[C]$\f[R] must have a non\-space character immediately to
4125+its right, while the closing \f[C]$\f[R] must have a non\-space
4126+character immediately to its left, and must not be followed immediately
4127+by a digit.
4128+Thus, \f[C]$20,000\ and\ $30,000\f[R] won\[aq]t parse as math.
4129+If for some reason you need to enclose text in literal \f[C]$\f[R]
41134130characters, backslash\-escape them and they won\[aq]t be treated as math
41144131delimiters.
41154132.PP
@@ -4117,44 +4134,44 @@ TeX math will be printed in all output formats.
41174134How it is rendered depends on the output format:
41184135.TP
41194136.B LaTeX
4120−It will appear verbatim surrounded by \f[C]\\(...\\)\f[] (for inline
4121−math) or \f[C]\\[...\\]\f[] (for display math).
4137+It will appear verbatim surrounded by \f[C]\[rs](...\[rs])\f[R] (for
4138+inline math) or \f[C]\[rs][...\[rs]]\f[R] (for display math).
41224139.RS
41234140.RE
41244141.TP
41254142.B Markdown, Emacs Org mode, ConTeXt, ZimWiki
4126−It will appear verbatim surrounded by \f[C]$...$\f[] (for inline math)
4127−or \f[C]$$...$$\f[] (for display math).
4143+It will appear verbatim surrounded by \f[C]$...$\f[R] (for inline math)
4144+or \f[C]$$...$$\f[R] (for display math).
41284145.RS
41294146.RE
41304147.TP
41314148.B reStructuredText
4132−It will be rendered using an interpreted text role \f[C]:math:\f[].
4149+It will be rendered using an interpreted text role \f[C]:math:\f[R].
41334150.RS
41344151.RE
41354152.TP
41364153.B AsciiDoc
4137−It will be rendered as \f[C]latexmath:[...]\f[].
4154+It will be rendered as \f[C]latexmath:[...]\f[R].
41384155.RS
41394156.RE
41404157.TP
41414158.B Texinfo
4142−It will be rendered inside a \f[C]\@math\f[] command.
4159+It will be rendered inside a \f[C]\[at]math\f[R] command.
41434160.RS
41444161.RE
41454162.TP
41464163.B groff man
4147−It will be rendered verbatim without \f[C]$\f[]\[aq]s.
4164+It will be rendered verbatim without \f[C]$\f[R]\[aq]s.
41484165.RS
41494166.RE
41504167.TP
41514168.B MediaWiki, DokuWiki
4152−It will be rendered inside \f[C]<math>\f[] tags.
4169+It will be rendered inside \f[C]<math>\f[R] tags.
41534170.RS
41544171.RE
41554172.TP
41564173.B Textile
4157−It will be rendered inside \f[C]<span\ class="math">\f[] tags.
4174+It will be rendered inside \f[C]<span\ class=\[dq]math\[dq]>\f[R] tags.
41584175.RS
41594176.RE
41604177.TP
@@ -4170,8 +4187,8 @@ It will be rendered, if possible, using MathML.
41704187.RE
41714188.TP
41724189.B DocBook
4173−If the \f[C]\-\-mathml\f[] flag is used, it will be rendered using
4174−MathML in an \f[C]inlineequation\f[] or \f[C]informalequation\f[] tag.
4190+If the \f[C]\-\-mathml\f[R] flag is used, it will be rendered using
4191+MathML in an \f[C]inlineequation\f[R] or \f[C]informalequation\f[R] tag.
41754192Otherwise it will be rendered, if possible, using Unicode characters.
41764193.RS
41774194.RE
@@ -4182,7 +4199,7 @@ It will be rendered using OMML math markup.
41824199.RE
41834200.TP
41844201.B FictionBook2
4185−If the \f[C]\-\-webtex\f[] option is used, formulas are rendered as
4202+If the \f[C]\-\-webtex\f[R] option is used, formulas are rendered as
41864203images using CodeCogs or other compatible web service, downloaded and
41874204embedded in the e\-book.
41884205Otherwise, they will appear verbatim.
@@ -4196,27 +4213,34 @@ Therefore see Math rendering in HTML above.
41964213.RS
41974214.RE
41984215.SS Raw HTML
4199−.SS Extension: \f[C]raw_html\f[]
4216+.SS Extension: \f[C]raw_html\f[R]
42004217.PP
42014218Markdown allows you to insert raw HTML (or DocBook) anywhere in a
4202−document (except verbatim contexts, where \f[C]<\f[], \f[C]>\f[], and
4203−\f[C]&\f[] are interpreted literally).
4219+document (except verbatim contexts, where \f[C]<\f[R], \f[C]>\f[R], and
4220+\f[C]&\f[R] are interpreted literally).
42044221(Technically this is not an extension, since standard Markdown allows
42054222it, but it has been made an extension so that it can be disabled if
42064223desired.)
42074224.PP
42084225The raw HTML is passed through unchanged in HTML, S5, Slidy, Slideous,
4209−DZSlides, EPUB, Markdown, Emacs Org mode, and Textile output, and
4210−suppressed in other formats.
4211−.SS Extension: \f[C]markdown_in_html_blocks\f[]
4212−.PP
4213−Standard Markdown allows you to include HTML "blocks": blocks of HTML
4214−between balanced tags that are separated from the surrounding text with
4215−blank lines, and start and end at the left margin.
4226+DZSlides, EPUB, Markdown, CommonMark, Emacs Org mode, and Textile
4227+output, and suppressed in other formats.
4228+.PP
4229+In the CommonMark format, if \f[C]raw_html\f[R] is enabled,
4230+superscripts, subscripts, strikeouts and small capitals will be
4231+represented as HTML.
4232+Otherwise, plain\-text fallbacks will be used.
4233+Note that even if \f[C]raw_html\f[R] is disabled, tables will be
4234+rendered with HTML syntax if they cannot use pipe syntax.
4235+.SS Extension: \f[C]markdown_in_html_blocks\f[R]
4236+.PP
4237+Standard Markdown allows you to include HTML \[dq]blocks\[dq]: blocks of
4238+HTML between balanced tags that are separated from the surrounding text
4239+with blank lines, and start and end at the left margin.
42164240Within these blocks, everything is interpreted as HTML, not Markdown; so
4217−(for example), \f[C]*\f[] does not signify emphasis.
4241+(for example), \f[C]*\f[R] does not signify emphasis.
42184242.PP
4219−Pandoc behaves this way when the \f[C]markdown_strict\f[] format is
4243+Pandoc behaves this way when the \f[C]markdown_strict\f[R] format is
42204244used; but by default, pandoc interprets material between HTML block tags
42214245as Markdown.
42224246Thus, for example, pandoc will turn
@@ -4229,7 +4253,7 @@ Thus, for example, pandoc will turn
42294253<td>[a\ link](http://google.com)</td>
42304254</tr>
42314255</table>
4232−\f[]
4256+\f[R]
42334257.fi
42344258.PP
42354259into
@@ -4239,37 +4263,37 @@ into
42394263<table>
42404264<tr>
42414265<td><em>one</em></td>
4242−<td><a\ href="http://google.com">a\ link</a></td>
4266+<td><a\ href=\[dq]http://google.com\[dq]>a\ link</a></td>
42434267</tr>
42444268</table>
4245−\f[]
4269+\f[R]
42464270.fi
42474271.PP
4248−whereas \f[C]Markdown.pl\f[] will preserve it as is.
4272+whereas \f[C]Markdown.pl\f[R] will preserve it as is.
42494273.PP
4250−There is one exception to this rule: text between \f[C]<script>\f[] and
4251−\f[C]<style>\f[] tags is not interpreted as Markdown.
4274+There is one exception to this rule: text between \f[C]<script>\f[R] and
4275+\f[C]<style>\f[R] tags is not interpreted as Markdown.
42524276.PP
42534277This departure from standard Markdown should make it easier to mix
42544278Markdown with HTML block elements.
42554279For example, one can surround a block of Markdown text with
4256−\f[C]<div>\f[] tags without preventing it from being interpreted as
4280+\f[C]<div>\f[R] tags without preventing it from being interpreted as
42574281Markdown.
4258−.SS Extension: \f[C]native_divs\f[]
4282+.SS Extension: \f[C]native_divs\f[R]
42594283.PP
4260−Use native pandoc \f[C]Div\f[] blocks for content inside \f[C]<div>\f[]
4261−tags.
4284+Use native pandoc \f[C]Div\f[R] blocks for content inside
4285+\f[C]<div>\f[R] tags.
42624286For the most part this should give the same output as
4263−\f[C]markdown_in_html_blocks\f[], but it makes it easier to write pandoc
4264−filters to manipulate groups of blocks.
4265−.SS Extension: \f[C]native_spans\f[]
4287+\f[C]markdown_in_html_blocks\f[R], but it makes it easier to write
4288+pandoc filters to manipulate groups of blocks.
4289+.SS Extension: \f[C]native_spans\f[R]
42664290.PP
4267−Use native pandoc \f[C]Span\f[] blocks for content inside
4268−\f[C]<span>\f[] tags.
4269−For the most part this should give the same output as \f[C]raw_html\f[],
4270−but it makes it easier to write pandoc filters to manipulate groups of
4271−inlines.
4272−.SS Extension: \f[C]raw_tex\f[]
4291+Use native pandoc \f[C]Span\f[R] blocks for content inside
4292+\f[C]<span>\f[R] tags.
4293+For the most part this should give the same output as
4294+\f[C]raw_html\f[R], but it makes it easier to write pandoc filters to
4295+manipulate groups of inlines.
4296+.SS Extension: \f[C]raw_tex\f[R]
42734297.PP
42744298In addition to raw HTML, pandoc allows raw LaTeX, TeX, and ConTeXt to be
42754299included in a document.
@@ -4279,21 +4303,21 @@ Thus, for example, you can use LaTeX to include BibTeX citations:
42794303.IP
42804304.nf
42814305\f[C]
4282−This\ result\ was\ proved\ in\ \\cite{jones.1967}.
4283−\f[]
4306+This\ result\ was\ proved\ in\ \[rs]cite{jones.1967}.
4307+\f[R]
42844308.fi
42854309.PP
42864310Note that in LaTeX environments, like
42874311.IP
42884312.nf
42894313\f[C]
4290−\\begin{tabular}{|l|l|}\\hline
4291−Age\ &\ Frequency\ \\\\\ \\hline
4292−18\-\-25\ \ &\ 15\ \\\\
4293−26\-\-35\ \ &\ 33\ \\\\
4294−36\-\-45\ \ &\ 22\ \\\\\ \\hline
4295−\\end{tabular}
4296−\f[]
4314+\[rs]begin{tabular}{|l|l|}\[rs]hline
4315+Age\ &\ Frequency\ \[rs]\[rs]\ \[rs]hline
4316+18\-\-25\ \ &\ 15\ \[rs]\[rs]
4317+26\-\-35\ \ &\ 33\ \[rs]\[rs]
4318+36\-\-45\ \ &\ 22\ \[rs]\[rs]\ \[rs]hline
4319+\[rs]end{tabular}
4320+\f[R]
42974321.fi
42984322.PP
42994323the material between the begin and end tags will be interpreted as raw
@@ -4302,61 +4326,61 @@ LaTeX, not as Markdown.
43024326Inline LaTeX is ignored in output formats other than Markdown, LaTeX,
43034327Emacs Org mode, and ConTeXt.
43044328.SS Generic raw attribute
4305−.SS Extension: \f[C]raw_attribute\f[]
4329+.SS Extension: \f[C]raw_attribute\f[R]
43064330.PP
43074331Inline spans and fenced code blocks with a special kind of attribute
43084332will be parsed as raw content with the designated format.
4309−For example, the following produces a raw groff \f[C]ms\f[] block:
4333+For example, the following produces a raw groff \f[C]ms\f[R] block:
43104334.IP
43114335.nf
43124336\f[C]
4313−```{=ms}
4337+\[ga]\[ga]\[ga]{=ms}
43144338\&.MYMACRO
43154339blah\ blah
4316−```
4317−\f[]
4340+\[ga]\[ga]\[ga]
4341+\f[R]
43184342.fi
43194343.PP
4320−And the following produces a raw \f[C]html\f[] inline element:
4344+And the following produces a raw \f[C]html\f[R] inline element:
43214345.IP
43224346.nf
43234347\f[C]
4324−This\ is\ `<a>html</a>`{=html}
4325−\f[]
4348+This\ is\ \[ga]<a>html</a>\[ga]{=html}
4349+\f[R]
43264350.fi
43274351.PP
4328−This can be useful to insert raw xml into \f[C]docx\f[] documents, e.g.
4352+This can be useful to insert raw xml into \f[C]docx\f[R] documents, e.g.
43294353a pagebreak:
43304354.IP
43314355.nf
43324356\f[C]
4333−```{=openxml}
4357+\[ga]\[ga]\[ga]{=openxml}
43344358<w:p>
43354359\ \ <w:r>
4336−\ \ \ \ <w:br\ w:type="page"/>
4360+\ \ \ \ <w:br\ w:type=\[dq]page\[dq]/>
43374361\ \ </w:r>
43384362</w:p>
4339−```
4340−\f[]
4363+\[ga]\[ga]\[ga]
4364+\f[R]
43414365.fi
43424366.PP
43434367The format name should match the target format name (see
4344−\f[C]\-t/\-\-to\f[], above, for a list, or use
4345−\f[C]pandoc\ \-\-list\-output\-formats\f[]).
4346−Use \f[C]openxml\f[] for \f[C]docx\f[] output, \f[C]opendocument\f[] for
4347−\f[C]odt\f[] output, \f[C]html5\f[] for \f[C]epub3\f[] output,
4348−\f[C]html4\f[] for \f[C]epub2\f[] output, and \f[C]latex\f[],
4349−\f[C]beamer\f[], \f[C]ms\f[], or \f[C]html5\f[] for \f[C]pdf\f[] output
4350−(depending on what you use for \f[C]\-\-pdf\-engine\f[]).
4368+\f[C]\-t/\-\-to\f[R], above, for a list, or use
4369+\f[C]pandoc\ \-\-list\-output\-formats\f[R]).
4370+Use \f[C]openxml\f[R] for \f[C]docx\f[R] output, \f[C]opendocument\f[R]
4371+for \f[C]odt\f[R] output, \f[C]html5\f[R] for \f[C]epub3\f[R] output,
4372+\f[C]html4\f[R] for \f[C]epub2\f[R] output, and \f[C]latex\f[R],
4373+\f[C]beamer\f[R], \f[C]ms\f[R], or \f[C]html5\f[R] for \f[C]pdf\f[R]
4374+output (depending on what you use for \f[C]\-\-pdf\-engine\f[R]).
43514375.PP
43524376This extension presupposes that the relevant kind of inline code or
43534377fenced code block is enabled.
43544378Thus, for example, to use a raw attribute with a backtick code block,
4355−\f[C]backtick_code_blocks\f[] must be enabled.
4379+\f[C]backtick_code_blocks\f[R] must be enabled.
43564380.PP
43574381The raw attribute cannot be combined with regular attributes.
43584382.SS LaTeX macros
4359−.SS Extension: \f[C]latex_macros\f[]
4383+.SS Extension: \f[C]latex_macros\f[R]
43604384.PP
43614385For output formats other than LaTeX, pandoc will parse LaTeX macro
43624386definitions and apply the resulting macros to all LaTeX math and raw
@@ -4366,20 +4390,20 @@ LaTeX:
43664390.IP
43674391.nf
43684392\f[C]
4369−\\newcommand{\\tuple}[1]{\\langle\ #1\ \\rangle}
4393+\[rs]newcommand{\[rs]tuple}[1]{\[rs]langle\ #1\ \[rs]rangle}
43704394
4371−$\\tuple{a,\ b,\ c}$
4372−\f[]
4395+$\[rs]tuple{a,\ b,\ c}$
4396+\f[R]
43734397.fi
43744398.PP
43754399Note that LaTeX macros will not be applied if they occur inside inside a
4376−raw span or block marked with the \f[C]raw_attribute\f[] extension.
4400+raw span or block marked with the \f[C]raw_attribute\f[R] extension.
43774401.PP
4378−When \f[C]latex_macros\f[] is disabled, the raw LaTeX and math will not
4402+When \f[C]latex_macros\f[R] is disabled, the raw LaTeX and math will not
43794403have macros applied.
43804404This is usually a better approach when you are targeting LaTeX or PDF.
43814405.PP
4382−Whether or not \f[C]latex_macros\f[] is enabled, the macro definitions
4406+Whether or not \f[C]latex_macros\f[R] is enabled, the macro definitions
43834407will still be passed through as raw LaTeX.
43844408.SS Links
43854409.PP
@@ -4392,8 +4416,8 @@ a link:
43924416.nf
43934417\f[C]
43944418<http://google.com>
4395−<sam\@green.eggs.ham>
4396−\f[]
4419+<sam\[at]green.eggs.ham>
4420+\f[R]
43974421.fi
43984422.SS Inline links
43994423.PP
@@ -4404,8 +4428,8 @@ the URL in parentheses.
44044428.nf
44054429\f[C]
44064430This\ is\ an\ [inline\ link](/url),\ and\ here\[aq]s\ [one\ with
4407−a\ title](http://fsf.org\ "click\ here\ for\ a\ good\ time!").
4408−\f[]
4431+a\ title](http://fsf.org\ \[dq]click\ here\ for\ a\ good\ time!\[dq]).
4432+\f[R]
44094433.fi
44104434.PP
44114435There can be no space between the bracketed part and the parenthesized
@@ -4414,39 +4438,39 @@ The link text can contain formatting (such as emphasis), but the title
44144438cannot.
44154439.PP
44164440Email addresses in inline links are not autodetected, so they have to be
4417−prefixed with \f[C]mailto\f[]:
4441+prefixed with \f[C]mailto\f[R]:
44184442.IP
44194443.nf
44204444\f[C]
4421−[Write\ me!](mailto:sam\@green.eggs.ham)
4422−\f[]
4445+[Write\ me!](mailto:sam\[at]green.eggs.ham)
4446+\f[R]
44234447.fi
44244448.SS Reference links
44254449.PP
4426−An \f[I]explicit\f[] reference link has two parts, the link itself and
4450+An \f[I]explicit\f[R] reference link has two parts, the link itself and
44274451the link definition, which may occur elsewhere in the document (either
44284452before or after the link).
44294453.PP
44304454The link consists of link text in square brackets, followed by a label
44314455in square brackets.
44324456(There cannot be space between the two unless the
4433−\f[C]spaced_reference_links\f[] extension is enabled.) The link
4457+\f[C]spaced_reference_links\f[R] extension is enabled.) The link
44344458definition consists of the bracketed label, followed by a colon and a
44354459space, followed by the URL, and optionally (after a space) a link title
44364460either in quotes or in parentheses.
44374461The label must not be parseable as a citation (assuming the
4438−\f[C]citations\f[] extension is enabled): citations take precedence over
4439−link labels.
4462+\f[C]citations\f[R] extension is enabled): citations take precedence
4463+over link labels.
44404464.PP
44414465Here are some examples:
44424466.IP
44434467.nf
44444468\f[C]
4445−[my\ label\ 1]:\ /foo/bar.html\ \ "My\ title,\ optional"
4469+[my\ label\ 1]:\ /foo/bar.html\ \ \[dq]My\ title,\ optional\[dq]
44464470[my\ label\ 2]:\ /foo
44474471[my\ label\ 3]:\ http://fsf.org\ (The\ free\ software\ foundation)
44484472[my\ label\ 4]:\ /bar#special\ \ \[aq]A\ title\ in\ single\ quotes\[aq]
4449−\f[]
4473+\f[R]
44504474.fi
44514475.PP
44524476The URL may optionally be surrounded by angle brackets:
@@ -4454,7 +4478,7 @@ The URL may optionally be surrounded by angle brackets:
44544478.nf
44554479\f[C]
44564480[my\ label\ 5]:\ <http://foo.bar.baz>
4457−\f[]
4481+\f[R]
44584482.fi
44594483.PP
44604484The title may go on the next line:
@@ -4462,8 +4486,8 @@ The title may go on the next line:
44624486.nf
44634487\f[C]
44644488[my\ label\ 3]:\ http://fsf.org
4465−\ \ "The\ free\ software\ foundation"
4466−\f[]
4489+\ \ \[dq]The\ free\ software\ foundation\[dq]
4490+\f[R]
44674491.fi
44684492.PP
44694493Note that link labels are not case sensitive.
@@ -4474,10 +4498,10 @@ So, this will work:
44744498Here\ is\ [my\ link][FOO]
44754499
44764500[Foo]:\ /bar/baz
4477−\f[]
4501+\f[R]
44784502.fi
44794503.PP
4480−In an \f[I]implicit\f[] reference link, the second pair of brackets is
4504+In an \f[I]implicit\f[R] reference link, the second pair of brackets is
44814505empty:
44824506.IP
44834507.nf
@@ -4485,10 +4509,10 @@ empty:
44854509See\ [my\ website][].
44864510
44874511[my\ website]:\ http://foo.bar.baz
4488−\f[]
4512+\f[R]
44894513.fi
44904514.PP
4491−Note: In \f[C]Markdown.pl\f[] and most other Markdown implementations,
4515+Note: In \f[C]Markdown.pl\f[R] and most other Markdown implementations,
44924516reference link definitions cannot occur in nested constructions such as
44934517list items or block quotes.
44944518Pandoc lifts this arbitrary seeming restriction.
@@ -4500,11 +4524,11 @@ implementations:
45004524>\ My\ block\ [quote].
45014525>
45024526>\ [quote]:\ /foo
4503−\f[]
4527+\f[R]
45044528.fi
4505−.SS Extension: \f[C]shortcut_reference_links\f[]
4529+.SS Extension: \f[C]shortcut_reference_links\f[R]
45064530.PP
4507−In a \f[I]shortcut\f[] reference link, the second pair of brackets may
4531+In a \f[I]shortcut\f[R] reference link, the second pair of brackets may
45084532be omitted entirely:
45094533.IP
45104534.nf
@@ -4512,7 +4536,7 @@ be omitted entirely:
45124536See\ [my\ website].
45134537
45144538[my\ website]:\ http://foo.bar.baz
4515−\f[]
4539+\f[R]
45164540.fi
45174541.SS Internal links
45184542.PP
@@ -4523,7 +4547,7 @@ For example:
45234547.nf
45244548\f[C]
45254549See\ the\ [Introduction](#introduction).
4526−\f[]
4550+\f[R]
45274551.fi
45284552.PP
45294553or
@@ -4533,26 +4557,27 @@ or
45334557See\ the\ [Introduction].
45344558
45354559[Introduction]:\ #introduction
4536−\f[]
4560+\f[R]
45374561.fi
45384562.PP
45394563Internal links are currently supported for HTML formats (including HTML
45404564slide shows and EPUB), LaTeX, and ConTeXt.
45414565.SS Images
45424566.PP
4543−A link immediately preceded by a \f[C]!\f[] will be treated as an image.
4567+A link immediately preceded by a \f[C]!\f[R] will be treated as an
4568+image.
45444569The link text will be used as the image\[aq]s alt text:
45454570.IP
45464571.nf
45474572\f[C]
4548−
4573+
45494574
45504575![movie\ reel]
45514576
45524577[movie\ reel]:\ movie.gif
4553−\f[]
4578+\f[R]
45544579.fi
4555−.SS Extension: \f[C]implicit_figures\f[]
4580+.SS Extension: \f[C]implicit_figures\f[R]
45564581.PP
45574582An image with nonempty alt text, occurring by itself in a paragraph,
45584583will be rendered as a figure with a caption.
@@ -4561,7 +4586,7 @@ The image\[aq]s alt text will be used as the caption.
45614586.nf
45624587\f[C]
45634588
4564−\f[]
4589+\f[R]
45654590.fi
45664591.PP
45674592How this is rendered depends on the output format.
@@ -4576,14 +4601,14 @@ One way to do this is to insert a nonbreaking space after the image:
45764601.IP
45774602.nf
45784603\f[C]
4579−![This\ image\ won\[aq]t\ be\ a\ figure](/url/of/image.png)\\
4580−\f[]
4604+![This\ image\ won\[aq]t\ be\ a\ figure](/url/of/image.png)\[rs]
4605+\f[R]
45814606.fi
45824607.PP
45834608Note that in reveal.js slide shows, an image in a paragraph by itself
4584−that has the \f[C]stretch\f[] class will fill the screen, and the
4609+that has the \f[C]stretch\f[R] class will fill the screen, and the
45854610caption and figure tags will be omitted.
4586−.SS Extension: \f[C]link_attributes\f[]
4611+.SS Extension: \f[C]link_attributes\f[R]
45874612.PP
45884613Attributes can be set on links and images:
45894614.IP
@@ -4592,68 +4617,72 @@ Attributes can be set on links and images:
45924617An\ inline\ {#id\ .class\ width=30\ height=20px}
45934618and\ a\ reference\ ![image][ref]\ with\ attributes.
45944619
4595−[ref]:\ foo.jpg\ "optional\ title"\ {#id\ .class\ key=val\ key2="val\ 2"}
4596−\f[]
4620+[ref]:\ foo.jpg\ \[dq]optional\ title\[dq]\ {#id\ .class\ key=val\ key2=\[dq]val\ 2\[dq]}
4621+\f[R]
45974622.fi
45984623.PP
45994624(This syntax is compatible with PHP Markdown Extra when only
4600−\f[C]#id\f[] and \f[C]\&.class\f[] are used.)
4625+\f[C]#id\f[R] and \f[C]\&.class\f[R] are used.)
46014626.PP
4602−For HTML and EPUB, all attributes except \f[C]width\f[] and
4603−\f[C]height\f[] (but including \f[C]srcset\f[] and \f[C]sizes\f[]) are
4604−passed through as is.
4627+For HTML and EPUB, all attributes except \f[C]width\f[R] and
4628+\f[C]height\f[R] (but including \f[C]srcset\f[R] and \f[C]sizes\f[R])
4629+are passed through as is.
46054630The other writers ignore attributes that are not supported by their
46064631output format.
46074632.PP
4608−The \f[C]width\f[] and \f[C]height\f[] attributes on images are treated
4609−specially.
4633+The \f[C]width\f[R] and \f[C]height\f[R] attributes on images are
4634+treated specially.
46104635When used without a unit, the unit is assumed to be pixels.
4611−However, any of the following unit identifiers can be used: \f[C]px\f[],
4612−\f[C]cm\f[], \f[C]mm\f[], \f[C]in\f[], \f[C]inch\f[] and \f[C]%\f[].
4636+However, any of the following unit identifiers can be used:
4637+\f[C]px\f[R], \f[C]cm\f[R], \f[C]mm\f[R], \f[C]in\f[R], \f[C]inch\f[R]
4638+and \f[C]%\f[R].
46134639There must not be any spaces between the number and the unit.
46144640For example:
46154641.IP
46164642.nf
46174643\f[C]
46184644{\ width=50%\ }
4619−\f[]
4645+\f[R]
46204646.fi
46214647.IP \[bu] 2
46224648Dimensions are converted to inches for output in page\-based formats
46234649like LaTeX.
46244650Dimensions are converted to pixels for output in HTML\-like formats.
4625−Use the \f[C]\-\-dpi\f[] option to specify the number of pixels per
4651+Use the \f[C]\-\-dpi\f[R] option to specify the number of pixels per
46264652inch.
46274653The default is 96dpi.
46284654.IP \[bu] 2
4629−The \f[C]%\f[] unit is generally relative to some available space.
4655+The \f[C]%\f[R] unit is generally relative to some available space.
46304656For example the above example will render to
4631−\f[C]<img\ href="file.jpg"\ style="width:\ 50%;"\ />\f[] (HTML),
4632−\f[C]\\includegraphics[width=0.5\\textwidth]{file.jpg}\f[] (LaTeX), or
4633−\f[C]\\externalfigure[file.jpg][width=0.5\\textwidth]\f[] (ConTeXt).
4657+\f[C]<img\ href=\[dq]file.jpg\[dq]\ style=\[dq]width:\ 50%;\[dq]\ />\f[R]
4658+(HTML),
4659+\f[C]\[rs]includegraphics[width=0.5\[rs]textwidth]{file.jpg}\f[R]
4660+(LaTeX), or
4661+\f[C]\[rs]externalfigure[file.jpg][width=0.5\[rs]textwidth]\f[R]
4662+(ConTeXt).
46344663.IP \[bu] 2
46354664Some output formats have a notion of a class (ConTeXt) or a unique
4636−identifier (LaTeX \f[C]\\caption\f[]), or both (HTML).
4665+identifier (LaTeX \f[C]\[rs]caption\f[R]), or both (HTML).
46374666.IP \[bu] 2
4638−When no \f[C]width\f[] or \f[C]height\f[] attributes are specified, the
4639−fallback is to look at the image resolution and the dpi metadata
4667+When no \f[C]width\f[R] or \f[C]height\f[R] attributes are specified,
4668+the fallback is to look at the image resolution and the dpi metadata
46404669embedded in the image file.
46414670.SS Divs and Spans
46424671.PP
4643−Using the \f[C]native_divs\f[] and \f[C]native_spans\f[] extensions (see
4644−above), HTML syntax can be used as part of markdown to create native
4645−\f[C]Div\f[] and \f[C]Span\f[] elements in the pandoc AST (as opposed to
4646−raw HTML).
4672+Using the \f[C]native_divs\f[R] and \f[C]native_spans\f[R] extensions
4673+(see above), HTML syntax can be used as part of markdown to create
4674+native \f[C]Div\f[R] and \f[C]Span\f[R] elements in the pandoc AST (as
4675+opposed to raw HTML).
46474676However, there is also nicer syntax available:
4648−.SS Extension: \f[C]fenced_divs\f[]
4677+.SS Extension: \f[C]fenced_divs\f[R]
46494678.PP
4650−Allow special fenced syntax for native \f[C]Div\f[] blocks.
4679+Allow special fenced syntax for native \f[C]Div\f[R] blocks.
46514680A Div starts with a fence containing at least three consecutive colons
46524681plus some attributes.
46534682The attributes may optionally be followed by another string of
46544683consecutive colons.
46554684The attribute syntax is exactly as in fenced code blocks (see Extension:
4656−\f[C]fenced_code_attributes\f[]).
4685+\f[C]fenced_code_attributes\f[R]).
46574686As with fenced code blocks, one can use either attributes in curly
46584687braces or a single unbraced word, which will be treated as a class name.
46594688The Div ends with another line containing a string of at least three
@@ -4670,11 +4699,11 @@ Here\ is\ a\ paragraph.
46704699
46714700And\ another.
46724701:::::
4673−\f[]
4702+\f[R]
46744703.fi
46754704.PP
46764705Fenced divs can be nested.
4677−Opening fences are distinguished because they \f[I]must\f[] have
4706+Opening fences are distinguished because they \f[I]must\f[R] have
46784707attributes:
46794708.IP
46804709.nf
@@ -4686,7 +4715,7 @@ This\ is\ a\ warning.
46864715This\ is\ a\ warning\ within\ a\ warning.
46874716:::
46884717::::::::::::::::::
4689−\f[]
4718+\f[R]
46904719.fi
46914720.PP
46924721Fences without attributes are always closing fences.
@@ -4694,29 +4723,29 @@ Unlike with fenced code blocks, the number of colons in the closing
46944723fence need not match the number in the opening fence.
46954724However, it can be helpful for visual clarity to use fences of different
46964725lengths to distinguish nested divs from their parents.
4697−.SS Extension: \f[C]bracketed_spans\f[]
4726+.SS Extension: \f[C]bracketed_spans\f[R]
46984727.PP
46994728A bracketed sequence of inlines, as one would use to begin a link, will
4700−be treated as a \f[C]Span\f[] with attributes if it is followed
4729+be treated as a \f[C]Span\f[R] with attributes if it is followed
47014730immediately by attributes:
47024731.IP
47034732.nf
47044733\f[C]
4705−[This\ is\ *some\ text*]{.class\ key="val"}
4706−\f[]
4734+[This\ is\ *some\ text*]{.class\ key=\[dq]val\[dq]}
4735+\f[R]
47074736.fi
47084737.SS Footnotes
4709−.SS Extension: \f[C]footnotes\f[]
4738+.SS Extension: \f[C]footnotes\f[R]
47104739.PP
47114740Pandoc\[aq]s Markdown allows footnotes, using the following syntax:
47124741.IP
47134742.nf
47144743\f[C]
4715−Here\ is\ a\ footnote\ reference,[^1]\ and\ another.[^longnote]
4744+Here\ is\ a\ footnote\ reference,[\[ha]1]\ and\ another.[\[ha]longnote]
47164745
4717−[^1]:\ Here\ is\ the\ footnote.
4746+[\[ha]1]:\ Here\ is\ the\ footnote.
47184747
4719−[^longnote]:\ Here\[aq]s\ one\ with\ multiple\ blocks.
4748+[\[ha]longnote]:\ Here\[aq]s\ one\ with\ multiple\ blocks.
47204749
47214750\ \ \ \ Subsequent\ paragraphs\ are\ indented\ to\ show\ that\ they
47224751belong\ to\ the\ previous\ footnote.
@@ -4729,7 +4758,7 @@ belong\ to\ the\ previous\ footnote.
47294758
47304759This\ paragraph\ won\[aq]t\ be\ part\ of\ the\ note,\ because\ it
47314760isn\[aq]t\ indented.
4732−\f[]
4761+\f[R]
47334762.fi
47344763.PP
47354764The identifiers in footnote references may not contain spaces, tabs, or
@@ -4742,7 +4771,7 @@ They may appear anywhere except inside other block elements (lists,
47424771block quotes, tables, etc.).
47434772Each footnote should be separated from surrounding content (including
47444773other footnotes) by blank lines.
4745−.SS Extension: \f[C]inline_notes\f[]
4774+.SS Extension: \f[C]inline_notes\f[R]
47464775.PP
47474776Inline footnotes are also allowed (though, unlike regular notes, they
47484777cannot contain multiple paragraphs).
@@ -4750,17 +4779,17 @@ The syntax is as follows:
47504779.IP
47514780.nf
47524781\f[C]
4753−Here\ is\ an\ inline\ note.^[Inlines\ notes\ are\ easier\ to\ write,\ since
4782+Here\ is\ an\ inline\ note.\[ha][Inlines\ notes\ are\ easier\ to\ write,\ since
47544783you\ don\[aq]t\ have\ to\ pick\ an\ identifier\ and\ move\ down\ to\ type\ the
47554784note.]
4756−\f[]
4785+\f[R]
47574786.fi
47584787.PP
47594788Inline and regular footnotes may be mixed freely.
47604789.SS Citations
4761−.SS Extension: \f[C]citations\f[]
4790+.SS Extension: \f[C]citations\f[R]
47624791.PP
4763−Using an external filter, \f[C]pandoc\-citeproc\f[], pandoc can
4792+Using an external filter, \f[C]pandoc\-citeproc\f[R], pandoc can
47644793automatically generate citations and a bibliography in a number of
47654794styles.
47664795Basic usage is
@@ -4768,14 +4797,14 @@ Basic usage is
47684797.nf
47694798\f[C]
47704799pandoc\ \-\-filter\ pandoc\-citeproc\ myinput.txt
4771−\f[]
4800+\f[R]
47724801.fi
47734802.PP
47744803In order to use this feature, you will need to specify a bibliography
4775−file using the \f[C]bibliography\f[] metadata field in a YAML metadata
4776−section, or \f[C]\-\-bibliography\f[] command line argument.
4777−You can supply multiple \f[C]\-\-bibliography\f[] arguments or set
4778−\f[C]bibliography\f[] metadata field to YAML array, if you want to use
4804+file using the \f[C]bibliography\f[R] metadata field in a YAML metadata
4805+section, or \f[C]\-\-bibliography\f[R] command line argument.
4806+You can supply multiple \f[C]\-\-bibliography\f[R] arguments or set
4807+\f[C]bibliography\f[R] metadata field to YAML array, if you want to use
47794808multiple bibliography files.
47804809The bibliography may have any of these formats:
47814810.PP
@@ -4845,54 +4874,54 @@ T}@T{
48454874T}
48464875.TE
48474876.PP
4848−Note that \f[C]\&.bib\f[] can be used with both BibTeX and BibLaTeX
4849−files; use \f[C]\&.bibtex\f[] to force BibTeX.
4877+Note that \f[C]\&.bib\f[R] can be used with both BibTeX and BibLaTeX
4878+files; use \f[C]\&.bibtex\f[R] to force BibTeX.
48504879.PP
4851−Note that \f[C]pandoc\-citeproc\ \-\-bib2json\f[] and
4852−\f[C]pandoc\-citeproc\ \-\-bib2yaml\f[] can produce \f[C]\&.json\f[] and
4853−\f[C]\&.yaml\f[] files from any of the supported formats.
4880+Note that \f[C]pandoc\-citeproc\ \-\-bib2json\f[R] and
4881+\f[C]pandoc\-citeproc\ \-\-bib2yaml\f[R] can produce \f[C]\&.json\f[R]
4882+and \f[C]\&.yaml\f[R] files from any of the supported formats.
48544883.PP
48554884In\-field markup: In BibTeX and BibLaTeX databases, pandoc\-citeproc
48564885parses a subset of LaTeX markup; in CSL YAML databases, pandoc Markdown;
48574886and in CSL JSON databases, an HTML\-like markup:
48584887.TP
4859−.B \f[C]<i>...</i>\f[]
4888+.B \f[C]<i>...</i>\f[R]
48604889italics
48614890.RS
48624891.RE
48634892.TP
4864−.B \f[C]<b>...</b>\f[]
4893+.B \f[C]<b>...</b>\f[R]
48654894bold
48664895.RS
48674896.RE
48684897.TP
4869−.B \f[C]<span\ style="font\-variant:small\-caps;">...</span>\f[] or \f[C]<sc>...</sc>\f[]
4898+.B \f[C]<span\ style=\[dq]font\-variant:small\-caps;\[dq]>...</span>\f[R] or \f[C]<sc>...</sc>\f[R]
48704899small capitals
48714900.RS
48724901.RE
48734902.TP
4874−.B \f[C]<sub>...</sub>\f[]
4903+.B \f[C]<sub>...</sub>\f[R]
48754904subscript
48764905.RS
48774906.RE
48784907.TP
4879−.B \f[C]<sup>...</sup>\f[]
4908+.B \f[C]<sup>...</sup>\f[R]
48804909superscript
48814910.RS
48824911.RE
48834912.TP
4884−.B \f[C]<span\ class="nocase">...</span>\f[]
4913+.B \f[C]<span\ class=\[dq]nocase\[dq]>...</span>\f[R]
48854914prevent a phrase from being capitalized as title case
48864915.RS
48874916.RE
48884917.PP
4889−\f[C]pandoc\-citeproc\ \-j\f[] and \f[C]\-y\f[] interconvert the CSL
4918+\f[C]pandoc\-citeproc\ \-j\f[R] and \f[C]\-y\f[R] interconvert the CSL
48904919JSON and CSL YAML formats as far as possible.
48914920.PP
48924921As an alternative to specifying a bibliography file using
4893−\f[C]\-\-bibliography\f[] or the YAML metadata field
4894−\f[C]bibliography\f[], you can include the citation data directly in the
4895−\f[C]references\f[] field of the document\[aq]s YAML metadata.
4922+\f[C]\-\-bibliography\f[R] or the YAML metadata field
4923+\f[C]bibliography\f[R], you can include the citation data directly in
4924+the \f[C]references\f[R] field of the document\[aq]s YAML metadata.
48964925The field should contain an array of YAML\-encoded references, for
48974926example:
48984927.IP
@@ -4923,80 +4952,84 @@ references:
49234952\ \ URL:\ http://www.nature.com/nature/journal/v171/n4356/abs/171737a0.html
49244953\ \ language:\ en\-GB
49254954\&...
4926−\f[]
4955+\f[R]
49274956.fi
49284957.PP
4929−(\f[C]pandoc\-citeproc\ \-\-bib2yaml\f[] can produce these from a
4958+(\f[C]pandoc\-citeproc\ \-\-bib2yaml\f[R] can produce these from a
49304959bibliography file in one of the supported formats.)
49314960.PP
49324961Citations and references can be formatted using any style supported by
49334962the Citation Style Language, listed in the Zotero Style Repository.
4934−These files are specified using the \f[C]\-\-csl\f[] option or the
4935−\f[C]csl\f[] metadata field.
4936−By default, \f[C]pandoc\-citeproc\f[] will use the Chicago Manual of
4963+These files are specified using the \f[C]\-\-csl\f[R] option or the
4964+\f[C]csl\f[R] metadata field.
4965+By default, \f[C]pandoc\-citeproc\f[R] will use the Chicago Manual of
49374966Style author\-date format.
49384967The CSL project provides further information on finding and editing
49394968styles.
49404969.PP
49414970To make your citations hyperlinks to the corresponding bibliography
4942−entries, add \f[C]link\-citations:\ true\f[] to your YAML metadata.
4971+entries, add \f[C]link\-citations:\ true\f[R] to your YAML metadata.
49434972.PP
49444973Citations go inside square brackets and are separated by semicolons.
4945−Each citation must have a key, composed of \[aq]\@\[aq] + the citation
4946−identifier from the database, and may optionally have a prefix, a
4947−locator, and a suffix.
4948−The citation key must begin with a letter, digit, or \f[C]_\f[], and may
4949−contain alphanumerics, \f[C]_\f[], and internal punctuation characters
4950−(\f[C]:.#$%&\-+?<>~/\f[]).
4974+Each citation must have a key, composed of \[aq]\[at]\[aq] + the
4975+citation identifier from the database, and may optionally have a prefix,
4976+a locator, and a suffix.
4977+The citation key must begin with a letter, digit, or \f[C]_\f[R], and
4978+may contain alphanumerics, \f[C]_\f[R], and internal punctuation
4979+characters (\f[C]:.#$%&\-+?<>\[ti]/\f[R]).
49514980Here are some examples:
49524981.IP
49534982.nf
49544983\f[C]
4955−Blah\ blah\ [see\ \@doe99,\ pp.\ 33\-35;\ also\ \@smith04,\ chap.\ 1].
4984+Blah\ blah\ [see\ \[at]doe99,\ pp.\ 33\-35;\ also\ \[at]smith04,\ chap.\ 1].
49564985
4957−Blah\ blah\ [\@doe99,\ pp.\ 33\-35,\ 38\-39\ and\ *passim*].
4986+Blah\ blah\ [\[at]doe99,\ pp.\ 33\-35,\ 38\-39\ and\ *passim*].
49584987
4959−Blah\ blah\ [\@smith04;\ \@doe99].
4960−\f[]
4988+Blah\ blah\ [\[at]smith04;\ \[at]doe99].
4989+\f[R]
49614990.fi
49624991.PP
4963−\f[C]pandoc\-citeproc\f[] detects locator terms in the CSL locale files.
4992+\f[C]pandoc\-citeproc\f[R] detects locator terms in the CSL locale
4993+files.
49644994Either abbreviated or unabbreviated forms are accepted.
4965−In the \f[C]en\-US\f[] locale, locator terms can be written in either
4966−singular or plural forms, as \f[C]book\f[], \f[C]bk.\f[]/\f[C]bks.\f[];
4967−\f[C]chapter\f[], \f[C]chap.\f[]/\f[C]chaps.\f[]; \f[C]column\f[],
4968−\f[C]col.\f[]/\f[C]cols.\f[]; \f[C]figure\f[],
4969−\f[C]fig.\f[]/\f[C]figs.\f[]; \f[C]folio\f[],
4970−\f[C]fol.\f[]/\f[C]fols.\f[]; \f[C]number\f[],
4971−\f[C]no.\f[]/\f[C]nos.\f[]; \f[C]line\f[], \f[C]l.\f[]/\f[C]ll.\f[];
4972−\f[C]note\f[], \f[C]n.\f[]/\f[C]nn.\f[]; \f[C]opus\f[],
4973−\f[C]op.\f[]/\f[C]opp.\f[]; \f[C]page\f[], \f[C]p.\f[]/\f[C]pp.\f[];
4974−\f[C]paragraph\f[], \f[C]para.\f[]/\f[C]paras.\f[]; \f[C]part\f[],
4975−\f[C]pt.\f[]/\f[C]pts.\f[]; \f[C]section\f[],
4976−\f[C]sec.\f[]/\f[C]secs.\f[]; \f[C]sub\ verbo\f[],
4977−\f[C]s.v.\f[]/\f[C]s.vv.\f[]; \f[C]verse\f[], \f[C]v.\f[]/\f[C]vv.\f[];
4978−\f[C]volume\f[], \f[C]vol.\f[]/\f[C]vols.\f[]; \f[C]¶\f[]/\f[C]¶¶\f[];
4979−\f[C]§\f[]/\f[C]§§\f[].
4980−If no locator term is used, "page" is assumed.
4981−.PP
4982−A minus sign (\f[C]\-\f[]) before the \f[C]\@\f[] will suppress mention
4983−of the author in the citation.
4995+In the \f[C]en\-US\f[R] locale, locator terms can be written in either
4996+singular or plural forms, as \f[C]book\f[R],
4997+\f[C]bk.\f[R]/\f[C]bks.\f[R]; \f[C]chapter\f[R],
4998+\f[C]chap.\f[R]/\f[C]chaps.\f[R]; \f[C]column\f[R],
4999+\f[C]col.\f[R]/\f[C]cols.\f[R]; \f[C]figure\f[R],
5000+\f[C]fig.\f[R]/\f[C]figs.\f[R]; \f[C]folio\f[R],
5001+\f[C]fol.\f[R]/\f[C]fols.\f[R]; \f[C]number\f[R],
5002+\f[C]no.\f[R]/\f[C]nos.\f[R]; \f[C]line\f[R],
5003+\f[C]l.\f[R]/\f[C]ll.\f[R]; \f[C]note\f[R], \f[C]n.\f[R]/\f[C]nn.\f[R];
5004+\f[C]opus\f[R], \f[C]op.\f[R]/\f[C]opp.\f[R]; \f[C]page\f[R],
5005+\f[C]p.\f[R]/\f[C]pp.\f[R]; \f[C]paragraph\f[R],
5006+\f[C]para.\f[R]/\f[C]paras.\f[R]; \f[C]part\f[R],
5007+\f[C]pt.\f[R]/\f[C]pts.\f[R]; \f[C]section\f[R],
5008+\f[C]sec.\f[R]/\f[C]secs.\f[R]; \f[C]sub\ verbo\f[R],
5009+\f[C]s.v.\f[R]/\f[C]s.vv.\f[R]; \f[C]verse\f[R],
5010+\f[C]v.\f[R]/\f[C]vv.\f[R]; \f[C]volume\f[R],
5011+\f[C]vol.\f[R]/\f[C]vols.\f[R]; \f[C]\[ps]\f[R]/\f[C]\[ps]\[ps]\f[R];
5012+\f[C]\[sc]\f[R]/\f[C]\[sc]\[sc]\f[R].
5013+If no locator term is used, \[dq]page\[dq] is assumed.
5014+.PP
5015+A minus sign (\f[C]\-\f[R]) before the \f[C]\[at]\f[R] will suppress
5016+mention of the author in the citation.
49845017This can be useful when the author is already mentioned in the text:
49855018.IP
49865019.nf
49875020\f[C]
4988−Smith\ says\ blah\ [\-\@smith04].
4989−\f[]
5021+Smith\ says\ blah\ [\-\[at]smith04].
5022+\f[R]
49905023.fi
49915024.PP
49925025You can also write an in\-text citation, as follows:
49935026.IP
49945027.nf
49955028\f[C]
4996−\@smith04\ says\ blah.
5029+\[at]smith04\ says\ blah.
49975030
4998−\@smith04\ [p.\ 33]\ says\ blah.
4999−\f[]
5031+\[at]smith04\ [p.\ 33]\ says\ blah.
5032+\f[R]
50005033.fi
50015034.PP
50025035If the style calls for a list of works cited, it will be placed at the
@@ -5008,31 +5041,31 @@ Normally, you will want to end your document with an appropriate header:
50085041last\ paragraph...
50095042
50105043#\ References
5011−\f[]
5044+\f[R]
50125045.fi
50135046.PP
50145047The bibliography will be inserted after this header.
5015−Note that the \f[C]unnumbered\f[] class will be added to this header, so
5016−that the section will not be numbered.
5048+Note that the \f[C]unnumbered\f[R] class will be added to this header,
5049+so that the section will not be numbered.
50175050.PP
50185051If you want to include items in the bibliography without actually citing
5019−them in the body text, you can define a dummy \f[C]nocite\f[] metadata
5052+them in the body text, you can define a dummy \f[C]nocite\f[R] metadata
50205053field and put the citations there:
50215054.IP
50225055.nf
50235056\f[C]
50245057\-\-\-
50255058nocite:\ |
5026−\ \ \@item1,\ \@item2
5059+\ \ \[at]item1,\ \[at]item2
50275060\&...
50285061
5029−\@item3
5030−\f[]
5062+\[at]item3
5063+\f[R]
50315064.fi
50325065.PP
5033−In this example, the document will contain a citation for \f[C]item3\f[]
5034−only, but the bibliography will contain entries for \f[C]item1\f[],
5035−\f[C]item2\f[], and \f[C]item3\f[].
5066+In this example, the document will contain a citation for
5067+\f[C]item3\f[R] only, but the bibliography will contain entries for
5068+\f[C]item1\f[R], \f[C]item2\f[R], and \f[C]item3\f[R].
50365069.PP
50375070It is possible to create a bibliography with all the citations, whether
50385071or not they appear in the document, by using a wildcard:
@@ -5041,16 +5074,16 @@ or not they appear in the document, by using a wildcard:
50415074\f[C]
50425075\-\-\-
50435076nocite:\ |
5044−\ \ \@*
5077+\ \ \[at]*
50455078\&...
5046−\f[]
5079+\f[R]
50475080.fi
50485081.PP
5049−For LaTeX output, you can also use \f[C]natbib\f[] or \f[C]biblatex\f[]
5050−to render the bibliography.
5082+For LaTeX output, you can also use \f[C]natbib\f[R] or
5083+\f[C]biblatex\f[R] to render the bibliography.
50515084In order to do so, specify bibliography files as outlined above, and add
5052−\f[C]\-\-natbib\f[] or \f[C]\-\-biblatex\f[] argument to \f[C]pandoc\f[]
5053−invocation.
5085+\f[C]\-\-natbib\f[R] or \f[C]\-\-biblatex\f[R] argument to
5086+\f[C]pandoc\f[R] invocation.
50545087Bear in mind that bibliography files have to be in respective format
50555088(either BibTeX or BibLaTeX).
50565089.PP
@@ -5058,31 +5091,31 @@ For more information, see the pandoc\-citeproc man page.
50585091.SS Non\-pandoc extensions
50595092.PP
50605093The following Markdown syntax extensions are not enabled by default in
5061−pandoc, but may be enabled by adding \f[C]+EXTENSION\f[] to the format
5062−name, where \f[C]EXTENSION\f[] is the name of the extension.
5063−Thus, for example, \f[C]markdown+hard_line_breaks\f[] is Markdown with
5094+pandoc, but may be enabled by adding \f[C]+EXTENSION\f[R] to the format
5095+name, where \f[C]EXTENSION\f[R] is the name of the extension.
5096+Thus, for example, \f[C]markdown+hard_line_breaks\f[R] is Markdown with
50645097hard line breaks.
5065−.SS Extension: \f[C]old_dashes\f[]
5098+.SS Extension: \f[C]old_dashes\f[R]
50665099.PP
50675100Selects the pandoc <= 1.8.2.1 behavior for parsing smart dashes:
5068−\f[C]\-\f[] before a numeral is an en\-dash, and \f[C]\-\-\f[] is an
5101+\f[C]\-\f[R] before a numeral is an en\-dash, and \f[C]\-\-\f[R] is an
50695102em\-dash.
5070−This option only has an effect if \f[C]smart\f[] is enabled.
5071−It is selected automatically for \f[C]textile\f[] input.
5072−.SS Extension: \f[C]angle_brackets_escapable\f[]
5103+This option only has an effect if \f[C]smart\f[R] is enabled.
5104+It is selected automatically for \f[C]textile\f[R] input.
5105+.SS Extension: \f[C]angle_brackets_escapable\f[R]
50735106.PP
5074−Allow \f[C]<\f[] and \f[C]>\f[] to be backslash\-escaped, as they can be
5075−in GitHub flavored Markdown but not original Markdown.
5076−This is implied by pandoc\[aq]s default \f[C]all_symbols_escapable\f[].
5077−.SS Extension: \f[C]lists_without_preceding_blankline\f[]
5107+Allow \f[C]<\f[R] and \f[C]>\f[R] to be backslash\-escaped, as they can
5108+be in GitHub flavored Markdown but not original Markdown.
5109+This is implied by pandoc\[aq]s default \f[C]all_symbols_escapable\f[R].
5110+.SS Extension: \f[C]lists_without_preceding_blankline\f[R]
50785111.PP
50795112Allow a list to occur right after a paragraph, with no intervening blank
50805113space.
5081−.SS Extension: \f[C]four_space_rule\f[]
5114+.SS Extension: \f[C]four_space_rule\f[R]
50825115.PP
50835116Selects the pandoc <= 2.0 behavior for parsing lists, so that four
50845117spaces indent are needed for list item continuation paragraphs.
5085−.SS Extension: \f[C]spaced_reference_links\f[]
5118+.SS Extension: \f[C]spaced_reference_links\f[R]
50865119.PP
50875120Allow whitespace between the two components of a reference link, for
50885121example,
@@ -5090,49 +5123,50 @@ example,
50905123.nf
50915124\f[C]
50925125[foo]\ [bar].
5093−\f[]
5126+\f[R]
50945127.fi
5095−.SS Extension: \f[C]hard_line_breaks\f[]
5128+.SS Extension: \f[C]hard_line_breaks\f[R]
50965129.PP
50975130Causes all newlines within a paragraph to be interpreted as hard line
50985131breaks instead of spaces.
5099−.SS Extension: \f[C]ignore_line_breaks\f[]
5132+.SS Extension: \f[C]ignore_line_breaks\f[R]
51005133.PP
51015134Causes newlines within a paragraph to be ignored, rather than being
51025135treated as spaces or as hard line breaks.
51035136This option is intended for use with East Asian languages where spaces
51045137are not used between words, but text is divided into lines for
51055138readability.
5106−.SS Extension: \f[C]east_asian_line_breaks\f[]
5139+.SS Extension: \f[C]east_asian_line_breaks\f[R]
51075140.PP
51085141Causes newlines within a paragraph to be ignored, rather than being
51095142treated as spaces or as hard line breaks, when they occur between two
51105143East Asian wide characters.
5111−This is a better choice than \f[C]ignore_line_breaks\f[] for texts that
5144+This is a better choice than \f[C]ignore_line_breaks\f[R] for texts that
51125145include a mix of East Asian wide characters and other characters.
5113−.SS Extension: \f[C]emoji\f[]
5146+.SS Extension: \f[C]emoji\f[R]
51145147.PP
5115−Parses textual emojis like \f[C]:smile:\f[] as Unicode emoticons.
5116−.SS Extension: \f[C]tex_math_single_backslash\f[]
5148+Parses textual emojis like \f[C]:smile:\f[R] as Unicode emoticons.
5149+.SS Extension: \f[C]tex_math_single_backslash\f[R]
51175150.PP
5118−Causes anything between \f[C]\\(\f[] and \f[C]\\)\f[] to be interpreted
5119−as inline TeX math, and anything between \f[C]\\[\f[] and \f[C]\\]\f[]
5120−to be interpreted as display TeX math.
5151+Causes anything between \f[C]\[rs](\f[R] and \f[C]\[rs])\f[R] to be
5152+interpreted as inline TeX math, and anything between \f[C]\[rs][\f[R]
5153+and \f[C]\[rs]]\f[R] to be interpreted as display TeX math.
51215154Note: a drawback of this extension is that it precludes escaping
5122−\f[C](\f[] and \f[C][\f[].
5123−.SS Extension: \f[C]tex_math_double_backslash\f[]
5155+\f[C](\f[R] and \f[C][\f[R].
5156+.SS Extension: \f[C]tex_math_double_backslash\f[R]
51245157.PP
5125−Causes anything between \f[C]\\\\(\f[] and \f[C]\\\\)\f[] to be
5126−interpreted as inline TeX math, and anything between \f[C]\\\\[\f[] and
5127−\f[C]\\\\]\f[] to be interpreted as display TeX math.
5128−.SS Extension: \f[C]markdown_attribute\f[]
5158+Causes anything between \f[C]\[rs]\[rs](\f[R] and \f[C]\[rs]\[rs])\f[R]
5159+to be interpreted as inline TeX math, and anything between
5160+\f[C]\[rs]\[rs][\f[R] and \f[C]\[rs]\[rs]]\f[R] to be interpreted as
5161+display TeX math.
5162+.SS Extension: \f[C]markdown_attribute\f[R]
51295163.PP
51305164By default, pandoc interprets material inside block\-level tags as
51315165Markdown.
51325166This extension changes the behavior so that Markdown is only parsed
51335167inside block\-level tags if the tags have the attribute
5134−\f[C]markdown=1\f[].
5135−.SS Extension: \f[C]mmd_title_block\f[]
5168+\f[C]markdown=1\f[R].
5169+.SS Extension: \f[C]mmd_title_block\f[R]
51365170.PP
51375171Enables a MultiMarkdown style title block at the top of the document,
51385172for example:
@@ -5144,49 +5178,49 @@ Author:\ \ John\ Doe
51445178Date:\ \ \ \ September\ 1,\ 2008
51455179Comment:\ This\ is\ a\ sample\ mmd\ title\ block,\ with
51465180\ \ \ \ \ \ \ \ \ a\ field\ spanning\ multiple\ lines.
5147−\f[]
5181+\f[R]
51485182.fi
51495183.PP
51505184See the MultiMarkdown documentation for details.
5151−If \f[C]pandoc_title_block\f[] or \f[C]yaml_metadata_block\f[] is
5152−enabled, it will take precedence over \f[C]mmd_title_block\f[].
5153−.SS Extension: \f[C]abbreviations\f[]
5185+If \f[C]pandoc_title_block\f[R] or \f[C]yaml_metadata_block\f[R] is
5186+enabled, it will take precedence over \f[C]mmd_title_block\f[R].
5187+.SS Extension: \f[C]abbreviations\f[R]
51545188.PP
51555189Parses PHP Markdown Extra abbreviation keys, like
51565190.IP
51575191.nf
51585192\f[C]
51595193*[HTML]:\ Hypertext\ Markup\ Language
5160−\f[]
5194+\f[R]
51615195.fi
51625196.PP
51635197Note that the pandoc document model does not support abbreviations, so
51645198if this extension is enabled, abbreviation keys are simply skipped (as
51655199opposed to being parsed as paragraphs).
5166−.SS Extension: \f[C]autolink_bare_uris\f[]
5200+.SS Extension: \f[C]autolink_bare_uris\f[R]
51675201.PP
51685202Makes all absolute URIs into links, even when not surrounded by pointy
5169−braces \f[C]<...>\f[].
5170−.SS Extension: \f[C]mmd_link_attributes\f[]
5203+braces \f[C]<...>\f[R].
5204+.SS Extension: \f[C]mmd_link_attributes\f[R]
51715205.PP
51725206Parses multimarkdown style key\-value attributes on link and image
51735207references.
5174−This extension should not be confused with the \f[C]link_attributes\f[]
5208+This extension should not be confused with the \f[C]link_attributes\f[R]
51755209extension.
51765210.IP
51775211.nf
51785212\f[C]
51795213This\ is\ a\ reference\ ![image][ref]\ with\ multimarkdown\ attributes.
51805214
5181−[ref]:\ http://path.to/image\ "Image\ title"\ width=20px\ height=30px
5182−\ \ \ \ \ \ \ id=myId\ class="myClass1\ myClass2"
5183−\f[]
5215+[ref]:\ http://path.to/image\ \[dq]Image\ title\[dq]\ width=20px\ height=30px
5216+\ \ \ \ \ \ \ id=myId\ class=\[dq]myClass1\ myClass2\[dq]
5217+\f[R]
51845218.fi
5185−.SS Extension: \f[C]mmd_header_identifiers\f[]
5219+.SS Extension: \f[C]mmd_header_identifiers\f[R]
51865220.PP
51875221Parses multimarkdown style header identifiers (in square brackets, after
5188−the header but before any trailing \f[C]#\f[]s in an ATX header).
5189−.SS Extension: \f[C]compact_definition_lists\f[]
5222+the header but before any trailing \f[C]#\f[R]s in an ATX header).
5223+.SS Extension: \f[C]compact_definition_lists\f[R]
51905224.PP
51915225Activates the definition list syntax of pandoc 1.12.x and earlier.
51925226This syntax differs from the one described above under Definition lists
@@ -5195,9 +5229,9 @@ in several respects:
51955229No blank line is required between consecutive items of the definition
51965230list.
51975231.IP \[bu] 2
5198−To get a "tight" or "compact" list, omit space between consecutive
5199−items; the space between a term and its definition does not affect
5200−anything.
5232+To get a \[dq]tight\[dq] or \[dq]compact\[dq] list, omit space between
5233+consecutive items; the space between a term and its definition does not
5234+affect anything.
52015235.IP \[bu] 2
52025236Lazy wrapping of paragraphs is not allowed: the entire definition must
52035237be indented four spaces.
@@ -5206,64 +5240,65 @@ be indented four spaces.
52065240In addition to pandoc\[aq]s extended Markdown, the following Markdown
52075241variants are supported:
52085242.TP
5209−.B \f[C]markdown_phpextra\f[] (PHP Markdown Extra)
5210−\f[C]footnotes\f[], \f[C]pipe_tables\f[], \f[C]raw_html\f[],
5211−\f[C]markdown_attribute\f[], \f[C]fenced_code_blocks\f[],
5212−\f[C]definition_lists\f[], \f[C]intraword_underscores\f[],
5213−\f[C]header_attributes\f[], \f[C]link_attributes\f[],
5214−\f[C]abbreviations\f[], \f[C]shortcut_reference_links\f[],
5215−\f[C]spaced_reference_links\f[].
5243+.B \f[C]markdown_phpextra\f[R] (PHP Markdown Extra)
5244+\f[C]footnotes\f[R], \f[C]pipe_tables\f[R], \f[C]raw_html\f[R],
5245+\f[C]markdown_attribute\f[R], \f[C]fenced_code_blocks\f[R],
5246+\f[C]definition_lists\f[R], \f[C]intraword_underscores\f[R],
5247+\f[C]header_attributes\f[R], \f[C]link_attributes\f[R],
5248+\f[C]abbreviations\f[R], \f[C]shortcut_reference_links\f[R],
5249+\f[C]spaced_reference_links\f[R].
52165250.RS
52175251.RE
52185252.TP
5219−.B \f[C]markdown_github\f[] (deprecated GitHub\-Flavored Markdown)
5220−\f[C]pipe_tables\f[], \f[C]raw_html\f[], \f[C]fenced_code_blocks\f[],
5221−\f[C]gfm_auto_identifiers\f[], \f[C]ascii_identifiers\f[],
5222−\f[C]backtick_code_blocks\f[], \f[C]autolink_bare_uris\f[],
5223−\f[C]space_in_atx_header\f[], \f[C]intraword_underscores\f[],
5224−\f[C]strikeout\f[], \f[C]emoji\f[], \f[C]shortcut_reference_links\f[],
5225−\f[C]angle_brackets_escapable\f[],
5226−\f[C]lists_without_preceding_blankline\f[].
5253+.B \f[C]markdown_github\f[R] (deprecated GitHub\-Flavored Markdown)
5254+\f[C]pipe_tables\f[R], \f[C]raw_html\f[R], \f[C]fenced_code_blocks\f[R],
5255+\f[C]gfm_auto_identifiers\f[R], \f[C]ascii_identifiers\f[R],
5256+\f[C]backtick_code_blocks\f[R], \f[C]autolink_bare_uris\f[R],
5257+\f[C]space_in_atx_header\f[R], \f[C]intraword_underscores\f[R],
5258+\f[C]strikeout\f[R], \f[C]emoji\f[R],
5259+\f[C]shortcut_reference_links\f[R], \f[C]angle_brackets_escapable\f[R],
5260+\f[C]lists_without_preceding_blankline\f[R].
52275261.RS
52285262.RE
52295263.TP
5230−.B \f[C]markdown_mmd\f[] (MultiMarkdown)
5231−\f[C]pipe_tables\f[], \f[C]raw_html\f[], \f[C]markdown_attribute\f[],
5232−\f[C]mmd_link_attributes\f[], \f[C]tex_math_double_backslash\f[],
5233−\f[C]intraword_underscores\f[], \f[C]mmd_title_block\f[],
5234−\f[C]footnotes\f[], \f[C]definition_lists\f[],
5235−\f[C]all_symbols_escapable\f[], \f[C]implicit_header_references\f[],
5236−\f[C]auto_identifiers\f[], \f[C]mmd_header_identifiers\f[],
5237−\f[C]shortcut_reference_links\f[], \f[C]implicit_figures\f[],
5238−\f[C]superscript\f[], \f[C]subscript\f[], \f[C]backtick_code_blocks\f[],
5239−\f[C]spaced_reference_links\f[], \f[C]raw_attribute\f[].
5264+.B \f[C]markdown_mmd\f[R] (MultiMarkdown)
5265+\f[C]pipe_tables\f[R], \f[C]raw_html\f[R], \f[C]markdown_attribute\f[R],
5266+\f[C]mmd_link_attributes\f[R], \f[C]tex_math_double_backslash\f[R],
5267+\f[C]intraword_underscores\f[R], \f[C]mmd_title_block\f[R],
5268+\f[C]footnotes\f[R], \f[C]definition_lists\f[R],
5269+\f[C]all_symbols_escapable\f[R], \f[C]implicit_header_references\f[R],
5270+\f[C]auto_identifiers\f[R], \f[C]mmd_header_identifiers\f[R],
5271+\f[C]shortcut_reference_links\f[R], \f[C]implicit_figures\f[R],
5272+\f[C]superscript\f[R], \f[C]subscript\f[R],
5273+\f[C]backtick_code_blocks\f[R], \f[C]spaced_reference_links\f[R],
5274+\f[C]raw_attribute\f[R].
52405275.RS
52415276.RE
52425277.TP
5243−.B \f[C]markdown_strict\f[] (Markdown.pl)
5244−\f[C]raw_html\f[], \f[C]shortcut_reference_links\f[],
5245−\f[C]spaced_reference_links\f[].
5278+.B \f[C]markdown_strict\f[R] (Markdown.pl)
5279+\f[C]raw_html\f[R], \f[C]shortcut_reference_links\f[R],
5280+\f[C]spaced_reference_links\f[R].
52465281.RS
52475282.RE
52485283.PP
5249−We also support \f[C]commonmark\f[] and \f[C]gfm\f[] (GitHub\-Flavored
5284+We also support \f[C]commonmark\f[R] and \f[C]gfm\f[R] (GitHub\-Flavored
52505285Markdown, which is implemented as a set of extensions on
5251−\f[C]commonmark\f[]).
5286+\f[C]commonmark\f[R]).
52525287.PP
5253−Note, however, that \f[C]commonmark\f[] and \f[C]gfm\f[] have limited
5288+Note, however, that \f[C]commonmark\f[R] and \f[C]gfm\f[R] have limited
52545289support for extensions.
5255−Only those listed below (and \f[C]smart\f[] and \f[C]raw_tex\f[]) will
5290+Only those listed below (and \f[C]smart\f[R] and \f[C]raw_tex\f[R]) will
52565291work.
52575292The extensions can, however, all be individually disabled.
5258−Also, \f[C]raw_tex\f[] only affects \f[C]gfm\f[] output, not input.
5293+Also, \f[C]raw_tex\f[R] only affects \f[C]gfm\f[R] output, not input.
52595294.TP
5260−.B \f[C]gfm\f[] (GitHub\-Flavored Markdown)
5261−\f[C]pipe_tables\f[], \f[C]raw_html\f[], \f[C]fenced_code_blocks\f[],
5262−\f[C]gfm_auto_identifiers\f[], \f[C]ascii_identifiers\f[],
5263−\f[C]backtick_code_blocks\f[], \f[C]autolink_bare_uris\f[],
5264−\f[C]intraword_underscores\f[], \f[C]strikeout\f[],
5265−\f[C]hard_line_breaks\f[], \f[C]emoji\f[],
5266−\f[C]shortcut_reference_links\f[], \f[C]angle_brackets_escapable\f[].
5295+.B \f[C]gfm\f[R] (GitHub\-Flavored Markdown)
5296+\f[C]pipe_tables\f[R], \f[C]raw_html\f[R], \f[C]fenced_code_blocks\f[R],
5297+\f[C]gfm_auto_identifiers\f[R], \f[C]ascii_identifiers\f[R],
5298+\f[C]backtick_code_blocks\f[R], \f[C]autolink_bare_uris\f[R],
5299+\f[C]intraword_underscores\f[R], \f[C]strikeout\f[R],
5300+\f[C]hard_line_breaks\f[R], \f[C]emoji\f[R],
5301+\f[C]shortcut_reference_links\f[R], \f[C]angle_brackets_escapable\f[R].
52675302.RS
52685303.RE
52695304.SH PRODUCING SLIDE SHOWS WITH PANDOC
@@ -5272,11 +5307,11 @@ You can use pandoc to produce an HTML + JavaScript slide presentation
52725307that can be viewed via a web browser.
52735308There are five ways to do this, using S5, DZSlides, Slidy, Slideous, or
52745309reveal.js.
5275−You can also produce a PDF slide show using LaTeX \f[C]beamer\f[], or
5310+You can also produce a PDF slide show using LaTeX \f[C]beamer\f[R], or
52765311slides shows in Microsoft PowerPoint format.
52775312.PP
52785313Here\[aq]s the Markdown source for a simple slide show,
5279−\f[C]habits.txt\f[]:
5314+\f[C]habits.txt\f[R]:
52805315.IP
52815316.nf
52825317\f[C]
@@ -5311,7 +5346,7 @@ Here\[aq]s the Markdown source for a simple slide show,
53115346
53125347\-\ Get\ in\ bed
53135348\-\ Count\ sheep
5314−\f[]
5349+\f[R]
53155350.fi
53165351.PP
53175352To produce an HTML/JavaScript slide show, simply type
@@ -5319,35 +5354,35 @@ To produce an HTML/JavaScript slide show, simply type
53195354.nf
53205355\f[C]
53215356pandoc\ \-t\ FORMAT\ \-s\ habits.txt\ \-o\ habits.html
5322−\f[]
5357+\f[R]
53235358.fi
53245359.PP
5325−where \f[C]FORMAT\f[] is either \f[C]s5\f[], \f[C]slidy\f[],
5326−\f[C]slideous\f[], \f[C]dzslides\f[], or \f[C]revealjs\f[].
5360+where \f[C]FORMAT\f[R] is either \f[C]s5\f[R], \f[C]slidy\f[R],
5361+\f[C]slideous\f[R], \f[C]dzslides\f[R], or \f[C]revealjs\f[R].
53275362.PP
53285363For Slidy, Slideous, reveal.js, and S5, the file produced by pandoc with
5329−the \f[C]\-s/\-\-standalone\f[] option embeds a link to JavaScript and
5364+the \f[C]\-s/\-\-standalone\f[R] option embeds a link to JavaScript and
53305365CSS files, which are assumed to be available at the relative path
5331−\f[C]s5/default\f[] (for S5), \f[C]slideous\f[] (for Slideous),
5332−\f[C]reveal.js\f[] (for reveal.js), or at the Slidy website at
5333−\f[C]w3.org\f[] (for Slidy).
5334−(These paths can be changed by setting the \f[C]slidy\-url\f[],
5335−\f[C]slideous\-url\f[], \f[C]revealjs\-url\f[], or \f[C]s5\-url\f[]
5366+\f[C]s5/default\f[R] (for S5), \f[C]slideous\f[R] (for Slideous),
5367+\f[C]reveal.js\f[R] (for reveal.js), or at the Slidy website at
5368+\f[C]w3.org\f[R] (for Slidy).
5369+(These paths can be changed by setting the \f[C]slidy\-url\f[R],
5370+\f[C]slideous\-url\f[R], \f[C]revealjs\-url\f[R], or \f[C]s5\-url\f[R]
53365371variables; see Variables for slides, above.) For DZSlides, the
53375372(relatively short) JavaScript and CSS are included in the file by
53385373default.
53395374.PP
5340−With all HTML slide formats, the \f[C]\-\-self\-contained\f[] option can
5341−be used to produce a single file that contains all of the data necessary
5342−to display the slide show, including linked scripts, stylesheets,
5343−images, and videos.
5375+With all HTML slide formats, the \f[C]\-\-self\-contained\f[R] option
5376+can be used to produce a single file that contains all of the data
5377+necessary to display the slide show, including linked scripts,
5378+stylesheets, images, and videos.
53445379.PP
53455380To produce a PDF slide show using beamer, type
53465381.IP
53475382.nf
53485383\f[C]
53495384pandoc\ \-t\ beamer\ habits.txt\ \-o\ habits.pdf
5350−\f[]
5385+\f[R]
53515386.fi
53525387.PP
53535388Note that a reveal.js slide show can also be converted to a PDF by
@@ -5358,16 +5393,16 @@ To produce a Powerpoint slide show, type
53585393.nf
53595394\f[C]
53605395pandoc\ habits.txt\ \-o\ habits.pptx
5361−\f[]
5396+\f[R]
53625397.fi
53635398.SS Structuring the slide show
53645399.PP
5365−By default, the \f[I]slide level\f[] is the highest header level in the
5400+By default, the \f[I]slide level\f[R] is the highest header level in the
53665401hierarchy that is followed immediately by content, and not another
53675402header, somewhere in the document.
53685403In the example above, level 1 headers are always followed by level 2
53695404headers, which are followed by content, so 2 is the slide level.
5370−This default can be overridden using the \f[C]\-\-slide\-level\f[]
5405+This default can be overridden using the \f[C]\-\-slide\-level\f[R]
53715406option.
53725407.PP
53735408The document is carved up into slides according to the following rules:
@@ -5376,14 +5411,14 @@ A horizontal rule always starts a new slide.
53765411.IP \[bu] 2
53775412A header at the slide level always starts a new slide.
53785413.IP \[bu] 2
5379−Headers \f[I]below\f[] the slide level in the hierarchy create headers
5380−\f[I]within\f[] a slide.
5414+Headers \f[I]below\f[R] the slide level in the hierarchy create headers
5415+\f[I]within\f[R] a slide.
53815416.IP \[bu] 2
5382−Headers \f[I]above\f[] the slide level in the hierarchy create "title
5383−slides," which just contain the section title and help to break the
5384−slide show into sections.
5417+Headers \f[I]above\f[R] the slide level in the hierarchy create
5418+\[dq]title slides,\[dq] which just contain the section title and help to
5419+break the slide show into sections.
53855420.IP \[bu] 2
5386−Content \f[I]above\f[] the slide level will not appear in the slide
5421+Content \f[I]above\f[R] the slide level will not appear in the slide
53875422show.
53885423.IP \[bu] 2
53895424A title page is constructed automatically from the document\[aq]s title
@@ -5404,13 +5439,13 @@ It is not recommended that you use deeper nesting of section levels with
54045439reveal.js.
54055440.SS Incremental lists
54065441.PP
5407−By default, these writers produce lists that display "all at once." If
5408−you want your lists to display incrementally (one item at a time), use
5409−the \f[C]\-i\f[] option.
5442+By default, these writers produce lists that display \[dq]all at
5443+once.\[dq] If you want your lists to display incrementally (one item at
5444+a time), use the \f[C]\-i\f[R] option.
54105445If you want a particular list to depart from the default, put it in a
5411−\f[C]div\f[] block with class \f[C]incremental\f[] or
5412−\f[C]nonincremental\f[].
5413−So, for example, using the \f[C]fenced\ div\f[] syntax, the following
5446+\f[C]div\f[R] block with class \f[C]incremental\f[R] or
5447+\f[C]nonincremental\f[R].
5448+So, for example, using the \f[C]fenced\ div\f[R] syntax, the following
54145449would be incremental regardless of the document default:
54155450.IP
54165451.nf
@@ -5421,7 +5456,7 @@ would be incremental regardless of the document default:
54215456\-\ Drink\ wine
54225457
54235458:::
5424−\f[]
5459+\f[R]
54255460.fi
54265461.PP
54275462or
@@ -5434,29 +5469,29 @@ or
54345469\-\ Drink\ wine
54355470
54365471:::
5437−\f[]
5472+\f[R]
54385473.fi
54395474.PP
5440−While using \f[C]incremental\f[] and \f[C]nonincremental\f[] divs are
5475+While using \f[C]incremental\f[R] and \f[C]nonincremental\f[R] divs are
54415476the recommended method of setting incremental lists on a per\-case
54425477basis, an older method is also supported: putting lists inside a
54435478blockquote will depart from the document default (that is, it will
5444−display incrementally without the \f[C]\-i\f[] option and all at once
5445−with the \f[C]\-i\f[] option):
5479+display incrementally without the \f[C]\-i\f[R] option and all at once
5480+with the \f[C]\-i\f[R] option):
54465481.IP
54475482.nf
54485483\f[C]
54495484>\ \-\ Eat\ spaghetti
54505485>\ \-\ Drink\ wine
5451−\f[]
5486+\f[R]
54525487.fi
54535488.PP
54545489Both methods allow incremental and nonincremental lists to be mixed in a
54555490single document.
54565491.SS Inserting pauses
54575492.PP
5458−You can add "pauses" within a slide by including a paragraph containing
5459−three dots, separated by spaces:
5493+You can add \[dq]pauses\[dq] within a slide by including a paragraph
5494+containing three dots, separated by spaces:
54605495.IP
54615496.nf
54625497\f[C]
@@ -5467,17 +5502,17 @@ content\ before\ the\ pause
54675502\&.\ .\ .
54685503
54695504content\ after\ the\ pause
5470−\f[]
5505+\f[R]
54715506.fi
54725507.SS Styling the slides
54735508.PP
54745509You can change the style of HTML slides by putting customized CSS files
5475−in \f[C]$DATADIR/s5/default\f[] (for S5), \f[C]$DATADIR/slidy\f[] (for
5476−Slidy), or \f[C]$DATADIR/slideous\f[] (for Slideous), where
5477−\f[C]$DATADIR\f[] is the user data directory (see
5478−\f[C]\-\-data\-dir\f[], above).
5510+in \f[C]$DATADIR/s5/default\f[R] (for S5), \f[C]$DATADIR/slidy\f[R] (for
5511+Slidy), or \f[C]$DATADIR/slideous\f[R] (for Slideous), where
5512+\f[C]$DATADIR\f[R] is the user data directory (see
5513+\f[C]\-\-data\-dir\f[R], above).
54795514The originals may be found in pandoc\[aq]s system data directory
5480−(generally \f[C]$CABALDIR/pandoc\-VERSION/s5/default\f[]).
5515+(generally \f[C]$CABALDIR/pandoc\-VERSION/s5/default\f[R]).
54815516Pandoc will look there for any files it does not find in the user data
54825517directory.
54835518.PP
@@ -5485,40 +5520,40 @@ For dzslides, the CSS is included in the HTML file itself, and may be
54855520modified there.
54865521.PP
54875522All reveal.js configuration options can be set through variables.
5488−For example, themes can be used by setting the \f[C]theme\f[] variable:
5523+For example, themes can be used by setting the \f[C]theme\f[R] variable:
54895524.IP
54905525.nf
54915526\f[C]
54925527\-V\ theme=moon
5493−\f[]
5528+\f[R]
54945529.fi
54955530.PP
5496−Or you can specify a custom stylesheet using the \f[C]\-\-css\f[]
5531+Or you can specify a custom stylesheet using the \f[C]\-\-css\f[R]
54975532option.
54985533.PP
5499−To style beamer slides, you can specify a \f[C]theme\f[],
5500−\f[C]colortheme\f[], \f[C]fonttheme\f[], \f[C]innertheme\f[], and
5501−\f[C]outertheme\f[], using the \f[C]\-V\f[] option:
5534+To style beamer slides, you can specify a \f[C]theme\f[R],
5535+\f[C]colortheme\f[R], \f[C]fonttheme\f[R], \f[C]innertheme\f[R], and
5536+\f[C]outertheme\f[R], using the \f[C]\-V\f[R] option:
55025537.IP
55035538.nf
55045539\f[C]
55055540pandoc\ \-t\ beamer\ habits.txt\ \-V\ theme:Warsaw\ \-o\ habits.pdf
5506−\f[]
5541+\f[R]
55075542.fi
55085543.PP
55095544Note that header attributes will turn into slide attributes (on a
5510−\f[C]<div>\f[] or \f[C]<section>\f[]) in HTML slide formats, allowing
5545+\f[C]<div>\f[R] or \f[C]<section>\f[R]) in HTML slide formats, allowing
55115546you to style individual slides.
55125547In beamer, the only header attribute that affects slides is the
5513−\f[C]allowframebreaks\f[] class, which sets the
5514−\f[C]allowframebreaks\f[] option, causing multiple slides to be created
5548+\f[C]allowframebreaks\f[R] class, which sets the
5549+\f[C]allowframebreaks\f[R] option, causing multiple slides to be created
55155550if the content overfills the frame.
55165551This is recommended especially for bibliographies:
55175552.IP
55185553.nf
55195554\f[C]
55205555#\ References\ {.allowframebreaks}
5521−\f[]
5556+\f[R]
55225557.fi
55235558.SS Speaker notes
55245559.PP
@@ -5535,10 +5570,10 @@ This\ is\ my\ note.
55355570\-\ like\ this\ list
55365571
55375572:::
5538−\f[]
5573+\f[R]
55395574.fi
55405575.PP
5541−To show the notes window in reveal.js, press \f[C]s\f[] while viewing
5576+To show the notes window in reveal.js, press \f[C]s\f[R] while viewing
55425577the presentation.
55435578Speaker notes in PowerPoint will be available, as usual, in handouts and
55445579presenter view.
@@ -5548,68 +5583,68 @@ not appear on the slides themselves.
55485583.SS Columns
55495584.PP
55505585To put material in side by side columns, you can use a native div
5551−container with class \f[C]columns\f[], containing two or more div
5552−containers with class \f[C]column\f[] and a \f[C]width\f[] attribute:
5586+container with class \f[C]columns\f[R], containing two or more div
5587+containers with class \f[C]column\f[R] and a \f[C]width\f[R] attribute:
55535588.IP
55545589.nf
55555590\f[C]
55565591::::::::::::::\ {.columns}
5557−:::\ {.column\ width="40%"}
5592+:::\ {.column\ width=\[dq]40%\[dq]}
55585593contents...
55595594:::
5560−:::\ {.column\ width="60%"}
5595+:::\ {.column\ width=\[dq]60%\[dq]}
55615596contents...
55625597:::
55635598::::::::::::::
5564−\f[]
5599+\f[R]
55655600.fi
55665601.SS Frame attributes in beamer
55675602.PP
5568−Sometimes it is necessary to add the LaTeX \f[C][fragile]\f[] option to
5569−a frame in beamer (for example, when using the \f[C]minted\f[]
5603+Sometimes it is necessary to add the LaTeX \f[C][fragile]\f[R] option to
5604+a frame in beamer (for example, when using the \f[C]minted\f[R]
55705605environment).
5571−This can be forced by adding the \f[C]fragile\f[] class to the header
5606+This can be forced by adding the \f[C]fragile\f[R] class to the header
55725607introducing the slide:
55735608.IP
55745609.nf
55755610\f[C]
55765611#\ Fragile\ slide\ {.fragile}
5577−\f[]
5612+\f[R]
55785613.fi
55795614.PP
55805615All of the other frame attributes described in Section 8.1 of the Beamer
5581−User\[aq]s Guide may also be used: \f[C]allowdisplaybreaks\f[],
5582−\f[C]allowframebreaks\f[], \f[C]b\f[], \f[C]c\f[], \f[C]t\f[],
5583−\f[C]environment\f[], \f[C]label\f[], \f[C]plain\f[], \f[C]shrink\f[],
5584−\f[C]standout\f[], \f[C]noframenumbering\f[].
5616+User\[aq]s Guide may also be used: \f[C]allowdisplaybreaks\f[R],
5617+\f[C]allowframebreaks\f[R], \f[C]b\f[R], \f[C]c\f[R], \f[C]t\f[R],
5618+\f[C]environment\f[R], \f[C]label\f[R], \f[C]plain\f[R],
5619+\f[C]shrink\f[R], \f[C]standout\f[R], \f[C]noframenumbering\f[R].
55855620.SS Background in reveal.js and beamer
55865621.PP
55875622Background images can be added to self\-contained reveal.js slideshows
55885623and to beamer slideshows.
55895624.PP
55905625For the same image on every slide, use the configuration option
5591−\f[C]background\-image\f[] either in the YAML metadata block or as a
5626+\f[C]background\-image\f[R] either in the YAML metadata block or as a
55925627command\-line variable.
55935628(There are no other options in beamer and the rest of this section
55945629concerns reveal.js slideshows.)
55955630.PP
55965631For reveal.js, you can instead use the reveal.js\-native option
5597−\f[C]parallaxBackgroundImage\f[].
5598−You can also set \f[C]parallaxBackgroundHorizontal\f[] and
5599−\f[C]parallaxBackgroundVertical\f[] the same way and must also set
5600−\f[C]parallaxBackgroundSize\f[] to have your values take effect.
5632+\f[C]parallaxBackgroundImage\f[R].
5633+You can also set \f[C]parallaxBackgroundHorizontal\f[R] and
5634+\f[C]parallaxBackgroundVertical\f[R] the same way and must also set
5635+\f[C]parallaxBackgroundSize\f[R] to have your values take effect.
56015636.PP
56025637To set an image for a particular reveal.js slide, add
5603−\f[C]{data\-background\-image="/path/to/image"}\f[] to the first
5604−slide\-level header on the slide (which may even be empty).
5638+\f[C]{data\-background\-image=\[dq]/path/to/image\[dq]}\f[R] to the
5639+first slide\-level header on the slide (which may even be empty).
56055640.PP
56065641In reveal.js\[aq]s overview mode, the parallaxBackgroundImage will show
56075642up only on the first slide.
56085643.PP
56095644Other reveal.js background settings also work on individual slides,
5610−including \f[C]data\-background\-size\f[],
5611−\f[C]data\-background\-repeat\f[], \f[C]data\-background\-color\f[],
5612−\f[C]data\-transition\f[], and \f[C]data\-transition\-speed\f[].
5645+including \f[C]data\-background\-size\f[R],
5646+\f[C]data\-background\-repeat\f[R], \f[C]data\-background\-color\f[R],
5647+\f[C]data\-transition\f[R], and \f[C]data\-transition\-speed\f[R].
56135648.PP
56145649See the reveal.js documentation for more details.
56155650.PP
@@ -5626,15 +5661,15 @@ parallaxBackgroundImage:\ /path/to/my/background_image.png
56265661
56275662Slide\ 1\ has\ background_image.png\ as\ its\ background.
56285663
5629−##\ {data\-background\-image="/path/to/special_image.jpg"}
5664+##\ {data\-background\-image=\[dq]/path/to/special_image.jpg\[dq]}
56305665
56315666Slide\ 2\ has\ a\ special\ image\ for\ its\ background,\ even\ though\ the\ header\ has\ no\ content.
5632−\f[]
5667+\f[R]
56335668.fi
56345669.SH CREATING EPUBS WITH PANDOC
56355670.SS EPUB Metadata
56365671.PP
5637−EPUB metadata may be specified using the \f[C]\-\-epub\-metadata\f[]
5672+EPUB metadata may be specified using the \f[C]\-\-epub\-metadata\f[R]
56385673option, but if the source document is Markdown, it is better to use a
56395674YAML metadata block.
56405675Here is an example:
@@ -5656,168 +5691,169 @@ identifier:
56565691\-\ scheme:\ DOI
56575692\ \ text:\ doi:10.234234.234/33
56585693publisher:\ \ My\ Press
5659−rights:\ ©\ 2007\ John\ Smith,\ CC\ BY\-NC
5694+rights:\ \[co]\ 2007\ John\ Smith,\ CC\ BY\-NC
56605695ibooks:
56615696\ \ version:\ 1.3.4
56625697\&...
5663−\f[]
5698+\f[R]
56645699.fi
56655700.PP
56665701The following fields are recognized:
56675702.TP
5668−.B \f[C]identifier\f[]
5669−Either a string value or an object with fields \f[C]text\f[] and
5670−\f[C]scheme\f[].
5671−Valid values for \f[C]scheme\f[] are \f[C]ISBN\-10\f[],
5672−\f[C]GTIN\-13\f[], \f[C]UPC\f[], \f[C]ISMN\-10\f[], \f[C]DOI\f[],
5673−\f[C]LCCN\f[], \f[C]GTIN\-14\f[], \f[C]ISBN\-13\f[],
5674−\f[C]Legal\ deposit\ number\f[], \f[C]URN\f[], \f[C]OCLC\f[],
5675−\f[C]ISMN\-13\f[], \f[C]ISBN\-A\f[], \f[C]JP\f[], \f[C]OLCC\f[].
5703+.B \f[C]identifier\f[R]
5704+Either a string value or an object with fields \f[C]text\f[R] and
5705+\f[C]scheme\f[R].
5706+Valid values for \f[C]scheme\f[R] are \f[C]ISBN\-10\f[R],
5707+\f[C]GTIN\-13\f[R], \f[C]UPC\f[R], \f[C]ISMN\-10\f[R], \f[C]DOI\f[R],
5708+\f[C]LCCN\f[R], \f[C]GTIN\-14\f[R], \f[C]ISBN\-13\f[R],
5709+\f[C]Legal\ deposit\ number\f[R], \f[C]URN\f[R], \f[C]OCLC\f[R],
5710+\f[C]ISMN\-13\f[R], \f[C]ISBN\-A\f[R], \f[C]JP\f[R], \f[C]OLCC\f[R].
56765711.RS
56775712.RE
56785713.TP
5679−.B \f[C]title\f[]
5680−Either a string value, or an object with fields \f[C]file\-as\f[] and
5681−\f[C]type\f[], or a list of such objects.
5682−Valid values for \f[C]type\f[] are \f[C]main\f[], \f[C]subtitle\f[],
5683−\f[C]short\f[], \f[C]collection\f[], \f[C]edition\f[],
5684−\f[C]extended\f[].
5714+.B \f[C]title\f[R]
5715+Either a string value, or an object with fields \f[C]file\-as\f[R] and
5716+\f[C]type\f[R], or a list of such objects.
5717+Valid values for \f[C]type\f[R] are \f[C]main\f[R], \f[C]subtitle\f[R],
5718+\f[C]short\f[R], \f[C]collection\f[R], \f[C]edition\f[R],
5719+\f[C]extended\f[R].
56855720.RS
56865721.RE
56875722.TP
5688−.B \f[C]creator\f[]
5689−Either a string value, or an object with fields \f[C]role\f[],
5690−\f[C]file\-as\f[], and \f[C]text\f[], or a list of such objects.
5691−Valid values for \f[C]role\f[] are MARC relators, but pandoc will
5692−attempt to translate the human\-readable versions (like "author" and
5693−"editor") to the appropriate marc relators.
5723+.B \f[C]creator\f[R]
5724+Either a string value, or an object with fields \f[C]role\f[R],
5725+\f[C]file\-as\f[R], and \f[C]text\f[R], or a list of such objects.
5726+Valid values for \f[C]role\f[R] are MARC relators, but pandoc will
5727+attempt to translate the human\-readable versions (like \[dq]author\[dq]
5728+and \[dq]editor\[dq]) to the appropriate marc relators.
56945729.RS
56955730.RE
56965731.TP
5697−.B \f[C]contributor\f[]
5698−Same format as \f[C]creator\f[].
5732+.B \f[C]contributor\f[R]
5733+Same format as \f[C]creator\f[R].
56995734.RS
57005735.RE
57015736.TP
5702−.B \f[C]date\f[]
5703−A string value in \f[C]YYYY\-MM\-DD\f[] format.
5737+.B \f[C]date\f[R]
5738+A string value in \f[C]YYYY\-MM\-DD\f[R] format.
57045739(Only the year is necessary.) Pandoc will attempt to convert other
57055740common date formats.
57065741.RS
57075742.RE
57085743.TP
5709−.B \f[C]lang\f[] (or legacy: \f[C]language\f[])
5744+.B \f[C]lang\f[R] (or legacy: \f[C]language\f[R])
57105745A string value in BCP 47 format.
57115746Pandoc will default to the local language if nothing is specified.
57125747.RS
57135748.RE
57145749.TP
5715−.B \f[C]subject\f[]
5750+.B \f[C]subject\f[R]
57165751A string value or a list of such values.
57175752.RS
57185753.RE
57195754.TP
5720−.B \f[C]description\f[]
5755+.B \f[C]description\f[R]
57215756A string value.
57225757.RS
57235758.RE
57245759.TP
5725−.B \f[C]type\f[]
5760+.B \f[C]type\f[R]
57265761A string value.
57275762.RS
57285763.RE
57295764.TP
5730−.B \f[C]format\f[]
5765+.B \f[C]format\f[R]
57315766A string value.
57325767.RS
57335768.RE
57345769.TP
5735−.B \f[C]relation\f[]
5770+.B \f[C]relation\f[R]
57365771A string value.
57375772.RS
57385773.RE
57395774.TP
5740−.B \f[C]coverage\f[]
5775+.B \f[C]coverage\f[R]
57415776A string value.
57425777.RS
57435778.RE
57445779.TP
5745−.B \f[C]rights\f[]
5780+.B \f[C]rights\f[R]
57465781A string value.
57475782.RS
57485783.RE
57495784.TP
5750−.B \f[C]cover\-image\f[]
5785+.B \f[C]cover\-image\f[R]
57515786A string value (path to cover image).
57525787.RS
57535788.RE
57545789.TP
5755−.B \f[C]stylesheet\f[]
5790+.B \f[C]stylesheet\f[R]
57565791A string value (path to CSS stylesheet).
57575792.RS
57585793.RE
57595794.TP
5760−.B \f[C]page\-progression\-direction\f[]
5761−Either \f[C]ltr\f[] or \f[C]rtl\f[].
5762−Specifies the \f[C]page\-progression\-direction\f[] attribute for the
5763−\f[C]spine\f[] element.
5795+.B \f[C]page\-progression\-direction\f[R]
5796+Either \f[C]ltr\f[R] or \f[C]rtl\f[R].
5797+Specifies the \f[C]page\-progression\-direction\f[R] attribute for the
5798+\f[C]spine\f[R] element.
57645799.RS
57655800.RE
57665801.TP
5767−.B \f[C]ibooks\f[]
5802+.B \f[C]ibooks\f[R]
57685803iBooks\-specific metadata, with the following fields:
57695804.RS
57705805.IP \[bu] 2
5771−\f[C]version\f[]: (string)
5806+\f[C]version\f[R]: (string)
57725807.IP \[bu] 2
5773−\f[C]specified\-fonts\f[]: \f[C]true\f[]|\f[C]false\f[] (default
5774−\f[C]false\f[])
5808+\f[C]specified\-fonts\f[R]: \f[C]true\f[R]|\f[C]false\f[R] (default
5809+\f[C]false\f[R])
57755810.IP \[bu] 2
5776−\f[C]ipad\-orientation\-lock\f[]:
5777−\f[C]portrait\-only\f[]|\f[C]landscape\-only\f[]
5811+\f[C]ipad\-orientation\-lock\f[R]:
5812+\f[C]portrait\-only\f[R]|\f[C]landscape\-only\f[R]
57785813.IP \[bu] 2
5779−\f[C]iphone\-orientation\-lock\f[]:
5780−\f[C]portrait\-only\f[]|\f[C]landscape\-only\f[]
5814+\f[C]iphone\-orientation\-lock\f[R]:
5815+\f[C]portrait\-only\f[R]|\f[C]landscape\-only\f[R]
57815816.IP \[bu] 2
5782−\f[C]binding\f[]: \f[C]true\f[]|\f[C]false\f[] (default \f[C]true\f[])
5817+\f[C]binding\f[R]: \f[C]true\f[R]|\f[C]false\f[R] (default
5818+\f[C]true\f[R])
57835819.IP \[bu] 2
5784−\f[C]scroll\-axis\f[]:
5785−\f[C]vertical\f[]|\f[C]horizontal\f[]|\f[C]default\f[]
5820+\f[C]scroll\-axis\f[R]:
5821+\f[C]vertical\f[R]|\f[C]horizontal\f[R]|\f[C]default\f[R]
57865822.RE
5787−.SS The \f[C]epub:type\f[] attribute
5823+.SS The \f[C]epub:type\f[R] attribute
57885824.PP
5789−For \f[C]epub3\f[] output, you can mark up the header that corresponds
5790−to an EPUB chapter using the \f[C]epub:type\f[] attribute.
5791−For example, to set the attribute to the value \f[C]prologue\f[], use
5825+For \f[C]epub3\f[R] output, you can mark up the header that corresponds
5826+to an EPUB chapter using the \f[C]epub:type\f[R] attribute.
5827+For example, to set the attribute to the value \f[C]prologue\f[R], use
57925828this markdown:
57935829.IP
57945830.nf
57955831\f[C]
57965832#\ My\ chapter\ {epub:type=prologue}
5797−\f[]
5833+\f[R]
57985834.fi
57995835.PP
58005836Which will result in:
58015837.IP
58025838.nf
58035839\f[C]
5804−<body\ epub:type="frontmatter">
5805−\ \ <section\ epub:type="prologue">
5840+<body\ epub:type=\[dq]frontmatter\[dq]>
5841+\ \ <section\ epub:type=\[dq]prologue\[dq]>
58065842\ \ \ \ <h1>My\ chapter</h1>
5807−\f[]
5843+\f[R]
58085844.fi
58095845.PP
5810−Pandoc will output \f[C]<body\ epub:type="bodymatter">\f[], unless you
5811−use one of the following values, in which case either
5812−\f[C]frontmatter\f[] or \f[C]backmatter\f[] will be output.
5846+Pandoc will output \f[C]<body\ epub:type=\[dq]bodymatter\[dq]>\f[R],
5847+unless you use one of the following values, in which case either
5848+\f[C]frontmatter\f[R] or \f[C]backmatter\f[R] will be output.
58135849.PP
58145850.TS
58155851tab(@);
58165852l l.
58175853T{
5818−\f[C]epub:type\f[] of first section
5854+\f[C]epub:type\f[R] of first section
58195855T}@T{
5820−\f[C]epub:type\f[] of body
5856+\f[C]epub:type\f[R] of body
58215857T}
58225858_
58235859T{
@@ -5904,22 +5940,22 @@ T}
59045940.SS Linked media
59055941.PP
59065942By default, pandoc will download media referenced from any
5907−\f[C]<img>\f[], \f[C]<audio>\f[], \f[C]<video>\f[] or \f[C]<source>\f[]
5908−element present in the generated EPUB, and include it in the EPUB
5909−container, yielding a completely self\-contained EPUB.
5943+\f[C]<img>\f[R], \f[C]<audio>\f[R], \f[C]<video>\f[R] or
5944+\f[C]<source>\f[R] element present in the generated EPUB, and include it
5945+in the EPUB container, yielding a completely self\-contained EPUB.
59105946If you want to link to external media resources instead, use raw HTML in
5911−your source and add \f[C]data\-external="1"\f[] to the tag with the
5912−\f[C]src\f[] attribute.
5947+your source and add \f[C]data\-external=\[dq]1\[dq]\f[R] to the tag with
5948+the \f[C]src\f[R] attribute.
59135949For example:
59145950.IP
59155951.nf
59165952\f[C]
5917−<audio\ controls="1">
5918−\ \ <source\ src="http://example.com/music/toccata.mp3"
5919−\ \ \ \ \ \ \ \ \ \ data\-external="1"\ type="audio/mpeg">
5953+<audio\ controls=\[dq]1\[dq]>
5954+\ \ <source\ src=\[dq]http://example.com/music/toccata.mp3\[dq]
5955+\ \ \ \ \ \ \ \ \ \ data\-external=\[dq]1\[dq]\ type=\[dq]audio/mpeg\[dq]>
59205956\ \ </source>
59215957</audio>
5922−\f[]
5958+\f[R]
59235959.fi
59245960.SH SYNTAX HIGHLIGHTING
59255961.PP
@@ -5929,44 +5965,44 @@ The Haskell library skylighting is used for highlighting.
59295965Currently highlighting is supported only for HTML, EPUB, Docx, Ms, and
59305966LaTeX/PDF output.
59315967To see a list of language names that pandoc will recognize, type
5932−\f[C]pandoc\ \-\-list\-highlight\-languages\f[].
5968+\f[C]pandoc\ \-\-list\-highlight\-languages\f[R].
59335969.PP
5934−The color scheme can be selected using the \f[C]\-\-highlight\-style\f[]
5935−option.
5936−The default color scheme is \f[C]pygments\f[], which imitates the
5970+The color scheme can be selected using the
5971+\f[C]\-\-highlight\-style\f[R] option.
5972+The default color scheme is \f[C]pygments\f[R], which imitates the
59375973default color scheme used by the Python library pygments (though
59385974pygments is not actually used to do the highlighting).
59395975To see a list of highlight styles, type
5940−\f[C]pandoc\ \-\-list\-highlight\-styles\f[].
5976+\f[C]pandoc\ \-\-list\-highlight\-styles\f[R].
59415977.PP
59425978If you are not satisfied with the predefined styles, you can use
5943−\f[C]\-\-print\-highlight\-style\f[] to generate a JSON
5944−\f[C]\&.theme\f[] file which can be modified and used as the argument to
5945−\f[C]\-\-highlight\-style\f[].
5946−To get a JSON version of the \f[C]pygments\f[] style, for example:
5979+\f[C]\-\-print\-highlight\-style\f[R] to generate a JSON
5980+\f[C]\&.theme\f[R] file which can be modified and used as the argument
5981+to \f[C]\-\-highlight\-style\f[R].
5982+To get a JSON version of the \f[C]pygments\f[R] style, for example:
59475983.IP
59485984.nf
59495985\f[C]
59505986pandoc\ \-\-print\-highlight\-style\ pygments\ >\ my.theme
5951−\f[]
5987+\f[R]
59525988.fi
59535989.PP
5954−Then edit \f[C]my.theme\f[] and use it like this:
5990+Then edit \f[C]my.theme\f[R] and use it like this:
59555991.IP
59565992.nf
59575993\f[C]
59585994pandoc\ \-\-highlight\-style\ my.theme
5959−\f[]
5995+\f[R]
59605996.fi
59615997.PP
59625998If you are not satisfied with the built\-in highlighting, or you want
59635999highlight a language that isn\[aq]t supported, you can use the
5964−\f[C]\-\-syntax\-definition\f[] option to load a KDE\-style XML syntax
6000+\f[C]\-\-syntax\-definition\f[R] option to load a KDE\-style XML syntax
59656001definition file.
59666002Before writing your own, have a look at KDE\[aq]s repository of syntax
59676003definitions.
59686004.PP
5969−To disable highlighting, use the \f[C]\-\-no\-highlight\f[] option.
6005+To disable highlighting, use the \f[C]\-\-no\-highlight\f[R] option.
59706006.SH CUSTOM STYLES IN DOCX
59716007.SS Input
59726008.PP
@@ -5974,16 +6010,16 @@ The docx reader, by default, only reads those styles that it can convert
59746010into pandoc elements, either by direct conversion or interpreting the
59756011derivation of the input document\[aq]s styles.
59766012.PP
5977−By enabling the \f[C]styles\f[] extension in the docx reader
5978−(\f[C]\-f\ docx+styles\f[]), you can produce output that maintains the
5979−styles of the input document, using the \f[C]custom\-style\f[] class.
6013+By enabling the \f[C]styles\f[R] extension in the docx reader
6014+(\f[C]\-f\ docx+styles\f[R]), you can produce output that maintains the
6015+styles of the input document, using the \f[C]custom\-style\f[R] class.
59806016Paragraph styles are interpreted as divs, while character styles are
59816017interpreted as spans.
59826018.PP
5983−For example, using the \f[C]custom\-style\-reference.docx\f[] file in
6019+For example, using the \f[C]custom\-style\-reference.docx\f[R] file in
59846020the test directory, we have the following different outputs:
59856021.PP
5986−Without the \f[C]+styles\f[] extension:
6022+Without the \f[C]+styles\f[R] extension:
59876023.IP
59886024.nf
59896025\f[C]
@@ -5994,7 +6030,7 @@ This\ is\ text\ with\ an\ *emphasized*\ text\ style.\ And\ this\ is\ text\ with\
59946030**strengthened**\ text\ style.
59956031
59966032>\ Here\ is\ a\ styled\ paragraph\ that\ inherits\ from\ Block\ Text.
5997−\f[]
6033+\f[R]
59986034.fi
59996035.PP
60006036And with the extension:
@@ -6003,20 +6039,20 @@ And with the extension:
60036039\f[C]
60046040$\ pandoc\ test/docx/custom\-style\-reference.docx\ \-f\ docx+styles\ \-t\ markdown
60056041
6006−:::\ {custom\-style="FirstParagraph"}
6042+:::\ {custom\-style=\[dq]FirstParagraph\[dq]}
60076043This\ is\ some\ text.
60086044:::
60096045
6010−:::\ {custom\-style="BodyText"}
6011−This\ is\ text\ with\ an\ [emphasized]{custom\-style="Emphatic"}\ text\ style.
6012−And\ this\ is\ text\ with\ a\ [strengthened]{custom\-style="Strengthened"}
6046+:::\ {custom\-style=\[dq]BodyText\[dq]}
6047+This\ is\ text\ with\ an\ [emphasized]{custom\-style=\[dq]Emphatic\[dq]}\ text\ style.
6048+And\ this\ is\ text\ with\ a\ [strengthened]{custom\-style=\[dq]Strengthened\[dq]}
60136049text\ style.
60146050:::
60156051
6016−:::\ {custom\-style="MyBlockStyle"}
6052+:::\ {custom\-style=\[dq]MyBlockStyle\[dq]}
60176053>\ Here\ is\ a\ styled\ paragraph\ that\ inherits\ from\ Block\ Text.
60186054:::
6019−\f[]
6055+\f[R]
60206056.fi
60216057.PP
60226058With these custom styles, you can use your input document as a
@@ -6028,38 +6064,38 @@ By default, pandoc\[aq]s docx output applies a predefined set of styles
60286064for blocks such as paragraphs and block quotes, and uses largely default
60296065formatting (italics, bold) for inlines.
60306066This will work for most purposes, especially alongside a
6031−\f[C]reference.docx\f[] file.
6067+\f[C]reference.docx\f[R] file.
60326068However, if you need to apply your own styles to blocks, or match a
60336069preexisting set of styles, pandoc allows you to define custom styles for
6034−blocks and text using \f[C]div\f[]s and \f[C]span\f[]s, respectively.
6070+blocks and text using \f[C]div\f[R]s and \f[C]span\f[R]s, respectively.
60356071.PP
6036−If you define a \f[C]div\f[] or \f[C]span\f[] with the attribute
6037−\f[C]custom\-style\f[], pandoc will apply your specified style to the
6072+If you define a \f[C]div\f[R] or \f[C]span\f[R] with the attribute
6073+\f[C]custom\-style\f[R], pandoc will apply your specified style to the
60386074contained elements.
6039−So, for example using the \f[C]bracketed_spans\f[] syntax,
6075+So, for example using the \f[C]bracketed_spans\f[R] syntax,
60406076.IP
60416077.nf
60426078\f[C]
6043−[Get\ out]{custom\-style="Emphatically"},\ he\ said.
6044−\f[]
6079+[Get\ out]{custom\-style=\[dq]Emphatically\[dq]},\ he\ said.
6080+\f[R]
60456081.fi
60466082.PP
6047−would produce a docx file with "Get out" styled with character style
6048−\f[C]Emphatically\f[].
6049−Similarly, using the \f[C]fenced_divs\f[] syntax,
6083+would produce a docx file with \[dq]Get out\[dq] styled with character
6084+style \f[C]Emphatically\f[R].
6085+Similarly, using the \f[C]fenced_divs\f[R] syntax,
60506086.IP
60516087.nf
60526088\f[C]
60536089Dickinson\ starts\ the\ poem\ simply:
60546090
6055−:::\ {custom\-style="Poetry"}
6091+:::\ {custom\-style=\[dq]Poetry\[dq]}
60566092|\ A\ Bird\ came\ down\ the\ Walk\-\-\-
60576093|\ He\ did\ not\ know\ I\ saw\-\-\-
60586094:::
6059−\f[]
6095+\f[R]
60606096.fi
60616097.PP
6062−would style the two contained lines with the \f[C]Poetry\f[] paragraph
6098+would style the two contained lines with the \f[C]Poetry\f[R] paragraph
60636099style.
60646100.PP
60656101If the styles are not yet in your reference.docx, they will be defined
@@ -6070,10 +6106,10 @@ This feature allows for greatest customization in conjunction with
60706106pandoc filters.
60716107If you want all paragraphs after block quotes to be indented, you can
60726108write a filter to apply the styles necessary.
6073−If you want all italics to be transformed to the \f[C]Emphasis\f[]
6109+If you want all italics to be transformed to the \f[C]Emphasis\f[R]
60746110character style (perhaps to change their color), you can write a filter
60756111which will transform all italicized inlines to inlines within an
6076−\f[C]Emphasis\f[] custom\-style \f[C]span\f[].
6112+\f[C]Emphasis\f[R] custom\-style \f[C]span\f[R].
60776113.SH CUSTOM WRITERS
60786114.PP
60796115Pandoc can be extended with custom writers written in lua.
@@ -6087,7 +6123,7 @@ For example:
60876123.nf
60886124\f[C]
60896125pandoc\ \-t\ data/sample.lua
6090−\f[]
6126+\f[R]
60916127.fi
60926128.PP
60936129Creating a custom writer requires writing a lua function for each
@@ -6098,11 +6134,11 @@ needs, do
60986134.nf
60996135\f[C]
61006136pandoc\ \-\-print\-default\-data\-file\ sample.lua
6101−\f[]
6137+\f[R]
61026138.fi
61036139.SH AUTHORS
61046140.PP
6105−Copyright 2006\-2017 John MacFarlane (jgm\@berkeley.edu).
6141+Copyright 2006\-2017 John MacFarlane (jgm\[at]berkeley.edu).
61066142Released under the GPL, version 2 or greater.
61076143This software carries no warranty of any kind.
61086144(See COPYRIGHT for full copyright and warranty notices.) For a full list