@@ -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,11 +554,8 @@ 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. 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.
557+ from a certain reviewer, say, or before a certain date. This
558+ option only affects the docx reader.
562559
563560`--extract-media=`*DIR*
564561
@@ -919,48 +916,48 @@ Options affecting specific writers
919916 Docx
920917
921918 : For best results, the reference docx should be a modified
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.
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.
947944
948945 ODT
949946
950947 : For best results, the reference ODT should be a modified
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.
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.
964961
965962`--epub-cover-image=`*FILE*
966963
@@ -975,8 +972,8 @@ Options affecting specific writers
975972 The file should contain a series of [Dublin Core elements].
976973 For example:
977974
978− <dc:rights>Creative Commons</dc:rights>
979− <dc:language>es-AR</dc:language>
975+ <dc:rights>Creative Commons</dc:rights>
976+ <dc:language>es-AR</dc:language>
980977
981978 By default, pandoc will include the following metadata elements:
982979 `<dc:title>` (from the document title), `<dc:creator>` (from the
@@ -1000,31 +997,31 @@ Options affecting specific writers
1000997 embedded fonts, you will need to add declarations like the following
1001998 to your CSS (see `--css`):
1002999
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"; }
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"; }
10281025
10291026`--epub-chapter-level=`*NUMBER*
10301027
@@ -1177,9 +1174,9 @@ of the following options.
11771174 formulas and an HTML file with links to these images.
11781175 So, the procedure is:
11791176
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
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
11831180
11841181`--mimetex`[`=`*URL*]
11851182
@@ -1216,11 +1213,11 @@ Options for wrapper scripts
12161213: Ignore command-line arguments (for use in wrapper scripts).
12171214 Regular pandoc options are not ignored. Thus, for example,
12181215
1219− pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1
1216+ pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1
12201217
12211218 is equivalent to
12221219
1223− pandoc -o foo.html -s
1220+ pandoc -o foo.html -s
12241221
12251222Templates
12261223=========
@@ -1266,13 +1263,13 @@ as the following:
12661263 if input is from stdin. You can use the following snippet in your template
12671264 to distinguish them:
12681265
1269− $if(sourcefile)$
1270− $for(sourcefile)$
1271− $sourcefile$
1272− $endfor$
1273− $else$
1274− (stdin)
1275− $endif$
1266+ $if(sourcefile)$
1267+ $for(sourcefile)$
1268+ $sourcefile$
1269+ $endfor$
1270+ $else$
1271+ (stdin)
1272+ $endif$
12761273
12771274 Similarly, `outputfile` can be `-` if output goes to the terminal.
12781275
@@ -1282,11 +1279,11 @@ as the following:
12821279 through a [pandoc title block][Extension: `pandoc_title_block`],
12831280 which allows for multiple authors, or through a YAML metadata block:
12841281
1285− ---
1286− author:
1287− - Aristotle
1288− - Peter Abelard
1289− ...
1282+ ---
1283+ author:
1284+ - Aristotle
1285+ - Peter Abelard
1286+ ...
12901287
12911288`subtitle`
12921289: document subtitle, included in HTML, EPUB, LaTeX, ConTeXt, and Word docx;
@@ -1334,11 +1331,11 @@ as the following:
13341331[^subtitle]: To make `subtitle` work with other LaTeX
13351332 document classes, you can add the following to `header-includes`:
13361333
1337− \providecommand{\subtitle}[1]{%
1338− \usepackage{titling}
1339− \posttitle{%
1340− \par\large#1\end{center}}
1341− }
1334+ \providecommand{\subtitle}[1]{%
1335+ \usepackage{titling}
1336+ \posttitle{%
1337+ \par\large#1\end{center}}
1338+ }
13421339
13431340Language variables
13441341------------------
@@ -1732,7 +1729,7 @@ Typography
17321729
17331730Interpret straight quotes as curly quotes, `---` as em-dashes,
17341731`--` as en-dashes, and `...` as ellipses. Nonbreaking spaces are
1735−inserted after certain abbreviations, such as "Mr."
1732+inserted after certain abbreviations, such as "Mr."
17361733
17371734This extension can be enabled/disabled for the following formats:
17381735
@@ -2209,9 +2206,9 @@ A block of text indented four spaces (or one tab) is treated as verbatim
22092206text: that is, special characters do not trigger special formatting,
22102207and all spaces and line breaks are preserved. For example,
22112208
2212− if (a > 3) {
2213− moveShip(5 * gravity, DOWN);
2214− }
2209+ if (a > 3) {
2210+ moveShip(5 * gravity, DOWN);
2211+ }
22152212
22162213The initial (four space or one tab) indentation is not considered part
22172214of the verbatim text, and is removed in the output.
@@ -2260,7 +2257,7 @@ this syntax:
22602257 ~~~~ {#mycode .haskell .numberLines startFrom="100"}
22612258 qsort [] = []
22622259 qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++
2263− qsort (filter (>= x) xs)
2260+ qsort (filter (>= x) xs)
22642261 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
22652262
22662263Here `mycode` is an identifier, `haskell` and `numberLines` are classes, and
@@ -2384,12 +2381,12 @@ the list marker.
23842381
23852382 * First paragraph.
23862383
2387− Continued.
2384+ Continued.
23882385
23892386 * Second paragraph. With a code block, which must be indented
2390− eight spaces:
2387+ eight spaces:
23912388
2392− { code }
2389+ { code }
23932390
23942391Exception: if the list marker is followed by an indented code
23952392block, which must begin 5 spaces after the list marker, then
@@ -2407,8 +2404,8 @@ containing list item.
24072404
24082405 * fruits
24092406 + apples
2410− - macintosh
2411− - red delicious
2407+ - macintosh
2408+ - red delicious
24122409 + pears
24132410 + peaches
24142411 * vegetables
@@ -2425,7 +2422,7 @@ other blocks in a list item, the first line of each must be indented.
24252422 + Another one; this looks
24262423 bad but is legal.
24272424
2428− Second paragraph of second
2425+ Second paragraph of second
24292426 list item.
24302427
24312428### Ordered lists ###
@@ -2459,18 +2456,18 @@ capital letter with a period, by at least two spaces.[^2]
24592456[^2]: The point of this rule is to ensure that normal paragraphs
24602457 starting with people's initials, like
24612458
2462− B. Russell was an English philosopher.
2459+ B. Russell was an English philosopher.
24632460
24642461 do not get treated as list items.
24652462
24662463 This rule will not prevent
24672464
2468− (C) 2007 Joe Smith
2465+ (C) 2007 Joe Smith
24692466
24702467 from being interpreted as a list item. In this case, a backslash
24712468 escape can be used:
24722469
2473− (C\) 2007 Joe Smith
2470+ (C\) 2007 Joe Smith
24742471
24752472The `fancy_lists` extension also allows '`#`' to be used as an
24762473ordered list marker in place of a numeral:
@@ -2489,9 +2486,9 @@ roman numerals:
24892486 9) Ninth
24902487 10) Tenth
24912488 11) Eleventh
2492− i. subone
2493− ii. subtwo
2494− iii. subthree
2489+ i. subone
2490+ ii. subtwo
2491+ iii. subthree
24952492
24962493Pandoc will start a new list each time a different type of list
24972494marker is used. So, the following will create three lists:
@@ -2523,9 +2520,9 @@ Pandoc supports definition lists, using the syntax of
25232520
25242521 : Definition 2
25252522
2526− { some code, part of Definition 2 }
2523+ { some code, part of Definition 2 }
25272524
2528− Third paragraph of definition 2.
2525+ Third paragraph of definition 2.
25292526
25302527Each term must fit on one line, which may optionally be followed by
25312528a blank line, and must be followed by one or more definitions.
@@ -2544,7 +2541,7 @@ at the beginning of a paragraph or other block element:
25442541 : Definition
25452542 with lazy continuation.
25462543
2547− Second paragraph of the definition.
2544+ Second paragraph of the definition.
25482545
25492546If you leave space before the definition (as in the example above),
25502547the text of the definition will be treated as a paragraph. In some
@@ -2607,9 +2604,9 @@ cases" involving lists. Consider this source:
26072604
26082605 + First
26092606 + Second:
2610− - Fee
2611− - Fie
2612− - Foe
2607+ - Fee
2608+ - Fie
2609+ - Foe
26132610
26142611 + Third
26152612
@@ -2632,7 +2629,7 @@ What if you want to put an indented code block after a list?
26322629 - item one
26332630 - item two
26342631
2635− { my code block }
2632+ { my code block }
26362633
26372634Trouble! Here pandoc (like other Markdown implementations) will treat
26382635`{ my code block }` as the second paragraph of item two, and not as
@@ -2647,7 +2644,7 @@ any format:
26472644
26482645 <!-- end of list -->
26492646
2650− { my code block }
2647+ { my code block }
26512648
26522649You can use the same trick if you want two consecutive lists instead
26532650of one big list:
@@ -2693,9 +2690,9 @@ Simple tables look like this:
26932690
26942691 Right Left Center Default
26952692 ------- ------ ---------- -------
2696− 12 12 12 12
2697− 123 123 123 123
2698− 1 1 1 1
2693+ 12 12 12 12
2694+ 123 123 123 123
2695+ 1 1 1 1
26992696
27002697 Table: Demonstration of simple table syntax.
27012698
@@ -2722,9 +2719,9 @@ The column headers may be omitted, provided a dashed line is used
27222719to end the table. For example:
27232720
27242721 ------- ------ ---------- -------
2725− 12 12 12 12
2726− 123 123 123 123
2727− 1 1 1 1
2722+ 12 12 12 12
2723+ 123 123 123 123
2724+ 1 1 1 1
27282725 ------- ------ ---------- -------
27292726
27302727When headers are omitted, column alignments are determined on the basis
@@ -2742,11 +2739,11 @@ not supported). Here is an example:
27422739 Header Aligned Aligned Aligned
27432740 ----------- ------- --------------- -------------------------
27442741 First row 12.0 Example of a row that
2745− spans multiple lines.
2742+ spans multiple lines.
27462743
27472744 Second row 5.0 Here's another one. Note
2748− the blank line between
2749− rows.
2745+ the blank line between
2746+ rows.
27502747 -------------------------------------------------------------
27512748
27522749 Table: Here's the caption. It, too, may span
@@ -2768,11 +2765,11 @@ Headers may be omitted in multiline tables as well as simple tables:
27682765
27692766 ----------- ------- --------------- -------------------------
27702767 First row 12.0 Example of a row that
2771− spans multiple lines.
2768+ spans multiple lines.
27722769
27732770 Second row 5.0 Here's another one. Note
2774− the blank line between
2775− rows.
2771+ the blank line between
2772+ rows.
27762773 ----------- ------- --------------- -------------------------
27772774
27782775 : Here's a multiline table without headers.
@@ -3532,7 +3529,7 @@ If you just want a regular inline image, just make sure it is not
35323529the only thing in the paragraph. One way to do this is to insert a
35333530nonbreaking space after the image:
35343531
3535− \
3532+ \
35363533
35373534Note that in reveal.js slide shows, an image in a paragraph
35383535by itself that has the `stretch` class will fill the screen,
@@ -3651,14 +3648,14 @@ Pandoc's Markdown allows footnotes, using the following syntax:
36513648
36523649 [^longnote]: Here's one with multiple blocks.
36533650
3654− Subsequent paragraphs are indented to show that they
3651+ Subsequent paragraphs are indented to show that they
36553652 belong to the previous footnote.
36563653
3657− { some.code }
3654+ { some.code }
36583655
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.
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.
36623659
36633660 This paragraph won't be part of the note, because it
36643661 isn't indented.
@@ -3758,16 +3755,16 @@ YAML-encoded references, for example:
37583755 id: WatsonCrick1953
37593756 author:
37603757 - family: Watson
3761− given: J. D.
3758+ given: J. D.
37623759 - family: Crick
3763− given: F. H. C.
3760+ given: F. H. C.
37643761 issued:
3765− date-parts:
3766− - - 1953
3767− - 4
3768− - 25
3762+ date-parts:
3763+ - - 1953
3764+ - 4
3765+ - 25
37693766 title: 'Molecular structure of nucleic acids: a structure for deoxyribose
3770− nucleic acid'
3767+ nucleic acid'
37713768 title-short: Molecular structure of nucleic acids
37723769 container-title: Nature
37733770 volume: 171
@@ -3968,7 +3965,7 @@ the document, for example:
39683965 Author: John Doe
39693966 Date: September 1, 2008
39703967 Comment: This is a sample mmd title block, with
3971− a field spanning multiple lines.
3968+ a field spanning multiple lines.
39723969
39733970See the MultiMarkdown documentation for details. If `pandoc_title_block` or
39743971`yaml_metadata_block` is enabled, it will take precedence over
@@ -3998,7 +3995,7 @@ and image references. This extension should not be confused with the
39983995 This is a reference ![image][ref] with multimarkdown attributes.
39993996
40003997 [ref]: http://path.to/image "Image title" width=20px height=30px
4001− id=myId class="myClass1 myClass2"
3998+ id=myId class="myClass1 myClass2"
40023999
40034000#### Extension: `mmd_header_identifiers` ####
40044001
@@ -4022,10 +4019,10 @@ in several respects:
40224019[^6]: To see why laziness is incompatible with relaxing the requirement
40234020 of a blank line between items, consider the following example:
40244021
4025− bar
4026− : definition
4027− foo
4028− : definition
4022+ bar
4023+ : definition
4024+ foo
4025+ : definition
40294026
40304027 Is this a single list item with two definitions of "bar," the first of
40314028 which is lazily wrapped, or two list items? To remove the ambiguity
@@ -4427,7 +4424,7 @@ with the `src` attribute. For example:
44274424
44284425 <audio controls="1">
44294426 <source src="http://example.com/music/toccata.mp3"
4430− data-external="1" type="audio/mpeg">
4427+ data-external="1" type="audio/mpeg">
44314428 </source>
44324429 </audio>
44334430