aboutsummaryrefslogtreecommitdiff
path: root/pandoc-cli
diff options
context:
space:
mode:
authorJohn MacFarlane <[email protected]>2025-05-14 14:52:12 -0700
committerJohn MacFarlane <[email protected]>2025-05-14 14:52:12 -0700
commit7b1add7c739439306a57b094b3e7e04240be9fa1 (patch)
tree38ca997da191017d0b6a068d581aa08404b432e5 /pandoc-cli
parentfdec82c5d8e8fbf81f1d36eb35d622a730bcaba6 (diff)
Update manual and man pages.
Diffstat (limited to 'pandoc-cli')
-rw-r--r--pandoc-cli/man/pandoc-lua.112
-rw-r--r--pandoc-cli/man/pandoc-server.1104
-rw-r--r--pandoc-cli/man/pandoc.11789
3 files changed, 967 insertions, 938 deletions
diff --git a/pandoc-cli/man/pandoc-lua.1 b/pandoc-cli/man/pandoc-lua.1
index 17d681aaf..7a53a3775 100644
--- a/pandoc-cli/man/pandoc-lua.1
+++ b/pandoc-cli/man/pandoc-lua.1
@@ -1,13 +1,13 @@
-.\" Automatically generated by Pandoc 3.6.4
+.\" Automatically generated by Pandoc 3.7
.\"
-.TH "pandoc-lua" "1" "September 22, 2022" "pandoc 3.6.4" "Pandoc User\[cq]s Guide"
+.TH "pandoc-lua" "1" "September 22, 2022" "pandoc 3.7" "Pandoc User\[cq]s Guide"
.SH SYNOPSIS
\f[CR]pandoc\-lua\f[R] [\f[I]options\f[R]] [\f[I]script\f[R]
[\f[I]args\f[R]]]
.SH DESCRIPTION
\f[CR]pandoc\-lua\f[R] is a standalone Lua interpreter with behavior
similar to that of the standard \f[CR]lua\f[R] executable, but exposing
-all of pandoc\[cq]s Lua libraries.
+all of pandoc\(cqs Lua libraries.
All \f[CR]pandoc.*\f[R] packages, as well as the packages \f[CR]re\f[R]
and \f[CR]lpeg\f[R], are available via global variables.
Furthermore, the globals \f[CR]PANDOC_VERSION\f[R],
@@ -27,7 +27,7 @@ When called without the option \f[CR]\-E\f[R], the interpreter checks
for an environment variable \f[CR]LUA_INIT\f[R] before running any
argument.
If the variable content has the format
-\f[I]\f[CI]\[at]filename\f[I]\f[R], then \f[CR]pandoc\-lua\f[R] executes
+\f[I]\f[CI]\(atfilename\f[I]\f[R], then \f[CR]pandoc\-lua\f[R] executes
the file.
Otherwise, \f[CR]pandoc\-lua\f[R] executes the string itself.
.SH OPTIONS
@@ -69,9 +69,9 @@ Exit the interactive mode by pressing \f[CR]Ctrl\-D\f[R] or
\f[CR]Ctrl\-C\f[R], or by typing \f[CR]os.exit()\f[R].
The \f[I]Isocline\f[R] library is used for line editing.
Press \f[CR]F1\f[R] to get a list of available keybindings; the
-\f[CR]ctrl\f[R] key is abbreviated as \f[CR]\[ha]\f[R] in that list.
+\f[CR]ctrl\f[R] key is abbreviated as \f[CR]\(ha\f[R] in that list.
.SH AUTHORS
-Copyright 2023 John MacFarlane (jgm\[at]berkeley.edu) and contributors.
+Copyright 2023 John MacFarlane (jgm\(atberkeley.edu) and contributors.
Released under the GPL, version 2 or later.
This software carries no warranty of any kind.
(See COPYRIGHT for full copyright and warranty notices.)
diff --git a/pandoc-cli/man/pandoc-server.1 b/pandoc-cli/man/pandoc-server.1
index cedac1996..5d2dcee42 100644
--- a/pandoc-cli/man/pandoc-server.1
+++ b/pandoc-cli/man/pandoc-server.1
@@ -1,6 +1,6 @@
-.\" Automatically generated by Pandoc 3.6.4
+.\" Automatically generated by Pandoc 3.7
.\"
-.TH "pandoc-server" "1" "August 15, 2022" "pandoc 3.6.4" "Pandoc User\[cq]s Guide"
+.TH "pandoc-server" "1" "August 15, 2022" "pandoc 3.7" "Pandoc User\[cq]s Guide"
.SH SYNOPSIS
\f[CR]pandoc\-server\f[R] [\f[I]options\f[R]]
.SH DESCRIPTION
@@ -10,7 +10,7 @@ It can be used either as a running server or as a CGI program.
.PP
To use \f[CR]pandoc\-server\f[R] as a CGI program, rename it (or symlink
it) as \f[CR]pandoc\-server.cgi\f[R].
-(Note: if you symlink it, you may need to adjust your webserver\[cq]s
+(Note: if you symlink it, you may need to adjust your webserver\(cqs
configuration in order to allow it to follow symlinks for the CGI
script.)
.PP
@@ -18,13 +18,13 @@ All pandoc functions are run in the PandocPure monad, which ensures that
they can do no I/O operations on the server.
This should provide a high degree of security.
This security does, however, impose certain limitations:
-.IP \[bu] 2
+.IP \(bu 2
PDFs cannot be produced.
-.IP \[bu] 2
+.IP \(bu 2
Filters are not supported.
-.IP \[bu] 2
+.IP \(bu 2
Resources cannot be fetched via HTTP.
-.IP \[bu] 2
+.IP \(bu 2
Any images, include files, or other resources needed for the document
conversion must be explicitly included in the request, via the
\f[CR]files\f[R] field (see below under API).
@@ -54,11 +54,11 @@ The root (\f[CR]/\f[R]) endpoint accepts only POST requests.
.SS Response
It returns a converted document in one of the following formats (in
order of preference), depending on the \f[CR]Accept\f[R] header:
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]application/octet\-stream\f[R]
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]text/plain\f[R]
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]application/json\f[R]
.PP
If the result is a binary format (e.g., \f[CR]epub\f[R] or
@@ -69,22 +69,22 @@ If a JSON response is given, it will have one of the following formats.
If the conversion is not successful:
.IP
.EX
-{ \[dq]error\[dq]: string with the error message }
+{ \(dqerror\(dq: string with the error message }
.EE
.PP
If the conversion is successful:
.IP
.EX
-{ \[dq]output\[dq]: string with textual or base64\-encoded binary output,
- \[dq]base64\[dq]: boolean (true means the \[dq]output\[dq] is base64\-encoded),
- \[dq]messages\[dq]: array of message objects (see below) }
+{ \(dqoutput\(dq: string with textual or base64\-encoded binary output,
+ \(dqbase64\(dq: boolean (true means the \(dqoutput\(dq is base64\-encoded),
+ \(dqmessages\(dq: array of message objects (see below) }
.EE
.PP
-Each element of the \[lq]messages\[rq] array will have the format
+Each element of the \(lqmessages\(rq array will have the format
.IP
.EX
-{ \[dq]message\[dq]: string,
- \[dq]verbosity\[dq]: string (either \[dq]WARNING\[dq] or \[dq]INFO\[dq]) }
+{ \(dqmessage\(dq: string,
+ \(dqverbosity\(dq: string (either \(dqWARNING\(dq or \(dqINFO\(dq) }
.EE
.SS Request
The body of the POST request should be a JSON object, with the following
@@ -100,11 +100,11 @@ Note: if the \f[CR]from\f[R] format is binary (e.g., \f[CR]epub\f[R] or
\f[CR]docx\f[R]), then \f[CR]text\f[R] should be a base64 encoding of
the document.
.TP
-\f[CR]from\f[R] (string, default \f[CR]\[dq]markdown\[dq]\f[R])
+\f[CR]from\f[R] (string, default \f[CR]\(dqmarkdown\(dq\f[R])
The input format, possibly with extensions, just as it is specified on
the pandoc command line.
.TP
-\f[CR]to\f[R] (string, default \f[CR]\[dq]html\[dq]\f[R])
+\f[CR]to\f[R] (string, default \f[CR]\(dqhtml\(dq\f[R])
The output format, possibly with extensions, just as it is specified on
the pandoc command line.
.TP
@@ -116,7 +116,7 @@ List of classes to be applied to indented Markdown code blocks.
.TP
\f[CR]default\-image\-extension\f[R] (string)
Extension to be applied to image sources that lack extensions
-(e.g.\ \f[CR]\[dq].jpg\[dq]\f[R]).
+(e.g.\ \f[CR]\(dq.jpg\(dq\f[R]).
.TP
\f[CR]metadata\f[R] (JSON map)
String\-valued metadata.
@@ -124,9 +124,9 @@ String\-valued metadata.
\f[CR]tab\-stop\f[R] (integer, default 4)
Tab stop (spaces per tab).
.TP
-\f[CR]track\-changes\f[R] (\f[CR]\[dq]accept\[dq]|\[dq]reject\[dq]|\[dq]all\[dq]\f[R])
+\f[CR]track\-changes\f[R] (\f[CR]\(dqaccept\(dq|\(dqreject\(dq|\(dqall\(dq\f[R])
Specifies what to do with insertions, deletions, and comments produced
-by the MS Word \[lq]Track Changes\[rq] feature.
+by the MS Word \(lqTrack Changes\(rq feature.
Only affects docx input.
.TP
\f[CR]abbreviations\f[R] (file path)
@@ -150,12 +150,12 @@ Variables to be interpolated in the template.
Dots\-per\-inch to use for conversions between pixels and other
measurements (for image sizes).
.TP
-\f[CR]wrap\f[R] (\f[CR]\[dq]auto\[dq]|\[dq]preserve\[dq]|\[dq]none\[dq]\f[R])
-Text wrapping option: either \f[CR]\[dq]auto\[dq]\f[R] (automatic
+\f[CR]wrap\f[R] (\f[CR]\(dqauto\(dq|\(dqpreserve\(dq|\(dqnone\(dq\f[R])
+Text wrapping option: either \f[CR]\(dqauto\(dq\f[R] (automatic
hard\-wrapping to fit within a column width),
-\f[CR]\[dq]preserve\[dq]\f[R] (insert newlines where they are present in
-the source), or \f[CR]\[dq]none\[dq]\f[R] (don\[cq]t insert any
-unnecessary newlines at all).
+\f[CR]\(dqpreserve\(dq\f[R] (insert newlines where they are present in
+the source), or \f[CR]\(dqnone\(dq\f[R] (don\(cqt insert any unnecessary
+newlines at all).
.TP
\f[CR]columns\f[R] (integer, default 72)
Column width (affects text wrapping and calculation of table column
@@ -179,11 +179,11 @@ instead of being passed through to the output format.
.TP
\f[CR]highlight\-style\f[R] (string, leave unset for no highlighting)
Specify the style to use for syntax highlighting of code.
-Standard styles are \f[CR]\[dq]pygments\[dq]\f[R] (the default),
-\f[CR]\[dq]kate\[dq]\f[R], \f[CR]\[dq]monochrome\[dq]\f[R],
-\f[CR]\[dq]breezeDark\[dq]\f[R], \f[CR]\[dq]espresso\[dq]\f[R],
-\f[CR]\[dq]zenburn\[dq]\f[R], \f[CR]\[dq]haddock\[dq]\f[R], and
-\f[CR]\[dq]tango\[dq]\f[R].
+Standard styles are \f[CR]\(dqpygments\(dq\f[R] (the default),
+\f[CR]\(dqkate\(dq\f[R], \f[CR]\(dqmonochrome\(dq\f[R],
+\f[CR]\(dqbreezeDark\(dq\f[R], \f[CR]\(dqespresso\(dq\f[R],
+\f[CR]\(dqzenburn\(dq\f[R], \f[CR]\(dqhaddock\(dq\f[R], and
+\f[CR]\(dqtango\(dq\f[R].
Alternatively, the path of a \f[CR].theme\f[R] with a KDE syntax theme
may be used (in this case, the relevant file contents must also be
included in \f[CR]files\f[R], see below).
@@ -204,7 +204,7 @@ the output.
\f[CR]reference\-links\f[R] (boolean, default false)
Create reference links rather than inline links in Markdown output.
.TP
-\f[CR]reference\-location\f[R] (\f[CR]\[dq]document\[dq]|\[dq]section\[dq]|\[dq]block\[dq]\f[R])
+\f[CR]reference\-location\f[R] (\f[CR]\(dqdocument\(dq|\(dqsection\(dq|\(dqblock\(dq\f[R])
Determines whether link references and footnotes are placed at the end
of the document, the end of the section, or the end of the block
(e.g.\ paragraph), in certain formats.
@@ -214,10 +214,10 @@ of the document, the end of the section, or the end of the block
Use Setext (underlined) headings instead of ATX (\f[CR]#\f[R]\-prefixed)
in Markdown output.
.TP
-\f[CR]top\-level\-division\f[R] (\f[CR]\[dq]default\[dq]|\[dq]part\[dq]|\[dq]chapter\[dq]|\[dq]section\[dq]\f[R])
+\f[CR]top\-level\-division\f[R] (\f[CR]\(dqdefault\(dq|\(dqpart\(dq|\(dqchapter\(dq|\(dqsection\(dq\f[R])
Determines how top\-level headings are interpreted in LaTeX, ConTeXt,
DocBook, and TEI.
-The \f[CR]\[dq]default\[dq]\f[R] value tries to choose the best
+The \f[CR]\(dqdefault\(dq\f[R] value tries to choose the best
interpretation based on heuristics.
.TP
\f[CR]number\-sections\f[R] (boolean, default false)
@@ -226,11 +226,11 @@ Automatically number sections (in supported formats).
\f[CR]number\-offset\f[R] (array of integers)
Offsets to be added to each component of the section number.
For example, \f[CR][1]\f[R] will cause the first section to be numbered
-\[lq]2\[rq] and the first subsection \[lq]2.1\[rq]; \f[CR][0,1]\f[R]
-will cause the first section to be numbered \[lq]1\[rq] and the first
-subsection \[lq]1.2.\[rq]
+\(lq2\(rq and the first subsection \(lq2.1\(rq; \f[CR][0,1]\f[R] will
+cause the first section to be numbered \(lq1\(rq and the first
+subsection \(lq1.2.\(rq
.TP
-\f[CR]html\-math\-method\f[R] (\f[CR]\[dq]plain\[dq]|\[dq]webtex\[dq]|\[dq]gladtex\[dq]|\[dq]mathml\[dq]|\[dq]mathjax\[dq]|\[dq]katex\[dq]\f[R])
+\f[CR]html\-math\-method\f[R] (\f[CR]\(dqplain\(dq|\(dqwebtex\(dq|\(dqgladtex\(dq|\(dqmathml\(dq|\(dqmathjax\(dq|\(dqkatex\(dq\f[R])
Determines how math is represented in HTML.
.TP
\f[CR]listings\f[R] (boolean, default false)
@@ -248,7 +248,7 @@ body text.
Arrange the document into a hierarchy of nested sections based on the
headings.
.TP
-\f[CR]email\-obfuscation\f[R] (\f[CR]\[dq]none\[dq]|\[dq]references\[dq]|\[dq]javascript\[dq]\f[R])
+\f[CR]email\-obfuscation\f[R] (\f[CR]\(dqnone\(dq|\(dqreferences\(dq|\(dqjavascript\(dq\f[R])
Determines how email addresses are obfuscated in HTML.
.TP
\f[CR]identifier\-prefix\f[R] (string)
@@ -276,14 +276,14 @@ Path of file containing Dublin core XML elements to be used for EPUB
metadata.
The contents of the file must be included under \f[CR]files\f[R].
.TP
-\f[CR]epub\-subdirectory\f[R] (string, default \[lq]EPUB\[rq])
+\f[CR]epub\-subdirectory\f[R] (string, default \(lqEPUB\(rq)
Name of content subdirectory in the EPUB container.
.TP
\f[CR]epub\-fonts\f[R] (array of file paths)
Fonts to include in the EPUB.
The fonts themselves must be included in \f[CR]files\f[R] (see below).
.TP
-\f[CR]ipynb\-output\f[R] (\f[CR]\[dq]best\[dq]|\[dq]all\[dq]|\[dq]none\[dq]\f[R])
+\f[CR]ipynb\-output\f[R] (\f[CR]\(dqbest\(dq|\(dqall\(dq|\(dqnone\(dq\f[R])
Determines how ipynb output cells are treated.
\f[CR]all\f[R] means that all of the data formats included in the
original are preserved.
@@ -303,7 +303,7 @@ The contents of the files must be included in \f[CR]files\f[R].
CSL style file.
The contents of the file must be included in \f[CR]files\f[R].
.TP
-\f[CR]cite\-method\f[R] (\f[CR]\[dq]citeproc\[dq]|\[dq]natbib\[dq]|\[dq]biblatex\[dq]\f[R])
+\f[CR]cite\-method\f[R] (\f[CR]\(dqciteproc\(dq|\(dqnatbib\(dq|\(dqbiblatex\(dq\f[R])
Determines how citations are formatted in LaTeX output.
.TP
\f[CR]files\f[R] (JSON mapping of file paths to base64\-encoded strings)
@@ -315,10 +315,10 @@ base 64 data, in which case it will be interpreted that way.
.SS \f[CR]/batch\f[R] endpoint
The \f[CR]/batch\f[R] endpoint behaves like the root endpoint, except
for these two points:
-.IP \[bu] 2
+.IP \(bu 2
It accepts a JSON array, each element of which is a JSON object like the
one expected by the root endpoint.
-.IP \[bu] 2
+.IP \(bu 2
It returns a JSON array of JSON results.
.PP
This endpoint can be used to convert a sequence of small snippets in one
@@ -330,21 +330,21 @@ headers.
.SS \f[CR]/babelmark\f[R] endpoint
The \f[CR]/babelmark\f[R] endpoint accepts a GET request with the
following query parameters:
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]text\f[R] (required string)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]from\f[R] (optional string, default is
-\f[CR]\[dq]markdown\[dq]\f[R])
-.IP \[bu] 2
-\f[CR]to\f[R] (optional string, default is \f[CR]\[dq]html\[dq]\f[R])
-.IP \[bu] 2
+\f[CR]\(dqmarkdown\(dq\f[R])
+.IP \(bu 2
+\f[CR]to\f[R] (optional string, default is \f[CR]\(dqhtml\(dq\f[R])
+.IP \(bu 2
\f[CR]standalone\f[R] (optional boolean, default is \f[CR]false\f[R])
.PP
It returns a JSON object with fields \f[CR]html\f[R] and
\f[CR]version\f[R].
This endpoint is designed to support the Babelmark website.
.SH AUTHORS
-Copyright 2022 John MacFarlane (jgm\[at]berkeley.edu).
+Copyright 2022 John MacFarlane (jgm\(atberkeley.edu).
Released under the GPL, version 2 or greater.
This software carries no warranty of any kind.
(See COPYRIGHT for full copyright and warranty notices.)
diff --git a/pandoc-cli/man/pandoc.1 b/pandoc-cli/man/pandoc.1
index 4e54ebdb4..e1f4cb2d4 100644
--- a/pandoc-cli/man/pandoc.1
+++ b/pandoc-cli/man/pandoc.1
@@ -1,6 +1,6 @@
-.\" Automatically generated by Pandoc 3.6.4
+.\" Automatically generated by Pandoc 3.7
.\"
-.TH "pandoc" "1" "March 16, 2025" "pandoc 3.6.4" "Pandoc User\[cq]s Guide"
+.TH "pandoc" "1" "2025\-05\-14" "pandoc 3.7" "Pandoc User\[cq]s Guide"
.SH NAME
pandoc - general markup converter
.SH SYNOPSIS
@@ -16,10 +16,10 @@ For the full lists of input and output formats, see the
\f[CR]\-\-from\f[R] and \f[CR]\-\-to\f[R] options below.
Pandoc can also produce PDF output: see creating a PDF, below.
.PP
-Pandoc\[cq]s enhanced version of Markdown includes syntax for tables,
+Pandoc\(cqs enhanced version of Markdown includes syntax for tables,
definition lists, metadata blocks, footnotes, citations, math, and much
more.
-See below under Pandoc\[cq]s Markdown.
+See below under Pandoc\(cqs Markdown.
.PP
Pandoc has a modular design: it consists of a set of readers, which
parse text in a given format and produce a native representation of the
@@ -29,15 +29,15 @@ Thus, adding an input or output format requires only adding a reader or
writer.
Users can also run custom pandoc filters to modify the intermediate AST.
.PP
-Because pandoc\[cq]s intermediate representation of a document is less
+Because pandoc\(cqs intermediate representation of a document is less
expressive than many of the formats it converts between, one should not
expect perfect conversions between every format and every other.
Pandoc attempts to preserve the structural elements of a document, but
not formatting details such as margin size.
And some document elements, such as complex tables, may not fit into
-pandoc\[cq]s simple document model.
-While conversions from pandoc\[cq]s Markdown to all formats aspire to be
-perfect, conversions from formats more expressive than pandoc\[cq]s
+pandoc\(cqs simple document model.
+While conversions from pandoc\(cqs Markdown to all formats aspire to be
+perfect, conversions from formats more expressive than pandoc\(cqs
Markdown can be expected to be lossy.
.SS Using pandoc
If no \f[I]input\-files\f[R] are specified, input is read from
@@ -98,10 +98,10 @@ pandoc \-o hello.tex hello.txt
.PP
will convert \f[CR]hello.txt\f[R] from Markdown to LaTeX.
If no output file is specified (so that output goes to
-\f[I]stdout\f[R]), or if the output file\[cq]s extension is unknown, the
+\f[I]stdout\f[R]), or if the output file\(cqs extension is unknown, the
output format will default to HTML.
If no input file is specified (so that input comes from
-\f[I]stdin\f[R]), or if the input files\[cq] extensions are unknown, the
+\f[I]stdin\f[R]), or if the input files\(cq extensions are unknown, the
input format will be assumed to be Markdown.
.SS Character encoding
Pandoc uses the UTF\-8 character encoding for both input and output.
@@ -193,7 +193,7 @@ It is possible to supply a custom User\-Agent string or other header
when requesting a document from a URL:
.IP
.EX
-pandoc \-f html \-t markdown \-\-request\-header User\-Agent:\[dq]Mozilla/5.0\[dq] \[rs]
+pandoc \-f html \-t markdown \-\-request\-header User\-Agent:\(dqMozilla/5.0\(dq \(rs
https://www.fsf.org
.EE
.SH OPTIONS
@@ -203,101 +203,101 @@ pandoc \-f html \-t markdown \-\-request\-header User\-Agent:\[dq]Mozilla/5.0\[d
Specify input format.
\f[I]FORMAT\f[R] can be:
.RS
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]bibtex\f[R] (BibTeX bibliography)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]biblatex\f[R] (BibLaTeX bibliography)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]bits\f[R] (BITS XML, alias for \f[CR]jats\f[R])
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]commonmark\f[R] (CommonMark Markdown)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]commonmark_x\f[R] (CommonMark Markdown with extensions)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]creole\f[R] (Creole 1.0)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]csljson\f[R] (CSL JSON bibliography)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]csv\f[R] (CSV table)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]tsv\f[R] (TSV table)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]djot\f[R] (Djot markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]docbook\f[R] (DocBook)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]docx\f[R] (Word docx)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]dokuwiki\f[R] (DokuWiki markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]endnotexml\f[R] (EndNote XML bibliography)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]epub\f[R] (EPUB)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]fb2\f[R] (FictionBook2 e\-book)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]gfm\f[R] (GitHub\-Flavored Markdown), or the deprecated and less
accurate \f[CR]markdown_github\f[R]; use \f[CR]markdown_github\f[R] only
if you need extensions not supported in \f[CR]gfm\f[R].
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]haddock\f[R] (Haddock markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]html\f[R] (HTML)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]ipynb\f[R] (Jupyter notebook)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]jats\f[R] (JATS XML)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]jira\f[R] (Jira/Confluence wiki markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]json\f[R] (JSON version of native AST)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]latex\f[R] (LaTeX)
-.IP \[bu] 2
-\f[CR]markdown\f[R] (Pandoc\[cq]s Markdown)
-.IP \[bu] 2
+.IP \(bu 2
+\f[CR]markdown\f[R] (Pandoc\(cqs Markdown)
+.IP \(bu 2
\f[CR]markdown_mmd\f[R] (MultiMarkdown)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]markdown_phpextra\f[R] (PHP Markdown Extra)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]markdown_strict\f[R] (original unextended Markdown)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]mediawiki\f[R] (MediaWiki markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]man\f[R] (roff man)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]mdoc\f[R] (mdoc manual page markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]muse\f[R] (Muse)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]native\f[R] (native Haskell)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]odt\f[R] (OpenDocument text document)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]opml\f[R] (OPML)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]org\f[R] (Emacs Org mode)
-.IP \[bu] 2
-\f[CR]pod\f[R] (Perl\[cq]s Plain Old Documentation)
-.IP \[bu] 2
+.IP \(bu 2
+\f[CR]pod\f[R] (Perl\(cqs Plain Old Documentation)
+.IP \(bu 2
\f[CR]ris\f[R] (RIS bibliography)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]rtf\f[R] (Rich Text Format)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]rst\f[R] (reStructuredText)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]t2t\f[R] (txt2tags)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]textile\f[R] (Textile)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]tikiwiki\f[R] (TikiWiki markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]twiki\f[R] (TWiki markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]typst\f[R] (typst)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]vimwiki\f[R] (Vimwiki)
-.IP \[bu] 2
+.IP \(bu 2
the path of a custom Lua reader, see Custom readers and writers below
.PP
Extensions can be individually enabled or disabled by appending
@@ -311,137 +311,137 @@ See \f[CR]\-\-list\-input\-formats\f[R] and
Specify output format.
\f[I]FORMAT\f[R] can be:
.RS
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]ansi\f[R] (text with ANSI escape codes, for terminal viewing)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]asciidoc\f[R] (modern AsciiDoc as interpreted by AsciiDoctor)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]asciidoc_legacy\f[R] (AsciiDoc as interpreted by
\f[CR]asciidoc\-py\f[R]).
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]asciidoctor\f[R] (deprecated synonym for \f[CR]asciidoc\f[R])
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]beamer\f[R] (LaTeX beamer slide show)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]bibtex\f[R] (BibTeX bibliography)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]biblatex\f[R] (BibLaTeX bibliography)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]chunkedhtml\f[R] (zip archive of multiple linked HTML files)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]commonmark\f[R] (CommonMark Markdown)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]commonmark_x\f[R] (CommonMark Markdown with extensions)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]context\f[R] (ConTeXt)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]csljson\f[R] (CSL JSON bibliography)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]djot\f[R] (Djot markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]docbook\f[R] or \f[CR]docbook4\f[R] (DocBook 4)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]docbook5\f[R] (DocBook 5)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]docx\f[R] (Word docx)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]dokuwiki\f[R] (DokuWiki markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]epub\f[R] or \f[CR]epub3\f[R] (EPUB v3 book)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]epub2\f[R] (EPUB v2)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]fb2\f[R] (FictionBook2 e\-book)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]gfm\f[R] (GitHub\-Flavored Markdown), or the deprecated and less
accurate \f[CR]markdown_github\f[R]; use \f[CR]markdown_github\f[R] only
if you need extensions not supported in \f[CR]gfm\f[R].
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]haddock\f[R] (Haddock markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]html\f[R] or \f[CR]html5\f[R] (HTML, i.e.\ HTML5/XHTML polyglot
markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]html4\f[R] (XHTML 1.0 Transitional)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]icml\f[R] (InDesign ICML)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]ipynb\f[R] (Jupyter notebook)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]jats_archiving\f[R] (JATS XML, Archiving and Interchange Tag Set)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]jats_articleauthoring\f[R] (JATS XML, Article Authoring Tag Set)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]jats_publishing\f[R] (JATS XML, Journal Publishing Tag Set)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]jats\f[R] (alias for \f[CR]jats_archiving\f[R])
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]jira\f[R] (Jira/Confluence wiki markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]json\f[R] (JSON version of native AST)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]latex\f[R] (LaTeX)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]man\f[R] (roff man)
-.IP \[bu] 2
-\f[CR]markdown\f[R] (Pandoc\[cq]s Markdown)
-.IP \[bu] 2
+.IP \(bu 2
+\f[CR]markdown\f[R] (Pandoc\(cqs Markdown)
+.IP \(bu 2
\f[CR]markdown_mmd\f[R] (MultiMarkdown)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]markdown_phpextra\f[R] (PHP Markdown Extra)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]markdown_strict\f[R] (original unextended Markdown)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]markua\f[R] (Markua)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]mediawiki\f[R] (MediaWiki markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]ms\f[R] (roff ms)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]muse\f[R] (Muse)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]native\f[R] (native Haskell)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]odt\f[R] (OpenDocument text document)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]opml\f[R] (OPML)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]opendocument\f[R] (OpenDocument XML)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]org\f[R] (Emacs Org mode)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]pdf\f[R] (PDF)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]plain\f[R] (plain text)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]pptx\f[R] (PowerPoint slide show)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]rst\f[R] (reStructuredText)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]rtf\f[R] (Rich Text Format)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]texinfo\f[R] (GNU Texinfo)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]textile\f[R] (Textile)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]slideous\f[R] (Slideous HTML and JavaScript slide show)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]slidy\f[R] (Slidy HTML and JavaScript slide show)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]dzslides\f[R] (DZSlides HTML5 + JavaScript slide show)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]revealjs\f[R] (reveal.js HTML5 + JavaScript slide show)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]s5\f[R] (S5 HTML and JavaScript slide show)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]tei\f[R] (TEI Simple)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]typst\f[R] (typst)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]xwiki\f[R] (XWiki markup)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]zimwiki\f[R] (ZimWiki markup)
-.IP \[bu] 2
+.IP \(bu 2
the path of a custom Lua writer, see Custom readers and writers below
.PP
Note that \f[CR]odt\f[R], \f[CR]docx\f[R], \f[CR]epub\f[R], and
@@ -477,12 +477,12 @@ subdirectory of the XDG data directory (by default,
If that directory does not exist and \f[CR]$HOME/.pandoc\f[R] exists, it
will be used (for backwards compatibility).
On Windows the default user data directory is
-\f[CR]%APPDATA%\[rs]pandoc\f[R].
+\f[CR]%APPDATA%\(rspandoc\f[R].
You can find the default user data directory on your system by looking
at the output of \f[CR]pandoc \-\-version\f[R].
Data files placed in this directory (for example,
\f[CR]reference.odt\f[R], \f[CR]reference.docx\f[R],
-\f[CR]epub.css\f[R], \f[CR]templates\f[R]) will override pandoc\[cq]s
+\f[CR]epub.css\f[R], \f[CR]templates\f[R]) will override pandoc\(cqs
normal defaults.
(Note that the user data directory is not created by pandoc, so you will
need to create it yourself if you want to make use of it.)
@@ -508,7 +508,7 @@ To enable bash completion with pandoc, add this to your
.RS
.IP
.EX
-eval \[dq]$(pandoc \-\-bash\-completion)\[dq]
+eval \(dq$(pandoc \-\-bash\-completion)\(dq
.EE
.RE
.TP
@@ -536,7 +536,7 @@ List supported output formats, one per line.
List supported extensions for \f[I]FORMAT\f[R], one per line, preceded
by a \f[CR]+\f[R] or \f[CR]\-\f[R] indicating whether it is enabled by
default in \f[I]FORMAT\f[R].
-If \f[I]FORMAT\f[R] is not specified, defaults for pandoc\[cq]s Markdown
+If \f[I]FORMAT\f[R] is not specified, defaults for pandoc\(cqs Markdown
are given.
.TP
\f[CR]\-\-list\-highlight\-languages\f[R]
@@ -575,7 +575,7 @@ Use \f[CI]\-\-shift\-heading\-level\-by\f[I]=X instead, where X = NUMBER
\- 1.\f[R] Specify the base level for headings (defaults to 1).
.TP
\f[CR]\-\-indented\-code\-classes=\f[R]\f[I]CLASSES\f[R]
-Specify classes to use for indented code blocks\[em]for example,
+Specify classes to use for indented code blocks\(emfor example,
\f[CR]perl,numberLines\f[R] or \f[CR]haskell\f[R].
Multiple classes may be separated by spaces or commas.
.TP
@@ -607,7 +607,7 @@ For example, a header with identifier \f[CR]foo\f[R] in
Specify an executable to be used as a filter transforming the pandoc AST
after the input is parsed and before the output is written.
The executable should read JSON from stdin and write JSON to stdout.
-The JSON must be formatted like pandoc\[cq]s own JSON input and output.
+The JSON must be formatted like pandoc\(cqs own JSON input and output.
The name of the output format will be passed to the filter as the first
argument.
Hence,
@@ -649,7 +649,7 @@ specified on the command line.
.TP
\f[CR]\-L\f[R] \f[I]SCRIPT\f[R], \f[CR]\-\-lua\-filter=\f[R]\f[I]SCRIPT\f[R]
Transform the document in a similar fashion as JSON filters (see
-\f[CR]\-\-filter\f[R]), but use pandoc\[cq]s built\-in Lua filtering
+\f[CR]\-\-filter\f[R]), but use pandoc\(cqs built\-in Lua filtering
system.
The given Lua script is expected to return a list of Lua filters which
will be applied in order.
@@ -660,7 +660,7 @@ applied.
.PP
The \f[CR]pandoc\f[R] Lua module provides helper functions for element
creation.
-It is always loaded into the script\[cq]s Lua environment.
+It is always loaded into the script\(cqs Lua environment.
.PP
See the Lua filters documentation for further details.
.PP
@@ -694,7 +694,7 @@ This option can be used with every input format, but string scalars in
the metadata file will always be parsed as Markdown.
(If the input format is Markdown or a Markdown variant, then the same
variant will be used to parse the metadata file; if it is a
-non\-Markdown format, pandoc\[cq]s default Markdown extensions will be
+non\-Markdown format, pandoc\(cqs default Markdown extensions will be
used.)
This option can be used repeatedly to include multiple metadata files;
values in files specified later on the command line will be preferred
@@ -717,7 +717,7 @@ Specify the number of spaces per tab (default is 4).
.TP
\f[CR]\-\-track\-changes=accept\f[R]|\f[CR]reject\f[R]|\f[CR]all\f[R]
Specifies what to do with insertions, deletions, and comments produced
-by the MS Word \[lq]Track Changes\[rq] feature.
+by the MS Word \(lqTrack Changes\(rq feature.
\f[CR]accept\f[R] (the default) processes all the insertions and
deletions.
\f[CR]reject\f[R] ignores them.
@@ -789,14 +789,35 @@ If this option is not used, a default template appropriate for the
output format will be used (see
\f[CR]\-D/\-\-print\-default\-template\f[R]).
.TP
-\f[CR]\-V\f[R] \f[I]KEY\f[R][\f[CR]=\f[R]\f[I]VAL\f[R]], \f[CR]\-\-variable=\f[R]\f[I]KEY\f[R][\f[CR]:\f[R]\f[I]VAL\f[R]]
+\f[CR]\-V\f[R] \f[I]KEY\f[R][\f[CR]=\f[R]\f[I]VAL\f[R]], \f[CR]\-\-variable=\f[R]\f[I]KEY\f[R][\f[CR]=\f[R]\f[I]VAL\f[R]]
Set the template variable \f[I]KEY\f[R] to the string value
\f[I]VAL\f[R] when rendering the document in standalone mode.
+Either \f[CR]:\f[R] or \f[CR]=\f[R] may be used to separate
+\f[I]KEY\f[R] from \f[I]VAL\f[R].
If no \f[I]VAL\f[R] is specified, the key will be given the value
\f[CR]true\f[R].
Structured values (lists, maps) cannot be assigned using this option,
but they can be assigned in the \f[CR]variables\f[R] section of a
-defaults file.
+defaults file or using the \f[CR]\-\-variable\-json\f[R] option.
+If the variable already has a \f[I]list\f[R] value, the value will be
+added to the list.
+If it already has another kind of value, it will be made into a list
+containing the previous and the new value.
+For example, \f[CR]\-V keyword=Joe \-V author=Sue\f[R] makes
+\f[CR]author\f[R] contain a list of strings: \f[CR]Joe\f[R] and
+\f[CR]Sue\f[R].
+.TP
+\f[CR]\-\-variable\-json=\f[R]\f[I]KEY\f[R][\f[CR]=\f[R]:\f[I]JSON\f[R]]
+Set the template variable \f[I]KEY\f[R] to the value specified by a JSON
+string (this may be a boolean, a string, a list, or a mapping; a number
+will be treated as a string).
+For example, \f[CR]\-\-variable\-json foo=false\f[R] will give
+\f[CR]foo\f[R] the boolean false value, while
+\f[CR]\-\-variable\-json foo=\(aq\(dqfalse\(dq\(aq\f[R] will give it the
+string value \f[CR]\(dqfalse\(dq\f[R].
+Either \f[CR]:\f[R] or \f[CR]=\f[R] may be used to separate
+\f[I]KEY\f[R] from \f[I]VAL\f[R].
+If the variable already has a value, this value will be replaced.
.TP
\f[CR]\-\-sandbox[=true|false]\f[R]
Run pandoc in a sandbox, limiting IO operations in readers and writers
@@ -886,10 +907,14 @@ and it has no effect on \f[CR]man\f[R], \f[CR]docbook4\f[R],
\f[CR]docbook5\f[R], or \f[CR]jats\f[R] output.
.RS
.PP
-Note that if you are producing a PDF via \f[CR]ms\f[R], the table of
-contents will appear at the beginning of the document, before the title.
+Note that if you are producing a PDF via \f[CR]ms\f[R] and using (the
+default) \f[CR]pdfroff\f[R] as a \f[CR]\-\-pdf\-engine\f[R], the table
+of contents will appear at the beginning of the document, before the
+title.
If you would prefer it to be at the end of the document, use the option
\f[CR]\-\-pdf\-engine\-opt=\-\-no\-toc\-relocation\f[R].
+If \f[CR]groff\f[R] is used as the \f[CR]\-\-pdf\-engine\f[R], the table
+of contents will always appear at the end of the document.
.RE
.TP
\f[CR]\-\-toc\-depth=\f[R]\f[I]NUMBER\f[R]
@@ -968,7 +993,7 @@ Implies \f[CR]\-\-standalone\f[R].
\f[CR]\-B\f[R] \f[I]FILE\f[R], \f[CR]\-\-include\-before\-body=\f[R]\f[I]FILE\f[R]|\f[I]URL\f[R]
Include contents of \f[I]FILE\f[R], verbatim, at the beginning of the
document body (e.g.\ after the \f[CR]<body>\f[R] tag in HTML, or the
-\f[CR]\[rs]begin{document}\f[R] command in LaTeX).
+\f[CR]\(rsbegin{document}\f[R] command in LaTeX).
This can be used to include navigation bars or banners in HTML
documents.
This option can be used repeatedly to include multiple files.
@@ -982,7 +1007,7 @@ appropriate OpenXML format.
\f[CR]\-A\f[R] \f[I]FILE\f[R], \f[CR]\-\-include\-after\-body=\f[R]\f[I]FILE\f[R]|\f[I]URL\f[R]
Include contents of \f[I]FILE\f[R], verbatim, at the end of the document
body (before the \f[CR]</body>\f[R] tag in HTML, or the
-\f[CR]\[rs]end{document}\f[R] command in LaTeX).
+\f[CR]\(rsend{document}\f[R] command in LaTeX).
This option can be used repeatedly to include multiple files.
They will be included in the order specified.
Implies \f[CR]\-\-standalone\f[R].
@@ -1016,7 +1041,7 @@ pandoc is generating LaTeX or HTML).
Set the request header \f[I]NAME\f[R] to the value \f[I]VAL\f[R] when
making HTTP requests (for example, when a URL is given on the command
line, or when resources used in a document must be downloaded).
-If you\[cq]re behind a proxy, you also need to set the environment
+If you\(cqre behind a proxy, you also need to set the environment
variable \f[CR]http_proxy\f[R] to \f[CR]http://...\f[R].
.TP
\f[CR]\-\-no\-check\-certificate[=true|false]\f[R]
@@ -1033,9 +1058,9 @@ signed).
Produce a standalone HTML file with no external dependencies, using
\f[CR]data:\f[R] URIs to incorporate the contents of linked scripts,
stylesheets, images, and videos.
-The resulting file should be \[lq]self\-contained,\[rq] in the sense
-that it needs no external files and no net access to be displayed
-properly by a browser.
+The resulting file should be \(lqself\-contained,\(rq in the sense that
+it needs no external files and no net access to be displayed properly by
+a browser.
This option works only with HTML output formats, including
\f[CR]html4\f[R], \f[CR]html5\f[R], \f[CR]html+lhs\f[R],
\f[CR]html5+lhs\f[R], \f[CR]s5\f[R], \f[CR]slidy\f[R],
@@ -1044,13 +1069,13 @@ Scripts, images, and stylesheets at absolute URLs will be downloaded;
those at relative URLs will be sought relative to the working directory
(if the first source file is local) or relative to the base URL (if the
first source file is remote).
-Elements with the attribute \f[CR]data\-external=\[dq]1\[dq]\f[R] will
-be left alone; the documents they link to will not be incorporated in
-the document.
+Elements with the attribute \f[CR]data\-external=\(dq1\(dq\f[R] will be
+left alone; the documents they link to will not be incorporated in the
+document.
Limitation: resources that are loaded dynamically through JavaScript
cannot be incorporated; as a result, fonts may be missing when
\f[CR]\-\-mathjax\f[R] is used, and some advanced features (e.g.\ zoom
-or speaker notes) may not work in an offline \[lq]self\-contained\[rq]
+or speaker notes) may not work in an offline \(lqself\-contained\(rq
\f[CR]reveal.js\f[R] slide show.
.RS
.PP
@@ -1132,7 +1157,7 @@ option is specified), \f[CR]chapter\f[R] is implied as the setting for
this option.
If \f[CR]beamer\f[R] is the output format, specifying either
\f[CR]chapter\f[R] or \f[CR]part\f[R] will cause top\-level headings to
-become \f[CR]\[rs]part{..}\f[R], while second\-level headings remain as
+become \f[CR]\(rspart{..}\f[R], while second\-level headings remain as
their default type.
.RS
.PP
@@ -1155,10 +1180,10 @@ Offsets for section heading numbers.
The first number is added to the section number for level\-1 headings,
the second for level\-2 headings, and so on.
So, for example, if you want the first level\-1 heading in your document
-to be numbered \[lq]6\[rq] instead of \[lq]1\[rq], specify
+to be numbered \(lq6\(rq instead of \(lq1\(rq, specify
\f[CR]\-\-number\-offset=5\f[R].
If your document starts with a level\-2 heading which you want to be
-numbered \[lq]1.5\[rq], specify \f[CR]\-\-number\-offset=1,4\f[R].
+numbered \(lq1.5\(rq, specify \f[CR]\-\-number\-offset=1,4\f[R].
\f[CR]\-\-number\-offset\f[R] only directly affects the number of the
first section heading in a document; subsequent numbers increment in the
normal way.
@@ -1265,87 +1290,85 @@ For best results, do not make changes to this file other than modifying
the styles used by pandoc:
.PP
Paragraph styles:
-.IP \[bu] 2
+.IP \(bu 2
Normal
-.IP \[bu] 2
+.IP \(bu 2
Body Text
-.IP \[bu] 2
+.IP \(bu 2
First Paragraph
-.IP \[bu] 2
+.IP \(bu 2
Compact
-.IP \[bu] 2
+.IP \(bu 2
Title
-.IP \[bu] 2
+.IP \(bu 2
Subtitle
-.IP \[bu] 2
+.IP \(bu 2
Author
-.IP \[bu] 2
+.IP \(bu 2
Date
-.IP \[bu] 2
+.IP \(bu 2
Abstract
-.IP \[bu] 2
+.IP \(bu 2
AbstractTitle
-.IP \[bu] 2
+.IP \(bu 2
Bibliography
-.IP \[bu] 2
+.IP \(bu 2
Heading 1
-.IP \[bu] 2
+.IP \(bu 2
Heading 2
-.IP \[bu] 2
+.IP \(bu 2
Heading 3
-.IP \[bu] 2
+.IP \(bu 2
Heading 4
-.IP \[bu] 2
+.IP \(bu 2
Heading 5
-.IP \[bu] 2
+.IP \(bu 2
Heading 6
-.IP \[bu] 2
+.IP \(bu 2
Heading 7
-.IP \[bu] 2
+.IP \(bu 2
Heading 8
-.IP \[bu] 2
+.IP \(bu 2
Heading 9
-.IP \[bu] 2
+.IP \(bu 2
Block Text [for block quotes]
-.IP \[bu] 2
+.IP \(bu 2
Footnote Block Text [for block quotes in footnotes]
-.IP \[bu] 2
+.IP \(bu 2
Source Code
-.IP \[bu] 2
+.IP \(bu 2
Footnote Text
-.IP \[bu] 2
+.IP \(bu 2
Definition Term
-.IP \[bu] 2
+.IP \(bu 2
Definition
-.IP \[bu] 2
+.IP \(bu 2
Caption
-.IP \[bu] 2
+.IP \(bu 2
Table Caption
-.IP \[bu] 2
+.IP \(bu 2
Image Caption
-.IP \[bu] 2
+.IP \(bu 2
Figure
-.IP \[bu] 2
+.IP \(bu 2
Captioned Figure
-.IP \[bu] 2
+.IP \(bu 2
TOC Heading
.PP
Character styles:
-.IP \[bu] 2
+.IP \(bu 2
Default Paragraph Font
-.IP \[bu] 2
-Body Text Char
-.IP \[bu] 2
+.IP \(bu 2
Verbatim Char
-.IP \[bu] 2
+.IP \(bu 2
Footnote Reference
-.IP \[bu] 2
+.IP \(bu 2
Hyperlink
-.IP \[bu] 2
+.IP \(bu 2
Section Number
.PP
Table style:
-.IP \[bu] 2
+.IP \(bu 2
Table
.RE
.TP
@@ -1375,19 +1398,19 @@ are most templates derived from these.
.PP
The specific requirement is that the template should contain layouts
with the following names (as seen within PowerPoint):
-.IP \[bu] 2
+.IP \(bu 2
Title Slide
-.IP \[bu] 2
+.IP \(bu 2
Title and Content
-.IP \[bu] 2
+.IP \(bu 2
Section Header
-.IP \[bu] 2
+.IP \(bu 2
Two Content
-.IP \[bu] 2
+.IP \(bu 2
Comparison
-.IP \[bu] 2
+.IP \(bu 2
Content with Caption
-.IP \[bu] 2
+.IP \(bu 2
Blank
.PP
For each name, the first layout found with that name will be used.
@@ -1418,7 +1441,7 @@ Some readers may be slow if the chapter files are too large, so for
large documents with few level\-1 headings, one might want to use a
chapter level of 2 or 3.
For chunked HTML, this option determines how much content goes in each
-\[lq]chunk.\[rq]
+\(lqchunk.\(rq
.TP
\f[CR]\-\-chunk\-template=\f[R]\f[I]PATHTEMPLATE\f[R]
Specify a template for the filenames in a \f[CR]chunkedhtml\f[R]
@@ -1429,8 +1452,8 @@ number of the chunk, \f[CR]%h\f[R] with the heading text (with
formatting removed), \f[CR]%i\f[R] with the section identifier.
For example, \f[CR]%section\-%s\-%i.html\f[R] might be resolved to
\f[CR]section\-1.1\-introduction.html\f[R].
-The characters \f[CR]/\f[R] and \f[CR]\[rs]\f[R] are not allowed in
-chunk templates and will be ignored.
+The characters \f[CR]/\f[R] and \f[CR]\(rs\f[R] are not allowed in chunk
+templates and will be ignored.
The default is \f[CR]%s\-%i.html\f[R].
.TP
\f[CR]\-\-epub\-chapter\-level=\f[R]\f[I]NUMBER\f[R]
@@ -1464,7 +1487,7 @@ By default, pandoc will include the following metadata elements:
(from the document authors), \f[CR]<dc:date>\f[R] (from the document
date, which should be in ISO 8601 format), \f[CR]<dc:language>\f[R]
(from the \f[CR]lang\f[R] variable, or, if is not set, the locale), and
-\f[CR]<dc:identifier id=\[dq]BookId\[dq]>\f[R] (a randomly generated
+\f[CR]<dc:identifier id=\(dqBookId\(dq>\f[R] (a randomly generated
UUID).
Any of these may be overridden by elements in the metadata file.
.PP
@@ -1485,31 +1508,31 @@ following to your CSS (see \f[CR]\-\-css\f[R]):
.RS
.IP
.EX
-\[at]font\-face {
+\(atfont\-face {
font\-family: DejaVuSans;
font\-style: normal;
font\-weight: normal;
- src:url(\[dq]../fonts/DejaVuSans\-Regular.ttf\[dq]);
+ src:url(\(dq../fonts/DejaVuSans\-Regular.ttf\(dq);
}
-\[at]font\-face {
+\(atfont\-face {
font\-family: DejaVuSans;
font\-style: normal;
font\-weight: bold;
- src:url(\[dq]../fonts/DejaVuSans\-Bold.ttf\[dq]);
+ src:url(\(dq../fonts/DejaVuSans\-Bold.ttf\(dq);
}
-\[at]font\-face {
+\(atfont\-face {
font\-family: DejaVuSans;
font\-style: italic;
font\-weight: normal;
- src:url(\[dq]../fonts/DejaVuSans\-Oblique.ttf\[dq]);
+ src:url(\(dq../fonts/DejaVuSans\-Oblique.ttf\(dq);
}
-\[at]font\-face {
+\(atfont\-face {
font\-family: DejaVuSans;
font\-style: italic;
font\-weight: bold;
- src:url(\[dq]../fonts/DejaVuSans\-BoldOblique.ttf\[dq]);
+ src:url(\(dq../fonts/DejaVuSans\-BoldOblique.ttf\(dq);
}
-body { font\-family: \[dq]DejaVuSans\[dq]; }
+body { font\-family: \(dqDejaVuSans\(dq; }
.EE
.RE
.TP
@@ -1533,35 +1556,44 @@ Use the specified engine when producing PDF output.
Valid values are \f[CR]pdflatex\f[R], \f[CR]lualatex\f[R],
\f[CR]xelatex\f[R], \f[CR]latexmk\f[R], \f[CR]tectonic\f[R],
\f[CR]wkhtmltopdf\f[R], \f[CR]weasyprint\f[R], \f[CR]pagedjs\-cli\f[R],
-\f[CR]prince\f[R], \f[CR]context\f[R], \f[CR]pdfroff\f[R], and
-\f[CR]typst\f[R].
+\f[CR]prince\f[R], \f[CR]context\f[R], \f[CR]groff\f[R],
+\f[CR]pdfroff\f[R], and \f[CR]typst\f[R].
If the engine is not in your PATH, the full path of the engine may be
specified here.
If this option is not specified, pandoc uses the following defaults
depending on the output format specified using \f[CR]\-t/\-\-to\f[R]:
.RS
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]\-t latex\f[R] or none: \f[CR]pdflatex\f[R] (other options:
\f[CR]xelatex\f[R], \f[CR]lualatex\f[R], \f[CR]tectonic\f[R],
\f[CR]latexmk\f[R])
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]\-t context\f[R]: \f[CR]context\f[R]
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]\-t html\f[R]: \f[CR]weasyprint\f[R] (other options:
\f[CR]prince\f[R], \f[CR]wkhtmltopdf\f[R], \f[CR]pagedjs\-cli\f[R]; see
print\-css.rocks for a good introduction to PDF generation from
HTML/CSS)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]\-t ms\f[R]: \f[CR]pdfroff\f[R]
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]\-t typst\f[R]: \f[CR]typst\f[R]
+.PP
+This option is normally intended to be used when a PDF file is specified
+as \f[CR]\-o/\-\-output\f[R].
+However, it may still have an effect when other output formats are
+requested.
+For example, \f[CR]ms\f[R] output will include \f[CR].pdfhref\f[R]
+macros only if a \f[CR]\-\-pdf\-engine\f[R] is selected, and the macros
+will be differently encoded depending on whether \f[CR]groff\f[R] or
+\f[CR]pdfroff\f[R] is specified.
.RE
.TP
\f[CR]\-\-pdf\-engine\-opt=\f[R]\f[I]STRING\f[R]
Use the given string as a command\-line argument to the
\f[CR]pdf\-engine\f[R].
For example, to use a persistent directory \f[CR]foo\f[R] for
-\f[CR]latexmk\f[R]\[cq]s auxiliary files, use
+\f[CR]latexmk\f[R]\(cqs auxiliary files, use
\f[CR]\-\-pdf\-engine\-opt=\-outdir=foo\f[R].
Note that no check for duplicate options is done.
.SS Citation rendering
@@ -1589,11 +1621,11 @@ For more information, see the section on Citations.
Note: if this option is specified, the \f[CR]citations\f[R] extension
will be disabled automatically in the writer, to ensure that the
citeproc\-generated citations will be rendered instead of the
-format\[cq]s own citation syntax.
+format\(cqs own citation syntax.
.RE
.TP
\f[CR]\-\-bibliography=\f[R]\f[I]FILE\f[R]
-Set the \f[CR]bibliography\f[R] field in the document\[cq]s metadata to
+Set the \f[CR]bibliography\f[R] field in the document\(cqs metadata to
\f[I]FILE\f[R], overriding any value set in the metadata.
If you supply this argument multiple times, each \f[I]FILE\f[R] will be
added to bibliography.
@@ -1602,7 +1634,7 @@ If \f[I]FILE\f[R] is not found relative to the working directory, it
will be sought in the resource path (see \f[CR]\-\-resource\-path\f[R]).
.TP
\f[CR]\-\-csl=\f[R]\f[I]FILE\f[R]
-Set the \f[CR]csl\f[R] field in the document\[cq]s metadata to
+Set the \f[CR]csl\f[R] field in the document\(cqs metadata to
\f[I]FILE\f[R], overriding any value set in the metadata.
(This is equivalent to \f[CR]\-\-metadata csl=FILE\f[R].)
If \f[I]FILE\f[R] is a URL, it will be fetched via HTTP.
@@ -1612,7 +1644,7 @@ and finally in the \f[CR]csl\f[R] subdirectory of the pandoc user data
directory.
.TP
\f[CR]\-\-citation\-abbreviations=\f[R]\f[I]FILE\f[R]
-Set the \f[CR]citation\-abbreviations\f[R] field in the document\[cq]s
+Set the \f[CR]citation\-abbreviations\f[R] field in the document\(cqs
metadata to \f[I]FILE\f[R], overriding any value set in the metadata.
(This is equivalent to
\f[CR]\-\-metadata citation\-abbreviations=FILE\f[R].)
@@ -1639,7 +1671,7 @@ with \f[CR]bibtex\f[R] or \f[CR]biber\f[R].
The default is to render TeX math as far as possible using Unicode
characters.
Formulas are put inside a \f[CR]span\f[R] with
-\f[CR]class=\[dq]math\[dq]\f[R], so that they may be styled differently
+\f[CR]class=\(dqmath\(dq\f[R], so that they may be styled differently
from the surrounding text if needed.
However, this gives acceptable results only for basic math, usually you
will want to use \f[CR]\-\-mathjax\f[R] or another of the following
@@ -1647,8 +1679,8 @@ options.
.TP
\f[CR]\-\-mathjax\f[R][\f[CR]=\f[R]\f[I]URL\f[R]]
Use MathJax to display embedded TeX math in HTML output.
-TeX math will be put between \f[CR]\[rs](...\[rs])\f[R] (for inline
-math) or \f[CR]\[rs][...\[rs]]\f[R] (for display math) and wrapped in
+TeX math will be put between \f[CR]\(rs(...\(rs)\f[R] (for inline math)
+or \f[CR]\(rs[...\(rs]\f[R] (for display math) and wrapped in
\f[CR]<span>\f[R] tags with class \f[CR]math\f[R].
Then the MathJax JavaScript will render it.
The \f[I]URL\f[R] should point to the \f[CR]MathJax.js\f[R] load script.
@@ -1672,7 +1704,7 @@ For SVG images you can for example use
If no URL is specified, the CodeCogs URL generating PNGs will be used
(\f[CR]https://latex.codecogs.com/png.latex?\f[R]).
Note: the \f[CR]\-\-webtex\f[R] option will affect Markdown output as
-well as HTML, which is useful if you\[cq]re targeting a version of
+well as HTML, which is useful if you\(cqre targeting a version of
Markdown without native math support.
.TP
\f[CR]\-\-katex\f[R][\f[CR]=\f[R]\f[I]URL\f[R]]
@@ -1849,35 +1881,34 @@ from stdin, and it can be an empty sequence \f[CR][]\f[R] for no input.
.IP
.EX
- command line defaults file
- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
- \-\-from markdown+emoji from: markdown+emoji
-
- reader: markdown+emoji
+ command line defaults file
+ \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+ \-\-from markdown+emoji from: markdown+emoji
+
+ reader: markdown+emoji
- to: markdown+hard_line_breaks
- \-\-to markdown+hard_line_breaks
-
- writer: markdown+hard_line_breaks
+ \-\-to markdown+hard_line_breaks to: markdown+hard_line_breaks
+
+ writer: markdown+hard_line_breaks
- \-\-output foo.pdf output\-file: foo.pdf
+ \-\-output foo.pdf output\-file: foo.pdf
- \-\-output \- output\-file:
+ \-\-output \- output\-file:
- \-\-data\-dir dir data\-dir: dir
+ \-\-data\-dir dir data\-dir: dir
- \-\-defaults file defaults:
- \- file
+ \-\-defaults file defaults:
+ \- file
- \-\-verbose verbosity: INFO
+ \-\-verbose verbosity: INFO
- \-\-quiet verbosity: ERROR
+ \-\-quiet verbosity: ERROR
- \-\-fail\-if\-warnings fail\-if\-warnings: true
+ \-\-fail\-if\-warnings fail\-if\-warnings: true
- \-\-sandbox sandbox: true
+ \-\-sandbox sandbox: true
- \-\-log=FILE log\-file: FILE
+ \-\-log=FILE log\-file: FILE
.EE
.RE
@@ -1892,44 +1923,43 @@ those in another file included with a \f[CR]defaults:\f[R] entry.
.IP
.EX
- command line defaults file
- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
- \-\-shift\-heading\-level\-by \-1 shift\-heading\-level\-by: \-1
+ command line defaults file
+ \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+ \-\-shift\-heading\-level\-by \-1 shift\-heading\-level\-by: \-1
- indented\-code\-classes:
- \-\-indented\-code\-classes python \- python
+ \-\-indented\-code\-classes python indented\-code\-classes:
+ \- python
-
- \-\-default\-image\-extension \[dq].jpg\[dq] default\-image\-extension: \[aq].jpg\[aq]
+ \-\-default\-image\-extension \(dq.jpg\(dq default\-image\-extension: \(aq.jpg\(aq
- \-\-file\-scope file\-scope: true
+ \-\-file\-scope file\-scope: true
- \-\-citeproc \[rs] filters:
- \- citeproc
- \-\-lua\-filter count\-words.lua \[rs] \- count\-words.lua
- \-\-filter special.lua \- type: json
- path: special.lua
+ \-\-citeproc \(rs filters:
+ \-\-lua\-filter count\-words.lua \(rs \- citeproc
+ \-\-filter special.lua \- count\-words.lua
+ \- type: json
+ path: special.lua
- \-\-metadata key=value \[rs] metadata:
- \-\-metadata key2 key: value
- key2: true
+ \-\-metadata key=value \(rs metadata:
+ \-\-metadata key2 key: value
+ key2: true
- \-\-metadata\-file meta.yaml metadata\-files:
- \- meta.yaml
-
- metadata\-file: meta.yaml
+ \-\-metadata\-file meta.yaml metadata\-files:
+ \- meta.yaml
+
+ metadata\-file: meta.yaml
- \-\-preserve\-tabs preserve\-tabs: true
+ \-\-preserve\-tabs preserve\-tabs: true
- \-\-tab\-stop 8 tab\-stop: 8
+ \-\-tab\-stop 8 tab\-stop: 8
- \-\-track\-changes accept track\-changes: accept
+ \-\-track\-changes accept track\-changes: accept
- \-\-extract\-media dir extract\-media: dir
+ \-\-extract\-media dir extract\-media: dir
- \-\-abbreviations abbrevs.txt abbreviations: abbrevs.txt
+ \-\-abbreviations abbrevs.txt abbreviations: abbrevs.txt
- \-\-trace trace: true
+ \-\-trace trace: true
.EE
.RE
@@ -1948,57 +1978,56 @@ or \f[CR]{type: citeproc}\f[R].
.IP
.EX
- command line defaults file
- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
- \-\-standalone standalone: true
+ command line defaults file
+ \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+ \-\-standalone standalone: true
- \-\-template letter template: letter
+ \-\-template letter template: letter
- \-\-variable key=val \[rs] variables:
- \-\-variable key2 key: val
- key2: true
+ \-\-variable key=val \(rs variables:
+ \-\-variable key2 key: val
+ key2: true
- \-\-eol nl eol: nl
+ \-\-eol nl eol: nl
- \-\-dpi 300 dpi: 300
+ \-\-dpi 300 dpi: 300
- \-\-wrap 60 wrap: 60
+ \-\-wrap 60 wrap: 60
- \-\-columns 72 columns: 72
+ \-\-columns 72 columns: 72
- \-\-table\-of\-contents table\-of\-contents: true
+ \-\-table\-of\-contents table\-of\-contents: true
- \-\-toc toc: true
+ \-\-toc toc: true
- \-\-toc\-depth 3 toc\-depth: 3
+ \-\-toc\-depth 3 toc\-depth: 3
- \-\-strip\-comments strip\-comments: true
+ \-\-strip\-comments strip\-comments: true
- \-\-no\-highlight highlight\-style: null
+ \-\-no\-highlight highlight\-style: null
- \-\-highlight\-style kate highlight\-style: kate
+ \-\-highlight\-style kate highlight\-style: kate
- syntax\-definitions:
- \-\-syntax\-definition mylang.xml \- mylang.xml
-
- syntax\-definition: mylang.xml
+ \-\-syntax\-definition mylang.xml syntax\-definitions:
+ \- mylang.xml
+
+ syntax\-definition: mylang.xml
- \-\-include\-in\-header inc.tex include\-in\-header:
- \- inc.tex
+ \-\-include\-in\-header inc.tex include\-in\-header:
+ \- inc.tex
- include\-before\-body:
-\-\-include\-before\-body inc.tex \- inc.tex
+ \-\-include\-before\-body inc.tex include\-before\-body:
+ \- inc.tex
- \-\-include\-after\-body inc.tex include\-after\-body:
- \- inc.tex
+ \-\-include\-after\-body inc.tex include\-after\-body:
+ \- inc.tex
- \-\-resource\-path .:foo resource\-path: [\[aq].\[aq],\[aq]foo\[aq]]
+ \-\-resource\-path .:foo resource\-path: [\(aq.\(aq,\(aqfoo\(aq]
- \-\-request\-header foo:bar request\-headers:
-
- \- [\[dq]User\-Agent\[dq], \[dq]Mozilla/5.0\[dq]]
+ \-\-request\-header foo:bar request\-headers:
+ \- [\(dqUser\-Agent\(dq, \(dqMozilla/5.0\(dq]
- \-\-no\-check\-certificate no\-check\-certificate: true
+ \-\-no\-check\-certificate no\-check\-certificate: true
.EE
.RE
@@ -2007,91 +2036,86 @@ or \f[CR]{type: citeproc}\f[R].
.IP
.EX
- command line defaults file
- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
- \-\-self\-contained self\-contained: true
+ command line defaults file
+ \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+ \-\-self\-contained self\-contained: true
- \-\-link\-images link\-images: true
+ \-\-link\-images link\-images: true
- \-\-html\-q\-tags html\-q\-tags: true
+ \-\-html\-q\-tags html\-q\-tags: true
- \-\-ascii ascii: true
+ \-\-ascii ascii: true
- \-\-reference\-links reference\-links: true
+ \-\-reference\-links reference\-links: true
- \-\-reference\-location block reference\-location: block
+ \-\-reference\-location block reference\-location: block
-
- \-\-figure\-caption\-position=above figure\-caption\-position: above
+ \-\-figure\-caption\-position=above figure\-caption\-position: above
- table\-caption\-position: below
- \-\-table\-caption\-position=below
+ \-\-table\-caption\-position=below table\-caption\-position: below
- \-\-markdown\-headings atx markdown\-headings: atx
+ \-\-markdown\-headings atx markdown\-headings: atx
- \-\-list\-tables list\-tables: true
+ \-\-list\-tables list\-tables: true
- \-\-top\-level\-division chapter top\-level\-division: chapter
+ \-\-top\-level\-division chapter top\-level\-division: chapter
- \-\-number\-sections number\-sections: true
+ \-\-number\-sections number\-sections: true
- \-\-number\-offset=1,4 number\-offset: \[rs][1,4\[rs]]
+ \-\-number\-offset=1,4 number\-offset: \(rs[1,4\(rs]
- \-\-listings listings: true
+ \-\-listings listings: true
- \-\-list\-of\-figures list\-of\-figures: true
+ \-\-list\-of\-figures list\-of\-figures: true
- \-\-lof lof: true
+ \-\-lof lof: true
- \-\-list\-of\-tables list\-of\-tables: true
+ \-\-list\-of\-tables list\-of\-tables: true
- \-\-lot lot: true
+ \-\-lot lot: true
- \-\-incremental incremental: true
+ \-\-incremental incremental: true
- \-\-slide\-level 2 slide\-level: 2
+ \-\-slide\-level 2 slide\-level: 2
- \-\-section\-divs section\-divs: true
+ \-\-section\-divs section\-divs: true
- email\-obfuscation: references
- \-\-email\-obfuscation references
+ \-\-email\-obfuscation references email\-obfuscation: references
- \-\-id\-prefix ch1 identifier\-prefix: ch1
+ \-\-id\-prefix ch1 identifier\-prefix: ch1
- \-\-title\-prefix MySite title\-prefix: MySite
+ \-\-title\-prefix MySite title\-prefix: MySite
- \-\-css styles/screen.css \[rs] css:
- \-\-css styles/special.css \- styles/screen.css
- \- styles/special.css
+ \-\-css styles/screen.css \(rs css:
+ \-\-css styles/special.css \- styles/screen.css
+ \- styles/special.css
- \-\-reference\-doc my.docx reference\-doc: my.docx
+ \-\-reference\-doc my.docx reference\-doc: my.docx
- \-\-epub\-cover\-image cover.jpg epub\-cover\-image: cover.jpg
+ \-\-epub\-cover\-image cover.jpg epub\-cover\-image: cover.jpg
- \-\-epub\-title\-page=false epub\-title\-page: false
+ \-\-epub\-title\-page=false epub\-title\-page: false
- \-\-epub\-metadata meta.xml epub\-metadata: meta.xml
+ \-\-epub\-metadata meta.xml epub\-metadata: meta.xml
- epub\-fonts:
- \-\-epub\-embed\-font special.otf \[rs] \- special.otf
- \- headline.otf
- \-\-epub\-embed\-font headline.otf
+ \-\-epub\-embed\-font special.otf \(rs epub\-fonts:
+ \-\-epub\-embed\-font headline.otf \- special.otf
+ \- headline.otf
- \-\-split\-level 2 split\-level: 2
+ \-\-split\-level 2 split\-level: 2
- \-\-chunk\-template=\[dq]%i.html\[dq] chunk\-template: \[dq]%i.html\[dq]
+ \-\-chunk\-template=\(dq%i.html\(dq chunk\-template: \(dq%i.html\(dq
- \-\-epub\-subdirectory=\[dq]\[dq] epub\-subdirectory: \[aq]\[aq]
+ \-\-epub\-subdirectory=\(dq\(dq epub\-subdirectory: \(aq\(aq
- \-\-ipynb\-output best ipynb\-output: best
+ \-\-ipynb\-output best ipynb\-output: best
- \-\-pdf\-engine xelatex pdf\-engine: xelatex
+ \-\-pdf\-engine xelatex pdf\-engine: xelatex
- pdf\-engine\-opts:
- \-\-pdf\-engine\-opt=\-\-shell\-escape \- \[aq]\-shell\-escape\[aq]
-
-
- pdf\-engine\-opt: \[aq]\-shell\-escape\[aq]
+ \-\-pdf\-engine\-opt=\-\-shell\-escape pdf\-engine\-opts:
+ \- \(aq\-shell\-escape\(aq
+
+ pdf\-engine\-opt: \(aq\-shell\-escape\(aq
.EE
.RE
@@ -2100,20 +2124,19 @@ or \f[CR]{type: citeproc}\f[R].
.IP
.EX
- command line defaults file
- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
- \-\-citeproc citeproc: true
+ command line defaults file
+ \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
+ \-\-citeproc citeproc: true
- \-\-bibliography logic.bib bibliography: logic.bib
+ \-\-bibliography logic.bib bibliography: logic.bib
- \-\-csl ieee.csl csl: ieee.csl
+ \-\-csl ieee.csl csl: ieee.csl
-
- \-\-citation\-abbreviations ab.json citation\-abbreviations: ab.json
+ \-\-citation\-abbreviations ab.json citation\-abbreviations: ab.json
- \-\-natbib cite\-method: natbib
+ \-\-natbib cite\-method: natbib
- \-\-biblatex cite\-method: biblatex
+ \-\-biblatex cite\-method: biblatex
.EE
.RE
@@ -2188,19 +2211,19 @@ format \f[I]FORMAT\f[R] by putting a file
\f[CR]templates/default.*FORMAT*\f[R] in the user data directory (see
\f[CR]\-\-data\-dir\f[R], above).
\f[I]Exceptions:\f[R]
-.IP \[bu] 2
+.IP \(bu 2
For \f[CR]odt\f[R] output, customize the \f[CR]default.opendocument\f[R]
template.
-.IP \[bu] 2
+.IP \(bu 2
For \f[CR]docx\f[R] output, customize the \f[CR]default.openxml\f[R]
template.
-.IP \[bu] 2
+.IP \(bu 2
For \f[CR]pdf\f[R] output, customize the \f[CR]default.latex\f[R]
template (or the \f[CR]default.context\f[R] template, if you use
\f[CR]\-t context\f[R], or the \f[CR]default.ms\f[R] template, if you
use \f[CR]\-t ms\f[R], or the \f[CR]default.html\f[R] template, if you
use \f[CR]\-t html\f[R]).
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]pptx\f[R] has no template.
.PP
Note that \f[CR]docx\f[R], \f[CR]odt\f[R], and \f[CR]pptx\f[R] output
@@ -2215,10 +2238,10 @@ arbitrary information at any point in the file.
They may be set at the command line using the
\f[CR]\-V/\-\-variable\f[R] option.
If a variable is not set, pandoc will look for the key in the
-document\[cq]s metadata, which can be set using either YAML metadata
+document\(cqs metadata, which can be set using either YAML metadata
blocks or with the \f[CR]\-M/\-\-metadata\f[R] option.
In addition, some variables are given default values by pandoc.
-See Variables below for a list of variables used in pandoc\[cq]s default
+See Variables below for a list of variables used in pandoc\(cqs default
templates.
.PP
If you use custom templates, you may need to revise them as pandoc
@@ -2269,16 +2292,16 @@ values.
So, for example, \f[CR]employee.salary\f[R] will return the value of the
\f[CR]salary\f[R] field of the object that is the value of the
\f[CR]employee\f[R] field.
-.IP \[bu] 2
+.IP \(bu 2
If the value of the variable is a simple value, it will be rendered
verbatim.
(Note that no escaping is done; the assumption is that the calling
program will escape the strings appropriately for the output format.)
-.IP \[bu] 2
+.IP \(bu 2
If the value is a list, the values will be concatenated.
-.IP \[bu] 2
+.IP \(bu 2
If the value is a map, the string \f[CR]true\f[R] will be rendered.
-.IP \[bu] 2
+.IP \(bu 2
Every other value will be rendered as the empty string.
.SS Conditionals
A conditional begins with \f[CR]if(variable)\f[R] (enclosed in matched
@@ -2289,13 +2312,13 @@ delimiters).
The \f[CR]if\f[R] section is used if \f[CR]variable\f[R] has a true
value, otherwise the \f[CR]else\f[R] section is used (if present).
The following values count as true:
-.IP \[bu] 2
+.IP \(bu 2
any map
-.IP \[bu] 2
+.IP \(bu 2
any array containing at least one true value
-.IP \[bu] 2
+.IP \(bu 2
any nonempty string
-.IP \[bu] 2
+.IP \(bu 2
boolean True
.PP
Note that in YAML metadata (and metadata specified on the command line
@@ -2350,14 +2373,14 @@ $endif$
A for loop begins with \f[CR]for(variable)\f[R] (enclosed in matched
delimiters) and ends with \f[CR]endfor\f[R] (enclosed in matched
delimiters).
-.IP \[bu] 2
+.IP \(bu 2
If \f[CR]variable\f[R] is an array, the material inside the loop will be
evaluated repeatedly, with \f[CR]variable\f[R] being set to each value
of the array in turn, and concatenated.
-.IP \[bu] 2
+.IP \(bu 2
If \f[CR]variable\f[R] is a map, the material inside will be set to the
map.
-.IP \[bu] 2
+.IP \(bu 2
If the value of the associated variable is not an array or a map, a
single iteration will be performed on its value.
.PP
@@ -2458,11 +2481,11 @@ The separator in this case is literal and (unlike with \f[CR]sep\f[R] in
an explicit \f[CR]for\f[R] loop) cannot contain interpolated variables
or other template directives.
.SS Nesting
-To ensure that content is \[lq]nested,\[rq] that is, subsequent lines
-indented, use the \f[CR]\[ha]\f[R] directive:
+To ensure that content is \(lqnested,\(rq that is, subsequent lines
+indented, use the \f[CR]\(ha\f[R] directive:
.IP
.EX
-$item.number$ $\[ha]$$item.description$ ($item.price$)
+$item.number$ $\(ha$$item.description$ ($item.price$)
.EE
.PP
In this example, if \f[CR]item.description\f[R] has multiple lines, they
@@ -2474,11 +2497,11 @@ will all be indented to line up with the first line:
.EE
.PP
To nest multiple lines to the same level, align them with the
-\f[CR]\[ha]\f[R] directive in the template.
+\f[CR]\(ha\f[R] directive in the template.
For example:
.IP
.EX
-$item.number$ $\[ha]$$item.description$ ($item.price$)
+$item.number$ $\(ha$$item.description$ ($item.price$)
(Available til $item.sellby$.)
.EE
.PP
@@ -2492,17 +2515,17 @@ will produce
.PP
If a variable occurs by itself on a line, preceded by whitespace and not
followed by further text or directives on the same line, and the
-variable\[cq]s value contains multiple lines, it will be nested
+variable\(cqs value contains multiple lines, it will be nested
automatically.
.SS Breakable spaces
Normally, spaces in the template itself (as opposed to values of the
interpolated variables) are not breakable, but they can be made
-breakable in part of the template by using the \f[CR]\[ti]\f[R] keyword
-(ended with another \f[CR]\[ti]\f[R]).
+breakable in part of the template by using the \f[CR]\(ti\f[R] keyword
+(ended with another \f[CR]\(ti\f[R]).
.IP
.EX
-$\[ti]$This long line may break if the document is rendered
-with a short line length.$\[ti]$
+$\(ti$This long line may break if the document is rendered
+with a short line length.$\(ti$
.EE
.SS Pipes
A pipe transforms the value of a variable or partial.
@@ -2535,69 +2558,69 @@ Some pipes take parameters:
.EX
|\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-|\-\-\-\-\-\-\-\-\-\-\-\-|
$for(employee)$
-$it.name.first/uppercase/left 20 \[dq]| \[dq]$$it.name.salary/right 10 \[dq] | \[dq] \[dq] |\[dq]$
+$it.name.first/uppercase/left 20 \(dq| \(dq$$it.name.salary/right 10 \(dq | \(dq \(dq |\(dq$
$endfor$
|\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-|\-\-\-\-\-\-\-\-\-\-\-\-|
.EE
.PP
Currently the following pipes are predefined:
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]pairs\f[R]: Converts a map or array to an array of maps, each with
\f[CR]key\f[R] and \f[CR]value\f[R] fields.
If the original value was an array, the \f[CR]key\f[R] will be the array
index, starting with 1.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]uppercase\f[R]: Converts text to uppercase.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]lowercase\f[R]: Converts text to lowercase.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]length\f[R]: Returns the length of the value: number of characters
for a textual value, number of elements for a map or array.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]reverse\f[R]: Reverses a textual value or array, and has no effect
on other values.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]first\f[R]: Returns the first value of an array, if applied to a
non\-empty array; otherwise returns the original value.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]last\f[R]: Returns the last value of an array, if applied to a
non\-empty array; otherwise returns the original value.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]rest\f[R]: Returns all but the first value of an array, if applied
to a non\-empty array; otherwise returns the original value.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]allbutlast\f[R]: Returns all but the last value of an array, if
applied to a non\-empty array; otherwise returns the original value.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]chomp\f[R]: Removes trailing newlines (and breakable space).
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]nowrap\f[R]: Disables line wrapping on breakable spaces.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]alpha\f[R]: Converts textual values that can be read as an integer
into lowercase alphabetic characters \f[CR]a..z\f[R] (mod 26).
This can be used to get lettered enumeration from array indices.
To get uppercase letters, chain with \f[CR]uppercase\f[R].
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]roman\f[R]: Converts textual values that can be read as an integer
into lowercase roman numerals.
This can be used to get lettered enumeration from array indices.
To get uppercase roman, chain with \f[CR]uppercase\f[R].
-.IP \[bu] 2
-\f[CR]left n \[dq]leftborder\[dq] \[dq]rightborder\[dq]\f[R]: Renders a
+.IP \(bu 2
+\f[CR]left n \(dqleftborder\(dq \(dqrightborder\(dq\f[R]: Renders a
textual value in a block of width \f[CR]n\f[R], aligned to the left,
with an optional left and right border.
Has no effect on other values.
This can be used to align material in tables.
Widths are positive integers indicating the number of characters.
-Borders are strings inside double quotes; literal \f[CR]\[dq]\f[R] and
-\f[CR]\[rs]\f[R] characters must be backslash\-escaped.
-.IP \[bu] 2
-\f[CR]right n \[dq]leftborder\[dq] \[dq]rightborder\[dq]\f[R]: Renders a
+Borders are strings inside double quotes; literal \f[CR]\(dq\f[R] and
+\f[CR]\(rs\f[R] characters must be backslash\-escaped.
+.IP \(bu 2
+\f[CR]right n \(dqleftborder\(dq \(dqrightborder\(dq\f[R]: Renders a
textual value in a block of width \f[CR]n\f[R], aligned to the right,
and has no effect on other values.
-.IP \[bu] 2
-\f[CR]center n \[dq]leftborder\[dq] \[dq]rightborder\[dq]\f[R]: Renders
-a textual value in a block of width \f[CR]n\f[R], aligned to the center,
+.IP \(bu 2
+\f[CR]center n \(dqleftborder\(dq \(dqrightborder\(dq\f[R]: Renders a
+textual value in a block of width \f[CR]n\f[R], aligned to the center,
and has no effect on other values.
.SS Variables
.SS Metadata variables
@@ -2660,8 +2683,8 @@ The following YAML metadata block for instance:
.IP
.EX
\-\-\-
-title: \[aq]This is the title\[aq]
-subtitle: \[dq]This is the subtitle\[dq]
+title: \(aqThis is the title\(aq
+subtitle: \(dqThis is the subtitle\(dq
author:
\- Author One
\- Author Two
@@ -2703,7 +2726,7 @@ Text in the main document language (British English).
> Cette citation est écrite en français canadien.
:::
-More text in English. [\[aq]Zitat auf Deutsch.\[aq]]{lang=de}
+More text in English. [\(aqZitat auf Deutsch.\(aq]{lang=de}
.EE
.RE
.TP
@@ -2739,7 +2762,7 @@ sets the CSS \f[CR]font\-family\f[R] property on the \f[CR]html\f[R]
element.
.TP
\f[CR]fontsize\f[R]
-sets the base CSS \f[CR]font\-size\f[R], which you\[cq]d usually set to
+sets the base CSS \f[CR]font\-size\f[R], which you\(cqd usually set to
e.g.\ \f[CR]20px\f[R], but it also accepts \f[CR]pt\f[R] (12pt = 16px in
most browsers).
.TP
@@ -2807,7 +2830,7 @@ author affiliations: can be a list when there are multiple authors
.TP
\f[CR]revealjs\-url\f[R]
base URL for reveal.js documents (defaults to
-\f[CR]https://unpkg.com/reveal.js\[at]\[ha]5/\f[R])
+\f[CR]https://unpkg.com/reveal.js\(at\(ha5\f[R])
.TP
\f[CR]s5\-url\f[R]
base URL for S5 documents (defaults to \f[CR]s5/default\f[R])
@@ -2836,7 +2859,7 @@ slide aspect ratio (\f[CR]43\f[R] for 4:3 [default], \f[CR]169\f[R] for
for 1.41:1, \f[CR]54\f[R] for 5:4, \f[CR]32\f[R] for 3:2)
.TP
\f[CR]beameroption\f[R]
-add extra beamer option with \f[CR]\[rs]setbeameroption{}\f[R]
+add extra beamer option with \f[CR]\(rssetbeameroption{}\f[R]
.TP
\f[CR]institute\f[R]
author affiliations: can be a list when there are multiple authors
@@ -2850,7 +2873,7 @@ navigation symbols; other valid values are \f[CR]frame\f[R],
\f[CR]vertical\f[R], and \f[CR]horizontal\f[R])
.TP
\f[CR]section\-titles\f[R]
-enables \[lq]title pages\[rq] for new sections (default is true)
+enables \(lqtitle pages\(rq for new sections (default is true)
.TP
\f[CR]theme\f[R], \f[CR]colortheme\f[R], \f[CR]fonttheme\f[R], \f[CR]innertheme\f[R], \f[CR]outertheme\f[R]
beamer themes
@@ -2878,10 +2901,10 @@ Pandoc uses these variables when creating a PDF with a LaTeX engine.
.SS Layout
.TP
\f[CR]block\-headings\f[R]
-make \f[CR]\[rs]paragraph\f[R] and \f[CR]\[rs]subparagraph\f[R]
-(fourth\- and fifth\-level headings, or fifth\- and sixth\-level with
-book classes) free\-standing rather than run\-in; requires further
-formatting to distinguish from \f[CR]\[rs]subsubsection\f[R] (third\- or
+make \f[CR]\(rsparagraph\f[R] and \f[CR]\(rssubparagraph\f[R] (fourth\-
+and fifth\-level headings, or fifth\- and sixth\-level with book
+classes) free\-standing rather than run\-in; requires further formatting
+to distinguish from \f[CR]\(rssubsubsection\f[R] (third\- or
fourth\-level headings).
Instead of using this option, KOMA\-Script can adjust headings more
extensively:
@@ -2891,14 +2914,14 @@ extensively:
\-\-\-
documentclass: scrartcl
header\-includes: |
- \[rs]RedeclareSectionCommand[
+ \(rsRedeclareSectionCommand[
beforeskip=\-10pt plus \-2pt minus \-1pt,
afterskip=1sp plus \-1sp minus 1sp,
- font=\[rs]normalfont\[rs]itshape]{paragraph}
- \[rs]RedeclareSectionCommand[
+ font=\(rsnormalfont\(rsitshape]{paragraph}
+ \(rsRedeclareSectionCommand[
beforeskip=\-10pt plus \-2pt minus \-1pt,
afterskip=1sp plus \-1sp minus 1sp,
- font=\[rs]normalfont\[rs]scshape,
+ font=\(rsnormalfont\(rsscshape,
indent=0pt]{subparagraph}
\&...
.EE
@@ -2968,7 +2991,7 @@ sets margins if \f[CR]geometry\f[R] is not used (otherwise
\f[CR]geometry\f[R] overrides these)
.TP
\f[CR]pagestyle\f[R]
-control \f[CR]\[rs]pagestyle{}\f[R]: the default article class supports
+control \f[CR]\(rspagestyle{}\f[R]: the default article class supports
\f[CR]plain\f[R] (default), \f[CR]empty\f[R] (no running heads or page
numbers), and \f[CR]headings\f[R] (section titles in running heads)
.TP
@@ -2990,8 +3013,8 @@ produce a handout version of Beamer slides (with overlays condensed into
single slides)
.TP
\f[CR]csquotes\f[R]
-load \f[CR]csquotes\f[R] package and use \f[CR]\[rs]enquote\f[R] or
-\f[CR]\[rs]enquote*\f[R] for quoted text.
+load \f[CR]csquotes\f[R] package and use \f[CR]\(rsenquote\f[R] or
+\f[CR]\(rsenquote*\f[R] for quoted text.
.TP
\f[CR]csquotesoptions\f[R]
options to use for \f[CR]csquotes\f[R] package (repeat for multiple
@@ -3000,7 +3023,7 @@ options).
\f[CR]babeloptions\f[R]
options to pass to the babel package (may be repeated for multiple
options).
-This defaults to \f[CR]provide=*\f[R] if the main language isn\[cq]t a
+This defaults to \f[CR]provide=*\f[R] if the main language isn\(cqt a
European language written with Latin or Cyrillic script or Vietnamese.
Most users will not need to adjust the default setting.
.SS Fonts
@@ -3066,7 +3089,7 @@ mainfontoptions:
.RE
.TP
\f[CR]mainfontfallback\f[R], \f[CR]sansfontfallback\f[R], \f[CR]monofontfallback\f[R]
-fonts to try if a glyph isn\[cq]t found in \f[CR]mainfont\f[R],
+fonts to try if a glyph isn\(cqt found in \f[CR]mainfont\f[R],
\f[CR]sansfont\f[R], or \f[CR]monofont\f[R] respectively.
These are lists.
The font name must be followed by a colon and optionally a set of
@@ -3076,8 +3099,8 @@ options, for example:
.EX
\-\-\-
mainfontfallback:
- \- \[dq]FreeSans:\[dq]
- \- \[dq]NotoColorEmoji:mode=harf\[dq]
+ \- \(dqFreeSans:\(dq
+ \- \(dqNotoColorEmoji:mode=harf\(dq
\&...
.EE
.PP
@@ -3092,8 +3115,8 @@ be used with the language:
.EX
\-\-\-
babelfonts:
- chinese\-hant: \[dq]Noto Serif CJK TC\[dq]
- russian: \[dq]Noto Serif\[dq]
+ chinese\-hant: \(dqNoto Serif CJK TC\(dq
+ russian: \(dqNoto Serif\(dq
\&...
.EE
.RE
@@ -3199,7 +3222,7 @@ Switching)
\f[CR]mainfontfallback\f[R], \f[CR]sansfontfallback\f[R], \f[CR]monofontfallback\f[R]
list of fonts to try, in order, if a glyph is not found in the main
font.
-Use \f[CR]\[rs]definefallbackfamily\f[R]\-compatible font name syntax.
+Use \f[CR]\(rsdefinefallbackfamily\f[R]\-compatible font name syntax.
Emoji fonts are unsupported.
.TP
\f[CR]margin\-left\f[R], \f[CR]margin\-right\f[R], \f[CR]margin\-top\f[R], \f[CR]margin\-bottom\f[R]
@@ -3241,7 +3264,7 @@ They can be obtained from ConTeXt ICC Profiles.
\f[CR]pdfaintent\f[R]
when used in conjunction with \f[CR]pdfa\f[R], specifies the output
intent for the colors,
-e.g.\ \f[CR]ISO coated v2 300\[rs]letterpercent\[rs]space (ECI)\f[R] If
+e.g.\ \f[CR]ISO coated v2 300\(rsletterpercent\(rsspace (ECI)\f[R] If
left unspecified, \f[CR]sRGB IEC61966\-2.1\f[R] is used as default.
.TP
\f[CR]toc\f[R]
@@ -3376,7 +3399,7 @@ contents specified by \f[CR]\-A/\-\-include\-after\-body\f[R] (may have
multiple values)
.TP
\f[CR]meta\-json\f[R]
-JSON representation of all of the document\[cq]s metadata.
+JSON representation of all of the document\(cqs metadata.
Field values are transformed to the selected output format.
.TP
\f[CR]numbersections\f[R]
@@ -3405,6 +3428,10 @@ the terminal.
If you need absolute paths, use e.g.\ \f[CR]$curdir$/$sourcefile$\f[R].
.RE
.TP
+\f[CR]pdf\-engine\f[R]
+name of PDF engine if provided using \f[CR]\-\-pdf\-engine\f[R], or the
+default engine for the format if PDF output is requested.
+.TP
\f[CR]curdir\f[R]
working directory from which pandoc is run.
.TP
@@ -3428,12 +3455,12 @@ An extension can be enabled by adding \f[CR]+EXTENSION\f[R] to the
format name and disabled by adding \f[CR]\-EXTENSION\f[R].
For example, \f[CR]\-\-from markdown_strict+footnotes\f[R] is strict
Markdown with footnotes enabled, while
-\f[CR]\-\-from markdown\-footnotes\-pipe_tables\f[R] is pandoc\[cq]s
+\f[CR]\-\-from markdown\-footnotes\-pipe_tables\f[R] is pandoc\(cqs
Markdown without footnotes or pipe tables.
.PP
The Markdown reader and writer make by far the most use of extensions.
Extensions only used by them are therefore covered in the section
-Pandoc\[cq]s Markdown below (see Markdown variants for
+Pandoc\(cqs Markdown below (see Markdown variants for
\f[CR]commonmark\f[R] and \f[CR]gfm\f[R]).
In the following, extensions that also work for other formats are
covered.
@@ -3447,7 +3474,7 @@ Interpret straight quotes as curly quotes, \f[CR]\-\-\-\f[R] as
em\-dashes, \f[CR]\-\-\f[R] as en\-dashes, and \f[CR]...\f[R] as
ellipses.
Nonbreaking spaces are inserted after certain abbreviations, such as
-\[lq]Mr.\[rq]
+\(lqMr.\(rq
.PP
This extension can be enabled/disabled for the following formats:
.TP
@@ -3469,9 +3496,9 @@ extension has the reverse effect: what would have been curly quotes
comes out straight.
.PP
In LaTeX, \f[CR]smart\f[R] means to use the standard TeX ligatures for
-quotation marks (\f[CR]\[ga]\[ga]\f[R] and \f[CR]\[aq]\[aq]\f[R] for
-double quotes, \f[CR]\[ga]\f[R] and \f[CR]\[aq]\f[R] for single quotes)
-and dashes (\f[CR]\-\-\f[R] for en\-dash and \f[CR]\-\-\-\f[R] for
+quotation marks (\f[CR]\(ga\(ga\f[R] and \f[CR]\(aq\(aq\f[R] for double
+quotes, \f[CR]\(ga\f[R] and \f[CR]\(aq\f[R] for single quotes) and
+dashes (\f[CR]\-\-\f[R] for en\-dash and \f[CR]\-\-\-\f[R] for
em\-dash).
If \f[CR]smart\f[R] is disabled, then in reading LaTeX pandoc will parse
these characters literally.
@@ -3497,21 +3524,21 @@ enabled by default in
.PP
The default algorithm used to derive the identifier from the heading
text is:
-.IP \[bu] 2
+.IP \(bu 2
Remove all formatting, links, etc.
-.IP \[bu] 2
+.IP \(bu 2
Remove all footnotes.
-.IP \[bu] 2
+.IP \(bu 2
Remove all non\-alphanumeric characters, except underscores, hyphens,
and periods.
-.IP \[bu] 2
+.IP \(bu 2
Replace all spaces and newlines with hyphens.
-.IP \[bu] 2
+.IP \(bu 2
Convert all alphabetic characters to lowercase.
-.IP \[bu] 2
+.IP \(bu 2
Remove everything up to the first letter (identifiers may not begin with
a number or punctuation mark).
-.IP \[bu] 2
+.IP \(bu 2
If nothing is left after this, use the identifier \f[CR]section\f[R].
.PP
Thus, for example,
@@ -3521,7 +3548,7 @@ Thus, for example,
Heading Identifier
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
Heading identifiers in HTML heading\-identifiers\-in\-html
- Maître d\[aq]hôtel maître\-dhôtel
+ Maître d\(aqhôtel maître\-dhôtel
*Dogs*?\-\-in *my* house? dogs\-\-in\-my\-house
[HTML], [S5], or [RTF]? html\-s5\-or\-rtf
3. Applications applications
@@ -3568,7 +3595,7 @@ Accents are stripped off of accented Latin letters, and non\-Latin
letters are omitted.
.SS Extension: \f[CR]gfm_auto_identifiers\f[R]
Changes the algorithm used by \f[CR]auto_identifiers\f[R] to conform to
-GitHub\[cq]s method.
+GitHub\(cqs method.
Spaces are converted to dashes (\f[CR]\-\f[R]), uppercase characters to
lowercase characters, and punctuation characters other than
\f[CR]\-\f[R] and \f[CR]_\f[R] are removed.
@@ -3577,19 +3604,19 @@ Emojis are replaced by their names.
The extensions \f[CR]tex_math_dollars\f[R], \f[CR]tex_math_gfm\f[R],
\f[CR]tex_math_single_backslash\f[R], and
\f[CR]tex_math_double_backslash\f[R] are described in the section about
-Pandoc\[cq]s Markdown.
+Pandoc\(cqs Markdown.
.PP
However, they can also be used with HTML input.
This is handy for reading web pages formatted using MathJax, for
example.
.SS Raw HTML/TeX
The following extensions are described in more detail in their
-respective sections of Pandoc\[cq]s Markdown:
-.IP \[bu] 2
+respective sections of Pandoc\(cqs Markdown:
+.IP \(bu 2
\f[CR]raw_html\f[R] allows HTML elements which are not representable in
-pandoc\[cq]s AST to be parsed as raw HTML.
+pandoc\(cqs AST to be parsed as raw HTML.
By default, this is disabled for HTML input.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]raw_tex\f[R] allows raw LaTeX, TeX, and ConTeXt to be included in
a document.
This extension can be enabled/disabled for the following formats (in
@@ -3598,7 +3625,7 @@ addition to \f[CR]markdown\f[R]):
.TP
input formats
\f[CR]latex\f[R], \f[CR]textile\f[R], \f[CR]html\f[R] (environments,
-\f[CR]\[rs]ref\f[R], and \f[CR]\[rs]eqref\f[R] only), \f[CR]ipynb\f[R]
+\f[CR]\(rsref\f[R], and \f[CR]\(rseqref\f[R] only), \f[CR]ipynb\f[R]
.TP
output formats
\f[CR]textile\f[R], \f[CR]commonmark\f[R]
@@ -3609,15 +3636,15 @@ with mime type \f[CR]text/html\f[R] in output cells.
Since the \f[CR]ipynb\f[R] reader attempts to preserve the richest
possible outputs when several options are given, you will get best
results if you disable \f[CR]raw_html\f[R] and \f[CR]raw_tex\f[R] when
-converting to formats like \f[CR]docx\f[R] which don\[cq]t allow raw
+converting to formats like \f[CR]docx\f[R] which don\(cqt allow raw
\f[CR]html\f[R] or \f[CR]tex\f[R].
.RE
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]native_divs\f[R] causes HTML \f[CR]div\f[R] elements to be parsed
as native pandoc Div blocks.
If you want them to be parsed as raw HTML, use
\f[CR]\-f html\-native_divs+raw_html\f[R].
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]native_spans\f[R] causes HTML \f[CR]span\f[R] elements to be
parsed as native pandoc Span inlines.
If you want them to be parsed as raw HTML, use
@@ -3641,13 +3668,13 @@ If you append \f[CR]+lhs\f[R] (or \f[CR]+literate_haskell\f[R]) to one
of the formats above, pandoc will treat the document as literate Haskell
source.
This means that
-.IP \[bu] 2
-In Markdown input, \[lq]bird track\[rq] sections will be parsed as
-Haskell code rather than block quotations.
-Text between \f[CR]\[rs]begin{code}\f[R] and \f[CR]\[rs]end{code}\f[R]
+.IP \(bu 2
+In Markdown input, \(lqbird track\(rq sections will be parsed as Haskell
+code rather than block quotations.
+Text between \f[CR]\(rsbegin{code}\f[R] and \f[CR]\(rsend{code}\f[R]
will also be treated as Haskell code.
For ATX\-style headings the character `=' will be used instead of `#'.
-.IP \[bu] 2
+.IP \(bu 2
In Markdown output, code blocks with classes \f[CR]haskell\f[R] and
\f[CR]literate\f[R] will be rendered using bird tracks, and block
quotations will be indented one space, so they will not be treated as
@@ -3656,19 +3683,19 @@ In addition, headings will be rendered setext\-style (with underlines)
rather than ATX\-style (with `#' characters).
(This is because ghc treats `#' characters in column 1 as introducing
line numbers.)
-.IP \[bu] 2
-In restructured text input, \[lq]bird track\[rq] sections will be parsed
+.IP \(bu 2
+In restructured text input, \(lqbird track\(rq sections will be parsed
as Haskell code.
-.IP \[bu] 2
+.IP \(bu 2
In restructured text output, code blocks with class \f[CR]haskell\f[R]
will be rendered using bird tracks.
-.IP \[bu] 2
+.IP \(bu 2
In LaTeX input, text in \f[CR]code\f[R] environments will be parsed as
Haskell code.
-.IP \[bu] 2
+.IP \(bu 2
In LaTeX output, code blocks with class \f[CR]haskell\f[R] will be
rendered inside \f[CR]code\f[R] environments.
-.IP \[bu] 2
+.IP \(bu 2
In HTML output, code blocks with class \f[CR]haskell\f[R] will be
rendered with class \f[CR]literatehaskell\f[R] and bird tracks.
.PP
@@ -3785,7 +3812,7 @@ native pandoc citations.
(Otherwise, the formatted citations generated by the bibliographic
software will be parsed as regular text.)
.SS Extension: \f[CR]fancy_lists\f[R] (org)
-Some aspects of Pandoc\[cq]s Markdown fancy lists are also accepted in
+Some aspects of Pandoc\(cqs Markdown fancy lists are also accepted in
\f[CR]org\f[R] input, mimicking the option
\f[CR]org\-list\-allow\-alphabetical\f[R] in Emacs.
As in Org Mode, enabling this extension allows lowercase and uppercase
@@ -3793,7 +3820,7 @@ alphabetical markers for ordered lists to be parsed in addition to
arabic ones.
Note that for Org, this does not include roman numerals or the
\f[CR]#\f[R] placeholder that are enabled by the extension in
-Pandoc\[cq]s Markdown.
+Pandoc\(cqs Markdown.
.SS Extension: \f[CR]element_citations\f[R]
In the \f[CR]jats\f[R] output formats, this causes reference items to be
replaced with \f[CR]<element\-citation>\f[R] elements.
@@ -3811,9 +3838,9 @@ This includes additional markers for paragraphs and alternative markup
for emphasized text.
The \f[CR]emphasis\-command\f[R] template variable is set if the
extension is enabled.
-.SH PANDOC\[cq]S MARKDOWN
+.SH PANDOC\(cqS MARKDOWN
Pandoc understands an extended and slightly revised version of John
-Gruber\[cq]s Markdown syntax.
+Gruber\(cqs Markdown syntax.
This document explains the syntax, noting differences from original
Markdown.
Except where noted, these differences can be suppressed by using the
@@ -3829,18 +3856,18 @@ easy to read:
.RS
.PP
A Markdown\-formatted document should be publishable as\-is, as plain
-text, without looking like it\[cq]s been marked up with tags or
+text, without looking like it\(cqs been marked up with tags or
formatting instructions.
.PD 0
.P
.PD
-\[en] John Gruber
+\(en John Gruber
.RE
.PP
-This principle has guided pandoc\[cq]s decisions in finding syntax for
+This principle has guided pandoc\(cqs decisions in finding syntax for
tables, footnotes, and other extensions.
.PP
-There is, however, one respect in which pandoc\[cq]s aims are different
+There is, however, one respect in which pandoc\(cqs aims are different
from the original aims of Markdown.
Whereas Markdown was originally designed with HTML generation in mind,
pandoc is designed for multiple output formats.
@@ -3861,9 +3888,9 @@ a hard line break, since trailing spaces in the cells are ignored.
.SS Headings
There are two kinds of headings: Setext and ATX.
.SS Setext\-style headings
-A setext\-style heading is a line of text \[lq]underlined\[rq] with a
-row of \f[CR]=\f[R] signs (for a level\-one heading) or \f[CR]\-\f[R]
-signs (for a level\-two heading):
+A setext\-style heading is a line of text \(lqunderlined\(rq with a row
+of \f[CR]=\f[R] signs (for a level\-one heading) or \f[CR]\-\f[R] signs
+(for a level\-two heading):
.IP
.EX
A level\-one heading
@@ -3935,7 +3962,7 @@ My other heading {#foo}
(This syntax is compatible with PHP Markdown Extra.)
.PP
Note that although this syntax allows assignment of classes and
-key/value attributes, writers generally don\[cq]t use all of this
+key/value attributes, writers generally don\(cqt use all of this
information.
Identifiers, classes, and key/value attributes are used in HTML and
HTML\-based formats such as EPUB and slidy.
@@ -4030,7 +4057,7 @@ be indented more than three spaces.)
> 2. Second item.
.EE
.PP
-A \[lq]lazy\[rq] form, which requires the \f[CR]>\f[R] character only on
+A \(lqlazy\(rq form, which requires the \f[CR]>\f[R] character only on
the first line of each block, is also allowed:
.IP
.EX
@@ -4073,7 +4100,7 @@ does not produce a nested block quote in pandoc:
.IP
.EX
> This is a block quote.
->> Not nested, since \[ga]blank_before_blockquote\[ga] is enabled by default
+>> Not nested, since \(gablank_before_blockquote\(ga is enabled by default
.EE
.SS Verbatim (code) blocks
.SS Indented code blocks
@@ -4096,18 +4123,17 @@ Note: blank lines in the verbatim text need not begin with four spaces.
.SS Extension: \f[CR]fenced_code_blocks\f[R]
In addition to standard indented code blocks, pandoc supports
\f[I]fenced\f[R] code blocks.
-These begin with a row of three or more tildes (\f[CR]\[ti]\f[R]) and
-end with a row of tildes that must be at least as long as the starting
-row.
+These begin with a row of three or more tildes (\f[CR]\(ti\f[R]) and end
+with a row of tildes that must be at least as long as the starting row.
Everything between these lines is treated as code.
No indentation is necessary:
.IP
.EX
-\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
+\(ti\(ti\(ti\(ti\(ti\(ti\(ti
if (a > 3) {
moveShip(5 * gravity, DOWN);
}
-\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]\[ti]
+\(ti\(ti\(ti\(ti\(ti\(ti\(ti
.EE
.PP
Like regular code blocks, fenced code blocks must be separated from
@@ -4117,25 +4143,25 @@ If the code itself contains a row of tildes or backticks, just use a
longer row of tildes or backticks at the start and end:
.IP
.EX
-\[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\(ti\(ti\(ti
code including tildes
-\[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\(ti\(ti\(ti
.EE
.SS Extension: \f[CR]backtick_code_blocks\f[R]
Same as \f[CR]fenced_code_blocks\f[R], but uses backticks
-(\f[CR]\[ga]\f[R]) instead of tildes (\f[CR]\[ti]\f[R]).
+(\f[CR]\(ga\f[R]) instead of tildes (\f[CR]\(ti\f[R]).
.SS Extension: \f[CR]fenced_code_attributes\f[R]
Optionally, you may attach attributes to fenced or backtick code block
using this syntax:
.IP
.EX
-\[ti]\[ti]\[ti]\[ti] {#mycode .haskell .numberLines startFrom=\[dq]100\[dq]}
+\(ti\(ti\(ti\(ti {#mycode .haskell .numberLines startFrom=\(dq100\(dq}
qsort [] = []
qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++
qsort (filter (>= x) xs)
-\[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]
+\(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
.EE
.PP
Here \f[CR]mycode\f[R] is an identifier, \f[CR]haskell\f[R] and
@@ -4151,7 +4177,7 @@ the code block above will appear highlighted, with numbered lines.
Otherwise, the code block above will appear as follows:
.IP
.EX
-<pre id=\[dq]mycode\[dq] class=\[dq]haskell numberLines\[dq] startFrom=\[dq]100\[dq]>
+<pre id=\(dqmycode\(dq class=\(dqhaskell numberLines\(dq startFrom=\(dq100\(dq>
<code>
...
</code>
@@ -4168,33 +4194,33 @@ A shortcut form can also be used for specifying the language of the code
block:
.IP
.EX
-\[ga]\[ga]\[ga]haskell
+\(ga\(ga\(gahaskell
qsort [] = []
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga
.EE
.PP
This is equivalent to:
.IP
.EX
-\[ga]\[ga]\[ga] {.haskell}
+\(ga\(ga\(ga {.haskell}
qsort [] = []
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga
.EE
.PP
This shortcut form may be combined with attributes:
.IP
.EX
-\[ga]\[ga]\[ga]haskell {.numberLines}
+\(ga\(ga\(gahaskell {.numberLines}
qsort [] = []
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga
.EE
.PP
Which is equivalent to:
.IP
.EX
-\[ga]\[ga]\[ga] {.haskell .numberLines}
+\(ga\(ga\(ga {.haskell .numberLines}
qsort [] = []
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga
.EE
.PP
If the \f[CR]fenced_code_attributes\f[R] extension is disabled, but
@@ -4215,7 +4241,7 @@ This is useful for verse and addresses:
.EX
| The limerick packs laughs anatomical
| In space that is quite economical.
-| But the good ones I\[aq]ve seen
+| But the good ones I\(aqve seen
| So seldom are clean
| And the clean ones so seldom are comical
@@ -4234,7 +4260,7 @@ begin with a space.
.EE
.PP
Inline formatting (such as emphasis) is allowed in the content (though
-it can\[cq]t cross line boundaries).
+it can\(cqt cross line boundaries).
Block\-level formatting (such as block quotes or lists) is not
recognized.
.PP
@@ -4252,8 +4278,8 @@ Here is a simple example:
* three
.EE
.PP
-This will produce a \[lq]compact\[rq] list.
-If you want a \[lq]loose\[rq] list, in which each item is formatted as a
+This will produce a \(lqcompact\(rq list.
+If you want a \(lqloose\(rq list, in which each item is formatted as a
paragraph, put spaces between the items:
.IP
.EX
@@ -4277,7 +4303,7 @@ List items look best if subsequent lines are flush with the first line
* and my second.
.EE
.PP
-But Markdown also allows a \[lq]lazy\[rq] format:
+But Markdown also allows a \(lqlazy\(rq format:
.IP
.EX
* here is my first
@@ -4330,8 +4356,8 @@ character after the list marker of the containing list item.
+ chard
.EE
.PP
-As noted above, Markdown allows you to write list items
-\[lq]lazily,\[rq] instead of indenting continuation lines.
+As noted above, Markdown allows you to write list items \(lqlazily,\(rq
+instead of indenting continuation lines.
However, if there are multiple paragraphs or other blocks in a list
item, the first line of each must be indented.
.IP
@@ -4385,7 +4411,7 @@ used as an ordered list marker in place of a numeral:
#. two
.EE
.PP
-Note: the `\f[CR]#\f[R]' ordered list marker doesn\[cq]t work with
+Note: the `\f[CR]#\f[R]' ordered list marker doesn\(cqt work with
\f[CR]commonmark\f[R].
.SS Extension: \f[CR]startnum\f[R]
Pandoc also pays attention to the type of list marker used, and to the
@@ -4459,7 +4485,7 @@ one or more block elements (paragraph, code block, list, etc.), each
indented four spaces or one tab stop.
The body of the definition (not including the first line) should be
indented four spaces.
-However, as with other Markdown lists, you can \[lq]lazily\[rq] omit
+However, as with other Markdown lists, you can \(lqlazily\(rq omit
indentation except at the beginning of a paragraph or other block
element:
.IP
@@ -4481,43 +4507,43 @@ definition:
.IP
.EX
Term 1
- \[ti] Definition 1
+ \(ti Definition 1
Term 2
- \[ti] Definition 2a
- \[ti] Definition 2b
+ \(ti Definition 2a
+ \(ti Definition 2b
.EE
.PP
Note that space between items in a definition list is required.
-(A variant that loosens this requirement, but disallows \[lq]lazy\[rq]
+(A variant that loosens this requirement, but disallows \(lqlazy\(rq
hard wrapping, can be activated with the
\f[CR]compact_definition_lists\f[R] extension.)
.SS Numbered example lists
.SS Extension: \f[CR]example_lists\f[R]
-The special list marker \f[CR]\[at]\f[R] can be used for sequentially
+The special list marker \f[CR]\(at\f[R] can be used for sequentially
numbered examples.
-The first list item with a \f[CR]\[at]\f[R] marker will be numbered `1',
+The first list item with a \f[CR]\(at\f[R] marker will be numbered `1',
the next `2', and so on, throughout the document.
The numbered examples need not occur in a single list; each new list
-using \f[CR]\[at]\f[R] will take up where the last stopped.
+using \f[CR]\(at\f[R] will take up where the last stopped.
So, for example:
.IP
.EX
-(\[at]) My first example will be numbered (1).
-(\[at]) My second example will be numbered (2).
+(\(at) My first example will be numbered (1).
+(\(at) My second example will be numbered (2).
Explanation of examples.
-(\[at]) My third example will be numbered (3).
+(\(at) My third example will be numbered (3).
.EE
.PP
Numbered examples can be labeled and referred to elsewhere in the
document:
.IP
.EX
-(\[at]good) This is a good example.
+(\(atgood) This is a good example.
-As (\[at]good) illustrates, ...
+As (\(atgood) illustrates, ...
.EE
.PP
The label can be any string of alphanumeric characters, underscores, or
@@ -4533,13 +4559,13 @@ the first non\-space character after the label would be awkward.
You can repeat an earlier numbered example by re\-using its label:
.IP
.EX
-(\[at]foo) Sample sentence.
+(\(atfoo) Sample sentence.
Intervening text...
This theory can explain the case we saw earlier (repeated):
-(\[at]foo) Sample sentence.
+(\(atfoo) Sample sentence.
.EE
.PP
This only works reliably, though, if the repeated item is in a list by
@@ -4560,8 +4586,8 @@ Here pandoc (like other Markdown implementations) will treat
\f[CR]{ my code block }\f[R] as the second paragraph of item two, and
not as a code block.
.PP
-To \[lq]cut off\[rq] the list after item two, you can insert some
-non\-indented content, like an HTML comment, which won\[cq]t produce
+To \(lqcut off\(rq the list after item two, you can insert some
+non\-indented content, like an HTML comment, which won\(cqt produce
visible output in any format:
.IP
.EX
@@ -4630,16 +4656,16 @@ Table: Demonstration of simple table syntax.
The header and table rows must each fit on one line.
Column alignments are determined by the position of the header text
relative to the dashed line below it:
-.IP \[bu] 2
+.IP \(bu 2
If the dashed line is flush with the header text on the right side but
extends beyond it on the left, the column is right\-aligned.
-.IP \[bu] 2
+.IP \(bu 2
If the dashed line is flush with the header text on the left side but
extends beyond it on the right, the column is left\-aligned.
-.IP \[bu] 2
+.IP \(bu 2
If the dashed line extends beyond the header text on both sides, the
column is centered.
-.IP \[bu] 2
+.IP \(bu 2
If the dashed line is flush with the header text on both sides, the
default alignment is used (in most cases, this will be left).
.PP
@@ -4676,22 +4702,22 @@ Here is an example:
First row 12.0 Example of a row that
spans multiple lines.
- Second row 5.0 Here\[aq]s another one. Note
+ Second row 5.0 Here\(aqs another one. Note
the blank line between
rows.
\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-Table: Here\[aq]s the caption. It, too, may span
+Table: Here\(aqs the caption. It, too, may span
multiple lines.
.EE
.PP
These work like simple tables, but with the following differences:
-.IP \[bu] 2
+.IP \(bu 2
They must begin with a row of dashes, before the header text (unless the
header row is omitted).
-.IP \[bu] 2
+.IP \(bu 2
They must end with a row of dashes, then a blank line.
-.IP \[bu] 2
+.IP \(bu 2
The rows must be separated by blank lines.
.PP
In multiline tables, the table parser pays attention to the widths of
@@ -4707,12 +4733,12 @@ The header may be omitted in multiline tables as well as simple tables:
First row 12.0 Example of a row that
spans multiple lines.
- Second row 5.0 Here\[aq]s another one. Note
+ Second row 5.0 Here\(aqs another one. Note
the blank line between
rows.
\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\- \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-
-: Here\[aq]s a multiline table without a header.
+: Here\(aqs a multiline table without a header.
.EE
.PP
It is possible for a multiline table to have just one row, but the row
@@ -4805,7 +4831,7 @@ use \f[CR]=\f[R] instead of \f[CR]\-\f[R]:
.PP
The foot must always be placed at the very bottom of the table.
.PP
-Grid tables can be created easily using Emacs\[cq] table\-mode
+Grid tables can be created easily using Emacs\(cq table\-mode
(\f[CR]M\-x table\-insert\f[R]).
.SS Extension: \f[CR]pipe_tables\f[R]
Pipe tables look like this:
@@ -4853,7 +4879,7 @@ contents will not be wrapped, and the cells will be sized to their
contents.
.PP
Note: pandoc also recognizes pipe tables of the following form, as can
-be produced by Emacs\[cq] orgtbl\-mode:
+be produced by Emacs\(cq orgtbl\-mode:
.IP
.EX
| One | Two |
@@ -4864,7 +4890,7 @@ be produced by Emacs\[cq] orgtbl\-mode:
.PP
The difference is that \f[CR]+\f[R] is used instead of \f[CR]|\f[R].
Other orgtbl features are not supported.
-In particular, to get non\-default column alignment, you\[cq]ll need to
+In particular, to get non\-default column alignment, you\(cqll need to
add colons as above.
.SS Metadata blocks
.SS Extension: \f[CR]pandoc_title_block\f[R]
@@ -4929,12 +4955,12 @@ All three metadata fields may contain standard inline formatting
Title blocks will always be parsed, but they will affect the output only
when the \f[CR]\-\-standalone\f[R] (\f[CR]\-s\f[R]) option is chosen.
In HTML output, titles will appear twice: once in the document
-head\[em]this is the title that will appear at the top of the window in
-a browser\[em]and once at the beginning of the document body.
+head\(emthis is the title that will appear at the top of the window in a
+browser\(emand once at the beginning of the document body.
The title in the document head can have an optional prefix attached
(\f[CR]\-\-title\-prefix\f[R] or \f[CR]\-T\f[R] option).
-The title in the body appears as an H1 element with class
-\[lq]title\[rq], so it can be suppressed or reformatted with CSS.
+The title in the body appears as an H1 element with class \(lqtitle\(rq,
+so it can be suppressed or reformatted with CSS.
If a title prefix is specified with \f[CR]\-T\f[R] and no title block
appears in the document, the title prefix will be used by itself as the
HTML title.
@@ -4959,13 +4985,13 @@ will yield a man page with the title \f[CR]PANDOC\f[R] and section 1.
% PANDOC(1) Pandoc User Manuals
.EE
.PP
-will also have \[lq]Pandoc User Manuals\[rq] in the footer.
+will also have \(lqPandoc User Manuals\(rq in the footer.
.IP
.EX
% PANDOC(1) Pandoc User Manuals | Version 4.0
.EE
.PP
-will also have \[lq]Version 4.0\[rq] in the header.
+will also have \(lqVersion 4.0\(rq in the header.
.SS Extension: \f[CR]yaml_metadata_block\f[R]
A YAML metadata block is a valid YAML object, delimited by a line of
three hyphens (\f[CR]\-\-\-\f[R]) at the top and a line of three hyphens
@@ -5025,7 +5051,7 @@ block\-level formatting:
.IP
.EX
\-\-\-
-title: \[aq]This is the title: it contains a colon\[aq]
+title: \(aqThis is the title: it contains a colon\(aq
author:
\- Author One
\- Author Two
@@ -5086,7 +5112,7 @@ $endif$
$endfor$
.EE
.PP
-Raw content to include in the document\[cq]s header may be specified
+Raw content to include in the document\(cqs header may be specified
using \f[CR]header\-includes\f[R]; however, it is important to mark up
this content as raw code for a particular output format, using the
\f[CR]raw_attribute\f[R] extension, or it will be interpreted as
@@ -5096,25 +5122,25 @@ For example:
.EX
header\-includes:
\- |
- \[ga]\[ga]\[ga]{=latex}
- \[rs]let\[rs]oldsection\[rs]section
- \[rs]renewcommand{\[rs]section}[1]{\[rs]clearpage\[rs]oldsection{#1}}
- \[ga]\[ga]\[ga]
+ \(ga\(ga\(ga{=latex}
+ \(rslet\(rsoldsection\(rssection
+ \(rsrenewcommand{\(rssection}[1]{\(rsclearpage\(rsoldsection{#1}}
+ \(ga\(ga\(ga
.EE
.PP
Note: the \f[CR]yaml_metadata_block\f[R] extension works with
\f[CR]commonmark\f[R] as well as \f[CR]markdown\f[R] (and it is enabled
by default in \f[CR]gfm\f[R] and \f[CR]commonmark_x\f[R]).
However, in these formats the following restrictions apply:
-.IP \[bu] 2
+.IP \(bu 2
The YAML metadata block must occur at the beginning of the document (and
there can be only one).
If multiple files are given as arguments to pandoc, only the first can
be a YAML metadata block.
-.IP \[bu] 2
+.IP \(bu 2
The leaf nodes of the YAML structure are parsed in isolation from each
other and from the rest of the document.
-So, for example, you can\[cq]t use a reference link in these contexts if
+So, for example, you can\(cqt use a reference link in these contexts if
the link definition is somewhere else in the document.
.SS Backslash escapes
.SS Extension: \f[CR]all_symbols_escapable\f[R]
@@ -5124,7 +5150,7 @@ would normally indicate formatting.
Thus, for example, if one writes
.IP
.EX
-*\[rs]*hello\[rs]**
+*\(rs*hello\(rs**
.EE
.PP
one will get
@@ -5139,29 +5165,28 @@ instead of
<strong>hello</strong>
.EE
.PP
-This rule is easier to remember than original Markdown\[cq]s rule, which
+This rule is easier to remember than original Markdown\(cqs rule, which
allows only the following characters to be backslash\-escaped:
.IP
.EX
-\[rs]\[ga]*_{}[]()>#+\-.!
+\(rs\(ga*_{}[]()>#+\-.!
.EE
.PP
(However, if the \f[CR]markdown_strict\f[R] format is used, the original
Markdown rule will be used.)
.PP
A backslash\-escaped space is parsed as a nonbreaking space.
-In TeX output, it will appear as \f[CR]\[ti]\f[R].
+In TeX output, it will appear as \f[CR]\(ti\f[R].
In HTML and XML output, it will appear as a literal unicode nonbreaking
-space character (note that it will thus actually look
-\[lq]invisible\[rq] in the generated HTML source; you can still use the
-\f[CR]\-\-ascii\f[R] command\-line option to make it appear as an
-explicit entity).
+space character (note that it will thus actually look \(lqinvisible\(rq
+in the generated HTML source; you can still use the \f[CR]\-\-ascii\f[R]
+command\-line option to make it appear as an explicit entity).
.PP
A backslash\-escaped newline (i.e.\ a backslash occurring at the end of
a line) is parsed as a hard line break.
-It will appear in TeX output as \f[CR]\[rs]\[rs]\f[R] and in HTML as
+It will appear in TeX output as \f[CR]\(rs\(rs\f[R] and in HTML as
\f[CR]<br />\f[R].
-This is a nice alternative to Markdown\[cq]s \[lq]invisible\[rq] way of
+This is a nice alternative to Markdown\(cqs \(lqinvisible\(rq way of
indicating hard line breaks using two trailing spaces on a line.
.PP
Backslash escapes do not work in verbatim contexts.
@@ -5185,7 +5210,7 @@ A \f[CR]*\f[R] or \f[CR]_\f[R] character surrounded by spaces, or
backslash\-escaped, will not trigger emphasis:
.IP
.EX
-This is * not emphasized *, and \[rs]*neither is this\[rs]*.
+This is * not emphasized *, and \(rs*neither is this\(rs*.
.EE
.SS Extension: \f[CR]intraword_underscores\f[R]
Because \f[CR]_\f[R] is sometimes used inside words and identifiers,
@@ -5199,43 +5224,43 @@ feas*ible*, not feas*able*.
.SS Strikeout
.SS Extension: \f[CR]strikeout\f[R]
To strike out a section of text with a horizontal line, begin and end it
-with \f[CR]\[ti]\[ti]\f[R].
+with \f[CR]\(ti\(ti\f[R].
Thus, for example,
.IP
.EX
-This \[ti]\[ti]is deleted text.\[ti]\[ti]
+This \(ti\(tiis deleted text.\(ti\(ti
.EE
.SS Superscripts and subscripts
.SS Extension: \f[CR]superscript\f[R], \f[CR]subscript\f[R]
Superscripts may be written by surrounding the superscripted text by
-\f[CR]\[ha]\f[R] characters; subscripts may be written by surrounding
-the subscripted text by \f[CR]\[ti]\f[R] characters.
+\f[CR]\(ha\f[R] characters; subscripts may be written by surrounding the
+subscripted text by \f[CR]\(ti\f[R] characters.
Thus, for example,
.IP
.EX
-H\[ti]2\[ti]O is a liquid. 2\[ha]10\[ha] is 1024.
+H\(ti2\(tiO is a liquid. 2\(ha10\(ha is 1024.
.EE
.PP
-The text between \f[CR]\[ha]...\[ha]\f[R] or \f[CR]\[ti]...\[ti]\f[R]
-may not contain spaces or newlines.
+The text between \f[CR]\(ha...\(ha\f[R] or \f[CR]\(ti...\(ti\f[R] may
+not contain spaces or newlines.
If the superscripted or subscripted text contains spaces, these spaces
must be escaped with backslashes.
(This is to prevent accidental superscripting and subscripting through
-the ordinary use of \f[CR]\[ti]\f[R] and \f[CR]\[ha]\f[R], and also bad
+the ordinary use of \f[CR]\(ti\f[R] and \f[CR]\(ha\f[R], and also bad
interactions with footnotes.)
Thus, if you want the letter P with `a cat' in subscripts, use
-\f[CR]P\[ti]a\[rs] cat\[ti]\f[R], not \f[CR]P\[ti]a cat\[ti]\f[R].
+\f[CR]P\(tia\(rs cat\(ti\f[R], not \f[CR]P\(tia cat\(ti\f[R].
.SS Verbatim
To make a short span of text verbatim, put it inside backticks:
.IP
.EX
-What is the difference between \[ga]>>=\[ga] and \[ga]>>\[ga]?
+What is the difference between \(ga>>=\(ga and \(ga>>\(ga?
.EE
.PP
If the verbatim text includes a backtick, use double backticks:
.IP
.EX
-Here is a literal backtick \[ga]\[ga] \[ga] \[ga]\[ga].
+Here is a literal backtick \(ga\(ga \(ga \(ga\(ga.
.EE
.PP
(The spaces after the opening backticks and before the closing backticks
@@ -5249,14 +5274,14 @@ Note that backslash\-escapes (and other Markdown constructs) do not work
in verbatim contexts:
.IP
.EX
-This is a backslash followed by an asterisk: \[ga]\[rs]*\[ga].
+This is a backslash followed by an asterisk: \(ga\(rs*\(ga.
.EE
.SS Extension: \f[CR]inline_code_attributes\f[R]
Attributes can be attached to verbatim text, just as with fenced code
blocks:
.IP
.EX
-\[ga]<$>\[ga]{.haskell}
+\(ga<$>\(ga{.haskell}
.EE
.SS Underline
To underline text, use the \f[CR]underline\f[R] class:
@@ -5269,7 +5294,7 @@ Or, without the \f[CR]bracketed_spans\f[R] extension (but with
\f[CR]native_spans\f[R]):
.IP
.EX
-<span class=\[dq]underline\[dq]>Underline</span>
+<span class=\(dqunderline\(dq>Underline</span>
.EE
.PP
This will work in all output formats that support underline.
@@ -5283,13 +5308,13 @@ To write small caps, use the \f[CR]smallcaps\f[R] class:
Or, without the \f[CR]bracketed_spans\f[R] extension:
.IP
.EX
-<span class=\[dq]smallcaps\[dq]>Small caps</span>
+<span class=\(dqsmallcaps\(dq>Small caps</span>
.EE
.PP
For compatibility with other Markdown flavors, CSS is also supported:
.IP
.EX
-<span style=\[dq]font\-variant:small\-caps;\[dq]>Small caps</span>
+<span style=\(dqfont\-variant:small\-caps;\(dq>Small caps</span>
.EE
.PP
This will work in all output formats that support small caps.
@@ -5304,7 +5329,7 @@ Or, without the \f[CR]bracketed_spans\f[R] extension (but with
\f[CR]native_spans\f[R]):
.IP
.EX
-<span class=\[dq]mark\[dq]>Mark</span>
+<span class=\(dqmark\(dq>Mark</span>
.EE
.PP
This will work in all output formats that support highlighting.
@@ -5316,9 +5341,9 @@ The opening \f[CR]$\f[R] must have a non\-space character immediately to
its right, while the closing \f[CR]$\f[R] must have a non\-space
character immediately to its left, and must not be followed immediately
by a digit.
-Thus, \f[CR]$20,000 and $30,000\f[R] won\[cq]t parse as math.
+Thus, \f[CR]$20,000 and $30,000\f[R] won\(cqt parse as math.
If for some reason you need to enclose text in literal \f[CR]$\f[R]
-characters, backslash\-escape them and they won\[cq]t be treated as math
+characters, backslash\-escape them and they won\(cqt be treated as math
delimiters.
.PP
For display math, use \f[CR]$$\f[R] delimiters.
@@ -5331,8 +5356,8 @@ TeX math will be printed in all output formats.
How it is rendered depends on the output format:
.TP
LaTeX
-It will appear verbatim surrounded by \f[CR]\[rs](...\[rs])\f[R] (for
-inline math) or \f[CR]\[rs][...\[rs]]\f[R] (for display math).
+It will appear verbatim surrounded by \f[CR]\(rs(...\(rs)\f[R] (for
+inline math) or \f[CR]\(rs[...\(rs]\f[R] (for display math).
.TP
Markdown, Emacs Org mode, ConTeXt, ZimWiki
It will appear verbatim surrounded by \f[CR]$...$\f[R] (for inline math)
@@ -5352,16 +5377,16 @@ For \f[CR]asciidoc_legacy\f[R] the bracketed material will also include
inline or display math delimiters.
.TP
Texinfo
-It will be rendered inside a \f[CR]\[at]math\f[R] command.
+It will be rendered inside a \f[CR]\(atmath\f[R] command.
.TP
roff man, Jira markup
-It will be rendered verbatim without \f[CR]$\f[R]\[cq]s.
+It will be rendered verbatim without \f[CR]$\f[R]\(cqs.
.TP
MediaWiki, DokuWiki
It will be rendered inside \f[CR]<math>\f[R] tags.
.TP
Textile
-It will be rendered inside \f[CR]<span class=\[dq]math\[dq]>\f[R] tags.
+It will be rendered inside \f[CR]<span class=\(dqmath\(dq>\f[R] tags.
.TP
RTF, OpenDocument
It will be rendered, if possible, using Unicode characters, and will
@@ -5412,7 +5437,7 @@ Otherwise, plain\-text fallbacks will be used.
Note that even if \f[CR]raw_html\f[R] is disabled, tables will be
rendered with HTML syntax if they cannot use pipe syntax.
.SS Extension: \f[CR]markdown_in_html_blocks\f[R]
-Original Markdown allows you to include HTML \[lq]blocks\[rq]: blocks of
+Original Markdown allows you to include HTML \(lqblocks\(rq: blocks of
HTML between balanced tags that are separated from the surrounding text
with blank lines, and start and end at the left margin.
Within these blocks, everything is interpreted as HTML, not Markdown; so
@@ -5438,7 +5463,7 @@ into
<table>
<tr>
<td><em>one</em></td>
-<td><a href=\[dq]https://google.com\[dq]>a link</a></td>
+<td><a href=\(dqhttps://google.com\(dq>a link</a></td>
</tr>
</table>
.EE
@@ -5474,18 +5499,18 @@ and ConTeXt writers.
Thus, for example, you can use LaTeX to include BibTeX citations:
.IP
.EX
-This result was proved in \[rs]cite{jones.1967}.
+This result was proved in \(rscite{jones.1967}.
.EE
.PP
Note that in LaTeX environments, like
.IP
.EX
-\[rs]begin{tabular}{|l|l|}\[rs]hline
-Age & Frequency \[rs]\[rs] \[rs]hline
-18\-\-25 & 15 \[rs]\[rs]
-26\-\-35 & 33 \[rs]\[rs]
-36\-\-45 & 22 \[rs]\[rs] \[rs]hline
-\[rs]end{tabular}
+\(rsbegin{tabular}{|l|l|}\(rshline
+Age & Frequency \(rs\(rs \(rshline
+18\-\-25 & 15 \(rs\(rs
+26\-\-35 & 33 \(rs\(rs
+36\-\-45 & 22 \(rs\(rs \(rshline
+\(rsend{tabular}
.EE
.PP
the material between the begin and end tags will be interpreted as raw
@@ -5503,16 +5528,16 @@ will be parsed as raw content with the designated format.
For example, the following produces a raw roff \f[CR]ms\f[R] block:
.IP
.EX
-\[ga]\[ga]\[ga]{=ms}
+\(ga\(ga\(ga{=ms}
\&.MYMACRO
blah blah
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga
.EE
.PP
And the following produces a raw \f[CR]html\f[R] inline element:
.IP
.EX
-This is \[ga]<a>html</a>\[ga]{=html}
+This is \(ga<a>html</a>\(ga{=html}
.EE
.PP
This can be useful to insert raw xml into \f[CR]docx\f[R] documents,
@@ -5520,13 +5545,13 @@ e.g.
a pagebreak:
.IP
.EX
-\[ga]\[ga]\[ga]{=openxml}
+\(ga\(ga\(ga{=openxml}
<w:p>
<w:r>
- <w:br w:type=\[dq]page\[dq]/>
+ <w:br w:type=\(dqpage\(dq/>
</w:r>
</w:p>
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga
.EE
.PP
The format name should match the target format name (see
@@ -5554,9 +5579,9 @@ So, for example, the following will work in all output formats, not just
LaTeX:
.IP
.EX
-\[rs]newcommand{\[rs]tuple}[1]{\[rs]langle #1 \[rs]rangle}
+\(rsnewcommand{\(rstuple}[1]{\(rslangle #1 \(rsrangle}
-$\[rs]tuple{a, b, c}$
+$\(rstuple{a, b, c}$
.EE
.PP
Note that LaTeX macros will not be applied if they occur inside a raw
@@ -5579,7 +5604,7 @@ a link:
.IP
.EX
<https://google.com>
-<sam\[at]green.eggs.ham>
+<sam\(atgreen.eggs.ham>
.EE
.SS Inline links
An inline link consists of the link text in square brackets, followed by
@@ -5587,8 +5612,8 @@ the URL in parentheses.
(Optionally, the URL can be followed by a link title, in quotes.)
.IP
.EX
-This is an [inline link](/url), and here\[aq]s [one with
-a title](https://fsf.org \[dq]click here for a good time!\[dq]).
+This is an [inline link](/url), and here\(aqs [one with
+a title](https://fsf.org \(dqclick here for a good time!\(dq).
.EE
.PP
There can be no space between the bracketed part and the parenthesized
@@ -5600,7 +5625,7 @@ Email addresses in inline links are not autodetected, so they have to be
prefixed with \f[CR]mailto\f[R]:
.IP
.EX
-[Write me!](mailto:sam\[at]green.eggs.ham)
+[Write me!](mailto:sam\(atgreen.eggs.ham)
.EE
.SS Reference links
An \f[I]explicit\f[R] reference link has two parts, the link itself and
@@ -5621,10 +5646,10 @@ over link labels.
Here are some examples:
.IP
.EX
-[my label 1]: /foo/bar.html \[dq]My title, optional\[dq]
+[my label 1]: /foo/bar.html \(dqMy title, optional\(dq
[my label 2]: /foo
[my label 3]: https://fsf.org (The Free Software Foundation)
-[my label 4]: /bar#special \[aq]A title in single quotes\[aq]
+[my label 4]: /bar#special \(aqA title in single quotes\(aq
.EE
.PP
The URL may optionally be surrounded by angle brackets:
@@ -5637,7 +5662,7 @@ The title may go on the next line:
.IP
.EX
[my label 3]: https://fsf.org
- \[dq]The Free Software Foundation\[dq]
+ \(dqThe Free Software Foundation\(dq
.EE
.PP
Note that link labels are not case sensitive.
@@ -5701,10 +5726,10 @@ slide shows and EPUB), LaTeX, and ConTeXt.
.SS Images
A link immediately preceded by a \f[CR]!\f[R] will be treated as an
image.
-The link text will be used as the image\[cq]s alt text:
+The link text will be used as the image\(cqs alt text:
.IP
.EX
-![la lune](lalune.jpg \[dq]Voyage to the moon\[dq])
+![la lune](lalune.jpg \(dqVoyage to the moon\(dq)
![movie reel]
@@ -5713,7 +5738,7 @@ The link text will be used as the image\[cq]s alt text:
.SS Extension: \f[CR]implicit_figures\f[R]
An image with nonempty alt text, occurring by itself in a paragraph,
will be rendered as a figure with a caption.
-The image\[cq]s alt text will be used as the caption.
+The image\(cqs alt text will be used as the caption.
.IP
.EX
![This is the caption](/url/of/image.png)
@@ -5721,7 +5746,7 @@ The image\[cq]s alt text will be used as the caption.
.PP
How this is rendered depends on the output format.
Some output formats (e.g.\ RTF) do not yet support figures.
-In those formats, you\[cq]ll just get an image in a paragraph by itself,
+In those formats, you\(cqll just get an image in a paragraph by itself,
with no caption.
.PP
If you just want a regular inline image, just make sure it is not the
@@ -5729,7 +5754,7 @@ only thing in the paragraph.
One way to do this is to insert a nonbreaking space after the image:
.IP
.EX
-![This image won\[aq]t be a figure](/url/of/image.png)\[rs]
+![This image won\(aqt be a figure](/url/of/image.png)\(rs
.EE
.PP
Note that in reveal.js slide shows, an image in a paragraph by itself
@@ -5742,7 +5767,7 @@ Attributes can be set on links and images:
An inline ![image](foo.jpg){#id .class width=30 height=20px}
and a reference ![image][ref] with attributes.
-[ref]: foo.jpg \[dq]optional title\[dq] {#id .class key=val key2=\[dq]val 2\[dq]}
+[ref]: foo.jpg \(dqoptional title\(dq {#id .class key=val key2=\(dqval 2\(dq}
.EE
.PP
(This syntax is compatible with PHP Markdown Extra when only
@@ -5768,33 +5793,31 @@ For example:
.EX
![](file.jpg){ width=50% }
.EE
-.IP \[bu] 2
+.IP \(bu 2
Dimensions may be converted to a form that is compatible with the output
format (for example, dimensions given in pixels will be converted to
inches when converting HTML to LaTeX).
Conversion between pixels and physical measurements is affected by the
\f[CR]\-\-dpi\f[R] option (by default, 96 dpi is assumed, unless the
image itself contains dpi information).
-.IP \[bu] 2
+.IP \(bu 2
The \f[CR]%\f[R] unit is generally relative to some available space.
For example the above example will render to the following.
.RS 2
-.IP \[bu] 2
-HTML:
-\f[CR]<img href=\[dq]file.jpg\[dq] style=\[dq]width: 50%;\[dq] />\f[R]
-.IP \[bu] 2
+.IP \(bu 2
+HTML: \f[CR]<img href=\(dqfile.jpg\(dq style=\(dqwidth: 50%;\(dq />\f[R]
+.IP \(bu 2
LaTeX:
-\f[CR]\[rs]includegraphics[width=0.5\[rs]textwidth,height=\[rs]textheight]{file.jpg}\f[R]
-(If you\[cq]re using a custom template, you need to configure
+\f[CR]\(rsincludegraphics[width=0.5\(rstextwidth,height=\(rstextheight]{file.jpg}\f[R]
+(If you\(cqre using a custom template, you need to configure
\f[CR]graphicx\f[R] as in the default template.)
-.IP \[bu] 2
-ConTeXt:
-\f[CR]\[rs]externalfigure[file.jpg][width=0.5\[rs]textwidth]\f[R]
+.IP \(bu 2
+ConTeXt: \f[CR]\(rsexternalfigure[file.jpg][width=0.5\(rstextwidth]\f[R]
.RE
-.IP \[bu] 2
+.IP \(bu 2
Some output formats have a notion of a class (ConTeXt) or a unique
-identifier (LaTeX \f[CR]\[rs]caption\f[R]), or both (HTML).
-.IP \[bu] 2
+identifier (LaTeX \f[CR]\(rscaption\f[R]), or both (HTML).
+.IP \(bu 2
When no \f[CR]width\f[R] or \f[CR]height\f[R] attributes are specified,
the fallback is to look at the image resolution and the dpi metadata
embedded in the image file.
@@ -5811,7 +5834,7 @@ plus some attributes.
The attributes may optionally be followed by another string of
consecutive colons.
.PP
-Note: the \f[CR]commonmark\f[R] parser doesn\[cq]t permit colons after
+Note: the \f[CR]commonmark\f[R] parser doesn\(cqt permit colons after
the attributes.
.PP
The attribute syntax is exactly as in fenced code blocks (see Extension:
@@ -5858,18 +5881,18 @@ be treated as a \f[CR]Span\f[R] with attributes if it is followed
immediately by attributes:
.IP
.EX
-[This is *some text*]{.class key=\[dq]val\[dq]}
+[This is *some text*]{.class key=\(dqval\(dq}
.EE
.SS Footnotes
.SS Extension: \f[CR]footnotes\f[R]
-Pandoc\[cq]s Markdown allows footnotes, using the following syntax:
+Pandoc\(cqs Markdown allows footnotes, using the following syntax:
.IP
.EX
-Here is a footnote reference,[\[ha]1] and another.[\[ha]longnote]
+Here is a footnote reference,[\(ha1] and another.[\(halongnote]
-[\[ha]1]: Here is the footnote.
+[\(ha1]: Here is the footnote.
-[\[ha]longnote]: Here\[aq]s one with multiple blocks.
+[\(halongnote]: Here\(aqs one with multiple blocks.
Subsequent paragraphs are indented to show that they
belong to the previous footnote.
@@ -5880,12 +5903,12 @@ belong to the previous footnote.
line. In this way, multi\-paragraph footnotes work like
multi\-paragraph list items.
-This paragraph won\[aq]t be part of the note, because it
-isn\[aq]t indented.
+This paragraph won\(aqt be part of the note, because it
+isn\(aqt indented.
.EE
.PP
The identifiers in footnote references may not contain spaces, tabs,
-newlines, or the characters \f[CR]\[ha]\f[R], \f[CR][\f[R], or
+newlines, or the characters \f[CR]\(ha\f[R], \f[CR][\f[R], or
\f[CR]]\f[R].
These identifiers are used only to correlate the footnote reference with
the note itself; in the output, footnotes will be numbered sequentially.
@@ -5901,8 +5924,8 @@ cannot contain multiple paragraphs).
The syntax is as follows:
.IP
.EX
-Here is an inline note.\[ha][Inline notes are easier to write, since
-you don\[aq]t have to pick an identifier and move down to type the
+Here is an inline note.\(ha[Inline notes are easier to write, since
+you don\(aqt have to pick an identifier and move down to type the
note.]
.EE
.PP
@@ -5910,12 +5933,12 @@ Inline and regular footnotes may be mixed freely.
.SS Citation syntax
.SS Extension: \f[CR]citations\f[R]
To cite a bibliographic item with an identifier foo, use the syntax
-\f[CR]\[at]foo\f[R].
+\f[CR]\(atfoo\f[R].
Normal citations should be included in square brackets, with semicolons
separating distinct items:
.IP
.EX
-Blah blah [\[at]doe99; \[at]smith2000; \[at]smith2004].
+Blah blah [\(atdoe99; \(atsmith2000; \(atsmith2004].
.EE
.PP
How this is rendered depends on the citation style.
@@ -5928,11 +5951,11 @@ Blah blah (Doe 1999, Smith 2000, 2004).
In a footnote style, it might render as
.IP
.EX
-Blah blah.[\[ha]1]
+Blah blah.[\(ha1]
-[\[ha]1]: John Doe, \[dq]Frogs,\[dq] *Journal of Amphibians* 44 (1999);
-Susan Smith, \[dq]Flies,\[dq] *Journal of Insects* (2000);
-Susan Smith, \[dq]Bees,\[dq] *Journal of Insects* (2004).
+[\(ha1]: John Doe, \(dqFrogs,\(dq *Journal of Amphibians* 44 (1999);
+Susan Smith, \(dqFlies,\(dq *Journal of Insects* (2000);
+Susan Smith, \(dqBees,\(dq *Journal of Insects* (2004).
.EE
.PP
See the CSL user documentation for more information about CSL styles and
@@ -5940,23 +5963,23 @@ how they affect rendering.
.PP
Unless a citation key starts with a letter, digit, or \f[CR]_\f[R], and
contains only alphanumerics and single internal punctuation characters
-(\f[CR]:.#$%&\-+?<>\[ti]/\f[R]), it must be surrounded by curly braces,
+(\f[CR]:.#$%&\-+?<>\(ti/\f[R]), it must be surrounded by curly braces,
which are not considered part of the key.
-In \f[CR]\[at]Foo_bar.baz.\f[R], the key is \f[CR]Foo_bar.baz\f[R]
+In \f[CR]\(atFoo_bar.baz.\f[R], the key is \f[CR]Foo_bar.baz\f[R]
because the final period is not \f[I]internal\f[R] punctuation, so it is
not included in the key.
-In \f[CR]\[at]{Foo_bar.baz.}\f[R], the key is \f[CR]Foo_bar.baz.\f[R],
+In \f[CR]\(at{Foo_bar.baz.}\f[R], the key is \f[CR]Foo_bar.baz.\f[R],
including the final period.
-In \f[CR]\[at]Foo_bar\-\-baz\f[R], the key is \f[CR]Foo_bar\f[R] because
+In \f[CR]\(atFoo_bar\-\-baz\f[R], the key is \f[CR]Foo_bar\f[R] because
the repeated internal punctuation characters terminate the key.
The curly braces are recommended if you use URLs as keys:
-\f[CR][\[at]{https://example.com/bib?name=foobar&date=2000}, p. 33]\f[R].
+\f[CR][\(at{https://example.com/bib?name=foobar&date=2000}, p. 33]\f[R].
.PP
Citation items may optionally include a prefix, a locator, and a suffix.
In
.IP
.EX
-Blah blah [see \[at]doe99, pp. 33\-35 and *passim*; \[at]smith04, chap. 1].
+Blah blah [see \(atdoe99, pp. 33\-35 and *passim*; \(atsmith04, chap. 1].
.EE
.PP
the first item (\f[CR]doe99\f[R]) has prefix \f[CR]see\f[R], locator
@@ -5987,36 +6010,36 @@ singular or plural forms, as \f[CR]book\f[R],
\f[CR]v.\f[R]/\f[CR]vv.\f[R]; \f[CR]volume\f[R],
\f[CR]vol.\f[R]/\f[CR]vols.\f[R]; \f[CR]¶\f[R]/\f[CR]¶¶\f[R];
\f[CR]§\f[R]/\f[CR]§§\f[R].
-If no locator term is used, \[lq]page\[rq] is assumed.
+If no locator term is used, \(lqpage\(rq is assumed.
.PP
In complex cases, you can force something to be treated as a locator by
enclosing it in curly braces or prevent parsing the suffix as locator by
prepending curly braces:
.IP
.EX
-[\[at]smith{ii, A, D\-Z}, with a suffix]
-[\[at]smith, {pp. iv, vi\-xi, (xv)\-(xvii)} with suffix here]
-[\[at]smith{}, 99 years later]
+[\(atsmith{ii, A, D\-Z}, with a suffix]
+[\(atsmith, {pp. iv, vi\-xi, (xv)\-(xvii)} with suffix here]
+[\(atsmith{}, 99 years later]
.EE
.PP
-A minus sign (\f[CR]\-\f[R]) before the \f[CR]\[at]\f[R] will suppress
+A minus sign (\f[CR]\-\f[R]) before the \f[CR]\(at\f[R] will suppress
mention of the author in the citation.
This can be useful when the author is already mentioned in the text:
.IP
.EX
-Smith says blah [\-\[at]smith04].
+Smith says blah [\-\(atsmith04].
.EE
.PP
You can also write an author\-in\-text citation, by omitting the square
brackets:
.IP
.EX
-\[at]smith04 says blah.
+\(atsmith04 says blah.
-\[at]smith04 [p. 33] says blah.
+\(atsmith04 [p. 33] says blah.
.EE
.PP
-This will cause the author\[cq]s name to be rendered, followed by the
+This will cause the author\(cqs name to be rendered, followed by the
bibliographical details.
Use this form when you want to make the citation the subject of a
sentence.
@@ -6082,32 +6105,32 @@ Allows attributes to be attached to any inline or block\-level element
when parsing \f[CR]commonmark\f[R].
The syntax for the attributes is the same as that used in
\f[CR]header_attributes\f[R].
-.IP \[bu] 2
+.IP \(bu 2
Attributes that occur immediately after an inline element affect that
element.
If they follow a space, then they belong to the space.
(Hence, this option subsumes \f[CR]inline_code_attributes\f[R] and
\f[CR]link_attributes\f[R].)
-.IP \[bu] 2
+.IP \(bu 2
Attributes that occur immediately before a block element, on a line by
themselves, affect that element.
-.IP \[bu] 2
+.IP \(bu 2
Consecutive attribute specifiers may be used, either for blocks or for
inlines.
Their attributes will be combined.
-.IP \[bu] 2
+.IP \(bu 2
Attributes that occur at the end of the text of a Setext or ATX heading
(separated by whitespace from the text) affect the heading element.
(Hence, this option subsumes \f[CR]header_attributes\f[R].)
-.IP \[bu] 2
+.IP \(bu 2
Attributes that occur after the opening fence in a fenced code block
affect the code block element.
(Hence, this option subsumes \f[CR]fenced_code_attributes\f[R].)
-.IP \[bu] 2
+.IP \(bu 2
Attributes that occur at the end of a reference link definition affect
links that refer to that definition.
.PP
-Note that pandoc\[cq]s AST does not currently allow attributes to be
+Note that pandoc\(cqs AST does not currently allow attributes to be
attached to arbitrary elements.
Hence a Span or Div container will be added if needed.
.SS Extension: \f[CR]old_dashes\f[R]
@@ -6119,8 +6142,7 @@ It is selected automatically for \f[CR]textile\f[R] input.
.SS Extension: \f[CR]angle_brackets_escapable\f[R]
Allow \f[CR]<\f[R] and \f[CR]>\f[R] to be backslash\-escaped, as they
can be in GitHub flavored Markdown but not original Markdown.
-This is implied by pandoc\[cq]s default
-\f[CR]all_symbols_escapable\f[R].
+This is implied by pandoc\(cqs default \f[CR]all_symbols_escapable\f[R].
.SS Extension: \f[CR]lists_without_preceding_blankline\f[R]
Allow a list to occur right after a paragraph, with no intervening blank
space.
@@ -6153,26 +6175,26 @@ that include a mix of East Asian wide characters and other characters.
Parses textual emojis like \f[CR]:smile:\f[R] as Unicode emoticons.
.SS Extension: \f[CR]tex_math_gfm\f[R]
Supports two GitHub\-specific formats for math.
-Inline math: \f[CR]$\[ga]e=mc\[ha]2\[ga]$\f[R].
+Inline math: \f[CR]$\(gae=mc\(ha2\(ga$\f[R].
.PP
Display math:
.IP
.EX
-\[ga]\[ga]\[ga] math
-e=mc\[ha]2
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga math
+e=mc\(ha2
+\(ga\(ga\(ga
.EE
.SS Extension: \f[CR]tex_math_single_backslash\f[R]
-Causes anything between \f[CR]\[rs](\f[R] and \f[CR]\[rs])\f[R] to be
-interpreted as inline TeX math, and anything between \f[CR]\[rs][\f[R]
-and \f[CR]\[rs]]\f[R] to be interpreted as display TeX math.
+Causes anything between \f[CR]\(rs(\f[R] and \f[CR]\(rs)\f[R] to be
+interpreted as inline TeX math, and anything between \f[CR]\(rs[\f[R]
+and \f[CR]\(rs]\f[R] to be interpreted as display TeX math.
Note: a drawback of this extension is that it precludes escaping
\f[CR](\f[R] and \f[CR][\f[R].
.SS Extension: \f[CR]tex_math_double_backslash\f[R]
-Causes anything between \f[CR]\[rs]\[rs](\f[R] and
-\f[CR]\[rs]\[rs])\f[R] to be interpreted as inline TeX math, and
-anything between \f[CR]\[rs]\[rs][\f[R] and \f[CR]\[rs]\[rs]]\f[R] to be
-interpreted as display TeX math.
+Causes anything between \f[CR]\(rs\(rs(\f[R] and \f[CR]\(rs\(rs)\f[R] to
+be interpreted as inline TeX math, and anything between
+\f[CR]\(rs\(rs[\f[R] and \f[CR]\(rs\(rs]\f[R] to be interpreted as
+display TeX math.
.SS Extension: \f[CR]markdown_attribute\f[R]
By default, pandoc interprets material inside block\-level tags as
Markdown.
@@ -6211,6 +6233,9 @@ Supports GitHub\-style Markdown alerts, like
> [!TIP]
> Helpful advice for doing things better or more easily.
.EE
+.PP
+Note: This extension currently only works with commonmark:
+\f[CR]commonmark\f[R], \f[CR]gfm\f[R], \f[CR]commonmark_x\f[R].
.SS Extension: \f[CR]autolink_bare_uris\f[R]
Makes all absolute URIs into links, even when not surrounded by pointy
braces \f[CR]<...>\f[R].
@@ -6223,8 +6248,8 @@ This extension should not be confused with the
.EX
This is a reference ![image][ref] with MultiMarkdown attributes.
-[ref]: https://path.to/image \[dq]Image title\[dq] width=20px height=30px
- id=myId class=\[dq]myClass1 myClass2\[dq]
+[ref]: https://path.to/image \(dqImage title\(dq width=20px height=30px
+ id=myId class=\(dqmyClass1 myClass2\(dq
.EE
.SS Extension: \f[CR]mmd_header_identifiers\f[R]
Parses MultiMarkdown\-style heading identifiers (in square brackets,
@@ -6234,14 +6259,14 @@ heading).
Activates the definition list syntax of pandoc 1.12.x and earlier.
This syntax differs from the one described above under Definition lists
in several respects:
-.IP \[bu] 2
+.IP \(bu 2
No blank line is required between consecutive items of the definition
list.
-.IP \[bu] 2
-To get a \[lq]tight\[rq] or \[lq]compact\[rq] list, omit space between
+.IP \(bu 2
+To get a \(lqtight\(rq or \(lqcompact\(rq list, omit space between
consecutive items; the space between a term and its definition does not
affect anything.
-.IP \[bu] 2
+.IP \(bu 2
Lazy wrapping of paragraphs is not allowed: the entire definition must
be indented four spaces.
.SS Extension: \f[CR]gutenberg\f[R]
@@ -6255,18 +6280,18 @@ added; other elements are placed in a surrounding Div or Span element
with a \f[CR]data\-pos\f[R] attribute.
.SS Extension: \f[CR]short_subsuperscripts\f[R]
Parse MultiMarkdown\-style subscripts and superscripts, which start with
-a `\[ti]' or `\[ha]' character, respectively, and include the
-alphanumeric sequence that follows.
+a `\(ti' or `\(ha' character, respectively, and include the alphanumeric
+sequence that follows.
For example:
.IP
.EX
-x\[ha]2 = 4
+x\(ha2 = 4
.EE
.PP
or
.IP
.EX
-Oxygen is O\[ti]2.
+Oxygen is O\(ti2.
.EE
.SS Extension: \f[CR]wikilinks_title_after_pipe\f[R]
Pandoc supports multiple Markdown wikilink syntaxes, regardless of
@@ -6285,21 +6310,21 @@ results in
[[title|URL]]
.EE
.SS Markdown variants
-In addition to pandoc\[cq]s extended Markdown, the following Markdown
+In addition to pandoc\(cqs extended Markdown, the following Markdown
variants are supported:
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]markdown_phpextra\f[R] (PHP Markdown Extra)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]markdown_github\f[R] (deprecated GitHub\-Flavored Markdown)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]markdown_mmd\f[R] (MultiMarkdown)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]markdown_strict\f[R] (Markdown.pl)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]commonmark\f[R] (CommonMark)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]gfm\f[R] (Github\-Flavored Markdown)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]commonmark_x\f[R] (CommonMark with many pandoc extensions)
.PP
To see which extensions are supported for a given format, and which are
@@ -6327,12 +6352,12 @@ pandoc \-\-citeproc myinput.txt
.EE
.PP
To use this feature, you will need to have
-.IP \[bu] 2
+.IP \(bu 2
a document containing citations (see Citation syntax);
-.IP \[bu] 2
+.IP \(bu 2
a source of bibliographic data: either an external bibliography file or
-a list of \f[CR]references\f[R] in the document\[cq]s YAML metadata;
-.IP \[bu] 2
+a list of \f[CR]references\f[R] in the document\(cqs YAML metadata;
+.IP \(bu 2
optionally, a CSL citation style.
.SS Specifying bibliographic data
You can specify an external bibliography using the
@@ -6369,7 +6394,7 @@ italics
\f[CR]<b>...</b>\f[R]
bold
.TP
-\f[CR]<span style=\[dq]font\-variant:small\-caps;\[dq]>...</span>\f[R] or \f[CR]<sc>...</sc>\f[R]
+\f[CR]<span style=\(dqfont\-variant:small\-caps;\(dq>...</span>\f[R] or \f[CR]<sc>...</sc>\f[R]
small capitals
.TP
\f[CR]<sub>...</sub>\f[R]
@@ -6378,13 +6403,13 @@ subscript
\f[CR]<sup>...</sup>\f[R]
superscript
.TP
-\f[CR]<span class=\[dq]nocase\[dq]>...</span>\f[R]
+\f[CR]<span class=\(dqnocase\(dq>...</span>\f[R]
prevent a phrase from being capitalized as title case
.PP
As an alternative to specifying a bibliography file using
\f[CR]\-\-bibliography\f[R] or the YAML metadata field
\f[CR]bibliography\f[R], you can include the citation data directly in
-the \f[CR]references\f[R] field of the document\[cq]s YAML metadata.
+the \f[CR]references\f[R] field of the document\(cqs YAML metadata.
The field should contain an array of YAML\-encoded references, for
example:
.IP
@@ -6403,8 +6428,8 @@ references:
\- \- 1953
\- 4
\- 25
- title: \[aq]Molecular structure of nucleic acids: a structure for
- deoxyribose nucleic acid\[aq]
+ title: \(aqMolecular structure of nucleic acids: a structure for
+ deoxyribose nucleic acid\(aq
title\-short: Molecular structure of nucleic acids
container\-title: Nature
volume: 171
@@ -6447,7 +6472,7 @@ pandoc chem.bib \-s \-\-citeproc \-o chem.pdf
.SS Capitalization in titles
If you are using a bibtex or biblatex bibliography, then observe the
following rules:
-.IP \[bu] 2
+.IP \(bu 2
English titles should be in title case.
Non\-English titles should be in sentence case, and the
\f[CR]langid\f[R] field in biblatex should be set to the relevant
@@ -6456,9 +6481,9 @@ language.
\f[CR]british\f[R], \f[CR]canadian\f[R], \f[CR]english\f[R],
\f[CR]australian\f[R], \f[CR]newzealand\f[R], \f[CR]USenglish\f[R], or
\f[CR]UKenglish\f[R].)
-.IP \[bu] 2
+.IP \(bu 2
As is standard with bibtex/biblatex, proper names should be protected
-with curly braces so that they won\[cq]t be lowercased in styles that
+with curly braces so that they won\(cqt be lowercased in styles that
call for sentence case.
For example:
.RS 2
@@ -6467,7 +6492,7 @@ For example:
title = {My Dinner with {Andre}}
.EE
.RE
-.IP \[bu] 2
+.IP \(bu 2
In addition, words that should remain lowercase (or camelCase) should be
protected:
.RS 2
@@ -6479,26 +6504,26 @@ title = {Spin Wave Dispersion on the {nm} Scale}
Though this is not necessary in bibtex/biblatex, it is necessary with
citeproc, which stores titles internally in sentence case, and converts
to title case in styles that require it.
-Here we protect \[lq]nm\[rq] so that it doesn\[cq]t get converted to
-\[lq]Nm\[rq] at this stage.
+Here we protect \(lqnm\(rq so that it doesn\(cqt get converted to
+\(lqNm\(rq at this stage.
.RE
.PP
If you are using a CSL bibliography (either JSON or YAML), then observe
the following rules:
-.IP \[bu] 2
+.IP \(bu 2
All titles should be in sentence case.
-.IP \[bu] 2
+.IP \(bu 2
Use the \f[CR]language\f[R] field for non\-English titles to prevent
their conversion to title case in styles that call for this.
(Conversion happens only if \f[CR]language\f[R] begins with
\f[CR]en\f[R] or is left empty.)
-.IP \[bu] 2
+.IP \(bu 2
Protect words that should not be converted to title case using this
syntax:
.RS 2
.IP
.EX
-Spin wave dispersion on the <span class=\[dq]nocase\[dq]>nm</span> scale
+Spin wave dispersion on the <span class=\(dqnocase\(dq>nm</span> scale
.EE
.RE
.SS Conference Papers, Published vs.\ Unpublished
@@ -6515,11 +6540,11 @@ use the biblatex entry type \f[CR]unpublished\f[R] with an
\f[CR]eventtitle\f[R] field (this entry type will be mapped to CSL
\f[CR]speech\f[R]).
Use the biblatex \f[CR]type\f[R] field to indicate the type,
-e.g.\ \[lq]Paper\[rq], or \[lq]Poster\[rq].
+e.g.\ \(lqPaper\(rq, or \(lqPoster\(rq.
\f[CR]venue\f[R] and \f[CR]eventdate\f[R] may be useful too, though
\f[CR]eventdate\f[R] will not be rendered by most CSL styles.
-Note that \f[CR]venue\f[R] is for the event\[cq]s venue, unlike
-\f[CR]location\f[R] which describes the publisher\[cq]s location; do not
+Note that \f[CR]venue\f[R] is for the event\(cqs venue, unlike
+\f[CR]location\f[R] which describes the publisher\(cqs location; do not
use the latter for an unpublished conference paper.
.SS Specifying a citation style
Citations and references can be formatted using any style supported by
@@ -6536,30 +6561,30 @@ styles.
The \f[CR]\-\-citation\-abbreviations\f[R] option (or the
\f[CR]citation\-abbreviations\f[R] metadata field) may be used to
specify a JSON file containing abbreviations of journals that should be
-used in formatted bibliographies when \f[CR]form=\[dq]short\[dq]\f[R] is
+used in formatted bibliographies when \f[CR]form=\(dqshort\(dq\f[R] is
specified.
The format of the file can be illustrated with an example:
.IP
.EX
-{ \[dq]default\[dq]: {
- \[dq]container\-title\[dq]: {
- \[dq]Lloyd\[aq]s Law Reports\[dq]: \[dq]Lloyd\[aq]s Rep\[dq],
- \[dq]Estates Gazette\[dq]: \[dq]EG\[dq],
- \[dq]Scots Law Times\[dq]: \[dq]SLT\[dq]
+{ \(dqdefault\(dq: {
+ \(dqcontainer\-title\(dq: {
+ \(dqLloyd\(aqs Law Reports\(dq: \(dqLloyd\(aqs Rep\(dq,
+ \(dqEstates Gazette\(dq: \(dqEG\(dq,
+ \(dqScots Law Times\(dq: \(dqSLT\(dq
}
}
}
.EE
.SS Citations in note styles
-Pandoc\[cq]s citation processing is designed to allow you to move
-between author\-date, numerical, and note styles without modifying the
-Markdown source.
-When you\[cq]re using a note style, avoid inserting footnotes manually.
+Pandoc\(cqs citation processing is designed to allow you to move between
+author\-date, numerical, and note styles without modifying the Markdown
+source.
+When you\(cqre using a note style, avoid inserting footnotes manually.
Instead, insert citations just as you would in an author\-date
-style\[em]for example,
+style\(emfor example,
.IP
.EX
-Blah blah [\[at]foo, p. 33].
+Blah blah [\(atfoo, p. 33].
.EE
.PP
The footnote will be created automatically.
@@ -6569,17 +6594,17 @@ or after the period, depending on the setting of
relevant metadata fields.
.PP
In some cases you may need to put a citation inside a regular footnote.
-Normal citations in footnotes (such as \f[CR][\[at]foo, p. 33]\f[R])
-will be rendered in parentheses.
-In\-text citations (such as \f[CR]\[at]foo [p. 33]\f[R]) will be
-rendered without parentheses.
+Normal citations in footnotes (such as \f[CR][\(atfoo, p. 33]\f[R]) will
+be rendered in parentheses.
+In\-text citations (such as \f[CR]\(atfoo [p. 33]\f[R]) will be rendered
+without parentheses.
(A comma will be added if appropriate.)
Thus:
.IP
.EX
-[\[ha]1]: Some studies [\[at]foo; \[at]bar, p. 33] show that
+[\(ha1]: Some studies [\(atfoo; \(atbar, p. 33] show that
frubulicious zoosnaps are quantical. For a survey
-of the literature, see \[at]baz [chap. 1].
+of the literature, see \(atbaz [chap. 1].
.EE
.SS Placement of the bibliography
If the style calls for a list of works cited, it will be placed in a div
@@ -6631,10 +6656,10 @@ field and put the citations there:
.EX
\-\-\-
nocite: |
- \[at]item1, \[at]item2
+ \(atitem1, \(atitem2
\&...
-\[at]item3
+\(atitem3
.EE
.PP
In this example, the document will contain a citation for
@@ -6647,7 +6672,7 @@ or not they appear in the document, by using a wildcard:
.EX
\-\-\-
nocite: |
- \[at]*
+ \(at*
\&...
.EE
.PP
@@ -6688,15 +6713,15 @@ A BCP 47 language tag is expected: for example, \f[CR]en\f[R],
The unicode extension syntax (after \f[CR]\-u\-\f[R]) may be used to
specify options for collation (sorting) more precisely.
Here are some examples:
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]zh\-u\-co\-pinyin\f[R]: Chinese with the Pinyin collation.
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]es\-u\-co\-trad\f[R]: Spanish with the traditional collation (with
\f[CR]Ch\f[R] sorting after \f[CR]C\f[R]).
-.IP \[bu] 2
-\f[CR]fr\-u\-kb\f[R]: French with \[lq]backwards\[rq] accent sorting
-(with \f[CR]coté\f[R] sorting after \f[CR]côte\f[R]).
-.IP \[bu] 2
+.IP \(bu 2
+\f[CR]fr\-u\-kb\f[R]: French with \(lqbackwards\(rq accent sorting (with
+\f[CR]coté\f[R] sorting after \f[CR]côte\f[R]).
+.IP \(bu 2
\f[CR]en\-US\-u\-kf\-upper\f[R]: English with uppercase letters sorting
before lower (default is lower before upper).
.RE
@@ -6705,10 +6730,9 @@ before lower (default is lower before upper).
If true (the default for note styles), pandoc will put footnote
references or superscripted numerical citations after following
punctuation.
-For example, if the source contains
-\f[CR]blah blah [\[at]jones99].\f[R], the result will look like
-\f[CR]blah blah.[\[ha]1]\f[R], with the note moved after the period and
-the space collapsed.
+For example, if the source contains \f[CR]blah blah [\(atjones99].\f[R],
+the result will look like \f[CR]blah blah.[\(ha1]\f[R], with the note
+moved after the period and the space collapsed.
If false, the space will still be collapsed, but the footnote will not
be moved after the punctuation.
The option may also be used in numerical styles that use superscripts
@@ -6722,7 +6746,7 @@ reveal.js.
You can also produce a PDF slide show using LaTeX \f[CR]beamer\f[R], or
slide shows in Microsoft PowerPoint format.
.PP
-Here\[cq]s the Markdown source for a simple slide show,
+Here\(cqs the Markdown source for a simple slide show,
\f[CR]habits.txt\f[R]:
.IP
.EX
@@ -6809,33 +6833,33 @@ This default can be overridden using the \f[CR]\-\-slide\-level\f[R]
option.
.PP
The document is carved up into slides according to the following rules:
-.IP \[bu] 2
+.IP \(bu 2
A horizontal rule always starts a new slide.
-.IP \[bu] 2
+.IP \(bu 2
A heading at the slide level always starts a new slide.
-.IP \[bu] 2
+.IP \(bu 2
Headings \f[I]below\f[R] the slide level in the hierarchy create
headings \f[I]within\f[R] a slide.
-(In beamer, a \[lq]block\[rq] will be created.
+(In beamer, a \(lqblock\(rq will be created.
If the heading has the class \f[CR]example\f[R], an
\f[CR]exampleblock\f[R] environment will be used; if it has the class
\f[CR]alert\f[R], an \f[CR]alertblock\f[R] will be used; otherwise a
regular \f[CR]block\f[R] will be used.)
-.IP \[bu] 2
+.IP \(bu 2
Headings \f[I]above\f[R] the slide level in the hierarchy create
-\[lq]title slides,\[rq] which just contain the section title and help to
+\(lqtitle slides,\(rq which just contain the section title and help to
break the slide show into sections.
Non\-slide content under these headings will be included on the title
slide (for HTML slide shows) or in a subsequent slide with the same
title (for beamer).
-.IP \[bu] 2
-A title page is constructed automatically from the document\[cq]s title
+.IP \(bu 2
+A title page is constructed automatically from the document\(cqs title
block, if present.
(In the case of beamer, this can be disabled by commenting out some
lines in the default template.)
.PP
These rules are designed to support many different styles of slide show.
-If you don\[cq]t care about structuring your slides into sections and
+If you don\(cqt care about structuring your slides into sections and
subsections, you can either just use level\-1 headings for all slides
(in that case, level 1 will be the slide level) or you can set
\f[CR]\-\-slide\-level=0\f[R].
@@ -6857,7 +6881,7 @@ from the metadata fields \f[CR]date\f[R], \f[CR]author\f[R], and
\f[CR]title\f[R], if they are present.
.TP
Section Header
-This layout is used for what pandoc calls \[lq]title slides\[rq], i.e.
+This layout is used for what pandoc calls \(lqtitle slides\(rq, i.e.
slides which start with a header which is above the slide level in the
hierarchy.
.TP
@@ -6867,7 +6891,7 @@ div with class \f[CR]columns\f[R] which contains at least two divs with
class \f[CR]column\f[R].
.TP
Comparison
-This layout is used instead of \[lq]Two Content\[rq] for any two\-column
+This layout is used instead of \(lqTwo Content\(rq for any two\-column
slides in which at least one column contains text followed by non\-text
(e.g.\ an image or a table).
.TP
@@ -6888,9 +6912,9 @@ These layouts are chosen from the default pptx reference doc included
with pandoc, unless an alternative reference doc is specified using
\f[CR]\-\-reference\-doc\f[R].
.SS Incremental lists
-By default, these writers produce lists that display \[lq]all at
-once.\[rq] If you want your lists to display incrementally (one item at
-a time), use the \f[CR]\-i\f[R] option.
+By default, these writers produce lists that display \(lqall at
+once.\(rq If you want your lists to display incrementally (one item at a
+time), use the \f[CR]\-i\f[R] option.
If you want a particular list to depart from the default, put it in a
\f[CR]div\f[R] block with class \f[CR]incremental\f[R] or
\f[CR]nonincremental\f[R].
@@ -6943,7 +6967,7 @@ direct child of the block quote:
> :::
.EE
.SS Inserting pauses
-You can add \[lq]pauses\[rq] within a slide by including a paragraph
+You can add \(lqpauses\(rq within a slide by including a paragraph
containing three dots, separated by spaces:
.IP
.EX
@@ -6963,7 +6987,7 @@ in \f[CR]$DATADIR/s5/default\f[R] (for S5), \f[CR]$DATADIR/slidy\f[R]
(for Slidy), or \f[CR]$DATADIR/slideous\f[R] (for Slideous), where
\f[CR]$DATADIR\f[R] is the user data directory (see
\f[CR]\-\-data\-dir\f[R], above).
-The originals may be found in pandoc\[cq]s system data directory
+The originals may be found in pandoc\(cqs system data directory
(generally \f[CR]$CABALDIR/pandoc\-VERSION/s5/default\f[R]).
Pandoc will look there for any files it does not find in the user data
directory.
@@ -7027,10 +7051,10 @@ attribute:
.IP
.EX
:::::::::::::: {.columns}
-::: {.column width=\[dq]40%\[dq]}
+::: {.column width=\(dq40%\(dq}
contents...
:::
-::: {.column width=\[dq]60%\[dq]}
+::: {.column width=\(dq60%\(dq}
contents...
:::
::::::::::::::
@@ -7045,10 +7069,10 @@ attribute or an \f[CR]onlytextwidth\f[R] class.
.IP
.EX
:::::::::::::: {.columns align=center totalwidth=8em}
-::: {.column width=\[dq]40%\[dq]}
+::: {.column width=\(dq40%\(dq}
contents...
:::
-::: {.column width=\[dq]60%\[dq] align=bottom}
+::: {.column width=\(dq60%\(dq align=bottom}
contents...
:::
::::::::::::::
@@ -7065,19 +7089,19 @@ the given value.
.IP
.EX
:::::::::::::: {.columns align=top .onlytextwidth}
-::: {.column width=\[dq]40%\[dq] align=center}
+::: {.column width=\(dq40%\(dq align=center}
contents...
:::
-::: {.column width=\[dq]60%\[dq]}
+::: {.column width=\(dq60%\(dq}
contents...
:::
::::::::::::::
.EE
.PP
The class \f[CR]onlytextwidth\f[R] sets the \f[CR]totalwidth\f[R] to
-\f[CR]\[rs]textwidth\f[R].
+\f[CR]\(rstextwidth\f[R].
.PP
-See Section 12.7 of the Beamer User\[cq]s Guide for more details.
+See Section 12.7 of the Beamer User\(cqs Guide for more details.
.SS Frame attributes in beamer
Sometimes it is necessary to add the LaTeX \f[CR][fragile]\f[R] option
to a frame in beamer (for example, when using the \f[CR]minted\f[R]
@@ -7090,7 +7114,7 @@ introducing the slide:
.EE
.PP
All of the other frame attributes described in Section 8.1 of the Beamer
-User\[cq]s Guide may also be used: \f[CR]allowdisplaybreaks\f[R],
+User\(cqs Guide may also be used: \f[CR]allowdisplaybreaks\f[R],
\f[CR]allowframebreaks\f[R], \f[CR]b\f[R], \f[CR]c\f[R], \f[CR]s\f[R],
\f[CR]t\f[R], \f[CR]environment\f[R], \f[CR]label\f[R],
\f[CR]plain\f[R], \f[CR]shrink\f[R], \f[CR]standout\f[R],
@@ -7107,7 +7131,7 @@ In addition, the \f[CR]frameoptions\f[R] attribute may be used to pass
arbitrary frame options to a beamer slide:
.IP
.EX
-# Heading {frameoptions=\[dq]squeeze,shrink,customoption=foobar\[dq]}
+# Heading {frameoptions=\(dqsqueeze,shrink,customoption=foobar\(dq}
.EE
.SS Background in reveal.js, beamer, and pptx
Background images can be added to self\-contained reveal.js slide shows,
@@ -7134,11 +7158,11 @@ behaviour.
See the reveal.js documentation for more details about the meaning of
these options.
.PP
-In reveal.js\[cq]s overview mode, the parallaxBackgroundImage will show
+In reveal.js\(cqs overview mode, the parallaxBackgroundImage will show
up only on the first slide.
.SS On individual slides (reveal.js, pptx)
To set an image for a particular reveal.js or pptx slide, add
-\f[CR]{background\-image=\[dq]/path/to/image\[dq]}\f[R] to the first
+\f[CR]{background\-image=\(dq/path/to/image\(dq}\f[R] to the first
slide\-level heading on the slide (which may even be empty).
.PP
As the HTML writers pass unknown attributes through, other reveal.js
@@ -7149,18 +7173,18 @@ background settings also work on individual slides, including
(The \f[CR]data\-\f[R] prefix will automatically be added.)
.PP
Note: \f[CR]data\-background\-image\f[R] is also supported in pptx for
-consistency with reveal.js \[en] if \f[CR]background\-image\f[R]
-isn\[cq]t found, \f[CR]data\-background\-image\f[R] will be checked.
+consistency with reveal.js \(en if \f[CR]background\-image\f[R] isn\(cqt
+found, \f[CR]data\-background\-image\f[R] will be checked.
.SS On the title slide (reveal.js, pptx)
To add a background image to the automatically generated title slide for
reveal.js, use the \f[CR]title\-slide\-attributes\f[R] variable in the
YAML metadata block.
It must contain a map of attribute names and values.
-(Note that the \f[CR]data\-\f[R] prefix is required here, as it
-isn\[cq]t added automatically.)
+(Note that the \f[CR]data\-\f[R] prefix is required here, as it isn\(cqt
+added automatically.)
.PP
For pptx, pass a \f[CR]\-\-reference\-doc\f[R] with the background image
-set on the \[lq]Title Slide\[rq] layout.
+set on the \(lqTitle Slide\(rq layout.
.SS Example (reveal.js)
.IP
.EX
@@ -7176,7 +7200,7 @@ title\-slide\-attributes:
Slide 1 has background_image.png as its background.
-## {background\-image=\[dq]/path/to/special_image.jpg\[dq]}
+## {background\-image=\(dq/path/to/special_image.jpg\(dq}
Slide 2 has a special image for its background, even though the heading has no content.
.EE
@@ -7236,8 +7260,8 @@ Valid values for \f[CR]type\f[R] are \f[CR]main\f[R],
Either a string value, or an object with fields \f[CR]role\f[R],
\f[CR]file\-as\f[R], and \f[CR]text\f[R], or a list of such objects.
Valid values for \f[CR]role\f[R] are MARC relators, but pandoc will
-attempt to translate the human\-readable versions (like \[lq]author\[rq]
-and \[lq]editor\[rq]) to the appropriate marc relators.
+attempt to translate the human\-readable versions (like \(lqauthor\(rq
+and \(lqeditor\(rq) to the appropriate marc relators.
.TP
\f[CR]contributor\f[R]
Same format as \f[CR]creator\f[R].
@@ -7303,15 +7327,15 @@ Specifies the \f[CR]page\-progression\-direction\f[R] attribute for the
.TP
\f[CR]accessModes\f[R]
An array of strings (schema).
-Defaults to \f[CR][\[dq]textual\[dq]]\f[R].
+Defaults to \f[CR][\(dqtextual\(dq]\f[R].
.TP
\f[CR]accessModeSufficient\f[R]
An array of strings (schema).
-Defaults to \f[CR][\[dq]textual\[dq]]\f[R].
+Defaults to \f[CR][\(dqtextual\(dq]\f[R].
.TP
\f[CR]accessibilityHazards\f[R]
An array of strings (schema).
-Defaults to \f[CR][\[dq]none\[dq]]\f[R].
+Defaults to \f[CR][\(dqnone\(dq]\f[R].
.TP
\f[CR]accessibilityFeatures\f[R]
An array of strings (schema).
@@ -7319,10 +7343,10 @@ Defaults to
.RS
.IP
.EX
-\- \[dq]alternativeText\[dq]
-\- \[dq]readingOrder\[dq]
-\- \[dq]structuralNavigation\[dq]
-\- \[dq]tableOfContents\[dq]
+\- \(dqalternativeText\(dq
+\- \(dqreadingOrder\(dq
+\- \(dqstructuralNavigation\(dq
+\- \(dqtableOfContents\(dq
.EE
.RE
.TP
@@ -7332,21 +7356,21 @@ A string value.
\f[CR]ibooks\f[R]
iBooks\-specific metadata, with the following fields:
.RS
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]version\f[R]: (string)
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]specified\-fonts\f[R]: \f[CR]true\f[R]|\f[CR]false\f[R] (default
\f[CR]false\f[R])
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]ipad\-orientation\-lock\f[R]:
\f[CR]portrait\-only\f[R]|\f[CR]landscape\-only\f[R]
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]iphone\-orientation\-lock\f[R]:
\f[CR]portrait\-only\f[R]|\f[CR]landscape\-only\f[R]
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]binding\f[R]: \f[CR]true\f[R]|\f[CR]false\f[R] (default
\f[CR]true\f[R])
-.IP \[bu] 2
+.IP \(bu 2
\f[CR]scroll\-axis\f[R]:
\f[CR]vertical\f[R]|\f[CR]horizontal\f[R]|\f[CR]default\f[R]
.RE
@@ -7363,12 +7387,12 @@ this Markdown:
Which will result in:
.IP
.EX
-<body epub:type=\[dq]frontmatter\[dq]>
- <section epub:type=\[dq]prologue\[dq]>
+<body epub:type=\(dqfrontmatter\(dq>
+ <section epub:type=\(dqprologue\(dq>
<h1>My chapter</h1>
.EE
.PP
-Pandoc will output \f[CR]<body epub:type=\[dq]bodymatter\[dq]>\f[R],
+Pandoc will output \f[CR]<body epub:type=\(dqbodymatter\(dq>\f[R],
unless you use one of the following values, in which case either
\f[CR]frontmatter\f[R] or \f[CR]backmatter\f[R] will be output.
.RS -14n
@@ -7406,25 +7430,25 @@ By default, pandoc will download media referenced from any
\f[CR]<source>\f[R] element present in the generated EPUB, and include
it in the EPUB container, yielding a completely self\-contained EPUB.
If you want to link to external media resources instead, use raw HTML in
-your source and add \f[CR]data\-external=\[dq]1\[dq]\f[R] to the tag
-with the \f[CR]src\f[R] attribute.
+your source and add \f[CR]data\-external=\(dq1\(dq\f[R] to the tag with
+the \f[CR]src\f[R] attribute.
For example:
.IP
.EX
-<audio controls=\[dq]1\[dq]>
- <source src=\[dq]https://example.com/music/toccata.mp3\[dq]
- data\-external=\[dq]1\[dq] type=\[dq]audio/mpeg\[dq]>
+<audio controls=\(dq1\(dq>
+ <source src=\(dqhttps://example.com/music/toccata.mp3\(dq
+ data\-external=\(dq1\(dq type=\(dqaudio/mpeg\(dq>
</source>
</audio>
.EE
.PP
If the input format already is HTML then
-\f[CR]data\-external=\[dq]1\[dq]\f[R] will work as expected for
+\f[CR]data\-external=\(dq1\(dq\f[R] will work as expected for
\f[CR]<img>\f[R] elements.
Similarly, for Markdown, external images can be declared with
\f[CR]![img](url){external=1}\f[R].
Note that this only works for images; the other media elements have no
-native representation in pandoc\[cq]s AST and require the use of raw
+native representation in pandoc\(cqs AST and require the use of raw
HTML.
.SS EPUB styling
By default, pandoc will include some basic styling contained in its
@@ -7434,10 +7458,10 @@ By default, pandoc will include some basic styling contained in its
To use a different CSS file, just use the \f[CR]\-\-css\f[R] command
line option.
A few inline styles are defined in addition; these are essential for
-correct formatting of pandoc\[cq]s HTML output.
+correct formatting of pandoc\(cqs HTML output.
.PP
The \f[CR]document\-css\f[R] variable may be set if the more opinionated
-styling of pandoc\[cq]s default HTML templates is desired (and in that
+styling of pandoc\(cqs default HTML templates is desired (and in that
case the variables defined in Variables for HTML may be used to
fine\-tune the style).
.SH CHUNKED HTML
@@ -7481,12 +7505,12 @@ jupyter:
codemirror_mode:
name: ipython
version: 2
- file_extension: \[dq].py\[dq]
- mimetype: \[dq]text/x\-python\[dq]
- name: \[dq]python\[dq]
- nbconvert_exporter: \[dq]python\[dq]
- pygments_lexer: \[dq]ipython2\[dq]
- version: \[dq]2.7.15\[dq]
+ file_extension: \(dq.py\(dq
+ mimetype: \(dqtext/x\-python\(dq
+ name: \(dqpython\(dq
+ nbconvert_exporter: \(dqpython\(dq
+ pygments_lexer: \(dqipython2\(dq
+ version: \(dq2.7.15\(dq
\-\-\-
# Lorem ipsum
@@ -7494,21 +7518,21 @@ jupyter:
**Lorem ipsum** dolor sit amet, consectetur adipiscing elit. Nunc luctus
bibendum felis dictum sodales.
-\[ga]\[ga]\[ga] code
-print(\[dq]hello\[dq])
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga code
+print(\(dqhello\(dq)
+\(ga\(ga\(ga
## Pyout
-\[ga]\[ga]\[ga] code
+\(ga\(ga\(ga code
from IPython.display import HTML
-HTML(\[dq]\[dq]\[dq]
+HTML(\(dq\(dq\(dq
<script>
-console.log(\[dq]hello\[dq]);
+console.log(\(dqhello\(dq);
</script>
<b>HTML</b>
-\[dq]\[dq]\[dq])
-\[ga]\[ga]\[ga]
+\(dq\(dq\(dq)
+\(ga\(ga\(ga
## Image
@@ -7531,45 +7555,45 @@ bibendum felis dictum sodales.
::::::
:::::: {.cell .code execution_count=1}
-\[ga]\[ga]\[ga] {.python}
-print(\[dq]hello\[dq])
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga {.python}
+print(\(dqhello\(dq)
+\(ga\(ga\(ga
::: {.output .stream .stdout}
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga
hello
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga
:::
::::::
:::::: {.cell .code execution_count=2}
-\[ga]\[ga]\[ga] {.python}
+\(ga\(ga\(ga {.python}
from IPython.display import HTML
-HTML(\[dq]\[dq]\[dq]
+HTML(\(dq\(dq\(dq
<script>
-console.log(\[dq]hello\[dq]);
+console.log(\(dqhello\(dq);
</script>
<b>HTML</b>
-\[dq]\[dq]\[dq])
-\[ga]\[ga]\[ga]
+\(dq\(dq\(dq)
+\(ga\(ga\(ga
::: {.output .execute_result execution_count=2}
-\[ga]\[ga]\[ga]{=html}
+\(ga\(ga\(ga{=html}
<script>
-console.log(\[dq]hello\[dq]);
+console.log(\(dqhello\(dq);
</script>
<b>HTML</b>
hello
-\[ga]\[ga]\[ga]
+\(ga\(ga\(ga
:::
::::::
.EE
.PP
If you include raw HTML or TeX in an output cell, use the raw attribute,
as shown in the last cell of the example above.
-Although pandoc can process \[lq]bare\[rq] raw HTML and TeX, the result
-is often interspersed raw elements and normal textual elements, and in
-an output cell pandoc expects a single, connected raw block.
+Although pandoc can process \(lqbare\(rq raw HTML and TeX, the result is
+often interspersed raw elements and normal textual elements, and in an
+output cell pandoc expects a single, connected raw block.
To avoid using raw HTML or TeX except when marked explicitly using raw
attributes, we recommend specifying the extensions
\f[CR]\-raw_html\-raw_tex+raw_attribute\f[R] when translating between
@@ -7615,21 +7639,21 @@ pandoc \-\-highlight\-style my.theme
.EE
.PP
If you are not satisfied with the built\-in highlighting, or you want to
-highlight a language that isn\[cq]t supported, you can use the
+highlight a language that isn\(cqt supported, you can use the
\f[CR]\-\-syntax\-definition\f[R] option to load a KDE\-style XML syntax
definition file.
-Before writing your own, have a look at KDE\[cq]s repository of syntax
+Before writing your own, have a look at KDE\(cqs repository of syntax
definitions.
.PP
-If you receive an error that pandoc \[lq]Could not read highlighting
-theme\[rq], check that the JSON file is encoded with UTF\-8 and has no
+If you receive an error that pandoc \(lqCould not read highlighting
+theme\(rq, check that the JSON file is encoded with UTF\-8 and has no
Byte\-Order Mark (BOM).
.PP
To disable highlighting, use the \f[CR]\-\-no\-highlight\f[R] option.
.SH CUSTOM STYLES
Custom styles can be used in the docx, odt and ICML formats.
.SS Output
-By default, pandoc\[cq]s odt, docx and ICML output applies a predefined
+By default, pandoc\(cqs odt, docx and ICML output applies a predefined
set of styles for blocks such as paragraphs and block quotes, and uses
largely default formatting (italics, bold) for inlines.
This will work for most purposes, especially alongside a reference doc
@@ -7646,17 +7670,17 @@ depends on a style, like headings, code blocks, block quotes, or links).
So, for example, using the \f[CR]bracketed_spans\f[R] syntax,
.IP
.EX
-[Get out]{custom\-style=\[dq]Emphatically\[dq]}, he said.
+[Get out]{custom\-style=\(dqEmphatically\(dq}, he said.
.EE
.PP
-would produce a file with \[lq]Get out\[rq] styled with character style
+would produce a file with \(lqGet out\(rq styled with character style
\f[CR]Emphatically\f[R].
Similarly, using the \f[CR]fenced_divs\f[R] syntax,
.IP
.EX
Dickinson starts the poem simply:
-::: {custom\-style=\[dq]Poetry\[dq]}
+::: {custom\-style=\(dqPoetry\(dq}
| A Bird came down the Walk\-\-\-
| He did not know I saw\-\-\-
:::
@@ -7679,12 +7703,12 @@ character style (perhaps to change their color), you can write a filter
which will transform all italicized inlines to inlines within an
\f[CR]Emphasis\f[R] custom\-style \f[CR]span\f[R].
.PP
-For docx or odt output, you don\[cq]t need to enable any extensions for
+For docx or odt output, you don\(cqt need to enable any extensions for
custom styles to work.
.SS Input
The docx reader, by default, only reads those styles that it can convert
into pandoc elements, either by direct conversion or interpreting the
-derivation of the input document\[cq]s styles.
+derivation of the input document\(cqs styles.
.PP
By enabling the \f[CR]styles\f[R] extension in the docx reader
(\f[CR]\-f docx+styles\f[R]), you can produce output that maintains the
@@ -7714,17 +7738,17 @@ And with the extension:
.EX
$ pandoc test/docx/custom\-style\-reference.docx \-f docx+styles \-t markdown
-::: {custom\-style=\[dq]First Paragraph\[dq]}
+::: {custom\-style=\(dqFirst Paragraph\(dq}
This is some text.
:::
-::: {custom\-style=\[dq]Body Text\[dq]}
-This is text with an [emphasized]{custom\-style=\[dq]Emphatic\[dq]} text style.
-And this is text with a [strengthened]{custom\-style=\[dq]Strengthened\[dq]}
+::: {custom\-style=\(dqBody Text\(dq}
+This is text with an [emphasized]{custom\-style=\(dqEmphatic\(dq} text style.
+And this is text with a [strengthened]{custom\-style=\(dqStrengthened\(dq}
text style.
:::
-::: {custom\-style=\[dq]My Block Style\[dq]}
+::: {custom\-style=\(dqMy Block Style\(dq}
> Here is a styled paragraph that inherits from Block Text.
:::
.EE
@@ -7836,7 +7860,7 @@ PDF/A and PDF/UA since version 57.
Tagged PDFs can created with
.IP
.EX
-pandoc \-\-pdf\-engine=weasyprint \[rs]
+pandoc \-\-pdf\-engine=weasyprint \(rs
\-\-pdf\-engine\-opt=\-\-pdf\-variant=pdf/ua\-1 ...
.EE
.PP
@@ -7848,7 +7872,7 @@ support for various PDF standards as well as tagging.
E.g.:
.IP
.EX
-pandoc \-\-pdf\-engine=prince \[rs]
+pandoc \-\-pdf\-engine=prince \(rs
\-\-pdf\-engine\-opt=\-\-tagged\-pdf ...
.EE
.PP
@@ -7879,7 +7903,7 @@ If you rename (or symlink) the pandoc executable to
exposing the same API as \f[CR]pandoc\-server\f[R].
.PP
\f[CR]pandoc\-server\f[R] is designed to be maximally secure; it uses
-Haskell\[cq]s type system to provide strong guarantees that no I/O will
+Haskell\(cqs type system to provide strong guarantees that no I/O will
be performed on the server during pandoc conversions.
.SH RUNNING PANDOC AS A LUA INTERPRETER
Calling the pandoc executable under the name \f[CR]pandoc\-lua\f[R] or
@@ -7887,6 +7911,11 @@ with \f[CR]lua\f[R] as the first argument will make it function as a
standalone Lua interpreter.
The behavior is mostly identical to that of the standalone
\f[CR]lua\f[R] executable, version 5.4.
+All \f[CR]pandoc.*\f[R] packages, as well as the packages \f[CR]re\f[R]
+and \f[CR]lpeg\f[R], are available via global variables.
+Furthermore, the globals \f[CR]PANDOC_VERSION\f[R],
+\f[CR]PANDOC_STATE\f[R], and \f[CR]PANDOC_API_VERSION\f[R] are set at
+startup.
For full documentation, see the pandoc\-lua man page.
.SH A NOTE ON SECURITY
.IP "1." 3
@@ -7920,7 +7949,7 @@ If untrusted HTML is processed on a server, this has the potential to
reveal anything readable by the process running the server.
Using the \f[CR]\-f html+raw_html\f[R] will mitigate this threat by
causing the whole \f[CR]iframe\f[R] to be parsed as a raw HTML block.
-Using \[ga]\[en]sandbox will also protect against the threat.
+Using \(ga\(ensandbox will also protect against the threat.
.IP "5." 3
If your application uses pandoc as a Haskell library (rather than
shelling out to the executable), it is possible to use it in a mode that
@@ -7930,7 +7959,7 @@ See the document Using the pandoc API for more details.
(This corresponds to the use of the \f[CR]\-\-sandbox\f[R] option on the
command line.)
.IP "6." 3
-Pandoc\[cq]s parsers can exhibit pathological performance on some corner
+Pandoc\(cqs parsers can exhibit pathological performance on some corner
cases.
It is wise to put any pandoc operations under a timeout, to avoid DOS
attacks that exploit these issues.
@@ -7950,7 +7979,7 @@ content in URLs and attributes.
To be safe, you should run all HTML generated from untrusted user input
through an HTML sanitizer.
.SH AUTHORS
-Copyright 2006\[en]2024 John MacFarlane (jgm\[at]berkeley.edu).
+Copyright 2006\(en2024 John MacFarlane (jgm\(atberkeley.edu).
Released under the GPL, version 2 or greater.
This software carries no warranty of any kind.
(See COPYRIGHT for full copyright and warranty notices.)
generated by cgit v1.2.3 (git 2.46.0) at 2026-01-26 21:48:24 +0000