@@ -349,15 +349,15 @@ General options
349349 If this option is not specified, the default user data directory
350350 will be used. This is, in UNIX:
351351
352− $HOME/.pandoc
352+ $HOME/.pandoc
353353
354354 in Windows XP:
355355
356− C:\Documents And Settings\USERNAME\Application Data\pandoc
356+ C:\Documents And Settings\USERNAME\Application Data\pandoc
357357
358358 and in Windows Vista or later:
359359
360− C:\Users\USERNAME\AppData\Roaming\pandoc
360+ C:\Users\USERNAME\AppData\Roaming\pandoc
361361
362362 You can find the default user data directory on your system by
363363 looking at the output of `pandoc --version`.
@@ -370,7 +370,7 @@ General options
370370: Generate a bash completion script. To enable bash completion
371371 with pandoc, add this to your `.bashrc`:
372372
373− eval "$(pandoc --bash-completion)"
373+ eval "$(pandoc --bash-completion)"
374374
375375`--verbose`
376376
@@ -468,11 +468,11 @@ Reader options
468468 JSON input and output. The name of the output format will be
469469 passed to the filter as the first argument. Hence,
470470
471− pandoc --filter ./caps.py -t latex
471+ pandoc --filter ./caps.py -t latex
472472
473473 is equivalent to
474474
475− pandoc -t json | ./caps.py latex | pandoc -f json -t latex
475+ pandoc -t json | ./caps.py latex | pandoc -f json -t latex
476476
477477 The latter form may be useful for debugging filters.
478478
@@ -511,15 +511,15 @@ Reader options
511511
512512 The following is an example lua script for macro-expansion:
513513
514− function expand_hello_world(inline)
515− if inline.c == '{{helloworld}}' then
516− return pandoc.Emph{ pandoc.Str "Hello, World" }
517− else
518− return inline
519− end
520− end
514+ function expand_hello_world(inline)
515+ if inline.c == '{{helloworld}}' then
516+ return pandoc.Emph{ pandoc.Str "Hello, World" }
517+ else
518+ return inline
519+ end
520+ end
521521
522− return {{Str = expand_hello_world}}
522+ return {{Str = expand_hello_world}}
523523
524524
525525`-M` *KEY*[`=`*VAL*], `--metadata=`*KEY*[`:`*VAL*]
@@ -554,8 +554,11 @@ Reader options
554554 `insertion`, `deletion`, `comment-start`, and `comment-end`
555555 classes, respectively. The author and time of change is
556556 included. `all` is useful for scripting: only accepting changes
557− from a certain reviewer, say, or before a certain date. This
558− option only affects the docx reader.
557+ from a certain reviewer, say, or before a certain date. If a
558+ paragraph is inserted or deleted, `track-changes=all` produces a
559+ span with the class `paragraph-insertion`/`paragraph-deletion`
560+ before the affected paragraph break. This option only affects the
561+ docx reader.
559562
560563`--extract-media=`*DIR*
561564
@@ -916,48 +919,48 @@ Options affecting specific writers
916919 Docx
917920
918921 : For best results, the reference docx should be a modified
919− version of a docx file produced using pandoc. The contents
920− of the reference docx are ignored, but its stylesheets and
921− document properties (including margins, page size, header,
922− and footer) are used in the new docx. If no reference docx
923− is specified on the command line, pandoc will look for a
924− file `reference.docx` in the user data directory (see
925− `--data-dir`). If this is not found either, sensible
926− defaults will be used.
927−
928− To produce a custom `reference.docx`, first get a copy of
929− the default `reference.docx`: `pandoc
930− --print-default-data-file reference.docx >
931− custom-reference.docx`. Then open `custom-reference.docx`
932− in Word, modify the styles as you wish, and save the file.
933− For best results, do not make changes to this file other
934− than modifying the styles used by pandoc: [paragraph]
935− Normal, Body Text, First Paragraph, Compact, Title,
936− Subtitle, Author, Date, Abstract, Bibliography, Heading 1,
937− Heading 2, Heading 3, Heading 4, Heading 5, Heading 6,
938− Heading 7, Heading 8, Heading 9, Block Text, Footnote Text,
939− Definition Term, Definition, Caption, Table Caption,
940− Image Caption, Figure, Captioned Figure, TOC Heading;
941− [character] Default Paragraph Font, Body Text Char,
942− Verbatim Char, Footnote Reference, Hyperlink; [table]
943− Table.
922+ version of a docx file produced using pandoc. The contents
923+ of the reference docx are ignored, but its stylesheets and
924+ document properties (including margins, page size, header,
925+ and footer) are used in the new docx. If no reference docx
926+ is specified on the command line, pandoc will look for a
927+ file `reference.docx` in the user data directory (see
928+ `--data-dir`). If this is not found either, sensible
929+ defaults will be used.
930+
931+ To produce a custom `reference.docx`, first get a copy of
932+ the default `reference.docx`: `pandoc
933+ --print-default-data-file reference.docx >
934+ custom-reference.docx`. Then open `custom-reference.docx`
935+ in Word, modify the styles as you wish, and save the file.
936+ For best results, do not make changes to this file other
937+ than modifying the styles used by pandoc: [paragraph]
938+ Normal, Body Text, First Paragraph, Compact, Title,
939+ Subtitle, Author, Date, Abstract, Bibliography, Heading 1,
940+ Heading 2, Heading 3, Heading 4, Heading 5, Heading 6,
941+ Heading 7, Heading 8, Heading 9, Block Text, Footnote Text,
942+ Definition Term, Definition, Caption, Table Caption,
943+ Image Caption, Figure, Captioned Figure, TOC Heading;
944+ [character] Default Paragraph Font, Body Text Char,
945+ Verbatim Char, Footnote Reference, Hyperlink; [table]
946+ Table.
944947
945948 ODT
946949
947950 : For best results, the reference ODT should be a modified
948− version of an ODT produced using pandoc. The contents of
949− the reference ODT are ignored, but its stylesheets are used
950− in the new ODT. If no reference ODT is specified on the
951− command line, pandoc will look for a file `reference.odt` in
952− the user data directory (see `--data-dir`). If this is not
953− found either, sensible defaults will be used.
954−
955− To produce a custom `reference.odt`, first get a copy of
956− the default `reference.odt`: `pandoc
957− --print-default-data-file reference.odt >
958− custom-reference.odt`. Then open `custom-reference.odt` in
959− LibreOffice, modify the styles as you wish, and save the
960− file.
951+ version of an ODT produced using pandoc. The contents of
952+ the reference ODT are ignored, but its stylesheets are used
953+ in the new ODT. If no reference ODT is specified on the
954+ command line, pandoc will look for a file `reference.odt` in
955+ the user data directory (see `--data-dir`). If this is not
956+ found either, sensible defaults will be used.
957+
958+ To produce a custom `reference.odt`, first get a copy of
959+ the default `reference.odt`: `pandoc
960+ --print-default-data-file reference.odt >
961+ custom-reference.odt`. Then open `custom-reference.odt` in
962+ LibreOffice, modify the styles as you wish, and save the
963+ file.
961964
962965`--epub-cover-image=`*FILE*
963966
@@ -972,8 +975,8 @@ Options affecting specific writers
972975 The file should contain a series of [Dublin Core elements].
973976 For example:
974977
975− <dc:rights>Creative Commons</dc:rights>
976− <dc:language>es-AR</dc:language>
978+ <dc:rights>Creative Commons</dc:rights>
979+ <dc:language>es-AR</dc:language>
977980
978981 By default, pandoc will include the following metadata elements:
979982 `<dc:title>` (from the document title), `<dc:creator>` (from the
@@ -997,31 +1000,31 @@ Options affecting specific writers
9971000 embedded fonts, you will need to add declarations like the following
9981001 to your CSS (see `--css`):
9991002
1000− @font-face {
1001− font-family: DejaVuSans;
1002− font-style: normal;
1003− font-weight: normal;
1004− src:url("DejaVuSans-Regular.ttf");
1005− }
1006− @font-face {
1007− font-family: DejaVuSans;
1008− font-style: normal;
1009− font-weight: bold;
1010− src:url("DejaVuSans-Bold.ttf");
1011− }
1012− @font-face {
1013− font-family: DejaVuSans;
1014− font-style: italic;
1015− font-weight: normal;
1016− src:url("DejaVuSans-Oblique.ttf");
1017− }
1018− @font-face {
1019− font-family: DejaVuSans;
1020− font-style: italic;
1021− font-weight: bold;
1022− src:url("DejaVuSans-BoldOblique.ttf");
1023− }
1024− body { font-family: "DejaVuSans"; }
1003+ @font-face {
1004+ font-family: DejaVuSans;
1005+ font-style: normal;
1006+ font-weight: normal;
1007+ src:url("DejaVuSans-Regular.ttf");
1008+ }
1009+ @font-face {
1010+ font-family: DejaVuSans;
1011+ font-style: normal;
1012+ font-weight: bold;
1013+ src:url("DejaVuSans-Bold.ttf");
1014+ }
1015+ @font-face {
1016+ font-family: DejaVuSans;
1017+ font-style: italic;
1018+ font-weight: normal;
1019+ src:url("DejaVuSans-Oblique.ttf");
1020+ }
1021+ @font-face {
1022+ font-family: DejaVuSans;
1023+ font-style: italic;
1024+ font-weight: bold;
1025+ src:url("DejaVuSans-BoldOblique.ttf");
1026+ }
1027+ body { font-family: "DejaVuSans"; }
10251028
10261029`--epub-chapter-level=`*NUMBER*
10271030
@@ -1174,9 +1177,9 @@ of the following options.
11741177 formulas and an HTML file with links to these images.
11751178 So, the procedure is:
11761179
1177− pandoc -s --gladtex input.md -o myfile.htex
1178− gladtex -d myfile-images myfile.htex
1179− # produces myfile.html and images in myfile-images
1180+ pandoc -s --gladtex input.md -o myfile.htex
1181+ gladtex -d myfile-images myfile.htex
1182+ # produces myfile.html and images in myfile-images
11801183
11811184`--mimetex`[`=`*URL*]
11821185
@@ -1213,11 +1216,11 @@ Options for wrapper scripts
12131216: Ignore command-line arguments (for use in wrapper scripts).
12141217 Regular pandoc options are not ignored. Thus, for example,
12151218
1216− pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1
1219+ pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1
12171220
12181221 is equivalent to
12191222
1220− pandoc -o foo.html -s
1223+ pandoc -o foo.html -s
12211224
12221225Templates
12231226=========
@@ -1263,13 +1266,13 @@ as the following:
12631266 if input is from stdin. You can use the following snippet in your template
12641267 to distinguish them:
12651268
1266− $if(sourcefile)$
1267− $for(sourcefile)$
1268− $sourcefile$
1269− $endfor$
1270− $else$
1271− (stdin)
1272− $endif$
1269+ $if(sourcefile)$
1270+ $for(sourcefile)$
1271+ $sourcefile$
1272+ $endfor$
1273+ $else$
1274+ (stdin)
1275+ $endif$
12731276
12741277 Similarly, `outputfile` can be `-` if output goes to the terminal.
12751278
@@ -1279,11 +1282,11 @@ as the following:
12791282 through a [pandoc title block][Extension: `pandoc_title_block`],
12801283 which allows for multiple authors, or through a YAML metadata block:
12811284
1282− ---
1283− author:
1284− - Aristotle
1285− - Peter Abelard
1286− ...
1285+ ---
1286+ author:
1287+ - Aristotle
1288+ - Peter Abelard
1289+ ...
12871290
12881291`subtitle`
12891292: document subtitle, included in HTML, EPUB, LaTeX, ConTeXt, and Word docx;
@@ -1331,11 +1334,11 @@ as the following:
13311334[^subtitle]: To make `subtitle` work with other LaTeX
13321335 document classes, you can add the following to `header-includes`:
13331336
1334− \providecommand{\subtitle}[1]{%
1335− \usepackage{titling}
1336− \posttitle{%
1337− \par\large#1\end{center}}
1338− }
1337+ \providecommand{\subtitle}[1]{%
1338+ \usepackage{titling}
1339+ \posttitle{%
1340+ \par\large#1\end{center}}
1341+ }
13391342
13401343Language variables
13411344------------------
@@ -1729,7 +1732,7 @@ Typography
17291732
17301733Interpret straight quotes as curly quotes, `---` as em-dashes,
17311734`--` as en-dashes, and `...` as ellipses. Nonbreaking spaces are
1732−inserted after certain abbreviations, such as "Mr."
1735+inserted after certain abbreviations, such as "Mr."
17331736
17341737This extension can be enabled/disabled for the following formats:
17351738
@@ -2206,9 +2209,9 @@ A block of text indented four spaces (or one tab) is treated as verbatim
22062209text: that is, special characters do not trigger special formatting,
22072210and all spaces and line breaks are preserved. For example,
22082211
2209− if (a > 3) {
2210− moveShip(5 * gravity, DOWN);
2211− }
2212+ if (a > 3) {
2213+ moveShip(5 * gravity, DOWN);
2214+ }
22122215
22132216The initial (four space or one tab) indentation is not considered part
22142217of the verbatim text, and is removed in the output.
@@ -2257,7 +2260,7 @@ this syntax:
22572260 ~~~~ {#mycode .haskell .numberLines startFrom="100"}
22582261 qsort [] = []
22592262 qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++
2260− qsort (filter (>= x) xs)
2263+ qsort (filter (>= x) xs)
22612264 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
22622265
22632266Here `mycode` is an identifier, `haskell` and `numberLines` are classes, and
@@ -2381,12 +2384,12 @@ the list marker.
23812384
23822385 * First paragraph.
23832386
2384− Continued.
2387+ Continued.
23852388
23862389 * Second paragraph. With a code block, which must be indented
2387− eight spaces:
2390+ eight spaces:
23882391
2389− { code }
2392+ { code }
23902393
23912394Exception: if the list marker is followed by an indented code
23922395block, which must begin 5 spaces after the list marker, then
@@ -2404,8 +2407,8 @@ containing list item.
24042407
24052408 * fruits
24062409 + apples
2407− - macintosh
2408− - red delicious
2410+ - macintosh
2411+ - red delicious
24092412 + pears
24102413 + peaches
24112414 * vegetables
@@ -2422,7 +2425,7 @@ other blocks in a list item, the first line of each must be indented.
24222425 + Another one; this looks
24232426 bad but is legal.
24242427
2425− Second paragraph of second
2428+ Second paragraph of second
24262429 list item.
24272430
24282431### Ordered lists ###
@@ -2456,18 +2459,18 @@ capital letter with a period, by at least two spaces.[^2]
24562459[^2]: The point of this rule is to ensure that normal paragraphs
24572460 starting with people's initials, like
24582461
2459− B. Russell was an English philosopher.
2462+ B. Russell was an English philosopher.
24602463
24612464 do not get treated as list items.
24622465
24632466 This rule will not prevent
24642467
2465− (C) 2007 Joe Smith
2468+ (C) 2007 Joe Smith
24662469
24672470 from being interpreted as a list item. In this case, a backslash
24682471 escape can be used:
24692472
2470− (C\) 2007 Joe Smith
2473+ (C\) 2007 Joe Smith
24712474
24722475The `fancy_lists` extension also allows '`#`' to be used as an
24732476ordered list marker in place of a numeral:
@@ -2486,9 +2489,9 @@ roman numerals:
24862489 9) Ninth
24872490 10) Tenth
24882491 11) Eleventh
2489− i. subone
2490− ii. subtwo
2491− iii. subthree
2492+ i. subone
2493+ ii. subtwo
2494+ iii. subthree
24922495
24932496Pandoc will start a new list each time a different type of list
24942497marker is used. So, the following will create three lists:
@@ -2520,9 +2523,9 @@ Pandoc supports definition lists, using the syntax of
25202523
25212524 : Definition 2
25222525
2523− { some code, part of Definition 2 }
2526+ { some code, part of Definition 2 }
25242527
2525− Third paragraph of definition 2.
2528+ Third paragraph of definition 2.
25262529
25272530Each term must fit on one line, which may optionally be followed by
25282531a blank line, and must be followed by one or more definitions.
@@ -2541,7 +2544,7 @@ at the beginning of a paragraph or other block element:
25412544 : Definition
25422545 with lazy continuation.
25432546
2544− Second paragraph of the definition.
2547+ Second paragraph of the definition.
25452548
25462549If you leave space before the definition (as in the example above),
25472550the text of the definition will be treated as a paragraph. In some
@@ -2604,9 +2607,9 @@ cases" involving lists. Consider this source:
26042607
26052608 + First
26062609 + Second:
2607− - Fee
2608− - Fie
2609− - Foe
2610+ - Fee
2611+ - Fie
2612+ - Foe
26102613
26112614 + Third
26122615
@@ -2629,7 +2632,7 @@ What if you want to put an indented code block after a list?
26292632 - item one
26302633 - item two
26312634
2632− { my code block }
2635+ { my code block }
26332636
26342637Trouble! Here pandoc (like other Markdown implementations) will treat
26352638`{ my code block }` as the second paragraph of item two, and not as
@@ -2644,7 +2647,7 @@ any format:
26442647
26452648 <!-- end of list -->
26462649
2647− { my code block }
2650+ { my code block }
26482651
26492652You can use the same trick if you want two consecutive lists instead
26502653of one big list:
@@ -2690,9 +2693,9 @@ Simple tables look like this:
26902693
26912694 Right Left Center Default
26922695 ------- ------ ---------- -------
2693− 12 12 12 12
2694− 123 123 123 123
2695− 1 1 1 1
2696+ 12 12 12 12
2697+ 123 123 123 123
2698+ 1 1 1 1
26962699
26972700 Table: Demonstration of simple table syntax.
26982701
@@ -2719,9 +2722,9 @@ The column headers may be omitted, provided a dashed line is used
27192722to end the table. For example:
27202723
27212724 ------- ------ ---------- -------
2722− 12 12 12 12
2723− 123 123 123 123
2724− 1 1 1 1
2725+ 12 12 12 12
2726+ 123 123 123 123
2727+ 1 1 1 1
27252728 ------- ------ ---------- -------
27262729
27272730When headers are omitted, column alignments are determined on the basis
@@ -2739,11 +2742,11 @@ not supported). Here is an example:
27392742 Header Aligned Aligned Aligned
27402743 ----------- ------- --------------- -------------------------
27412744 First row 12.0 Example of a row that
2742− spans multiple lines.
2745+ spans multiple lines.
27432746
27442747 Second row 5.0 Here's another one. Note
2745− the blank line between
2746− rows.
2748+ the blank line between
2749+ rows.
27472750 -------------------------------------------------------------
27482751
27492752 Table: Here's the caption. It, too, may span
@@ -2765,11 +2768,11 @@ Headers may be omitted in multiline tables as well as simple tables:
27652768
27662769 ----------- ------- --------------- -------------------------
27672770 First row 12.0 Example of a row that
2768− spans multiple lines.
2771+ spans multiple lines.
27692772
27702773 Second row 5.0 Here's another one. Note
2771− the blank line between
2772− rows.
2774+ the blank line between
2775+ rows.
27732776 ----------- ------- --------------- -------------------------
27742777
27752778 : Here's a multiline table without headers.
@@ -3529,7 +3532,7 @@ If you just want a regular inline image, just make sure it is not
35293532the only thing in the paragraph. One way to do this is to insert a
35303533nonbreaking space after the image:
35313534
3532− \
3535+ \
35333536
35343537Note that in reveal.js slide shows, an image in a paragraph
35353538by itself that has the `stretch` class will fill the screen,
@@ -3648,14 +3651,14 @@ Pandoc's Markdown allows footnotes, using the following syntax:
36483651
36493652 [^longnote]: Here's one with multiple blocks.
36503653
3651− Subsequent paragraphs are indented to show that they
3654+ Subsequent paragraphs are indented to show that they
36523655 belong to the previous footnote.
36533656
3654− { some.code }
3657+ { some.code }
36553658
3656− The whole paragraph can be indented, or just the first
3657− line. In this way, multi-paragraph footnotes work like
3658− multi-paragraph list items.
3659+ The whole paragraph can be indented, or just the first
3660+ line. In this way, multi-paragraph footnotes work like
3661+ multi-paragraph list items.
36593662
36603663 This paragraph won't be part of the note, because it
36613664 isn't indented.
@@ -3755,16 +3758,16 @@ YAML-encoded references, for example:
37553758 id: WatsonCrick1953
37563759 author:
37573760 - family: Watson
3758− given: J. D.
3761+ given: J. D.
37593762 - family: Crick
3760− given: F. H. C.
3763+ given: F. H. C.
37613764 issued:
3762− date-parts:
3763− - - 1953
3764− - 4
3765− - 25
3765+ date-parts:
3766+ - - 1953
3767+ - 4
3768+ - 25
37663769 title: 'Molecular structure of nucleic acids: a structure for deoxyribose
3767− nucleic acid'
3770+ nucleic acid'
37683771 title-short: Molecular structure of nucleic acids
37693772 container-title: Nature
37703773 volume: 171
@@ -3965,7 +3968,7 @@ the document, for example:
39653968 Author: John Doe
39663969 Date: September 1, 2008
39673970 Comment: This is a sample mmd title block, with
3968− a field spanning multiple lines.
3971+ a field spanning multiple lines.
39693972
39703973See the MultiMarkdown documentation for details. If `pandoc_title_block` or
39713974`yaml_metadata_block` is enabled, it will take precedence over
@@ -3995,7 +3998,7 @@ and image references. This extension should not be confused with the
39953998 This is a reference ![image][ref] with multimarkdown attributes.
39963999
39974000 [ref]: http://path.to/image "Image title" width=20px height=30px
3998− id=myId class="myClass1 myClass2"
4001+ id=myId class="myClass1 myClass2"
39994002
40004003#### Extension: `mmd_header_identifiers` ####
40014004
@@ -4019,10 +4022,10 @@ in several respects:
40194022[^6]: To see why laziness is incompatible with relaxing the requirement
40204023 of a blank line between items, consider the following example:
40214024
4022− bar
4023− : definition
4024− foo
4025− : definition
4025+ bar
4026+ : definition
4027+ foo
4028+ : definition
40264029
40274030 Is this a single list item with two definitions of "bar," the first of
40284031 which is lazily wrapped, or two list items? To remove the ambiguity
@@ -4424,7 +4427,7 @@ with the `src` attribute. For example:
44244427
44254428 <audio controls="1">
44264429 <source src="http://example.com/music/toccata.mp3"
4427− data-external="1" type="audio/mpeg">
4430+ data-external="1" type="audio/mpeg">
44284431 </source>
44294432 </audio>
44304433