README · typeable/pandoc

1398[^3]: I have also been influenced by the suggestions of [David Wheeler](http://www.justatheory.com/computers/markup/modest-markdown-proposal.html).

1399

1400[PHP Markdown Extra]: http://www.michelf.com/projects/php-markdown/extra/

1401

1402

1403### Numbered example lists ###

1404

1405**Extension: `example_lists`**

1406

1407The special list marker `@` can be used for sequentially numbered

1408examples. The first list item with a `@` marker will be numbered '1',

1409the next '2', and so on, throughout the document. The numbered examples

1410need not occur in a single list; each new list using `@` will take up

1411where the last stopped. So, for example:

1412

1413 (@) My first example will be numbered (1).

1414 (@) My second example will be numbered (2).

1415

1416 Explanation of examples.

1417

1418 (@) My third example will be numbered (3).

1419

1420Numbered examples can be labeled and referred to elsewhere in the

1421document:

1422

1423 (@good) This is a good example.

1424

1425 As (@good) illustrates, ...

1426

1427The label can be any string of alphanumeric characters, underscores,

1428or hyphens.

1429

1430

1431### Compact and loose lists ###

1432

1433Pandoc behaves differently from `Markdown.pl` on some "edge

1434cases" involving lists. Consider this source:

1435

1436 + First

1437 + Second:

1438 - Fee

1439 - Fie

1440 - Foe

1441

1442 + Third

1443

1444Pandoc transforms this into a "compact list" (with no `<p>` tags around

1445"First", "Second", or "Third"), while markdown puts `<p>` tags around

1446"Second" and "Third" (but not "First"), because of the blank space

1447around "Third". Pandoc follows a simple rule: if the text is followed by

1448a blank line, it is treated as a paragraph. Since "Second" is followed

1449by a list, and not a blank line, it isn't treated as a paragraph. The

1450fact that the list is followed by a blank line is irrelevant. (Note:

1451Pandoc works this way even when the `markdown_strict` format is specified. This

1452behavior is consistent with the official markdown syntax description,

1453even though it is different from that of `Markdown.pl`.)

1454

1455

1456### Ending a list ###

1457

1458What if you want to put an indented code block after a list?

1459

1460 - item one

1461 - item two

1462

1463 { my code block }

1464

1465Trouble! Here pandoc (like other markdown implementations) will treat

1466`{ my code block }` as the second paragraph of item two, and not as

1467a code block.

1468

1469To "cut off" the list after item two, you can insert some non-indented

1470content, like an HTML comment, which won't produce visible output in

1471any format:

1472

1473 - item one

1474 - item two

1475

1476

1477

1478 { my code block }

1479

1480You can use the same trick if you want two consecutive lists instead

1481of one big list:

1482

1483 1. one

1484 2. two

1485 3. three

1486

1487

1488

1489 1. uno

1490 2. dos

1491 3. tres

1492

1493Horizontal rules

1494----------------

1495

1496A line containing a row of three or more `*`, `-`, or `_` characters

1497(optionally separated by spaces) produces a horizontal rule:

1499 * * * *

1501 ---------------

1504Tables

1505------

1506

1507Four kinds of tables may be used. The first three kinds presuppose the use of

1508a fixed-width font, such as Courier. The fourth kind can be used with

1509proportionally spaced fonts, as it does not require lining up columns.

1510

1511### Simple tables

1512

1513**Extension: `simple_tables`, `table_captions`**

1514

1515Simple tables look like this:

1516

1517 Right Left Center Default

1518 ------- ------ ---------- -------

1519 12 12 12 12

1520 123 123 123 123

1521 1 1 1 1

1522

1523 Table: Demonstration of simple table syntax.

1524

1525The headers and table rows must each fit on one line. Column

1526alignments are determined by the position of the header text relative

1527to the dashed line below it:[^4]

1528

1529 - If the dashed line is flush with the header text on the right side

1530 but extends beyond it on the left, the column is right-aligned.

1531 - If the dashed line is flush with the header text on the left side

1532 but extends beyond it on the right, the column is left-aligned.

1533 - If the dashed line extends beyond the header text on both sides,

1534 the column is centered.

1535 - If the dashed line is flush with the header text on both sides,

1536 the default alignment is used (in most cases, this will be left).

1537

1538[^4]: This scheme is due to Michel Fortin, who proposed it on the

1539 [Markdown discussion list](http://six.pairlist.net/pipermail/markdown-discuss/2005-March/001097.html).

1540

1541The table must end with a blank line, or a line of dashes followed by

1542a blank line. A caption may optionally be provided (as illustrated in

1543the example above). A caption is a paragraph beginning with the string

1544`Table:` (or just `:`), which will be stripped off. It may appear either

1545before or after the table.

1546

1547The column headers may be omitted, provided a dashed line is used

1548to end the table. For example:

1549

1550 ------- ------ ---------- -------

1551 12 12 12 12

1552 123 123 123 123

1553 1 1 1 1

1554 ------- ------ ---------- -------

1555

1556When headers are omitted, column alignments are determined on the basis

1557of the first line of the table body. So, in the tables above, the columns

1558would be right, left, center, and right aligned, respectively.

1559

1560### Multiline tables

1561

1562**Extension: `multiline_tables`, `table_captions`**

1563

1564Multiline tables allow headers and table rows to span multiple lines

1565of text (but cells that span multiple columns or rows of the table are

1566not supported). Here is an example:

1567

1568 -------------------------------------------------------------

1569 Centered Default Right Left

1570 Header Aligned Aligned Aligned

1571 ----------- ------- --------------- -------------------------

1572 First row 12.0 Example of a row that

1573 spans multiple lines.

1574

1575 Second row 5.0 Here's another one. Note

1576 the blank line between

1577 rows.

1578 -------------------------------------------------------------

1579

1580 Table: Here's the caption. It, too, may span

1581 multiple lines.

1582

1583These work like simple tables, but with the following differences:

1584

1585 - They must begin with a row of dashes, before the header text

1586 (unless the headers are omitted).

1587 - They must end with a row of dashes, then a blank line.

1588 - The rows must be separated by blank lines.

1589

1590In multiline tables, the table parser pays attention to the widths of

1591the columns, and the writers try to reproduce these relative widths in

1592the output. So, if you find that one of the columns is too narrow in the

1593output, try widening it in the markdown source.

1594

1595Headers may be omitted in multiline tables as well as simple tables:

1596

1597 ----------- ------- --------------- -------------------------

1598 First row 12.0 Example of a row that

1599 spans multiple lines.

1600

1601 Second row 5.0 Here's another one. Note

1602 the blank line between

1603 rows.

1604 ----------- ------- --------------- -------------------------

1605

1606 : Here's a multiline table without headers.

1607

1608It is possible for a multiline table to have just one row, but the row

1609should be followed by a blank line (and then the row of dashes that ends

1610the table), or the table may be interpreted as a simple table.

1611

1612### Grid tables

1613

1614**Extension: `grid_tables`, `table_captions`**

1615

1616Grid tables look like this:

1617

1618 : Sample grid table.

1619

1620 +---------------+---------------+--------------------+

1621 | Fruit | Price | Advantages |

1622 +===============+===============+====================+

1623 | Bananas | $1.34 | - built-in wrapper |

1624 | | | - bright color |

1625 +---------------+---------------+--------------------+

1626 | Oranges | $2.10 | - cures scurvy |

1627 | | | - tasty |

1628 +---------------+---------------+--------------------+

1629

1630The row of `=`s separates the header from the table body, and can be

1631omitted for a headerless table. The cells of grid tables may contain

1632arbitrary block elements (multiple paragraphs, code blocks, lists,

1633etc.). Alignments are not supported, nor are cells that span multiple

1634columns or rows. Grid tables can be created easily using [Emacs table mode].

1635

1636 [Emacs table mode]: http://table.sourceforge.net/

1637

1638### Pipe tables

1639

1640**Extension: `pipe_tables`, `table_captions`**

1641

1642Pipe tables look like this:

1643

1645 |------:|:-----|---------|:------:|

1646 | 12 | 12 | 12 | 12 |

1647 | 123 | 123 | 123 | 123 |

1648 | 1 | 1 | 1 | 1 |

1649

1650 : Demonstration of simple table syntax.

1651

1652The syntax is [the same as in PHP markdown extra]. The beginning and

1653ending pipe characters are optional, but pipes are required between all

1654columns. The colons indicate column alignment as shown. The header

1655can be omitted, but the horizontal line must still be included, as

1656it defines column alignments.

1657

1658Since the pipes indicate column boundaries, columns need not be vertically

1659aligned, as they are in the above example. So, this is a perfectly

1660legal (though ugly) pipe table:

1661

1662 fruit| price

1663 -----|-----:

1664 apple|2.05

1665 pear|1.37

1666 orange|3.09

1667

1668The cells of pipe tables cannot contain block elements like paragraphs

1669and lists, and cannot span multiple lines.

1670

1671 [the same as in PHP markdown extra]:

1672 http://michelf.ca/projects/php-markdown/extra/#table

1673

1674Note: Pandoc also recognizes pipe tables of the following

1675form, as can produced by Emacs' orgtbl-mode:

1676

1677 | One | Two |

1678 |-----+-------|

1679 | my | table |

1680 | is | nice |

1681

1682The difference is that `+` is used instead of `|`. Other orgtbl features

1683are not supported. In particular, to get non-default column alignment,

1684you'll need to add colons as above.

1685

1686Title block

1687-----------

1688

1689**Extension: `pandoc_title_block`**

1690

1691If the file begins with a title block

1692

1693 % title

1694 % author(s) (separated by semicolons)

1695 % date

1696

1697it will be parsed as bibliographic information, not regular text. (It

1698will be used, for example, in the title of standalone LaTeX or HTML

1699output.) The block may contain just a title, a title and an author,

1700or all three elements. If you want to include an author but no

1701title, or a title and a date but no author, you need a blank line:

1702

1703 %

1704 % Author

1705

1706 % My title

1707 %

1708 % June 15, 2006

1709

1710The title may occupy multiple lines, but continuation lines must

1711begin with leading space, thus:

1712

1713 % My title

1714 on multiple lines

1715

1716If a document has multiple authors, the authors may be put on

1717separate lines with leading space, or separated by semicolons, or

1718both. So, all of the following are equivalent:

1719

1720 % Author One

1721 Author Two

1722

1723 % Author One; Author Two

1724

1725 % Author One;

1726 Author Two

1727

1728The date must fit on one line.

1729

1730All three metadata fields may contain standard inline formatting

1731(italics, links, footnotes, etc.).

1732

1733Title blocks will always be parsed, but they will affect the output only

1734when the `--standalone` (`-s`) option is chosen. In HTML output, titles

1735will appear twice: once in the document head -- this is the title that

1736will appear at the top of the window in a browser -- and once at the

1737beginning of the document body. The title in the document head can have

1738an optional prefix attached (`--title-prefix` or `-T` option). The title

1739in the body appears as an H1 element with class "title", so it can be

1740suppressed or reformatted with CSS. If a title prefix is specified with

1741`-T` and no title block appears in the document, the title prefix will

1742be used by itself as the HTML title.

1743

1744The man page writer extracts a title, man page section number, and

1745other header and footer information from the title line. The title

1746is assumed to be the first word on the title line, which may optionally

1747end with a (single-digit) section number in parentheses. (There should

1748be no space between the title and the parentheses.) Anything after

1749this is assumed to be additional footer and header text. A single pipe

1750character (`|`) should be used to separate the footer text from the header

1751text. Thus,

1752

1753 % PANDOC(1)

1754

1755will yield a man page with the title `PANDOC` and section 1.

1756

1757 % PANDOC(1) Pandoc User Manuals

1758

1759will also have "Pandoc User Manuals" in the footer.

1760

1761 % PANDOC(1) Pandoc User Manuals | Version 4.0

1762

1763will also have "Version 4.0" in the header.

1764

1765YAML metadata block

1766-------------------

1767

1768**Extension: `yaml_metadata_block`**

1769

1770A YAML metadata block is a valid YAML object, delimited by a line of three

1771hyphens (`---`) at the top and a line of three hyphens (`---`) or three dots

1772(`...`) at the bottom. A YAML metadata block may occur anywhere in the

1773document, but if it is not at the beginning, it must be preceded by a blank

1774line.

1775

1776Metadata will be taken from the fields of the YAML object and added to any

1777existing document metadata. Metadata can contain lists and objects (nested

1778arbitrarily), but all string scalars will be interpreted as markdown. Fields

1779with names ending in an underscore will be ignored by pandoc. (They may be

1780given a role by external processors.)

1781

1782A document may contain multiple metadata blocks. The metadata fields will

1783be combined through a *left-biased union*: if two metadata blocks attempt

1784to set the same field, the value from the first block will be taken.

1785

1786Note that YAML escaping rules must be followed. Thus, for example,

1787if a title contains a colon, it must be quoted. The pipe character

1788(`|`) can be used to begin an indented block that will be interpreted

1789literally, without need for escaping. This form is necessary

1790when the field contains blank lines:

1791

1792 ---

1793 title: 'This is the title: it contains a colon'

1794 author:

1795 - name: Author One

1796 affiliation: University of Somewhere

1797 - name: Author Two

1798 affiliation: University of Nowhere

1799 tags: [nothing, nothingness]

1800 abstract: |

1801 This is the abstract.

1802

1803 It consists of two paragraphs.

1804 ...

1805

1806Template variables will be set automatically from the metadata. Thus, for

1807example, in writing HTML, the variable `abstract` will be set to the HTML

1808equivalent of the markdown in the `abstract` field:

1809

1810 <p>This is the abstract.</p>

1811 <p>It consists of two paragraphs.</p>

1812

1813

1814Backslash escapes

1815-----------------

1816

1817**Extension: `all_symbols_escapable`**

1818

1819Except inside a code block or inline code, any punctuation or space

1820character preceded by a backslash will be treated literally, even if it

1821would normally indicate formatting. Thus, for example, if one writes

1822

1823 *\*hello\**

1824

1825one will get

1826

1827 <em>*hello*</em>

1828

1829instead of

1830

1831 <strong>hello</strong>

1832

1833This rule is easier to remember than standard markdown's rule,

1834which allows only the following characters to be backslash-escaped:

1835

1836 \`*_{}[]()>#+-.!

1837

1838(However, if the `markdown_strict` format is used, the standard markdown rule

1839will be used.)

1840

1841A backslash-escaped space is parsed as a nonbreaking space. It will

1842appear in TeX output as `~` and in HTML and XML as `\ ` or

1843`\ `.

1844

1845A backslash-escaped newline (i.e. a backslash occurring at the end of

1846a line) is parsed as a hard line break. It will appear in TeX output as

1847`\\` and in HTML as `<br />`. This is a nice alternative to

1848markdown's "invisible" way of indicating hard line breaks using

1849two trailing spaces on a line.

1850

1851Backslash escapes do not work in verbatim contexts.

1852

1853Smart punctuation

1854-----------------

1855

1856**Extension**

1857

1858If the `--smart` option is specified, pandoc will produce typographically

1859correct output, converting straight quotes to curly quotes, `---` to

1860em-dashes, `--` to en-dashes, and `...` to ellipses. Nonbreaking spaces

1861are inserted after certain abbreviations, such as "Mr."

1862

1863Note: if your LaTeX template uses the `csquotes` package, pandoc will

1864detect automatically this and use `\enquote{...}` for quoted text.

1865

1866Inline formatting

1867-----------------

1868

1869### Emphasis ###

1870

1871To *emphasize* some text, surround it with `*`s or `_`, like this:

1872

1873 This text is _emphasized with underscores_, and this

1874 is *emphasized with asterisks*.

1875

1876Double `*` or `_` produces **strong emphasis**:

1877

1878 This is **strong emphasis** and __with underscores__.

1879

1880A `*` or `_` character surrounded by spaces, or backslash-escaped,

1881will not trigger emphasis:

1882

1883 This is * not emphasized *, and \*neither is this\*.

1884

1885**Extension: `intraword_underscores`**

1886

1887Because `_` is sometimes used inside words and identifiers,

1888pandoc does not interpret a `_` surrounded by alphanumeric

1889characters as an emphasis marker. If you want to emphasize

1890just part of a word, use `*`:

1891

1892 feas*ible*, not feas*able*.

1893

1894

1895### Strikeout ###

1896

1897**Extension: `strikeout`**

1898

1899To strikeout a section of text with a horizontal line, begin and end it

1900with `~~`. Thus, for example,

1901

1902 This ~~is deleted text.~~

1903

1904

1905### Superscripts and subscripts ###

1906

1907**Extension: `superscript`, `subscript`**

1908

1909Superscripts may be written by surrounding the superscripted text by `^`

1910characters; subscripts may be written by surrounding the subscripted

1911text by `~` characters. Thus, for example,

1912

1913 H~2~O is a liquid. 2^10^ is 1024.

1914

1915If the superscripted or subscripted text contains spaces, these spaces

1916must be escaped with backslashes. (This is to prevent accidental

1917superscripting and subscripting through the ordinary use of `~` and `^`.)

1918Thus, if you want the letter P with 'a cat' in subscripts, use

1919`P~a\ cat~`, not `P~a cat~`.

1920

1921

1922### Verbatim ###

1923

1924To make a short span of text verbatim, put it inside backticks:

1925

1926 What is the difference between `>>=` and `>>`?

1927

1928If the verbatim text includes a backtick, use double backticks:

1929

1930 Here is a literal backtick `` ` ``.

1931

1932(The spaces after the opening backticks and before the closing

1933backticks will be ignored.)

1934

1935The general rule is that a verbatim span starts with a string

1936of consecutive backticks (optionally followed by a space)

1937and ends with a string of the same number of backticks (optionally

1938preceded by a space).

1939

1940Note that backslash-escapes (and other markdown constructs) do not

1941work in verbatim contexts:

1942

1943 This is a backslash followed by an asterisk: `\*`.

1944

1945**Extension: `inline_code_attributes`**

1946

1947Attributes can be attached to verbatim text, just as with

1948[fenced code blocks](#fenced-code-blocks):

1949

1950 `<$>`{.haskell}

1951

1952Math

1953----

1954

1955**Extension: `tex_math_dollars`**

1956

1957Anything between two `$` characters will be treated as TeX math. The

1958opening `$` must have a character immediately to its right, while the

1959closing `$` must have a character immediately to its left. Thus,

1960`$20,000 and $30,000` won't parse as math. If for some reason

1961you need to enclose text in literal `$` characters, backslash-escape

1962them and they won't be treated as math delimiters.

1963

1964TeX math will be printed in all output formats. How it is rendered

1965depends on the output format:

1966

1967Markdown, LaTeX, Org-Mode, ConTeXt

1968 ~ It will appear verbatim between `$` characters.

1969

1970reStructuredText

1971 ~ It will be rendered using an interpreted text role `:math:`, as described

1972 [here](http://www.american.edu/econ/itex2mml/mathhack.rst).

1973

1974AsciiDoc

1975 ~ It will be rendered as `latexmath:[...]`.

1976

1977Texinfo

1978 ~ It will be rendered inside a `@math` command.

1979

1980groff man

1981 ~ It will be rendered verbatim without `$`'s.

1982

1983MediaWiki

1984 ~ It will be rendered inside `<math>` tags.

1985

1986Textile

1987 ~ It will be rendered inside `<span class="math">` tags.

1988

1989RTF, OpenDocument, ODT

1990 ~ It will be rendered, if possible, using unicode characters,

1991 and will otherwise appear verbatim.

1992

1993Docbook

1994 ~ If the `--mathml` flag is used, it will be rendered using mathml

1995 in an `inlineequation` or `informalequation` tag. Otherwise it

1996 will be rendered, if possible, using unicode characters.

1997

1998Docx

1999 ~ It will be rendered using OMML math markup.

2000

2001FictionBook2

2002 ~ If the `--webtex` option is used, formulas are rendered as images

2003 using Google Charts or other compatible web service, downloaded

2004 and embedded in the e-book. Otherwise, they will appear verbatim.

2005

2006HTML, Slidy, DZSlides, S5, EPUB

2007 ~ The way math is rendered in HTML will depend on the

2008 command-line options selected:

2009

2010 1. The default is to render TeX math as far as possible using unicode

2011 characters, as with RTF, DocBook, and OpenDocument output. Formulas

2012 are put inside a `span` with `class="math"`, so that they may be

2013 styled differently from the surrounding text if needed.

2014

2015 2. If the `--latexmathml` option is used, TeX math will be displayed

2016 between `$` or `$$` characters and put in `<span>` tags with class `LaTeX`.

2017 The [LaTeXMathML] script will be used to render it as formulas.

2018 (This trick does not work in all browsers, but it works in Firefox.

2019 In browsers that do not support LaTeXMathML, TeX math will appear

2020 verbatim between `$` characters.)

2021

2022 3. If the `--jsmath` option is used, TeX math will be put inside

2023 `<span>` tags (for inline math) or `<div>` tags (for display math)

2024 with class `math`. The [jsMath] script will be used to render

2025 it.

2026

2027 4. If the `--mimetex` option is used, the [mimeTeX] CGI script will

2028 be called to generate images for each TeX formula. This should

2029 work in all browsers. The `--mimetex` option takes an optional URL

2030 as argument. If no URL is specified, it will be assumed that the

2031 mimeTeX CGI script is at `/cgi-bin/mimetex.cgi`.

2032

2033 5. If the `--gladtex` option is used, TeX formulas will be enclosed

2034 in `<eq>` tags in the HTML output. The resulting `htex` file may then

2035 be processed by [gladTeX], which will produce image files for each

2036 formula and an `html` file with links to these images. So, the

2037 procedure is:

2038

2039 pandoc -s --gladtex myfile.txt -o myfile.htex

2040 gladtex -d myfile-images myfile.htex

2041 # produces myfile.html and images in myfile-images

2042

2043 6. If the `--webtex` option is used, TeX formulas will be converted

2044 to `<img>` tags that link to an external script that converts

2045 formulas to images. The formula will be URL-encoded and concatenated

2046 with the URL provided. If no URL is specified, the Google Chart

2047 API will be used (`http://chart.apis.google.com/chart?cht=tx&chl=`).

2048

2049 7. If the `--mathjax` option is used, TeX math will be displayed

2050 between `$...$` (for inline math) or `\[...\]` (for display

2051 math) and put in `<span>` tags with class `math`.

2052 The [MathJax] script will be used to render it as formulas.

2053

2054Raw HTML

2055--------

2056

2057**Extension: `raw_html`**

2058

2059Markdown allows you to insert raw HTML (or DocBook) anywhere in a document

2060(except verbatim contexts, where `<`, `>`, and `&` are interpreted

2061literally). (Techncially this is not an extension, since standard

2062markdown allows it, but it has been made an extension so that it can

2063be disabled if desired.)

2064

2065The raw HTML is passed through unchanged in HTML, S5, Slidy, Slideous,

2066DZSlides, EPUB, Markdown, and Textile output, and suppressed in other

2067formats.

2068

2069**Extension: `markdown_in_html_blocks`**

2070

2071Standard markdown allows you to include HTML "blocks": blocks

2072of HTML between balanced tags that are separated from the surrounding text

2073with blank lines, and start and end at the left margin. Within

2074these blocks, everything is interpreted as HTML, not markdown;

2075so (for example), `*` does not signify emphasis.

2076

2077Pandoc behaves this way when the `markdown_strict` format is used; but

2078by default, pandoc interprets material between HTML block tags as markdown.

2079Thus, for example, Pandoc will turn

2080

2081 <table>

2082 <tr>

2083 <td>*one*</td>

2084 <td>[a link](http://google.com)</td>

2085 </tr>

2086 </table>

2087

2088into

2089

2090 <table>

2091 <tr>

2092 <td><em>one</em></td>

2093 <td><a href="http://google.com">a link</a></td>

2094 </tr>

2095 </table>

2096

2097whereas `Markdown.pl` will preserve it as is.

2098

2099There is one exception to this rule: text between `<script>` and

2100`<style>` tags is not interpreted as markdown.

2101

2102This departure from standard markdown should make it easier to mix

2103markdown with HTML block elements. For example, one can surround

2104a block of markdown text with `<div>` tags without preventing it

2105from being interpreted as markdown.

2106

2107Raw TeX

2108-------

2109

2110**Extension: `raw_tex`**

2111

2112In addition to raw HTML, pandoc allows raw LaTeX, TeX, and ConTeXt to be

2113included in a document. Inline TeX commands will be preserved and passed

2114unchanged to the LaTeX and ConTeXt writers. Thus, for example, you can use

2115LaTeX to include BibTeX citations:

2116

2117 This result was proved in \cite{jones.1967}.

2118

2119Note that in LaTeX environments, like

2120

2121 \begin{tabular}{|l|l|}\hline

2122 Age & Frequency \\ \hline

2123 18--25 & 15 \\

2124 26--35 & 33 \\

2125 36--45 & 22 \\ \hline

2126 \end{tabular}

2127

2128the material between the begin and end tags will be interpreted as raw

2129LaTeX, not as markdown.

2130

2131Inline LaTeX is ignored in output formats other than Markdown, LaTeX,

2132and ConTeXt.

2133

2134LaTeX macros

2135------------

2136

2137**Extension: `latex_macros`**

2138

2139For output formats other than LaTeX, pandoc will parse LaTeX `\newcommand` and

2140`\renewcommand` definitions and apply the resulting macros to all LaTeX

2141math. So, for example, the following will work in all output formats,

2142not just LaTeX:

2143

2144 \newcommand{\tuple}[1]{\langle #1 \rangle}

2145

2146 $\tuple{a, b, c}$

2147

2148In LaTeX output, the `\newcommand` definition will simply be passed

2149unchanged to the output.

2150

2151

2152Links

2153-----

2154

2155Markdown allows links to be specified in several ways.

2156

2157### Automatic links ###

2158

2159If you enclose a URL or email address in pointy brackets, it

2160will become a link:

2161

2162 <http://google.com>

2163 <sam@green.eggs.ham>

2164

2165### Inline links ###

2166

2167An inline link consists of the link text in square brackets,

2168followed by the URL in parentheses. (Optionally, the URL can

2169be followed by a link title, in quotes.)

2170

2171 This is an [inline link](/url), and here's [one with

2172 a title](http://fsf.org "click here for a good time!").

2173

2174There can be no space between the bracketed part and the parenthesized part.

2175The link text can contain formatting (such as emphasis), but the title cannot.

2176

2177

2178### Reference links ###

2179

2180An *explicit* reference link has two parts, the link itself and the link

2181definition, which may occur elsewhere in the document (either

2182before or after the link).

2183

2184The link consists of link text in square brackets, followed by a label in

2185square brackets. (There can be space between the two.) The link definition

2186consists of the bracketed label, followed by a colon and a space, followed by

2187the URL, and optionally (after a space) a link title either in quotes or in

2188parentheses.

2189

2190Here are some examples:

2191

2192 [my label 1]: /foo/bar.html "My title, optional"

2193 [my label 2]: /foo

2194 [my label 3]: http://fsf.org (The free software foundation)

2195 [my label 4]: /bar#special 'A title in single quotes'

2196

2197The URL may optionally be surrounded by angle brackets:

2198

2199 [my label 5]: <http://foo.bar.baz>

2200

2201The title may go on the next line:

2202

2203 [my label 3]: http://fsf.org

2204 "The free software foundation"

2205

2206Note that link labels are not case sensitive. So, this will work:

2207

2208 Here is [my link][FOO]

2209

2210 [Foo]: /bar/baz

2211

2212In an *implicit* reference link, the second pair of brackets is

2213empty, or omitted entirely:

2214

2215 See [my website][], or [my website].

2216

2217 [my website]: http://foo.bar.baz

2218

2219Note: In `Markdown.pl` and most other markdown implementations,

2220reference link definitions cannot occur in nested constructions

2221such as list items or block quotes. Pandoc lifts this arbitrary

2222seeming restriction. So the following is fine in pandoc, though

2223not in most other implementations:

2224

2225 > My block [quote].

2226 >

2227 > [quote]: /foo

2228

2229### Internal links

2230

2231To link to another section of the same document, use the automatically

2232generated identifier (see [Header identifiers in HTML, LaTeX, and

2233ConTeXt](#header-identifiers-in-html-latex-and-context), below).

2234For example:

2235

2236 See the [Introduction](#introduction).

2237

2238or

2239

2240 See the [Introduction].

2241

2242 [Introduction]: #introduction

2243

2244Internal links are currently supported for HTML formats (including

2245HTML slide shows and EPUB), LaTeX, and ConTeXt.

2246

2247Images

2248------

2249

2250A link immediately preceded by a `!` will be treated as an image.

2251The link text will be used as the image's alt text:

2252

2253 ![la lune](lalune.jpg "Voyage to the moon")

2254

2255 ![movie reel]

2256

2257 [movie reel]: movie.gif

2258

2259### Pictures with captions ###

2260

2261**Extension: `implicit_figures`**

2262

2263An image occurring by itself in a paragraph will be rendered as

2264a figure with a caption.[^5] (In LaTeX, a figure environment will be

2265used; in HTML, the image will be placed in a `div` with class

2266`figure`, together with a caption in a `p` with class `caption`.)

2267The image's alt text will be used as the caption.

2268

2269 ![This is the caption](/url/of/image.png)

2270

2271[^5]: This feature is not yet implemented for RTF, OpenDocument, or

2272 ODT. In those formats, you'll just get an image in a paragraph by

2273 itself, with no caption.

2274

2275If you just want a regular inline image, just make sure it is not

2276the only thing in the paragraph. One way to do this is to insert a

2277nonbreaking space after the image:

2278

2279 ![This image won't be a figure](/url/of/image.png)\

2280

2281

2282Footnotes

2283---------

2284

2285**Extension: `footnotes`**

2286

2287Pandoc's markdown allows footnotes, using the following syntax:

2288

2289 Here is a footnote reference,[^1] and another.[^longnote]

2290

2291 [^1]: Here is the footnote.

2292

2293 [^longnote]: Here's one with multiple blocks.

2294

2295 Subsequent paragraphs are indented to show that they

2296 belong to the previous footnote.

2297

2298 { some.code }

2299

2300 The whole paragraph can be indented, or just the first

2301 line. In this way, multi-paragraph footnotes work like

2302 multi-paragraph list items.

2303

2304 This paragraph won't be part of the note, because it

2305 isn't indented.

2306

2307The identifiers in footnote references may not contain spaces, tabs,

2308or newlines. These identifiers are used only to correlate the

2309footnote reference with the note itself; in the output, footnotes

2310will be numbered sequentially.

2311

2312The footnotes themselves need not be placed at the end of the

2313document. They may appear anywhere except inside other block elements

2314(lists, block quotes, tables, etc.).

2315

2316**Extension: `inline_notes`**

2317

2318Inline footnotes are also allowed (though, unlike regular notes,

2319they cannot contain multiple paragraphs). The syntax is as follows:

2320

2321 Here is an inline note.^[Inlines notes are easier to write, since

2322 you don't have to pick an identifier and move down to type the

2323 note.]

2324

2325Inline and regular footnotes may be mixed freely.

2326

2327

2328Citations

2329---------

2330

2331**Extension: `citations`**

2332

2333Using an external filter, `pandoc-citeproc`, pandoc can automatically generate

2334citations and a bibliography in a number of styles. Basic usage is

2335

2336 pandoc --filter pandoc-citeproc myinput.txt

2337

2338In order to use this feature, you will need to specify a bibliography file

2339using the `bibliography` metadata field in a YAML metadata section.

2340The bibliography may have any of these formats:

2341

2342 Format File extension

2343 ------------ --------------

2344 MODS .mods

2345 BibLaTeX .bib

2346 BibTeX .bibtex

2347 RIS .ris

2348 EndNote .enl

2349 EndNote XML .xml

2350 ISI .wos

2351 MEDLINE .medline

2352 Copac .copac

2353 JSON citeproc .json

2354

2355Note that `.bib` can generally be used with both BibTeX and BibLaTeX

2356files, but you can use `.bibtex` to force BibTeX.

2357

2358Alternatively you can use a `references` field in the document's YAML

2359metadata. This should include an array of YAML-encoded references,

2360for example:

2361

2362 ---

2363 references:

2364 - id: fenner2012a

2365 title: One-click science marketing

2366 author:

2367 - family: Fenner

2368 given: Martin

2369 container-title: Nature Materials

2370 volume: 11

2371 URL: 'http://dx.doi.org/10.1038/nmat3283'

2372 DOI: 10.1038/nmat3283

2373 issue: 4

2374 publisher: Nature Publishing Group

2375 page: 261-263

2376 type: article-journal

2377 issued:

2378 year: 2012

2379 month: 3

2380 ...

2381

2382(The program `mods2yaml`, which comes with `pandoc-citeproc`, can help produce

2383these from a MODS reference collection.)

2384

2385By default, `pandoc-citeproc` will use a Chicago author-date format for

2386citations and references. To use another style, you will need to specify

2387a [CSL] 1.0 style file in the `csl` metadata field. A primer on creating and

2388modifying CSL styles can be found at

2389<http://citationstyles.org/downloads/primer.html>. A repository of CSL styles

2390can be found at <https://github.com/citation-style-language/styles>. See also

2391<http://zotero.org/styles> for easy browsing.

2392

2393Citations go inside square brackets and are separated by semicolons.

2394Each citation must have a key, composed of '@' + the citation

2395identifier from the database, and may optionally have a prefix,

2396a locator, and a suffix. Here are some examples:

2397

2398 Blah blah [see @doe99, pp. 33-35; also @smith04, ch. 1].

2399

2400 Blah blah [@doe99, pp. 33-35, 38-39 and *passim*].

2401

2402 Blah blah [@smith04; @doe99].

2403

2404A minus sign (`-`) before the `@` will suppress mention of

2405the author in the citation. This can be useful when the

2406author is already mentioned in the text:

2407

2408 Smith says blah [-@smith04].

2409

2410You can also write an in-text citation, as follows:

2411

2412 @smith04 says blah.

2413

2414 @smith04 [p. 33] says blah.

2415

2416If the style calls for a list of works cited, it will be placed

2417at the end of the document. Normally, you will want to end your

2418document with an appropriate header:

2419

2420 last paragraph...

2421

2422 # References

2423

2424The bibliography will be inserted after this header.

2425

2426Non-pandoc extensions

2427---------------------

2428

2429The following markdown syntax extensions are not enabled by default

2430in pandoc, but may be enabled by adding `+EXTENSION` to the format

2431name, where `EXTENSION` is the name of the extension. Thus, for

2432example, `markdown+hard_line_breaks` is markdown with hard line breaks.

2433

2434**Extension: `hard_line_breaks`**\

2435Causes all newlines within a paragraph to be interpreted as hard line

2436breaks instead of spaces.

2437

2438**Extension: `ignore_line_breaks`**\

2439Causes newlines within a paragraph to be ignored, rather than being

2440treated as spaces or as hard line breaks. This option is intended for

2441use with East Asian languages where spaces are not used between words,

2442but text is divided into lines for readability.

2443

2444**Extension: `tex_math_single_backslash`**\

2445Causes anything between `$` and `$` to be interpreted as inline

2446TeX math, and anything between `\[` and `\]` to be interpreted

2447as display TeX math. Note: a drawback of this extension is that

2448it precludes escaping `(` and `[`.

2449

2450**Extension: `tex_math_double_backslash`**\

2451Causes anything between `\$` and `\$` to be interpreted as inline

2452TeX math, and anything between `\\[` and `\\]` to be interpreted

2453as display TeX math.

2454

2455**Extension: `markdown_attribute`**\

2456By default, pandoc interprets material inside block-level tags as markdown.

2457This extension changes the behavior so that markdown is only parsed

2458inside block-level tags if the tags have the attribute `markdown=1`.

2459

2460**Extension: `mmd_title_block`**\

2461Enables a [MultiMarkdown] style title block at the top of

2462the document, for example:

2463

2464 Title: My title

2465 Author: John Doe

2466 Date: September 1, 2008

2467 Comment: This is a sample mmd title block, with

2468 a field spanning multiple lines.

2469

2470See the MultiMarkdown documentation for details. Note that only title,

2471author, and date are recognized; other fields are simply ignored by

2472pandoc. If `pandoc_title_block` or `yaml_metadata_block` is enabled,

2473it will take precedence over `mmd_title_block`.

2474

2475 [MultiMarkdown]: http://fletcherpenney.net/multimarkdown/

2476

2477**Extension: `abbreviations`**\

2478Parses PHP Markdown Extra abbreviation keys, like

2479

2480 *[HTML]: Hyper Text Markup Language

2481

2482Note that the pandoc document model does not support

2483abbreviations, so if this extension is enabled, abbreviation keys are

2484simply skipped (as opposed to being parsed as paragraphs).

2485

2486**Extension: `autolink_bare_uris`**\

2487Makes all absolute URIs into links, even when not surrounded by

2488pointy braces `<...>`.

2489

2490**Extension: `ascii_identifiers`**\

2491Causes the identifiers produced by `auto_identifiers` to be pure ASCII.

2492Accents are stripped off of accented latin letters, and non-latin

2493letters are omitted.

2494

2495**Extension: `link_attributes`**\

2496Parses multimarkdown style key-value attributes on link and image references.

2497Note that pandoc's internal document model provides nowhere to put

2498these, so they are presently just ignored.

2499

2500**Extension: `mmd_header_identifiers`**\

2501Parses multimarkdown style header identifiers (in square brackets,

2502after the header but before any trailing `#`s in an ATX header).

2503

2504Markdown variants

2505-----------------

2506

2507In addition to pandoc's extended markdown, the following markdown

2508variants are supported:

2509

2510`markdown_phpextra` (PHP Markdown Extra)

2511: `footnotes`, `pipe_tables`, `raw_html`, `markdown_attribute`,

2512 `fenced_code_blocks`, `definition_lists`, `intraword_underscores`,

2513 `header_attributes`, `abbreviations`.

2514

2515`markdown_github` (Github-flavored Markdown)

2516: `pipe_tables`, `raw_html`, `tex_math_single_backslash`,

2517 `fenced_code_blocks`, `fenced_code_attributes`, `auto_identifiers`,

2518 `ascii_identifiers`, `backtick_code_blocks`, `autolink_bare_uris`,

2519 `intraword_underscores`, `strikeout`, `hard_line_breaks`

2520

2521`markdown_mmd` (MultiMarkdown)

2522: `pipe_tables` `raw_html`, `markdown_attribute`, `link_attributes`,

2523 `raw_tex`, `tex_math_double_backslash`, `intraword_underscores`,

2524 `mmd_title_block`, `footnotes`, `definition_lists`,

2525 `all_symbols_escapable`, `implicit_header_references`,

2526 `auto_identifiers`, `mmd_header_identifiers`

2527

2528`markdown_strict` (Markdown.pl)

2529: `raw_html`

2530

2531Producing slide shows with Pandoc

2532=================================

2533

2534You can use Pandoc to produce an HTML + javascript slide presentation

2535that can be viewed via a web browser. There are five ways to do this,

2536using [S5], [DZSlides], [Slidy], [Slideous], or [reveal.js].

2537You can also produce a PDF slide show using LaTeX [beamer].

2538

2539Here's the markdown source for a simple slide show, `habits.txt`:

2540

2541 % Habits

2542 % John Doe

2543 % March 22, 2005

2544

2545 # In the morning

2546

2547 ## Getting up

2548

2549 - Turn off alarm

2550 - Get out of bed

2551

2552 ## Breakfast

2553

2554 - Eat eggs

2555 - Drink coffee

2556

2557 # In the evening

2558

2559 ## Dinner

2560

2561 - Eat spaghetti

2562 - Drink wine

2563

2564 ------------------

2565

2566 ![picture of spaghetti](images/spaghetti.jpg)

2567

2568 ## Going to sleep

2569

2570 - Get in bed

2571 - Count sheep

2572

2573To produce an HTML/javascript slide show, simply type

2574

2575 pandoc -t FORMAT -s habits.txt -o habits.html

2576

2577where `FORMAT` is either `s5`, `slidy`, `slideous`, `dzslides`, or `revealjs`.

2578

2579For Slidy, Slideous, reveal.js, and S5, the file produced by pandoc with the

2580`-s/--standalone` option embeds a link to javascripts and CSS files, which are

2581assumed to be available at the relative path `s5/default` (for S5), `slideous`

2582(for Slideous), `reveal.js` (for reveal.js), or at the Slidy website at

2583`w3.org` (for Slidy). (These paths can be changed by setting the `slidy-url`,

2584`slideous-url`, `revealjs-url`, or `s5-url` variables; see `--variable`,

2585above.) For DZSlides, the (relatively short) javascript and css are included in

2586the file by default.

2587

2588With all HTML slide formats, the `--self-contained` option can be used to

2589produce a single file that contains all of the data necessary to display the

2590slide show, including linked scripts, stylesheets, images, and videos.

2591

2592To produce a PDF slide show using beamer, type

2593

2594 pandoc -t beamer habits.txt -o habits.pdf

2595

2596Note that a reveal.js slide show can also be converted to a PDF

2597by printing it to a file from the browser.

2598

2599Structuring the slide show

2600--------------------------

2601

2602By default, the *slide level* is the highest header level in

2603the hierarchy that is followed immediately by content, and not another

2604header, somewhere in the document. In the example above, level 1 headers

2605are always followed by level 2 headers, which are followed by content,

2606so 2 is the slide level. This default can be overridden using

2607the `--slide-level` option.

2608

2609The document is carved up into slides according to the following

2610rules:

2611

2612 * A horizontal rule always starts a new slide.

2613

2614 * A header at the slide level always starts a new slide.

2615

2616 * Headers *below* the slide level in the hierarchy create

2617 headers *within* a slide.

2618

2619 * Headers *above* the slide level in the hierarchy create

2620 "title slides," which just contain the section title

2621 and help to break the slide show into sections.

2622

2623 * A title page is constructed automatically from the document's title

2624 block, if present. (In the case of beamer, this can be disabled

2625 by commenting out some lines in the default template.)

2626

2627These rules are designed to support many different styles of slide show. If

2628you don't care about structuring your slides into sections and subsections,

2629you can just use level 1 headers for all each slide. (In that case, level 1

2630will be the slide level.) But you can also structure the slide show into

2631sections, as in the example above.

2632

2633Note: in reveal.js slide shows, if slide level is 2, a two-dimensional

2634layout will be produced, with level 1 headers building horizontally

2635and level 2 headers building vertically. It is not recommended that

2636you use deeper nesting of section levels with reveal.js.

2637

2638Incremental lists

2639-----------------

2640

2641By default, these writers produces lists that display "all at once."

2642If you want your lists to display incrementally (one item at a time),

2643use the `-i` option. If you want a particular list to depart from the

2644default (that is, to display incrementally without the `-i` option and

2645all at once with the `-i` option), put it in a block quote:

2646

2647 > - Eat spaghetti

2648 > - Drink wine

2649

2650In this way incremental and nonincremental lists can be mixed in

2651a single document.

2652

2653Inserting pauses

2654----------------

2655

2656In reveal.js and beamer slide shows, you can add "pauses" within

2657a slide by including a paragraph containing three dots, separated

2658by spaces:

2659

2660 # Slide with a pause

2661

2662 content before the pause

2663

2664 . . .

2665

2666 content after the pause

2667

2668Styling the slides

2669------------------

2670

2671You can change the style of HTML slides by putting customized CSS files

2672in `$DATADIR/s5/default` (for S5), `$DATADIR/slidy` (for Slidy),

2673or `$DATADIR/slideous` (for Slideous),

2674where `$DATADIR` is the user data directory (see `--data-dir`, above).

2675The originals may be found in pandoc's system data directory (generally

2676`$CABALDIR/pandoc-VERSION/s5/default`). Pandoc will look there for any

2677files it does not find in the user data directory.

2678

2679For dzslides, the CSS is included in the HTML file itself, and may

2680be modified there.

2681

2682For reveal.js, themes can be used by setting the `theme` variable,

2683for example:

2684

2685 -V theme=moon

2686

2687Or you can specify a custom stylesheet using the `--css` option.

2688

2689To style beamer slides, you can specify a beamer "theme" or "colortheme"

2690using the `-V` option:

2691

2692 pandoc -t beamer habits.txt -V theme:Warsaw -o habits.pdf

2693

2694Note that header attributes will turn into slide attributes

2695(on a `<div>` or `<section>`) in HTML slide formats, allowing you

2696to style individual slides. In Beamer, the only header attribute

2697that affects slides is the `allowframebreaks` class, which sets the

2698`allowframebreaks` option, causing multiple slides to be created

2699if the content overfills the frame. This is recommended especially for

2700bibliographies:

2701

2702 # References {.allowframebreaks}

2703

2704Literate Haskell support

2705========================

2706

2707If you append `+lhs` (or `+literate_haskell`) to an appropriate input or output

2708format (`markdown`, `mardkown_strict`, `rst`, or `latex` for input or output;

2709`beamer`, `html` or `html5` for output only), pandoc will treat the document as

2710literate Haskell source. This means that

2711

2712 - In markdown input, "bird track" sections will be parsed as Haskell

2713 code rather than block quotations. Text between `\begin{code}`

2714 and `\end{code}` will also be treated as Haskell code.

2715

2716 - In markdown output, code blocks with classes `haskell` and `literate`

2717 will be rendered using bird tracks, and block quotations will be

2718 indented one space, so they will not be treated as Haskell code.

2719 In addition, headers will be rendered setext-style (with underlines)

2720 rather than atx-style (with '#' characters). (This is because ghc

2721 treats '#' characters in column 1 as introducing line numbers.)

2722

2723 - In restructured text input, "bird track" sections will be parsed

2724 as Haskell code.

2725

2726 - In restructured text output, code blocks with class `haskell` will

2727 be rendered using bird tracks.

2728

2729 - In LaTeX input, text in `code` environments will be parsed as

2730 Haskell code.

2731

2732 - In LaTeX output, code blocks with class `haskell` will be rendered

2733 inside `code` environments.

2734

2735 - In HTML output, code blocks with class `haskell` will be rendered

2736 with class `literatehaskell` and bird tracks.

2737

2738Examples:

2739

2740 pandoc -f markdown+lhs -t html

2741

2742reads literate Haskell source formatted with markdown conventions and writes

2743ordinary HTML (without bird tracks).

2744

2745 pandoc -f markdown+lhs -t html+lhs

2746

2747writes HTML with the Haskell code in bird tracks, so it can be copied

2748and pasted as literate Haskell source.

2749

2750Custom writers

2751==============

2752

2753Pandoc can be extended with custom writers written in [lua]. (Pandoc

2754includes a lua interpreter, so lua need not be installed separately.)

2755

2756To use a custom writer, simply specify the path to the lua script

2757in place of the output format. For example:

2758

2759 pandoc -t data/sample.lua

2760

2761Creating a custom writer requires writing a lua function for each

2762possible element in a pandoc document. To get a documented example

2763which you can modify according to your needs, do

2764

2765 pandoc --print-default-data-file sample.lua

2766

2767Authors

2768=======

2769

2771[GPL], version 2 or greater. This software carries no warranty of

2772any kind. (See COPYRIGHT for full copyright and warranty notices.)

2773Other contributors include Recai Oktaş, Paulo Tanimoto, Peter Wang,

2774Andrea Rossato, Eric Kow, infinity0x, Luke Plant, shreevatsa.public,

2775Puneeth Chaganti, Paul Rivier, rodja.trappe, Bradley Kuhn, thsutton,

2776Nathan Gass, Jonathan Daugherty, Jérémy Bobbio, Justin Bogner, qerub,

2777Christopher Sawicki, Kelsey Hightower, Masayoshi Takahashi, Antoine

2778Latter, Ralf Stephan, Eric Seidel, B. Scott Michel, Gavin Beatty,

2779Sergey Astanin, Arlo O'Keeffe, Denis Laxalde, Brent Yorgey, David Lazar,

2780Jamie F. Olson.

2781

2782[markdown]: http://daringfireball.net/projects/markdown/

2783[reStructuredText]: http://docutils.sourceforge.net/docs/ref/rst/introduction.html

2784[S5]: http://meyerweb.com/eric/tools/s5/

2785[Slidy]: http://www.w3.org/Talks/Tools/Slidy/

2786[Slideous]: http://goessner.net/articles/slideous/

2787[HTML]: http://www.w3.org/TR/html40/

2788[HTML 5]: http://www.w3.org/TR/html5/

2789[XHTML]: http://www.w3.org/TR/xhtml1/

2790[LaTeX]: http://www.latex-project.org/

2791[beamer]: http://www.tex.ac.uk/CTAN/macros/latex/contrib/beamer

2792[ConTeXt]: http://www.pragma-ade.nl/

2793[RTF]: http://en.wikipedia.org/wiki/Rich_Text_Format

2794[DocBook]: http://www.docbook.org/

2795[OPML]: http://dev.opml.org/spec2.html

2796[OpenDocument]: http://opendocument.xml.org/

2797[ODT]: http://en.wikipedia.org/wiki/OpenDocument

2798[Textile]: http://redcloth.org/textile

2799[MediaWiki markup]: http://www.mediawiki.org/wiki/Help:Formatting

2800[Haddock markup]: http://www.haskell.org/haddock/doc/html/ch03s08.html

2801[groff man]: http://developer.apple.com/DOCUMENTATION/Darwin/Reference/ManPages/man7/groff_man.7.html

2802[Haskell]: http://www.haskell.org/

2803[GNU Texinfo]: http://www.gnu.org/software/texinfo/

2804[Emacs Org-Mode]: http://orgmode.org

2805[AsciiDoc]: http://www.methods.co.nz/asciidoc/

2806[EPUB]: http://www.idpf.org/

2807[GPL]: http://www.gnu.org/copyleft/gpl.html "GNU General Public License"

2808[DZSlides]: http://paulrouget.com/dzslides/

2809[ISO 8601 format]: http://www.w3.org/TR/NOTE-datetime

2810[Word docx]: http://www.microsoft.com/interop/openup/openxml/default.aspx

2811[PDF]: http://www.adobe.com/pdf/

2812[reveal.js]: http://lab.hakim.se/reveal-js/

2813[FictionBook2]: http://www.fictionbook.org/index.php/Eng:XML_Schema_Fictionbook_2.1

2814[lua]: TODO

2815