@@ -1,10 +1,10 @@
2−.TH PANDOC 1 "November 4, 2017" "pandoc 2.0.1.1"
2+.TH PANDOC 1 "November 11, 2017" "pandoc 2.0.1.1"
4pandoc - general markup converter
4pandoc - general markup converter
5.SH SYNOPSIS
5.SH SYNOPSIS
7−\f[C]pandoc\f[] [\f[I]options\f[]] [\f[I]input\-file\f[]]\&...
7+\f[C]pandoc\f[] [\f[I]options\f[]] [\f[I]input\-file\f[]]...
8.SH DESCRIPTION
8.SH DESCRIPTION
10Pandoc is a Haskell library for converting from one markup format to
10Pandoc is a Haskell library for converting from one markup format to
@@ -25,13 +25,13 @@ It can also produce PDF output on systems where LaTeX, ConTeXt,
25\f[C]pdfroff\f[], \f[C]wkhtmltopdf\f[], \f[C]prince\f[], or
25\f[C]pdfroff\f[], \f[C]wkhtmltopdf\f[], \f[C]prince\f[], or
26\f[C]weasyprint\f[] is installed.
26\f[C]weasyprint\f[] is installed.
28−Pandoc's enhanced version of Markdown includes syntax for footnotes,
28+Pandoc\[aq]s enhanced version of Markdown includes syntax for footnotes,
29tables, flexible ordered lists, definition lists, fenced code blocks,
29tables, flexible ordered lists, definition lists, fenced code blocks,
30superscripts and subscripts, strikeout, metadata blocks, automatic
30superscripts and subscripts, strikeout, metadata blocks, automatic
31tables of contents, embedded LaTeX math, citations, and Markdown inside
31tables of contents, embedded LaTeX math, citations, and Markdown inside
32HTML block elements.
32HTML block elements.
33−(These enhancements, described further under Pandoc's Markdown, can be
33+(These enhancements, described further under Pandoc\[aq]s Markdown, can
34−disabled using the \f[C]markdown_strict\f[] input or output format.)
34+be disabled using the \f[C]markdown_strict\f[] input or output format.)
36In contrast to most existing tools for converting Markdown to HTML,
36In contrast to most existing tools for converting Markdown to HTML,
37which use regex substitutions, pandoc has a modular design: it consists
37which use regex substitutions, pandoc has a modular design: it consists
@@ -41,16 +41,16 @@ convert this native representation into a target format.
41Thus, adding an input or output format requires only adding a reader or
41Thus, adding an input or output format requires only adding a reader or
44−Because pandoc's intermediate representation of a document is less
44+Because pandoc\[aq]s intermediate representation of a document is less
45expressive than many of the formats it converts between, one should not
45expressive than many of the formats it converts between, one should not
46expect perfect conversions between every format and every other.
46expect perfect conversions between every format and every other.
47Pandoc attempts to preserve the structural elements of a document, but
47Pandoc attempts to preserve the structural elements of a document, but
48not formatting details such as margin size.
48not formatting details such as margin size.
49And some document elements, such as complex tables, may not fit into
49And some document elements, such as complex tables, may not fit into
50−pandoc's simple document model.
50+pandoc\[aq]s simple document model.
51−While conversions from pandoc's Markdown to all formats aspire to be
51+While conversions from pandoc\[aq]s Markdown to all formats aspire to be
52−perfect, conversions from formats more expressive than pandoc's Markdown
52+perfect, conversions from formats more expressive than pandoc\[aq]s
53−can be expected to be lossy.
53+Markdown can be expected to be lossy.
54.SS Using \f[C]pandoc\f[]
54.SS Using \f[C]pandoc\f[]
56If no \f[I]input\-file\f[] is specified, input is read from
56If no \f[I]input\-file\f[] is specified, input is read from
@@ -150,11 +150,11 @@ pandoc\ \-o\ hello.tex\ hello.txt
151will convert \f[C]hello.txt\f[] from Markdown to LaTeX.
151will convert \f[C]hello.txt\f[] from Markdown to LaTeX.
152If no output file is specified (so that output goes to \f[I]stdout\f[]),
152If no output file is specified (so that output goes to \f[I]stdout\f[]),
153−or if the output file's extension is unknown, the output format will
153+or if the output file\[aq]s extension is unknown, the output format will
154default to HTML.
154default to HTML.
155If no input file is specified (so that input comes from \f[I]stdin\f[]),
155If no input file is specified (so that input comes from \f[I]stdin\f[]),
156−or if the input files' extensions are unknown, the input format will be
156+or if the input files\[aq] extensions are unknown, the input format will
157−assumed to be Markdown unless explicitly specified.
157+be assumed to be Markdown unless explicitly specified.
159Pandoc uses the UTF\-8 character encoding for both input and output.
159Pandoc uses the UTF\-8 character encoding for both input and output.
160If your local character encoding is not UTF\-8, you should pipe input
160If your local character encoding is not UTF\-8, you should pipe input
@@ -228,7 +228,7 @@ If \f[C]wkhtmltopdf\f[] is used, then the variables
228.B \f[C]\-f\f[] \f[I]FORMAT\f[], \f[C]\-r\f[] \f[I]FORMAT\f[], \f[C]\-\-from=\f[]\f[I]FORMAT\f[], \f[C]\-\-read=\f[]\f[I]FORMAT\f[]
228.B \f[C]\-f\f[] \f[I]FORMAT\f[], \f[C]\-r\f[] \f[I]FORMAT\f[], \f[C]\-\-from=\f[]\f[I]FORMAT\f[], \f[C]\-\-read=\f[]\f[I]FORMAT\f[]
229Specify input format.
229Specify input format.
230\f[I]FORMAT\f[] can be \f[C]native\f[] (native Haskell), \f[C]json\f[]
230\f[I]FORMAT\f[] can be \f[C]native\f[] (native Haskell), \f[C]json\f[]
231−(JSON version of native AST), \f[C]markdown\f[] (pandoc's extended
231+(JSON version of native AST), \f[C]markdown\f[] (pandoc\[aq]s extended
232Markdown), \f[C]markdown_strict\f[] (original unextended Markdown),
232Markdown), \f[C]markdown_strict\f[] (original unextended Markdown),
233\f[C]markdown_phpextra\f[] (PHP Markdown Extra), \f[C]markdown_mmd\f[]
233\f[C]markdown_phpextra\f[] (PHP Markdown Extra), \f[C]markdown_mmd\f[]
234(MultiMarkdown), \f[C]gfm\f[] (GitHub\-Flavored Markdown),
234(MultiMarkdown), \f[C]gfm\f[] (GitHub\-Flavored Markdown),
@@ -250,9 +250,10 @@ appending \f[C]+EXTENSION\f[] or \f[C]\-EXTENSION\f[] to the format
251So, for example, \f[C]markdown_strict+footnotes+definition_lists\f[] is
251So, for example, \f[C]markdown_strict+footnotes+definition_lists\f[] is
252strict Markdown with footnotes and definition lists enabled, and
252strict Markdown with footnotes and definition lists enabled, and
253−\f[C]markdown\-pipe_tables+hard_line_breaks\f[] is pandoc's Markdown
253+\f[C]markdown\-pipe_tables+hard_line_breaks\f[] is pandoc\[aq]s Markdown
254without pipe tables and with hard line breaks.
254without pipe tables and with hard line breaks.
255−See Pandoc's Markdown, below, for a list of extensions and their names.
255+See Pandoc\[aq]s Markdown, below, for a list of extensions and their
256See \f[C]\-\-list\-input\-formats\f[] and \f[C]\-\-list\-extensions\f[],
257See \f[C]\-\-list\-input\-formats\f[] and \f[C]\-\-list\-extensions\f[],
@@ -262,16 +263,17 @@ below.
262Specify output format.
263Specify output format.
263\f[I]FORMAT\f[] can be \f[C]native\f[] (native Haskell), \f[C]json\f[]
264\f[I]FORMAT\f[] can be \f[C]native\f[] (native Haskell), \f[C]json\f[]
264(JSON version of native AST), \f[C]plain\f[] (plain text),
265(JSON version of native AST), \f[C]plain\f[] (plain text),
265−\f[C]markdown\f[] (pandoc's extended Markdown), \f[C]markdown_strict\f[]
266+\f[C]markdown\f[] (pandoc\[aq]s extended Markdown),
267+\f[C]markdown_strict\f[] (original unextended Markdown),
266−(original unextended Markdown), \f[C]markdown_phpextra\f[] (PHP Markdown
268+\f[C]markdown_phpextra\f[] (PHP Markdown Extra), \f[C]markdown_mmd\f[]
267−Extra), \f[C]markdown_mmd\f[] (MultiMarkdown), \f[C]gfm\f[]
269+(MultiMarkdown), \f[C]gfm\f[] (GitHub\-Flavored Markdown),
268−(GitHub\-Flavored Markdown), \f[C]commonmark\f[] (CommonMark Markdown),
270+\f[C]commonmark\f[] (CommonMark Markdown), \f[C]rst\f[]
269−\f[C]rst\f[] (reStructuredText), \f[C]html4\f[] (XHTML 1.0
271+(reStructuredText), \f[C]html4\f[] (XHTML 1.0 Transitional),
270−Transitional), \f[C]html\f[] or \f[C]html5\f[] (HTML5/XHTML polyglot
272+\f[C]html\f[] or \f[C]html5\f[] (HTML5/XHTML polyglot markup),
271−markup), \f[C]latex\f[] (LaTeX), \f[C]beamer\f[] (LaTeX beamer slide
273+\f[C]latex\f[] (LaTeX), \f[C]beamer\f[] (LaTeX beamer slide show),
272−show), \f[C]context\f[] (ConTeXt), \f[C]man\f[] (groff man),
274+\f[C]context\f[] (ConTeXt), \f[C]man\f[] (groff man), \f[C]mediawiki\f[]
273−\f[C]mediawiki\f[] (MediaWiki markup), \f[C]dokuwiki\f[] (DokuWiki
275+(MediaWiki markup), \f[C]dokuwiki\f[] (DokuWiki markup),
274−markup), \f[C]zimwiki\f[] (ZimWiki markup), \f[C]textile\f[] (Textile),
276+\f[C]zimwiki\f[] (ZimWiki markup), \f[C]textile\f[] (Textile),
275\f[C]org\f[] (Emacs Org mode), \f[C]texinfo\f[] (GNU Texinfo),
277\f[C]org\f[] (Emacs Org mode), \f[C]texinfo\f[] (GNU Texinfo),
276\f[C]opml\f[] (OPML), \f[C]docbook\f[] or \f[C]docbook4\f[] (DocBook 4),
278\f[C]opml\f[] (OPML), \f[C]docbook\f[] or \f[C]docbook4\f[] (DocBook 4),
277\f[C]docbook5\f[] (DocBook 5), \f[C]jats\f[] (JATS XML),
279\f[C]docbook5\f[] (DocBook 5), \f[C]jats\f[] (JATS XML),
@@ -345,7 +347,7 @@ You can find the default user data directory on your system by looking
345at the output of \f[C]pandoc\ \-\-version\f[].
347at the output of \f[C]pandoc\ \-\-version\f[].
346A \f[C]reference.odt\f[], \f[C]reference.docx\f[], \f[C]epub.css\f[],
348A \f[C]reference.odt\f[], \f[C]reference.docx\f[], \f[C]epub.css\f[],
347\f[C]templates\f[], \f[C]slidy\f[], \f[C]slideous\f[], or \f[C]s5\f[]
349\f[C]templates\f[], \f[C]slidy\f[], \f[C]slideous\f[], or \f[C]s5\f[]
348−directory placed in this directory will override pandoc's normal
350+directory placed in this directory will override pandoc\[aq]s normal
@@ -398,7 +400,7 @@ List supported output formats, one per line.
398.B \f[C]\-\-list\-extensions\f[]
400.B \f[C]\-\-list\-extensions\f[]
399List supported Markdown extensions, one per line, followed by a
401List supported Markdown extensions, one per line, followed by a
400\f[C]+\f[] or \f[C]\-\f[] indicating whether it is enabled by default in
402\f[C]+\f[] or \f[C]\-\f[] indicating whether it is enabled by default in
401−pandoc's Markdown.
403+pandoc\[aq]s Markdown.
@@ -430,7 +432,7 @@ Specify the base level for headers (defaults to 1).
432.B \f[C]\-\-indented\-code\-classes=\f[]\f[I]CLASSES\f[]
434.B \f[C]\-\-indented\-code\-classes=\f[]\f[I]CLASSES\f[]
433−Specify classes to use for indented code blocks\[en]for example,
435+Specify classes to use for indented code blocks\-\-for example,
434\f[C]perl,numberLines\f[] or \f[C]haskell\f[].
436\f[C]perl,numberLines\f[] or \f[C]haskell\f[].
435Multiple classes may be separated by spaces or commas.
437Multiple classes may be separated by spaces or commas.
@@ -458,7 +460,7 @@ Reading binary files (docx, odt, epub) implies \f[C]\-\-file\-scope\f[].
458Specify an executable to be used as a filter transforming the pandoc AST
460Specify an executable to be used as a filter transforming the pandoc AST
459after the input is parsed and before the output is written.
461after the input is parsed and before the output is written.
460The executable should read JSON from stdin and write JSON to stdout.
462The executable should read JSON from stdin and write JSON to stdout.
461−The JSON must be formatted like pandoc's own JSON input and output.
463+The JSON must be formatted like pandoc\[aq]s own JSON input and output.
462The name of the output format will be passed to the filter as the first
464The name of the output format will be passed to the filter as the first
@@ -501,7 +503,8 @@ a specified full or relative path (executable or non\-executable)
502.B \f[C]\-\-lua\-filter=\f[]\f[I]SCRIPT\f[]
504.B \f[C]\-\-lua\-filter=\f[]\f[I]SCRIPT\f[]
503Transform the document in a similar fashion as JSON filters (see
505Transform the document in a similar fashion as JSON filters (see
504−\f[C]\-\-filter\f[]), but use pandoc's build\-in lua filtering system.
506+\f[C]\-\-filter\f[]), but use pandoc\[aq]s build\-in lua filtering
505The given lua script is expected to return a list of lua filters which
508The given lua script is expected to return a list of lua filters which
506will be applied in order.
509will be applied in order.
507Each lua filter must contain element\-transforming functions indexed by
510Each lua filter must contain element\-transforming functions indexed by
@@ -511,7 +514,7 @@ applied.
512The \f[C]pandoc\f[] lua module provides helper functions for element
515The \f[C]pandoc\f[] lua module provides helper functions for element
514−It is always loaded into the script's lua environment.
517+It is always loaded into the script\[aq]s lua environment.
516The following is an example lua script for macro\-expansion:
519The following is an example lua script for macro\-expansion:
@@ -558,7 +561,7 @@ Specify the number of spaces per tab (default is 4).
559.B \f[C]\-\-track\-changes=accept\f[]|\f[C]reject\f[]|\f[C]all\f[]
562.B \f[C]\-\-track\-changes=accept\f[]|\f[C]reject\f[]|\f[C]all\f[]
560Specifies what to do with insertions, deletions, and comments produced
563Specifies what to do with insertions, deletions, and comments produced
561−by the MS Word \[lq]Track Changes\[rq] feature.
564+by the MS Word "Track Changes" feature.
562\f[C]accept\f[] (the default), inserts all insertions, and ignores all
565\f[C]accept\f[] (the default), inserts all insertions, and ignores all
563deletions.
566deletions.
564\f[C]reject\f[] inserts all deletions and ignores insertions.
567\f[C]reject\f[] inserts all deletions and ignores insertions.
@@ -603,8 +606,8 @@ sentence\-ending space in formats like LaTeX.
603.SS General writer options
606.SS General writer options
605.B \f[C]\-s\f[], \f[C]\-\-standalone\f[]
608.B \f[C]\-s\f[], \f[C]\-\-standalone\f[]
606−Produce output with an appropriate header and footer (e.g.\ a standalone
609+Produce output with an appropriate header and footer (e.g.
607−HTML, LaTeX, TEI, or RTF file, not a fragment).
610+a standalone HTML, LaTeX, TEI, or RTF file, not a fragment).
608This option is set automatically for \f[C]pdf\f[], \f[C]epub\f[],
611This option is set automatically for \f[C]pdf\f[], \f[C]epub\f[],
609\f[C]epub3\f[], \f[C]fb2\f[], \f[C]docx\f[], and \f[C]odt\f[] output.
612\f[C]epub3\f[], \f[C]fb2\f[], \f[C]docx\f[], and \f[C]odt\f[] output.
@@ -760,8 +763,9 @@ Implies \f[C]\-\-standalone\f[].
761.B \f[C]\-B\f[] \f[I]FILE\f[], \f[C]\-\-include\-before\-body=\f[]\f[I]FILE\f[]
764.B \f[C]\-B\f[] \f[I]FILE\f[], \f[C]\-\-include\-before\-body=\f[]\f[I]FILE\f[]
762Include contents of \f[I]FILE\f[], verbatim, at the beginning of the
765Include contents of \f[I]FILE\f[], verbatim, at the beginning of the
763−document body (e.g.\ after the \f[C]<body>\f[] tag in HTML, or the
767+after the \f[C]<body>\f[] tag in HTML, or the \f[C]\\begin{document}\f[]
764−\f[C]\\begin{document}\f[] command in LaTeX).
768+command in LaTeX).
765This can be used to include navigation bars or banners in HTML
769This can be used to include navigation bars or banners in HTML
766documents.
770documents.
767This option can be used repeatedly to include multiple files.
771This option can be used repeatedly to include multiple files.
@@ -805,9 +809,9 @@ line, or when resources used in a document must be downloaded).
805Produce a standalone HTML file with no external dependencies, using
809Produce a standalone HTML file with no external dependencies, using
806\f[C]data:\f[] URIs to incorporate the contents of linked scripts,
810\f[C]data:\f[] URIs to incorporate the contents of linked scripts,
807stylesheets, images, and videos.
811stylesheets, images, and videos.
808−The resulting file should be \[lq]self\-contained,\[rq] in the sense
812+The resulting file should be "self\-contained," in the sense that it
809−that it needs no external files and no net access to be displayed
813+needs no external files and no net access to be displayed properly by a
810−properly by a browser.
814+browser.
811This option works only with HTML output formats, including
815This option works only with HTML output formats, including
812\f[C]html4\f[], \f[C]html5\f[], \f[C]html+lhs\f[], \f[C]html5+lhs\f[],
816\f[C]html4\f[], \f[C]html5\f[], \f[C]html+lhs\f[], \f[C]html5+lhs\f[],
813\f[C]s5\f[], \f[C]slidy\f[], \f[C]slideous\f[], \f[C]dzslides\f[], and
817\f[C]s5\f[], \f[C]slidy\f[], \f[C]slideous\f[], \f[C]dzslides\f[], and
@@ -821,9 +825,9 @@ alone; the documents they link to will not be incorporated in the
822Limitation: resources that are loaded dynamically through JavaScript
826Limitation: resources that are loaded dynamically through JavaScript
823cannot be incorporated; as a result, \f[C]\-\-self\-contained\f[] does
827cannot be incorporated; as a result, \f[C]\-\-self\-contained\f[] does
824−not work with \f[C]\-\-mathjax\f[], and some advanced features
828+not work with \f[C]\-\-mathjax\f[], and some advanced features (e.g.
825−(e.g.\ zoom or speaker notes) may not work in an offline
829+zoom or speaker notes) may not work in an offline "self\-contained"
826−\[lq]self\-contained\[rq] \f[C]reveal.js\f[] slide show.
830+\f[C]reveal.js\f[] slide show.
@@ -890,16 +894,15 @@ Sections with class \f[C]unnumbered\f[] will never be numbered, even if
893−.B \f[C]\-\-number\-offset=\f[]\f[I]NUMBER\f[][\f[C],\f[]\f[I]NUMBER\f[]\f[C],\f[]\f[I]\&...\f[]]
897+.B \f[C]\-\-number\-offset=\f[]\f[I]NUMBER\f[][\f[C],\f[]\f[I]NUMBER\f[]\f[C],\f[]\f[I]...\f[]]
894Offset for section headings in HTML output (ignored in other output
898Offset for section headings in HTML output (ignored in other output
896The first number is added to the section number for top\-level headers,
900The first number is added to the section number for top\-level headers,
897the second for second\-level headers, and so on.
901the second for second\-level headers, and so on.
898So, for example, if you want the first top\-level header in your
902So, for example, if you want the first top\-level header in your
899−document to be numbered \[lq]6\[rq], specify
903+document to be numbered "6", specify \f[C]\-\-number\-offset=5\f[].
900−\f[C]\-\-number\-offset=5\f[].
901If your document starts with a level\-2 header which you want to be
904If your document starts with a level\-2 header which you want to be
902−numbered \[lq]1.5\[rq], specify \f[C]\-\-number\-offset=1,4\f[].
905+numbered "1.5", specify \f[C]\-\-number\-offset=1,4\f[].
903Offsets are 0 by default.
906Offsets are 0 by default.
904Implies \f[C]\-\-number\-sections\f[].
907Implies \f[C]\-\-number\-sections\f[].
@@ -1111,7 +1114,7 @@ body\ {\ font\-family:\ "DejaVuSans";\ }
1112.B \f[C]\-\-epub\-chapter\-level=\f[]\f[I]NUMBER\f[]
1115.B \f[C]\-\-epub\-chapter\-level=\f[]\f[I]NUMBER\f[]
1113Specify the header level at which to split the EPUB into separate
1116Specify the header level at which to split the EPUB into separate
1114−\[lq]chapter\[rq] files.
1117+"chapter" files.
1115The default is to split into chapters at level 1 headers.
1118The default is to split into chapters at level 1 headers.
1116This option only affects the internal composition of the EPUB, not the
1119This option only affects the internal composition of the EPUB, not the
1117way chapters and sections are displayed to users.
1120way chapters and sections are displayed to users.
@@ -1148,7 +1151,7 @@ Note that no check for duplicate options is done.
1148.SS Citation rendering
1151.SS Citation rendering
1150.B \f[C]\-\-bibliography=\f[]\f[I]FILE\f[]
1153.B \f[C]\-\-bibliography=\f[]\f[I]FILE\f[]
1151−Set the \f[C]bibliography\f[] field in the document's metadata to
1154+Set the \f[C]bibliography\f[] field in the document\[aq]s metadata to
1152\f[I]FILE\f[], overriding any value set in the metadata, and process
1155\f[I]FILE\f[], overriding any value set in the metadata, and process
1153citations using \f[C]pandoc\-citeproc\f[].
1156citations using \f[C]pandoc\-citeproc\f[].
1154(This is equivalent to
1157(This is equivalent to
@@ -1162,15 +1165,15 @@ added to bibliography.
1164.B \f[C]\-\-csl=\f[]\f[I]FILE\f[]
1167.B \f[C]\-\-csl=\f[]\f[I]FILE\f[]
1165−Set the \f[C]csl\f[] field in the document's metadata to \f[I]FILE\f[],
1168+Set the \f[C]csl\f[] field in the document\[aq]s metadata to
1166−overriding any value set in the metadata.
1169+\f[I]FILE\f[], overriding any value set in the metadata.
1167(This is equivalent to \f[C]\-\-metadata\ csl=FILE\f[].) This option is
1170(This is equivalent to \f[C]\-\-metadata\ csl=FILE\f[].) This option is
1168only relevant with \f[C]pandoc\-citeproc\f[].
1171only relevant with \f[C]pandoc\-citeproc\f[].
1172.B \f[C]\-\-citation\-abbreviations=\f[]\f[I]FILE\f[]
1175.B \f[C]\-\-citation\-abbreviations=\f[]\f[I]FILE\f[]
1173−Set the \f[C]citation\-abbreviations\f[] field in the document's
1176+Set the \f[C]citation\-abbreviations\f[] field in the document\[aq]s
1174metadata to \f[I]FILE\f[], overriding any value set in the metadata.
1177metadata to \f[I]FILE\f[], overriding any value set in the metadata.
1175(This is equivalent to
1178(This is equivalent to
1176\f[C]\-\-metadata\ citation\-abbreviations=FILE\f[].) This option is
1179\f[C]\-\-metadata\ citation\-abbreviations=FILE\f[].) This option is
@@ -1196,66 +1199,46 @@ with \f[C]bibtex\f[] or \f[C]biber\f[].
1198.SS Math rendering in HTML
1201.SS Math rendering in HTML
1200−.B \f[C]\-m\f[] [\f[I]URL\f[]], \f[C]\-\-latexmathml\f[][\f[C]=\f[]\f[I]URL\f[]]
1203+The default is to render TeX math as far as possible using Unicode
1201−Use the LaTeXMathML script to display embedded TeX math in HTML output.
1204+characters.
1202−To insert a link to a local copy of the \f[C]LaTeXMathML.js\f[] script,
1205+Formulas are put inside a \f[C]span\f[] with \f[C]class="math"\f[], so
1203−provide a \f[I]URL\f[].
1206+that they may be styled differently from the surrounding text if needed.
1204−If no \f[I]URL\f[] is provided, the contents of the script will be
1207+However, this gives acceptable results only for basic math, usually you
1205−inserted directly into the HTML header, preserving portability at the
1208+will want to use \f[C]\-\-mathjax\f[] or another of the following
1206−price of efficiency.
1209+options.
1207−If you plan to use math on several pages, it is much better to link to a
1208−copy of the script, so it can be cached.
1212−.B \f[C]\-\-mathml\f[]
1213−Convert TeX math to MathML (in \f[C]docbook4\f[], \f[C]docbook5\f[],
1214−\f[C]jats\f[], \f[C]html4\f[] and \f[C]html5\f[]).
1215−This is the default in \f[C]odt\f[] output.
1219−.B \f[C]\-\-jsmath\f[][\f[C]=\f[]\f[I]URL\f[]]
1220−Use jsMath to display embedded TeX math in HTML output.
1221−The \f[I]URL\f[] should point to the jsMath load script (e.g.
1222−\f[C]jsMath/easy/load.js\f[]); if provided, it will be linked to in the
1223−header of standalone HTML documents.
1224−If a \f[I]URL\f[] is not provided, no link to the jsMath load script
1225−will be inserted; it is then up to the author to provide such a link in
1230.B \f[C]\-\-mathjax\f[][\f[C]=\f[]\f[I]URL\f[]]
1211.B \f[C]\-\-mathjax\f[][\f[C]=\f[]\f[I]URL\f[]]
1231Use MathJax to display embedded TeX math in HTML output.
1212Use MathJax to display embedded TeX math in HTML output.
1213+TeX math will be put between \f[C]\\(...\\)\f[] (for inline math) or
1214+\f[C]\\[...\\]\f[] (for display math) and wrapped in \f[C]<span>\f[]
1215+tags with class \f[C]math\f[].
1216+Then the MathJax JavaScript will render it.
1232The \f[I]URL\f[] should point to the \f[C]MathJax.js\f[] load script.
1217The \f[I]URL\f[] should point to the \f[C]MathJax.js\f[] load script.
1233−If a \f[I]URL\f[] is not provided, a link to the MathJax CDN will be
1218+If a \f[I]URL\f[] is not provided, a link to the Cloudflare CDN will be
1234inserted.
1219inserted.
1238−.B \f[C]\-\-gladtex\f[]
1223+.B \f[C]\-\-mathml\f[]
1239−Enclose TeX math in \f[C]<eq>\f[] tags in HTML output.
1224+Convert TeX math to MathML (in \f[C]epub3\f[], \f[C]docbook4\f[],
1240−These can then be processed by gladTeX to produce links to images of the
1225+\f[C]docbook5\f[], \f[C]jats\f[], \f[C]html4\f[] and \f[C]html5\f[]).
1241−typeset formulas.
1226+This is the default in \f[C]odt\f[] output.
1242−.RS
1227+Note that currently only Firefox and Safari (and select e\-book readers)
1243−.RE
1228+natively support MathML.
1245−.B \f[C]\-\-mimetex\f[][\f[C]=\f[]\f[I]URL\f[]]
1246−Render TeX math using the mimeTeX CGI script.
1247−If \f[I]URL\f[] is not specified, it is assumed that the script is at
1248−\f[C]/cgi\-bin/mimetex.cgi\f[].
1252.B \f[C]\-\-webtex\f[][\f[C]=\f[]\f[I]URL\f[]]
1232.B \f[C]\-\-webtex\f[][\f[C]=\f[]\f[I]URL\f[]]
1253−Render TeX formulas using an external script that converts TeX formulas
1233+Convert TeX formulas to \f[C]<img>\f[] tags that link to an external
1254−to images.
1234+script that converts formulas to images.
1255−The formula will be concatenated with the URL provided.
1235+The formula will be URL\-encoded and concatenated with the URL provided.
1236+For SVG images you can for example use
1237+\f[C]\-\-webtex\ https://latex.codecogs.com/svg.latex?\f[].
1256−If \f[I]URL\f[] is not specified, the CodeCogs will be used.
1238+If no URL is specified, the CodeCogs URL generating PNGs will be used
1239+(\f[C]https://latex.codecogs.com/png.latex?\f[]).
1257Note: the \f[C]\-\-webtex\f[] option will affect Markdown output as well
1240Note: the \f[C]\-\-webtex\f[] option will affect Markdown output as well
1258−as HTML, which is useful if you're targeting a version of Markdown
1241+as HTML, which is useful if you\[aq]re targeting a version of Markdown
1259without native math support.
1242without native math support.
@@ -1265,7 +1248,6 @@ Use KaTeX to display embedded TeX math in HTML output.
1265The \f[I]URL\f[] is the base URL for the KaTeX library.
1248The \f[I]URL\f[] is the base URL for the KaTeX library.
1266If a \f[I]URL\f[] is not provided, a link to the KaTeX CDN will be
1249If a \f[I]URL\f[] is not provided, a link to the KaTeX CDN will be
1267inserted.
1250inserted.
1268−Note: KaTeX seems to work best with \f[C]html5\f[] output.
@@ -1276,6 +1258,60 @@ inserted.
1276Note that this option does not imply \f[C]\-\-katex\f[].
1258Note that this option does not imply \f[C]\-\-katex\f[].
1262+.B \f[C]\-m\f[] [\f[I]URL\f[]], \f[C]\-\-latexmathml\f[][\f[C]=\f[]\f[I]URL\f[]]
1263+\f[I]Deprecated.\f[] Use the LaTeXMathML script to display embedded TeX
1264+math in HTML output.
1265+TeX math will be displayed between \f[C]$\f[] or \f[C]$$\f[] characters
1266+and put in \f[C]<span>\f[] tags with class \f[C]LaTeX\f[].
1267+The LaTeXMathML JavaScript will then change it to MathML.
1268+Note that currently only Firefox and Safari (and select e\-book readers)
1269+natively support MathML.
1270+To insert a link the \f[C]LaTeXMathML.js\f[] script, provide a
1275+.B \f[C]\-\-jsmath\f[][\f[C]=\f[]\f[I]URL\f[]]
1276+\f[I]Deprecated.\f[] Use jsMath (the predecessor of MathJax) to display
1277+embedded TeX math in HTML output.
1278+TeX math will be put inside \f[C]<span>\f[] tags (for inline math) or
1279+\f[C]<div>\f[] tags (for display math) with class \f[C]math\f[] and
1280+rendered by the jsMath script.
1281+The \f[I]URL\f[] should point to the script (e.g.
1282+\f[C]jsMath/easy/load.js\f[]); if provided, it will be linked to in the
1283+header of standalone HTML documents.
1284+If a \f[I]URL\f[] is not provided, no link to the jsMath load script
1285+will be inserted; it is then up to the author to provide such a link in
1290+.B \f[C]\-\-gladtex\f[]
1291+\f[I]Deprecated.\f[] Enclose TeX math in \f[C]<eq>\f[] tags in HTML
1293+The resulting HTML can then be processed by gladTeX to produce images of
1294+the typeset formulas and an HTML file with links to these images.
1295+So, the procedure is:
1300+pandoc\ \-s\ \-\-gladtex\ input.md\ \-o\ myfile.htex
1301+gladtex\ \-d\ myfile\-images\ myfile.htex
1302+#\ produces\ myfile.html\ and\ images\ in\ myfile\-images
1307+.B \f[C]\-\-mimetex\f[][\f[C]=\f[]\f[I]URL\f[]]
1308+\f[I]Deprecated.\f[] Render TeX math using the mimeTeX CGI script, which
1309+generates an image for each TeX formula.
1310+This should work in all browsers.
1311+If \f[I]URL\f[] is not specified, it is assumed that the script is at
1312+\f[C]/cgi\-bin/mimetex.cgi\f[].
1279.SS Options for wrapper scripts
1315.SS Options for wrapper scripts
1281.B \f[C]\-\-dump\-args\f[]
1317.B \f[C]\-\-dump\-args\f[]
@@ -1461,7 +1497,7 @@ body of document
1463.B \f[C]meta\-json\f[]
1499.B \f[C]meta\-json\f[]
1464−JSON representation of all of the document's metadata.
1500+JSON representation of all of the document\[aq]s metadata.
1465Field values are transformed to the selected output format.
1501Field values are transformed to the selected output format.
@@ -1504,8 +1540,8 @@ For bidirectional documents, native pandoc \f[C]span\f[]s and
1504\f[C]div\f[]s with the \f[C]dir\f[] attribute (value \f[C]rtl\f[] or
1540\f[C]div\f[]s with the \f[C]dir\f[] attribute (value \f[C]rtl\f[] or
1505\f[C]ltr\f[]) can be used to override the base direction in some output
1541\f[C]ltr\f[]) can be used to override the base direction in some output
1507−This may not always be necessary if the final renderer (e.g.\ the
1543+This may not always be necessary if the final renderer (e.g.
1508−browser, when generating HTML) supports the Unicode Bidirectional
1544+the browser, when generating HTML) supports the Unicode Bidirectional
1509Algorithm.
1545Algorithm.
1511When using LaTeX for bidirectional documents, only the \f[C]xelatex\f[]
1547When using LaTeX for bidirectional documents, only the \f[C]xelatex\f[]
@@ -1565,8 +1601,8 @@ controls navigation symbols in \f[C]beamer\f[] documents (default is
1567.B \f[C]section\-titles\f[]
1603.B \f[C]section\-titles\f[]
1568−enables on \[lq]title pages\[rq] for new sections in \f[C]beamer\f[]
1604+enables on "title pages" for new sections in \f[C]beamer\f[] documents
1569−documents (default = true).
1605+(default = true).
@@ -1974,10 +2010,10 @@ merge in changes after each pandoc release.
1975Templates may contain comments: anything on a line after \f[C]$\-\-\f[]
2011Templates may contain comments: anything on a line after \f[C]$\-\-\f[]
1976will be treated as a comment and ignored.
2012will be treated as a comment and ignored.
1977−.SH PANDOC'S MARKDOWN
2013+.SH PANDOC\[aq]S MARKDOWN
1979Pandoc understands an extended and slightly revised version of John
2015Pandoc understands an extended and slightly revised version of John
1980−Gruber's Markdown syntax.
2016+Gruber\[aq]s Markdown syntax.
1981This document explains the syntax, noting differences from standard
2017This document explains the syntax, noting differences from standard
1982Markdown.
2018Markdown.
1983Except where noted, these differences can be suppressed by using the
2019Except where noted, these differences can be suppressed by using the
@@ -1986,7 +2022,7 @@ An extensions can be enabled by adding \f[C]+EXTENSION\f[] to the format
1986name and disabled by adding \f[C]\-EXTENSION\f[].
2022name and disabled by adding \f[C]\-EXTENSION\f[].
1987For example, \f[C]markdown_strict+footnotes\f[] is strict Markdown with
2023For example, \f[C]markdown_strict+footnotes\f[] is strict Markdown with
1988footnotes enabled, while \f[C]markdown\-footnotes\-pipe_tables\f[] is
2024footnotes enabled, while \f[C]markdown\-footnotes\-pipe_tables\f[] is
1989−pandoc's Markdown without footnotes or pipe tables.
2025+pandoc\[aq]s Markdown without footnotes or pipe tables.
1990.SS Philosophy
2026.SS Philosophy
1992Markdown is designed to be easy to write, and, even more importantly,
2028Markdown is designed to be easy to write, and, even more importantly,
@@ -1994,16 +2030,16 @@ easy to read:
1996A Markdown\-formatted document should be publishable as\-is, as plain
2032A Markdown\-formatted document should be publishable as\-is, as plain
1997−text, without looking like it's been marked up with tags or formatting
2033+text, without looking like it\[aq]s been marked up with tags or
1998−instructions.
2034+formatting instructions.
1999−\[en] John Gruber
2035+\-\- John Gruber
2002−This principle has guided pandoc's decisions in finding syntax for
2038+This principle has guided pandoc\[aq]s decisions in finding syntax for
2003tables, footnotes, and other extensions.
2039tables, footnotes, and other extensions.
2005−There is, however, one respect in which pandoc's aims are different from
2041+There is, however, one respect in which pandoc\[aq]s aims are different
2006−the original aims of Markdown.
2042+from the original aims of Markdown.
2007Whereas Markdown was originally designed with HTML generation in mind,
2043Whereas Markdown was originally designed with HTML generation in mind,
2008pandoc is designed for multiple output formats.
2044pandoc is designed for multiple output formats.
2009Thus, while pandoc allows the embedding of raw HTML, it discourages it,
2045Thus, while pandoc allows the embedding of raw HTML, it discourages it,
@@ -2027,8 +2063,8 @@ a hard line break, since trailing spaces in the cells are ignored.
2027There are two kinds of headers: Setext and ATX.
2063There are two kinds of headers: Setext and ATX.
2028.SS Setext\-style headers
2064.SS Setext\-style headers
2030−A setext\-style header is a line of text \[lq]underlined\[rq] with a row
2066+A setext\-style header is a line of text "underlined" with a row of
2031−of \f[C]=\f[] signs (for a level one header) or \f[C]\-\f[] signs (for a
2067+\f[C]=\f[] signs (for a level one header) or \f[C]\-\f[] signs (for a
2032level two header):
2068level two header):
@@ -2116,7 +2152,7 @@ My\ other\ header\ \ \ {#foo}
2116(This syntax is compatible with PHP Markdown Extra.)
2152(This syntax is compatible with PHP Markdown Extra.)
2118Note that although this syntax allows assignment of classes and
2154Note that although this syntax allows assignment of classes and
2119−key/value attributes, writers generally don't use all of this
2155+key/value attributes, writers generally don\[aq]t use all of this
2120information.
2156information.
2121Identifiers, classes, and key/value attributes are used in HTML and
2157Identifiers, classes, and key/value attributes are used in HTML and
2122HTML\-based formats such as EPUB and slidy.
2158HTML\-based formats such as EPUB and slidy.
@@ -2315,8 +2351,8 @@ indented more than three spaces.)
2318−A \[lq]lazy\[rq] form, which requires the \f[C]>\f[] character only on
2354+A "lazy" form, which requires the \f[C]>\f[] character only on the first
2319−the first line of each block, is also allowed:
2355+line of each block, is also allowed:
@@ -2448,9 +2484,9 @@ Here \f[C]mycode\f[] is an identifier, \f[C]haskell\f[] and
2448with value \f[C]100\f[].
2484with value \f[C]100\f[].
2449Some output formats can use this information to do syntax highlighting.
2485Some output formats can use this information to do syntax highlighting.
2450Currently, the only output formats that uses this information are HTML,
2486Currently, the only output formats that uses this information are HTML,
2487+LaTeX, Docx, and Ms.
2451−LaTeX, Docx, and Ms.\ If highlighting is supported for your output
2488+If highlighting is supported for your output format and language, then
2452−format and language, then the code block above will appear highlighted,
2489+the code block above will appear highlighted, with numbered lines.
2453−with numbered lines.
2454(To see which languages are supported, type
2490(To see which languages are supported, type
2455\f[C]pandoc\ \-\-list\-highlight\-languages\f[].) Otherwise, the code
2491\f[C]pandoc\ \-\-list\-highlight\-languages\f[].) Otherwise, the code
2456block above will appear as follows:
2492block above will appear as follows:
@@ -2550,8 +2586,8 @@ Here is a simple example:
2553−This will produce a \[lq]compact\[rq] list.
2589+This will produce a "compact" list.
2554−If you want a \[lq]loose\[rq] list, in which each item is formatted as a
2590+If you want a "loose" list, in which each item is formatted as a
2555paragraph, put spaces between the items:
2591paragraph, put spaces between the items:
@@ -2579,7 +2615,7 @@ List items look best if subsequent lines are flush with the first line
2582−But Markdown also allows a \[lq]lazy\[rq] format:
2618+But Markdown also allows a "lazy" format:
@@ -2641,8 +2677,8 @@ character after the list marker of the containing list item.
2644−As noted above, Markdown allows you to write list items
2680+As noted above, Markdown allows you to write list items "lazily,"
2645−\[lq]lazily,\[rq] instead of indenting continuation lines.
2681+instead of indenting continuation lines.
2646However, if there are multiple paragraphs or other blocks in a list
2682However, if there are multiple paragraphs or other blocks in a list
2647item, the first line of each must be indented.
2683item, the first line of each must be indented.
@@ -2696,8 +2732,8 @@ They must be separated from the text that follows by at least one space,
2696and, if the list marker is a capital letter with a period, by at least
2732and, if the list marker is a capital letter with a period, by at least
2697two spaces.
2733two spaces.
2699−The \f[C]fancy_lists\f[] extension also allows `\f[C]#\f[]' to be used
2735+The \f[C]fancy_lists\f[] extension also allows \[aq]\f[C]#\f[]\[aq] to
2700−as an ordered list marker in place of a numeral:
2736+be used as an ordered list marker in place of a numeral:
@@ -2779,9 +2815,8 @@ one or more block elements (paragraph, code block, list, etc.), each
2779indented four spaces or one tab stop.
2815indented four spaces or one tab stop.
2780The body of the definition (including the first line, aside from the
2816The body of the definition (including the first line, aside from the
2781colon or tilde) should be indented four spaces.
2817colon or tilde) should be indented four spaces.
2782−However, as with other Markdown lists, you can \[lq]lazily\[rq] omit
2818+However, as with other Markdown lists, you can "lazily" omit indentation
2783−indentation except at the beginning of a paragraph or other block
2819+except at the beginning of a paragraph or other block element:
@@ -2813,16 +2848,16 @@ Term\ 2
2815Note that space between items in a definition list is required.
2850Note that space between items in a definition list is required.
2816−(A variant that loosens this requirement, but disallows \[lq]lazy\[rq]
2851+(A variant that loosens this requirement, but disallows "lazy" hard
2817−hard wrapping, can be activated with \f[C]compact_definition_lists\f[]:
2852+wrapping, can be activated with \f[C]compact_definition_lists\f[]: see
2818−see Non\-pandoc extensions, below.)
2853+Non\-pandoc extensions, below.)
2819.SS Numbered example lists
2854.SS Numbered example lists
2820.SS Extension: \f[C]example_lists\f[]
2855.SS Extension: \f[C]example_lists\f[]
2822The special list marker \f[C]\@\f[] can be used for sequentially
2857The special list marker \f[C]\@\f[] can be used for sequentially
2823numbered examples.
2858numbered examples.
2824−The first list item with a \f[C]\@\f[] marker will be numbered `1', the
2859+The first list item with a \f[C]\@\f[] marker will be numbered
2825−next `2', and so on, throughout the document.
2860+\[aq]1\[aq], the next \[aq]2\[aq], and so on, throughout the document.
2826The numbered examples need not occur in a single list; each new list
2861The numbered examples need not occur in a single list; each new list
2827using \f[C]\@\f[] will take up where the last stopped.
2862using \f[C]\@\f[] will take up where the last stopped.
2828So, for example:
2863So, for example:
@@ -2853,8 +2888,8 @@ The label can be any string of alphanumeric characters, underscores, or
2854.SS Compact and loose lists
2889.SS Compact and loose lists
2856−Pandoc behaves differently from \f[C]Markdown.pl\f[] on some \[lq]edge
2891+Pandoc behaves differently from \f[C]Markdown.pl\f[] on some "edge
2857−cases\[rq] involving lists.
2892+cases" involving lists.
2858Consider this source:
2893Consider this source:
@@ -2869,15 +2904,14 @@ Consider this source:
2872−Pandoc transforms this into a \[lq]compact list\[rq] (with no
2907+Pandoc transforms this into a "compact list" (with no \f[C]<p>\f[] tags
2873−\f[C]<p>\f[] tags around \[lq]First\[rq], \[lq]Second\[rq], or
2874−\[lq]Third\[rq]), while Markdown puts \f[C]<p>\f[] tags around
2908+around "First", "Second", or "Third"), while Markdown puts \f[C]<p>\f[]
2875−\[lq]Second\[rq] and \[lq]Third\[rq] (but not \[lq]First\[rq]), because
2909+tags around "Second" and "Third" (but not "First"), because of the blank
2876−of the blank space around \[lq]Third\[rq].
2910+space around "Third".
2877Pandoc follows a simple rule: if the text is followed by a blank line,
2911Pandoc follows a simple rule: if the text is followed by a blank line,
2878it is treated as a paragraph.
2912it is treated as a paragraph.
2879−Since \[lq]Second\[rq] is followed by a list, and not a blank line, it
2913+Since "Second" is followed by a list, and not a blank line, it isn\[aq]t
2880−isn't treated as a paragraph.
2914+treated as a paragraph.
2881The fact that the list is followed by a blank line is irrelevant.
2915The fact that the list is followed by a blank line is irrelevant.
2882(Note: Pandoc works this way even when the \f[C]markdown_strict\f[]
2916(Note: Pandoc works this way even when the \f[C]markdown_strict\f[]
2883format is specified.
2917format is specified.
@@ -2901,9 +2935,9 @@ Trouble! Here pandoc (like other Markdown implementations) will treat
2901\f[C]{\ my\ code\ block\ }\f[] as the second paragraph of item two, and
2935\f[C]{\ my\ code\ block\ }\f[] as the second paragraph of item two, and
2902not as a code block.
2936not as a code block.
2904−To \[lq]cut off\[rq] the list after item two, you can insert some
2938+To "cut off" the list after item two, you can insert some non\-indented
2905−non\-indented content, like an HTML comment, which won't produce visible
2939+content, like an HTML comment, which won\[aq]t produce visible output in
2906−output in any format:
2940+any format:
@@ -3176,7 +3210,7 @@ wrap, with the relative cell widths determined by the widths of the
3176separator lines.
3210separator lines.
3178Note: pandoc also recognizes pipe tables of the following form, as can
3212Note: pandoc also recognizes pipe tables of the following form, as can
3179−be produced by Emacs' orgtbl\-mode:
3213+be produced by Emacs\[aq] orgtbl\-mode:
@@ -3189,8 +3223,8 @@ be produced by Emacs' orgtbl\-mode:
3190The difference is that \f[C]+\f[] is used instead of \f[C]|\f[].
3224The difference is that \f[C]+\f[] is used instead of \f[C]|\f[].
3191Other orgtbl features are not supported.
3225Other orgtbl features are not supported.
3192−In particular, to get non\-default column alignment, you'll need to add
3226+In particular, to get non\-default column alignment, you\[aq]ll need to
3193−colons as above.
3227+add colons as above.
3194.SS Metadata blocks
3228.SS Metadata blocks
3195.SS Extension: \f[C]pandoc_title_block\f[]
3229.SS Extension: \f[C]pandoc_title_block\f[]
@@ -3255,13 +3289,13 @@ All three metadata fields may contain standard inline formatting
3256Title blocks will always be parsed, but they will affect the output only
3290Title blocks will always be parsed, but they will affect the output only
3257when the \f[C]\-\-standalone\f[] (\f[C]\-s\f[]) option is chosen.
3291when the \f[C]\-\-standalone\f[] (\f[C]\-s\f[]) option is chosen.
3258−In HTML output, titles will appear twice: once in the document head
3292+In HTML output, titles will appear twice: once in the document head \-\-
3259−\[en] this is the title that will appear at the top of the window in a
3293+this is the title that will appear at the top of the window in a browser
3260−browser \[en] and once at the beginning of the document body.
3294+\-\- and once at the beginning of the document body.
3261The title in the document head can have an optional prefix attached
3295The title in the document head can have an optional prefix attached
3262(\f[C]\-\-title\-prefix\f[] or \f[C]\-T\f[] option).
3296(\f[C]\-\-title\-prefix\f[] or \f[C]\-T\f[] option).
3263−The title in the body appears as an H1 element with class
3297+The title in the body appears as an H1 element with class "title", so it
3264−\[lq]title\[rq], so it can be suppressed or reformatted with CSS.
3298+can be suppressed or reformatted with CSS.
3265If a title prefix is specified with \f[C]\-T\f[] and no title block
3299If a title prefix is specified with \f[C]\-T\f[] and no title block
3266appears in the document, the title prefix will be used by itself as the
3300appears in the document, the title prefix will be used by itself as the
3267HTML title.
3301HTML title.
@@ -3290,7 +3324,7 @@ will yield a man page with the title \f[C]PANDOC\f[] and section 1.
3293−will also have \[lq]Pandoc User Manuals\[rq] in the footer.
3327+will also have "Pandoc User Manuals" in the footer.
@@ -3298,7 +3332,7 @@ will also have \[lq]Pandoc User Manuals\[rq] in the footer.
3301−will also have \[lq]Version 4.0\[rq] in the header.
3335+will also have "Version 4.0" in the header.
3302.SS Extension: \f[C]yaml_metadata_block\f[]
3336.SS Extension: \f[C]yaml_metadata_block\f[]
3304A YAML metadata block is a valid YAML object, delimited by a line of
3338A YAML metadata block is a valid YAML object, delimited by a line of
@@ -3438,7 +3472,7 @@ instead of
3441−This rule is easier to remember than standard Markdown's rule, which
3475+This rule is easier to remember than standard Markdown\[aq]s rule, which
3442allows only the following characters to be backslash\-escaped:
3476allows only the following characters to be backslash\-escaped:
@@ -3454,11 +3488,12 @@ A backslash\-escaped space is parsed as a nonbreaking space.
3454It will appear in TeX output as \f[C]~\f[] and in HTML and XML as
3488It will appear in TeX output as \f[C]~\f[] and in HTML and XML as
3455\f[C]\\ \f[] or \f[C]\\ \f[].
3489\f[C]\\ \f[] or \f[C]\\ \f[].
3457−A backslash\-escaped newline (i.e.\ a backslash occurring at the end of
3491+A backslash\-escaped newline (i.e.
3458−a line) is parsed as a hard line break.
3492+a backslash occurring at the end of a line) is parsed as a hard line
3459It will appear in TeX output as \f[C]\\\\\f[] and in HTML as
3494It will appear in TeX output as \f[C]\\\\\f[] and in HTML as
3460\f[C]<br\ />\f[].
3495\f[C]<br\ />\f[].
3461−This is a nice alternative to Markdown's \[lq]invisible\[rq] way of
3496+This is a nice alternative to Markdown\[aq]s "invisible" way of
3462indicating hard line breaks using two trailing spaces on a line.
3497indicating hard line breaks using two trailing spaces on a line.
3464Backslash escapes do not work in verbatim contexts.
3499Backslash escapes do not work in verbatim contexts.
@@ -3533,8 +3568,8 @@ If the superscripted or subscripted text contains spaces, these spaces
3533must be escaped with backslashes.
3568must be escaped with backslashes.
3534(This is to prevent accidental superscripting and subscripting through
3569(This is to prevent accidental superscripting and subscripting through
3535the ordinary use of \f[C]~\f[] and \f[C]^\f[].) Thus, if you want the
3570the ordinary use of \f[C]~\f[] and \f[C]^\f[].) Thus, if you want the
3536−letter P with `a cat' in subscripts, use \f[C]P~a\\\ cat~\f[], not
3571+letter P with \[aq]a cat\[aq] in subscripts, use \f[C]P~a\\\ cat~\f[],
3537−\f[C]P~a\ cat~\f[].
3572+not \f[C]P~a\ cat~\f[].
3538.SS Verbatim
3573.SS Verbatim
3540To make a short span of text verbatim, put it inside backticks:
3575To make a short span of text verbatim, put it inside backticks:
@@ -3613,9 +3648,9 @@ The opening \f[C]$\f[] must have a non\-space character immediately to
3613its right, while the closing \f[C]$\f[] must have a non\-space character
3648its right, while the closing \f[C]$\f[] must have a non\-space character
3614immediately to its left, and must not be followed immediately by a
3649immediately to its left, and must not be followed immediately by a
3616−Thus, \f[C]$20,000\ and\ $30,000\f[] won't parse as math.
3651+Thus, \f[C]$20,000\ and\ $30,000\f[] won\[aq]t parse as math.
3617If for some reason you need to enclose text in literal \f[C]$\f[]
3652If for some reason you need to enclose text in literal \f[C]$\f[]
3618−characters, backslash\-escape them and they won't be treated as math
3653+characters, backslash\-escape them and they won\[aq]t be treated as math
3619delimiters.
3654delimiters.
3621TeX math will be printed in all output formats.
3656TeX math will be printed in all output formats.
@@ -3642,7 +3677,7 @@ It will be rendered inside a \f[C]\@math\f[] command.
3644.B groff man
3679.B groff man
3645−It will be rendered verbatim without \f[C]$\f[]'s.
3680+It will be rendered verbatim without \f[C]$\f[]\[aq]s.
@@ -3689,64 +3724,9 @@ Otherwise, they will appear verbatim.
3690.B HTML, Slidy, DZSlides, S5, EPUB
3725.B HTML, Slidy, DZSlides, S5, EPUB
3691The way math is rendered in HTML will depend on the command\-line
3726The way math is rendered in HTML will depend on the command\-line
3692−options selected:
3727+options selected.
3728+Therefore see Math rendering in HTML above.
3695−The default is to render TeX math as far as possible using Unicode
3696−characters, as with RTF, DocBook, and OpenDocument output.
3697−Formulas are put inside a \f[C]span\f[] with \f[C]class="math"\f[], so
3698−that they may be styled differently from the surrounding text if needed.
3700−If the \f[C]\-\-latexmathml\f[] option is used, TeX math will be
3701−displayed between \f[C]$\f[] or \f[C]$$\f[] characters and put in
3702−\f[C]<span>\f[] tags with class \f[C]LaTeX\f[].
3703−The LaTeXMathML script will be used to render it as formulas.
3704−(This trick does not work in all browsers, but it works in Firefox.
3705−In browsers that do not support LaTeXMathML, TeX math will appear
3706−verbatim between \f[C]$\f[] characters.)
3708−If the \f[C]\-\-jsmath\f[] option is used, TeX math will be put inside
3709−\f[C]<span>\f[] tags (for inline math) or \f[C]<div>\f[] tags (for
3710−display math) with class \f[C]math\f[].
3711−The jsMath script will be used to render it.
3713−If the \f[C]\-\-mimetex\f[] option is used, the mimeTeX CGI script will
3714−be called to generate images for each TeX formula.
3715−This should work in all browsers.
3716−The \f[C]\-\-mimetex\f[] option takes an optional URL as argument.
3717−If no URL is specified, it will be assumed that the mimeTeX CGI script
3718−is at \f[C]/cgi\-bin/mimetex.cgi\f[].
3720−If the \f[C]\-\-gladtex\f[] option is used, TeX formulas will be
3721−enclosed in \f[C]<eq>\f[] tags in the HTML output.
3722−The resulting \f[C]htex\f[] file may then be processed by gladTeX, which
3723−will produce image files for each formula and an HTML file with links to
3725−So, the procedure is:
3730−pandoc\ \-s\ \-\-gladtex\ myfile.txt\ \-o\ myfile.htex
3731−gladtex\ \-d\ myfile\-images\ myfile.htex
3732−#\ produces\ myfile.html\ and\ images\ in\ myfile\-images
3737−If the \f[C]\-\-webtex\f[] option is used, TeX formulas will be
3738−converted to \f[C]<img>\f[] tags that link to an external script that
3739−converts formulas to images.
3740−The formula will be URL\-encoded and concatenated with the URL provided.
3741−For SVG images you can for example use
3742−\f[C]\-\-webtex\ https://latex.codecogs.com/svg.latex?\f[].
3743−If no URL is specified, the CodeCogs URL generating PNGs will be used
3744−(\f[C]https://latex.codecogs.com/png.latex?\f[]).
3746−If the \f[C]\-\-mathjax\f[] option is used, TeX math will be displayed
3747−between \f[C]\\(...\\)\f[] (for inline math) or \f[C]\\[...\\]\f[] (for
3748−display math) and put in \f[C]<span>\f[] tags with class \f[C]math\f[].
3749−The MathJax script will be used to render it as formulas.
3751.SS Raw HTML
3731.SS Raw HTML
3752.SS Extension: \f[C]raw_html\f[]
3732.SS Extension: \f[C]raw_html\f[]
@@ -3763,9 +3743,9 @@ DZSlides, EPUB, Markdown, Emacs Org mode, and Textile output, and
3763suppressed in other formats.
3743suppressed in other formats.
3764.SS Extension: \f[C]markdown_in_html_blocks\f[]
3744.SS Extension: \f[C]markdown_in_html_blocks\f[]
3766−Standard Markdown allows you to include HTML \[lq]blocks\[rq]: blocks of
3746+Standard Markdown allows you to include HTML "blocks": blocks of HTML
3767−HTML between balanced tags that are separated from the surrounding text
3747+between balanced tags that are separated from the surrounding text with
3768−with blank lines, and start and end at the left margin.
3748+blank lines, and start and end at the left margin.
3769Within these blocks, everything is interpreted as HTML, not Markdown; so
3749Within these blocks, everything is interpreted as HTML, not Markdown; so
3770(for example), \f[C]*\f[] does not signify emphasis.
3750(for example), \f[C]*\f[] does not signify emphasis.
@@ -4116,7 +4096,7 @@ slide shows and EPUB), LaTeX, and ConTeXt.
4116.SS Images
4096.SS Images
4118A link immediately preceded by a \f[C]!\f[] will be treated as an image.
4098A link immediately preceded by a \f[C]!\f[] will be treated as an image.
4119−The link text will be used as the image's alt text:
4099+The link text will be used as the image\[aq]s alt text:
@@ -4131,7 +4111,7 @@ The link text will be used as the image's alt text:
4132An image with nonempty alt text, occurring by itself in a paragraph,
4112An image with nonempty alt text, occurring by itself in a paragraph,
4133will be rendered as a figure with a caption.
4113will be rendered as a figure with a caption.
4134−The image's alt text will be used as the caption.
4114+The image\[aq]s alt text will be used as the caption.
@@ -4140,8 +4120,9 @@ The image's alt text will be used as the caption.
4142How this is rendered depends on the output format.
4122How this is rendered depends on the output format.
4123+Some output formats (e.g.
4143−Some output formats (e.g.\ RTF) do not yet support figures.
4124+RTF) do not yet support figures.
4144−In those formats, you'll just get an image in a paragraph by itself,
4125+In those formats, you\[aq]ll just get an image in a paragraph by itself,
4145with no caption.
4126with no caption.
4147If you just want a regular inline image, just make sure it is not the
4128If you just want a regular inline image, just make sure it is not the
@@ -4227,7 +4208,7 @@ attributes:
4227.SS Footnotes
4208.SS Footnotes
4228.SS Extension: \f[C]footnotes\f[]
4209.SS Extension: \f[C]footnotes\f[]
4230−Pandoc's Markdown allows footnotes, using the following syntax:
4211+Pandoc\[aq]s Markdown allows footnotes, using the following syntax:
@@ -4282,11 +4263,10 @@ Inline and regular footnotes may be mixed freely.
4282Interpret straight quotes as curly quotes, \f[C]\-\-\-\f[] as
4263Interpret straight quotes as curly quotes, \f[C]\-\-\-\f[] as
4283em\-dashes, \f[C]\-\-\f[] as en\-dashes, and \f[C]\&...\f[] as ellipses.
4264em\-dashes, \f[C]\-\-\f[] as en\-dashes, and \f[C]\&...\f[] as ellipses.
4284Nonbreaking spaces are inserted after certain abbreviations, such as
4265Nonbreaking spaces are inserted after certain abbreviations, such as
4285−\[lq]Mr.\[rq] This option currently affects the input formats
4266+"Mr." This option currently affects the input formats \f[C]markdown\f[],
4286−\f[C]markdown\f[], \f[C]commonmark\f[], \f[C]latex\f[],
4267+\f[C]commonmark\f[], \f[C]latex\f[], \f[C]mediawiki\f[], \f[C]org\f[],
4287−\f[C]mediawiki\f[], \f[C]org\f[], \f[C]rst\f[], and \f[C]twiki\f[], and
4268+\f[C]rst\f[], and \f[C]twiki\f[], and the output formats
4288−the output formats \f[C]markdown\f[], \f[C]latex\f[], and
4269+\f[C]markdown\f[], \f[C]latex\f[], and \f[C]context\f[].
4291Note: If you are \f[I]writing\f[] Markdown, then the \f[C]smart\f[]
4271Note: If you are \f[I]writing\f[] Markdown, then the \f[C]smart\f[]
4292extension has the reverse effect: what would have been curly quotes
4272extension has the reverse effect: what would have been curly quotes
@@ -4436,7 +4416,7 @@ JSON and CSL YAML formats as far as possible.
4436As an alternative to specifying a bibliography file using
4416As an alternative to specifying a bibliography file using
4437\f[C]\-\-bibliography\f[] or the YAML metadata field
4417\f[C]\-\-bibliography\f[] or the YAML metadata field
4438\f[C]bibliography\f[], you can include the citation data directly in the
4418\f[C]bibliography\f[], you can include the citation data directly in the
4439−\f[C]references\f[] field of the document's YAML metadata.
4419+\f[C]references\f[] field of the document\[aq]s YAML metadata.
4440The field should contain an array of YAML\-encoded references, for
4420The field should contain an array of YAML\-encoded references, for
@@ -4486,7 +4466,7 @@ To make your citations hyperlinks to the corresponding bibliography
4486entries, add \f[C]link\-citations:\ true\f[] to your YAML metadata.
4466entries, add \f[C]link\-citations:\ true\f[] to your YAML metadata.
4488Citations go inside square brackets and are separated by semicolons.
4468Citations go inside square brackets and are separated by semicolons.
4489−Each citation must have a key, composed of `\@' + the citation
4469+Each citation must have a key, composed of \[aq]\@\[aq] + the citation
4490identifier from the database, and may optionally have a prefix, a
4470identifier from the database, and may optionally have a prefix, a
4491locator, and a suffix.
4471locator, and a suffix.
4492The citation key must begin with a letter, digit, or \f[C]_\f[], and may
4472The citation key must begin with a letter, digit, or \f[C]_\f[], and may
@@ -4521,7 +4501,7 @@ singular or plural forms, as \f[C]book\f[], \f[C]bk.\f[]/\f[C]bks.\f[];
4521\f[C]s.v.\f[]/\f[C]s.vv.\f[]; \f[C]verse\f[], \f[C]v.\f[]/\f[C]vv.\f[];
4501\f[C]s.v.\f[]/\f[C]s.vv.\f[]; \f[C]verse\f[], \f[C]v.\f[]/\f[C]vv.\f[];
4522\f[C]volume\f[], \f[C]vol.\f[]/\f[C]vols.\f[]; \f[C]¶\f[]/\f[C]¶¶\f[];
4502\f[C]volume\f[], \f[C]vol.\f[]/\f[C]vols.\f[]; \f[C]¶\f[]/\f[C]¶¶\f[];
4523\f[C]§\f[]/\f[C]§§\f[].
4503\f[C]§\f[]/\f[C]§§\f[].
4524−If no locator term is used, \[lq]page\[rq] is assumed.
4504+If no locator term is used, "page" is assumed.
4526A minus sign (\f[C]\-\f[]) before the \f[C]\@\f[] will suppress mention
4506A minus sign (\f[C]\-\f[]) before the \f[C]\@\f[] will suppress mention
4527of the author in the citation.
4507of the author in the citation.
@@ -4617,7 +4597,7 @@ It is selected automatically for \f[C]textile\f[] input.
4618Allow \f[C]<\f[] and \f[C]>\f[] to be backslash\-escaped, as they can be
4598Allow \f[C]<\f[] and \f[C]>\f[] to be backslash\-escaped, as they can be
4619in GitHub flavored Markdown but not original Markdown.
4599in GitHub flavored Markdown but not original Markdown.
4620−This is implied by pandoc's default \f[C]all_symbols_escapable\f[].
4600+This is implied by pandoc\[aq]s default \f[C]all_symbols_escapable\f[].
4621.SS Extension: \f[C]lists_without_preceding_blankline\f[]
4601.SS Extension: \f[C]lists_without_preceding_blankline\f[]
4623Allow a list to occur right after a paragraph, with no intervening blank
4603Allow a list to occur right after a paragraph, with no intervening blank
@@ -4745,15 +4725,15 @@ in several respects:
4745No blank line is required between consecutive items of the definition
4725No blank line is required between consecutive items of the definition
4747.IP \[bu] 2
4727.IP \[bu] 2
4748−To get a \[lq]tight\[rq] or \[lq]compact\[rq] list, omit space between
4728+To get a "tight" or "compact" list, omit space between consecutive
4749−consecutive items; the space between a term and its definition does not
4729+items; the space between a term and its definition does not affect
4750−affect anything.
4730+anything.
4751.IP \[bu] 2
4731.IP \[bu] 2
4752Lazy wrapping of paragraphs is not allowed: the entire definition must
4732Lazy wrapping of paragraphs is not allowed: the entire definition must
4753be indented four spaces.
4733be indented four spaces.
4754.SS Markdown variants
4734.SS Markdown variants
4756−In addition to pandoc's extended Markdown, the following Markdown
4736+In addition to pandoc\[aq]s extended Markdown, the following Markdown
4757variants are supported:
4737variants are supported:
4759.B \f[C]markdown_phpextra\f[] (PHP Markdown Extra)
4739.B \f[C]markdown_phpextra\f[] (PHP Markdown Extra)
@@ -4834,7 +4814,8 @@ There are five ways to do this, using S5, DZSlides, Slidy, Slideous, or
4834reveal.js.
4814reveal.js.
4835You can also produce a PDF slide show using LaTeX \f[C]beamer\f[].
4815You can also produce a PDF slide show using LaTeX \f[C]beamer\f[].
4837−Here's the Markdown source for a simple slide show, \f[C]habits.txt\f[]:
4817+Here\[aq]s the Markdown source for a simple slide show,
4818+\f[C]habits.txt\f[]:
@@ -4929,20 +4910,20 @@ A header at the slide level always starts a new slide.
4929Headers \f[I]below\f[] the slide level in the hierarchy create headers
4910Headers \f[I]below\f[] the slide level in the hierarchy create headers
4930\f[I]within\f[] a slide.
4911\f[I]within\f[] a slide.
4931.IP \[bu] 2
4912.IP \[bu] 2
4932−Headers \f[I]above\f[] the slide level in the hierarchy create
4913+Headers \f[I]above\f[] the slide level in the hierarchy create "title
4933−\[lq]title slides,\[rq] which just contain the section title and help to
4914+slides," which just contain the section title and help to break the
4934−break the slide show into sections.
4915+slide show into sections.
4935.IP \[bu] 2
4916.IP \[bu] 2
4936Content \f[I]above\f[] the slide level will not appear in the slide
4917Content \f[I]above\f[] the slide level will not appear in the slide
4938.IP \[bu] 2
4919.IP \[bu] 2
4939−A title page is constructed automatically from the document's title
4920+A title page is constructed automatically from the document\[aq]s title
4940block, if present.
4921block, if present.
4941(In the case of beamer, this can be disabled by commenting out some
4922(In the case of beamer, this can be disabled by commenting out some
4942lines in the default template.)
4923lines in the default template.)
4944These rules are designed to support many different styles of slide show.
4925These rules are designed to support many different styles of slide show.
4945−If you don't care about structuring your slides into sections and
4926+If you don\[aq]t care about structuring your slides into sections and
4946subsections, you can just use level 1 headers for all each slide.
4927subsections, you can just use level 1 headers for all each slide.
4947(In that case, level 1 will be the slide level.) But you can also
4928(In that case, level 1 will be the slide level.) But you can also
4948structure the slide show into sections, as in the example above.
4929structure the slide show into sections, as in the example above.
@@ -4954,9 +4935,9 @@ It is not recommended that you use deeper nesting of section levels with
4954reveal.js.
4935reveal.js.
4955.SS Incremental lists
4936.SS Incremental lists
4957−By default, these writers produce lists that display \[lq]all at
4938+By default, these writers produce lists that display "all at once." If
4958−once.\[rq] If you want your lists to display incrementally (one item at
4939+you want your lists to display incrementally (one item at a time), use
4959−a time), use the \f[C]\-i\f[] option.
4940+the \f[C]\-i\f[] option.
4960If you want a particular list to depart from the default (that is, to
4941If you want a particular list to depart from the default (that is, to
4961display incrementally without the \f[C]\-i\f[] option and all at once
4942display incrementally without the \f[C]\-i\f[] option and all at once
4962with the \f[C]\-i\f[] option), put it in a block quote:
4943with the \f[C]\-i\f[] option), put it in a block quote:
@@ -4972,8 +4953,8 @@ In this way incremental and nonincremental lists can be mixed in a
4972single document.
4953single document.
4973.SS Inserting pauses
4954.SS Inserting pauses
4975−You can add \[lq]pauses\[rq] within a slide by including a paragraph
4956+You can add "pauses" within a slide by including a paragraph containing
4976−containing three dots, separated by spaces:
4957+three dots, separated by spaces:
@@ -4993,8 +4974,8 @@ in \f[C]$DATADIR/s5/default\f[] (for S5), \f[C]$DATADIR/slidy\f[] (for
4993Slidy), or \f[C]$DATADIR/slideous\f[] (for Slideous), where
4974Slidy), or \f[C]$DATADIR/slideous\f[] (for Slideous), where
4994\f[C]$DATADIR\f[] is the user data directory (see
4975\f[C]$DATADIR\f[] is the user data directory (see
4995\f[C]\-\-data\-dir\f[], above).
4976\f[C]\-\-data\-dir\f[], above).
4996−The originals may be found in pandoc's system data directory (generally
4977+The originals may be found in pandoc\[aq]s system data directory
4997−\f[C]$CABALDIR/pandoc\-VERSION/s5/default\f[]).
4978+(generally \f[C]$CABALDIR/pandoc\-VERSION/s5/default\f[]).
4998Pandoc will look there for any files it does not find in the user data
4979Pandoc will look there for any files it does not find in the user data
4999directory.
4980directory.
@@ -5092,7 +5073,7 @@ introducing the slide:
5094All of the other frame attributes described in Section 8.1 of the Beamer
5075All of the other frame attributes described in Section 8.1 of the Beamer
5095−User's Guide may also be used: \f[C]allowdisplaybreaks\f[],
5076+User\[aq]s Guide may also be used: \f[C]allowdisplaybreaks\f[],
5096\f[C]allowframebreaks\f[], \f[C]b\f[], \f[C]c\f[], \f[C]t\f[],
5077\f[C]allowframebreaks\f[], \f[C]b\f[], \f[C]c\f[], \f[C]t\f[],
5097\f[C]environment\f[], \f[C]label\f[], \f[C]plain\f[], \f[C]shrink\f[].
5078\f[C]environment\f[], \f[C]label\f[], \f[C]plain\f[], \f[C]shrink\f[].
5098.SH CREATING EPUBS WITH PANDOC
5079.SH CREATING EPUBS WITH PANDOC
@@ -5153,8 +5134,8 @@ Valid values for \f[C]type\f[] are \f[C]main\f[], \f[C]subtitle\f[],
5153Either a string value, or an object with fields \f[C]role\f[],
5134Either a string value, or an object with fields \f[C]role\f[],
5154\f[C]file\-as\f[], and \f[C]text\f[], or a list of such objects.
5135\f[C]file\-as\f[], and \f[C]text\f[], or a list of such objects.
5155Valid values for \f[C]role\f[] are MARC relators, but pandoc will
5136Valid values for \f[C]role\f[] are MARC relators, but pandoc will
5156−attempt to translate the human\-readable versions (like \[lq]author\[rq]
5137+attempt to translate the human\-readable versions (like "author" and
5157−and \[lq]editor\[rq]) to the appropriate marc relators.
5138+"editor") to the appropriate marc relators.
@@ -5276,23 +5257,24 @@ output; \f[C]beamer\f[], \f[C]html4\f[] or \f[C]html5\f[] for output
5276only), pandoc will treat the document as literate Haskell source.
5257only), pandoc will treat the document as literate Haskell source.
5277This means that
5258This means that
5278.IP \[bu] 2
5259.IP \[bu] 2
5279−In Markdown input, \[lq]bird track\[rq] sections will be parsed as
5260+In Markdown input, "bird track" sections will be parsed as Haskell code
5280−Haskell code rather than block quotations.
5261+rather than block quotations.
5281Text between \f[C]\\begin{code}\f[] and \f[C]\\end{code}\f[] will also
5262Text between \f[C]\\begin{code}\f[] and \f[C]\\end{code}\f[] will also
5282be treated as Haskell code.
5263be treated as Haskell code.
5283−For ATX\-style headers the character `=' will be used instead of `#'.
5264+For ATX\-style headers the character \[aq]=\[aq] will be used instead of
5284.IP \[bu] 2
5266.IP \[bu] 2
5285In Markdown output, code blocks with classes \f[C]haskell\f[] and
5267In Markdown output, code blocks with classes \f[C]haskell\f[] and
5286\f[C]literate\f[] will be rendered using bird tracks, and block
5268\f[C]literate\f[] will be rendered using bird tracks, and block
5287quotations will be indented one space, so they will not be treated as
5269quotations will be indented one space, so they will not be treated as
5288Haskell code.
5270Haskell code.
5289In addition, headers will be rendered setext\-style (with underlines)
5271In addition, headers will be rendered setext\-style (with underlines)
5290−rather than ATX\-style (with `#' characters).
5272+rather than ATX\-style (with \[aq]#\[aq] characters).
5291−(This is because ghc treats `#' characters in column 1 as introducing
5273+(This is because ghc treats \[aq]#\[aq] characters in column 1 as
5292−line numbers.)
5274+introducing line numbers.)
5293.IP \[bu] 2
5275.IP \[bu] 2
5294−In restructured text input, \[lq]bird track\[rq] sections will be parsed
5276+In restructured text input, "bird track" sections will be parsed as
5295−as Haskell code.
5277+Haskell code.
5296.IP \[bu] 2
5278.IP \[bu] 2
5297In restructured text output, code blocks with class \f[C]haskell\f[]
5279In restructured text output, code blocks with class \f[C]haskell\f[]
5298will be rendered using bird tracks.
5280will be rendered using bird tracks.
@@ -5327,8 +5309,9 @@ writes HTML with the Haskell code in bird tracks, so it can be copied
5327and pasted as literate Haskell source.
5309and pasted as literate Haskell source.
5329Note that GHC expects the bird tracks in the first column, so indentend
5311Note that GHC expects the bird tracks in the first column, so indentend
5312+literate code blocks (e.g.
5330−literate code blocks (e.g.\ inside an itemized environment) will not be
5313+inside an itemized environment) will not be picked up by the Haskell
5331−picked up by the Haskell compiler.
5314+compiler.
5332.SH SYNTAX HIGHLIGHTING
5315.SH SYNTAX HIGHLIGHTING
5334Pandoc will automatically highlight syntax in fenced code blocks that
5317Pandoc will automatically highlight syntax in fenced code blocks that
@@ -5349,8 +5332,8 @@ To see a list of highlight styles, type
5349To disable highlighting, use the \f[C]\-\-no\-highlight\f[] option.
5332To disable highlighting, use the \f[C]\-\-no\-highlight\f[] option.
5350.SH CUSTOM STYLES IN DOCX OUTPUT
5333.SH CUSTOM STYLES IN DOCX OUTPUT
5352−By default, pandoc's docx output applies a predefined set of styles for
5335+By default, pandoc\[aq]s docx output applies a predefined set of styles
5353−blocks such as paragraphs and block quotes, and uses largely default
5336+for blocks such as paragraphs and block quotes, and uses largely default
5354formatting (italics, bold) for inlines.
5337formatting (italics, bold) for inlines.
5355This will work for most purposes, especially alongside a
5338This will work for most purposes, especially alongside a
5356\f[C]reference.docx\f[] file.
5339\f[C]reference.docx\f[] file.
@@ -5369,8 +5352,8 @@ So, for example,
5372−would produce a docx file with \[lq]Get out,\[rq] styled with character
5355+would produce a docx file with "Get out," styled with character style
5373−style \f[C]Emphatically\f[].
5356+\f[C]Emphatically\f[].
5374Similarly,
5357Similarly,