README · typeable/pandoc

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

1426

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

1428

1429

1430### Numbered example lists ###

1431

1432**Extension: `example_lists`**

1433

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

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

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

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

1438where the last stopped. So, for example:

1439

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

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

1442

1443 Explanation of examples.

1444

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

1446

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

1448document:

1449

1450 (@good) This is a good example.

1451

1452 As (@good) illustrates, ...

1453

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

1455or hyphens.

1456

1457

1458### Compact and loose lists ###

1459

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

1461cases" involving lists. Consider this source:

1462

1463 + First

1464 + Second:

1465 - Fee

1466 - Fie

1467 - Foe

1468

1469 + Third

1470

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

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

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

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

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

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

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

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

1479behavior is consistent with the official markdown syntax description,

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

1481

1482

1483### Ending a list ###

1484

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

1486

1487 - item one

1488 - item two

1489

1490 { my code block }

1491

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

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

1494a code block.

1495

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

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

1498any format:

1499

1500 - item one

1501 - item two

1502

1503

1504

1505 { my code block }

1506

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

1508of one big list:

1509

1510 1. one

1511 2. two

1512 3. three

1513

1514

1515

1516 1. uno

1517 2. dos

1518 3. tres

1519

1520Horizontal rules

1521----------------

1522

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

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

1526 * * * *

1528 ---------------

1531Tables

1532------

1533

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

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

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

1537

1538### Simple tables

1539

1540**Extension: `simple_tables`, `table_captions`**

1541

1542Simple tables look like this:

1543

1544 Right Left Center Default

1545 ------- ------ ---------- -------

1546 12 12 12 12

1547 123 123 123 123

1548 1 1 1 1

1549

1550 Table: Demonstration of simple table syntax.

1551

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

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

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

1555

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

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

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

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

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

1561 the column is centered.

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

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

1564

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

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

1567

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

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

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

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

1572before or after the table.

1573

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

1575to end the table. For example:

1576

1577 ------- ------ ---------- -------

1578 12 12 12 12

1579 123 123 123 123

1580 1 1 1 1

1581 ------- ------ ---------- -------

1582

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

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

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

1586

1587### Multiline tables

1588

1589**Extension: `multiline_tables`, `table_captions`**

1590

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

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

1593not supported). Here is an example:

1594

1595 -------------------------------------------------------------

1596 Centered Default Right Left

1597 Header Aligned Aligned Aligned

1598 ----------- ------- --------------- -------------------------

1599 First row 12.0 Example of a row that

1600 spans multiple lines.

1601

1602 Second row 5.0 Here's another one. Note

1603 the blank line between

1604 rows.

1605 -------------------------------------------------------------

1606

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

1608 multiple lines.

1609

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

1611

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

1613 (unless the headers are omitted).

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

1615 - The rows must be separated by blank lines.

1616

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

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

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

1620output, try widening it in the markdown source.

1621

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

1623

1624 ----------- ------- --------------- -------------------------

1625 First row 12.0 Example of a row that

1626 spans multiple lines.

1627

1628 Second row 5.0 Here's another one. Note

1629 the blank line between

1630 rows.

1631 ----------- ------- --------------- -------------------------

1632

1633 : Here's a multiline table without headers.

1634

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

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

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

1638

1639### Grid tables

1640

1641**Extension: `grid_tables`, `table_captions`**

1642

1643Grid tables look like this:

1644

1645 : Sample grid table.

1646

1647 +---------------+---------------+--------------------+

1648 | Fruit | Price | Advantages |

1649 +===============+===============+====================+

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

1651 | | | - bright color |

1652 +---------------+---------------+--------------------+

1653 | Oranges | $2.10 | - cures scurvy |

1654 | | | - tasty |

1655 +---------------+---------------+--------------------+

1656

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

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

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

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

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

1662

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

1664

1665### Pipe tables

1666

1667**Extension: `pipe_tables`, `table_captions`**

1668

1669Pipe tables look like this:

1670

1672 |------:|:-----|---------|:------:|

1673 | 12 | 12 | 12 | 12 |

1674 | 123 | 123 | 123 | 123 |

1675 | 1 | 1 | 1 | 1 |

1676

1677 : Demonstration of simple table syntax.

1678

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

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

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

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

1683it defines column alignments.

1684

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

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

1687legal (though ugly) pipe table:

1688

1689 fruit| price

1690 -----|-----:

1691 apple|2.05

1692 pear|1.37

1693 orange|3.09

1694

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

1696and lists, and cannot span multiple lines.

1697

1698 [the same as in PHP markdown extra]:

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

1700

1701Note: Pandoc also recognizes pipe tables of the following

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

1703

1704 | One | Two |

1705 |-----+-------|

1706 | my | table |

1707 | is | nice |

1708

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

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

1711you'll need to add colons as above.

1712

1713Title block

1714-----------

1715

1716**Extension: `pandoc_title_block`**

1717

1718If the file begins with a title block

1719

1720 % title

1721 % author(s) (separated by semicolons)

1722 % date

1723

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

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

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

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

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

1729

1730 %

1731 % Author

1732

1733 % My title

1734 %

1735 % June 15, 2006

1736

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

1738begin with leading space, thus:

1739

1740 % My title

1741 on multiple lines

1742

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

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

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

1746

1747 % Author One

1748 Author Two

1749

1750 % Author One; Author Two

1751

1752 % Author One;

1753 Author Two

1754

1755The date must fit on one line.

1756

1757All three metadata fields may contain standard inline formatting

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

1759

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

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

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

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

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

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

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

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

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

1769be used by itself as the HTML title.

1770

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

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

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

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

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

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

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

1778text. Thus,

1779

1780 % PANDOC(1)

1781

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

1783

1784 % PANDOC(1) Pandoc User Manuals

1785

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

1787

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

1789

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

1791

1792YAML metadata block

1793-------------------

1794

1795**Extension: `yaml_metadata_block`**

1796

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

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

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

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

1801line.

1802

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

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

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

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

1807given a role by external processors.)

1808

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

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

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

1812

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

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

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

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

1817when the field contains blank lines:

1818

1819 ---

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

1821 author:

1822 - name: Author One

1823 affiliation: University of Somewhere

1824 - name: Author Two

1825 affiliation: University of Nowhere

1826 tags: [nothing, nothingness]

1827 abstract: |

1828 This is the abstract.

1829

1830 It consists of two paragraphs.

1831 ...

1832

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

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

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

1836

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

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

1839

1840

1841Backslash escapes

1842-----------------

1843

1844**Extension: `all_symbols_escapable`**

1845

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

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

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

1849

1850 *\*hello\**

1851

1852one will get

1853

1854 <em>*hello*</em>

1855

1856instead of

1857

1858 <strong>hello</strong>

1859

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

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

1862

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

1864

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

1866will be used.)

1867

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

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

1870`\ `.

1871

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

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

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

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

1876two trailing spaces on a line.

1877

1878Backslash escapes do not work in verbatim contexts.

1879

1880Smart punctuation

1881-----------------

1882

1883**Extension**

1884

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

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

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

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

1889

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

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

1892

1893Inline formatting

1894-----------------

1895

1896### Emphasis ###

1897

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

1899

1900 This text is _emphasized with underscores_, and this

1901 is *emphasized with asterisks*.

1902

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

1904

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

1906

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

1908will not trigger emphasis:

1909

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

1911

1912**Extension: `intraword_underscores`**

1913

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

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

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

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

1918

1919 feas*ible*, not feas*able*.

1920

1921

1922### Strikeout ###

1923

1924**Extension: `strikeout`**

1925

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

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

1928

1929 This ~~is deleted text.~~

1930

1931

1932### Superscripts and subscripts ###

1933

1934**Extension: `superscript`, `subscript`**

1935

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

1937characters; subscripts may be written by surrounding the subscripted

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

1939

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

1941

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

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

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

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

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

1947

1948

1949### Verbatim ###

1950

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

1952

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

1954

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

1956

1957 Here is a literal backtick `` ` ``.

1958

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

1960backticks will be ignored.)

1961

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

1963of consecutive backticks (optionally followed by a space)

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

1965preceded by a space).

1966

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

1968work in verbatim contexts:

1969

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

1971

1972**Extension: `inline_code_attributes`**

1973

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

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

1976

1977 `<$>`{.haskell}

1978

1979Math

1980----

1981

1982**Extension: `tex_math_dollars`**

1983

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

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

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

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

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

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

1990

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

1992depends on the output format:

1993

1994Markdown, LaTeX, Org-Mode, ConTeXt

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

1996

1997reStructuredText

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

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

2000

2001AsciiDoc

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

2003

2004Texinfo

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

2006

2007groff man

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

2009

2010MediaWiki

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

2012

2013Textile

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

2015

2016RTF, OpenDocument, ODT

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

2018 and will otherwise appear verbatim.

2019

2020Docbook

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

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

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

2024

2025Docx

2026 ~ It will be rendered using OMML math markup.

2027

2028FictionBook2

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

2030 using Google Charts or other compatible web service, downloaded

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

2032

2033HTML, Slidy, DZSlides, S5, EPUB

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

2035 command-line options selected:

2036

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

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

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

2040 styled differently from the surrounding text if needed.

2041

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

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

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

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

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

2047 verbatim between `$` characters.)

2048

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

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

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

2052 it.

2053

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

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

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

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

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

2059

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

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

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

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

2064 procedure is:

2065

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

2067 gladtex -d myfile-images myfile.htex

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

2069

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

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

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

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

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

2075

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

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

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

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

2080

2081Raw HTML

2082--------

2083

2084**Extension: `raw_html`**

2085

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

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

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

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

2090be disabled if desired.)

2091

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

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

2094formats.

2095

2096**Extension: `markdown_in_html_blocks`**

2097

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

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

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

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

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

2103

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

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

2106Thus, for example, Pandoc will turn

2107

2108 <table>

2109 <tr>

2110 <td>*one*</td>

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

2112 </tr>

2113 </table>

2114

2115into

2116

2117 <table>

2118 <tr>

2119 <td><em>one</em></td>

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

2121 </tr>

2122 </table>

2123

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

2125

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

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

2128

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

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

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

2132from being interpreted as markdown.

2133

2134Raw TeX

2135-------

2136

2137**Extension: `raw_tex`**

2138

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

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

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

2142LaTeX to include BibTeX citations:

2143

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

2145

2146Note that in LaTeX environments, like

2147

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

2149 Age & Frequency \\ \hline

2150 18--25 & 15 \\

2151 26--35 & 33 \\

2152 36--45 & 22 \\ \hline

2153 \end{tabular}

2154

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

2156LaTeX, not as markdown.

2157

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

2159and ConTeXt.

2160

2161LaTeX macros

2162------------

2163

2164**Extension: `latex_macros`**

2165

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

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

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

2169not just LaTeX:

2170

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

2172

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

2174

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

2176unchanged to the output.

2177

2178

2179Links

2180-----

2181

2182Markdown allows links to be specified in several ways.

2183

2184### Automatic links ###

2185

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

2187will become a link:

2188

2189 <http://google.com>

2190 <sam@green.eggs.ham>

2191

2192### Inline links ###

2193

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

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

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

2197

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

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

2200

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

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

2203

2204

2205### Reference links ###

2206

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

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

2209before or after the link).

2210

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

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

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

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

2215parentheses.

2216

2217Here are some examples:

2218

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

2220 [my label 2]: /foo

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

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

2223

2224The URL may optionally be surrounded by angle brackets:

2225

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

2227

2228The title may go on the next line:

2229

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

2231 "The free software foundation"

2232

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

2234

2235 Here is [my link][FOO]

2236

2237 [Foo]: /bar/baz

2238

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

2240empty, or omitted entirely:

2241

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

2243

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

2245

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

2247reference link definitions cannot occur in nested constructions

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

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

2250not in most other implementations:

2251

2252 > My block [quote].

2253 >

2254 > [quote]: /foo

2255

2256### Internal links

2257

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

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

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

2261For example:

2262

2263 See the [Introduction](#introduction).

2264

2265or

2266

2267 See the [Introduction].

2268

2269 [Introduction]: #introduction

2270

2271Internal links are currently supported for HTML formats (including

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

2273

2274Images

2275------

2276

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

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

2279

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

2281

2282 ![movie reel]

2283

2284 [movie reel]: movie.gif

2285

2286### Pictures with captions ###

2287

2288**Extension: `implicit_figures`**

2289

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

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

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

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

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

2295

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

2297

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

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

2300 itself, with no caption.

2301

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

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

2304nonbreaking space after the image:

2305

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

2307

2308

2309Footnotes

2310---------

2311

2312**Extension: `footnotes`**

2313

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

2315

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

2317

2318 [^1]: Here is the footnote.

2319

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

2321

2322 Subsequent paragraphs are indented to show that they

2323 belong to the previous footnote.

2324

2325 { some.code }

2326

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

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

2329 multi-paragraph list items.

2330

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

2332 isn't indented.

2333

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

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

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

2337will be numbered sequentially.

2338

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

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

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

2342

2343**Extension: `inline_notes`**

2344

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

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

2347

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

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

2350 note.]

2351

2352Inline and regular footnotes may be mixed freely.

2353

2354

2355Citations

2356---------

2357

2358**Extension: `citations`**

2359

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

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

2362

2363 pandoc --filter pandoc-citeproc myinput.txt

2364

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

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

2367The bibliography may have any of these formats:

2368

2369 Format File extension

2370 ------------ --------------

2371 MODS .mods

2372 BibLaTeX .bib

2373 BibTeX .bibtex

2374 RIS .ris

2375 EndNote .enl

2376 EndNote XML .xml

2377 ISI .wos

2378 MEDLINE .medline

2379 Copac .copac

2380 JSON citeproc .json

2381

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

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

2384

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

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

2387for example:

2388

2389 ---

2390 references:

2391 - id: fenner2012a

2392 title: One-click science marketing

2393 author:

2394 - family: Fenner

2395 given: Martin

2396 container-title: Nature Materials

2397 volume: 11

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

2399 DOI: 10.1038/nmat3283

2400 issue: 4

2401 publisher: Nature Publishing Group

2402 page: 261-263

2403 type: article-journal

2404 issued:

2405 year: 2012

2406 month: 3

2407 ...

2408

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

2410these from a MODS reference collection.)

2411

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

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

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

2415modifying CSL styles can be found at

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

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

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

2419

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

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

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

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

2424

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

2426

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

2428

2429 Blah blah [@smith04; @doe99].

2430

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

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

2433author is already mentioned in the text:

2434

2435 Smith says blah [-@smith04].

2436

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

2438

2439 @smith04 says blah.

2440

2441 @smith04 [p. 33] says blah.

2442

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

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

2445document with an appropriate header:

2446

2447 last paragraph...

2448

2449 # References

2450

2451The bibliography will be inserted after this header.

2452

2453Non-pandoc extensions

2454---------------------

2455

2456The following markdown syntax extensions are not enabled by default

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

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

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

2460

2461**Extension: `lists_without_preceding_blankline`**\

2462Allow a list to occur right after a paragraph, with no intervening

2463blank space.

2464

2465**Extension: `hard_line_breaks`**\

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

2467breaks instead of spaces.

2468

2469**Extension: `ignore_line_breaks`**\

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

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

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

2473but text is divided into lines for readability.

2474

2475**Extension: `tex_math_single_backslash`**\

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

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

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

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

2480

2481**Extension: `tex_math_double_backslash`**\

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

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

2484as display TeX math.

2485

2486**Extension: `markdown_attribute`**\

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

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

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

2490

2491**Extension: `mmd_title_block`**\

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

2493the document, for example:

2494

2495 Title: My title

2496 Author: John Doe

2497 Date: September 1, 2008

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

2499 a field spanning multiple lines.

2500

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

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

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

2504it will take precedence over `mmd_title_block`.

2505

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

2507

2508**Extension: `abbreviations`**\

2509Parses PHP Markdown Extra abbreviation keys, like

2510

2511 *[HTML]: Hyper Text Markup Language

2512

2513Note that the pandoc document model does not support

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

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

2516

2517**Extension: `autolink_bare_uris`**\

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

2519pointy braces `<...>`.

2520

2521**Extension: `ascii_identifiers`**\

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

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

2524letters are omitted.

2525

2526**Extension: `link_attributes`**\

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

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

2529these, so they are presently just ignored.

2530

2531**Extension: `mmd_header_identifiers`**\

2532Parses multimarkdown style header identifiers (in square brackets,

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

2534

2535Markdown variants

2536-----------------

2537

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

2539variants are supported:

2540

2541`markdown_phpextra` (PHP Markdown Extra)

2542: `footnotes`, `pipe_tables`, `raw_html`, `markdown_attribute`,

2543 `fenced_code_blocks`, `definition_lists`, `intraword_underscores`,

2544 `header_attributes`, `abbreviations`.

2545

2546`markdown_github` (Github-flavored Markdown)

2547: `pipe_tables`, `raw_html`, `tex_math_single_backslash`,

2548 `fenced_code_blocks`, `fenced_code_attributes`, `auto_identifiers`,

2549 `ascii_identifiers`, `backtick_code_blocks`, `autolink_bare_uris`,

2550 `intraword_underscores`, `strikeout`, `hard_line_breaks`

2551

2552`markdown_mmd` (MultiMarkdown)

2553: `pipe_tables` `raw_html`, `markdown_attribute`, `link_attributes`,

2554 `raw_tex`, `tex_math_double_backslash`, `intraword_underscores`,

2555 `mmd_title_block`, `footnotes`, `definition_lists`,

2556 `all_symbols_escapable`, `implicit_header_references`,

2557 `auto_identifiers`, `mmd_header_identifiers`

2558

2559`markdown_strict` (Markdown.pl)

2560: `raw_html`

2561

2562Producing slide shows with Pandoc

2563=================================

2564

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

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

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

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

2569

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

2571

2572 % Habits

2573 % John Doe

2574 % March 22, 2005

2575

2576 # In the morning

2577

2578 ## Getting up

2579

2580 - Turn off alarm

2581 - Get out of bed

2582

2583 ## Breakfast

2584

2585 - Eat eggs

2586 - Drink coffee

2587

2588 # In the evening

2589

2590 ## Dinner

2591

2592 - Eat spaghetti

2593 - Drink wine

2594

2595 ------------------

2596

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

2598

2599 ## Going to sleep

2600

2601 - Get in bed

2602 - Count sheep

2603

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

2605

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

2607

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

2609

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

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

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

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

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

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

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

2617the file by default.

2618

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

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

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

2622

2623To produce a PDF slide show using beamer, type

2624

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

2626

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

2628by printing it to a file from the browser.

2629

2630Structuring the slide show

2631--------------------------

2632

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

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

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

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

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

2638the `--slide-level` option.

2639

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

2641rules:

2642

2643 * A horizontal rule always starts a new slide.

2644

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

2646

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

2648 headers *within* a slide.

2649

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

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

2652 and help to break the slide show into sections.

2653

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

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

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

2657

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

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

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

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

2662sections, as in the example above.

2663

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

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

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

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

2668

2669Incremental lists

2670-----------------

2671

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

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

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

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

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

2677

2678 > - Eat spaghetti

2679 > - Drink wine

2680

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

2682a single document.

2683

2684Inserting pauses

2685----------------

2686

2687You can add "pauses" within a slide by including a paragraph containing

2688three dots, separated by spaces:

2689

2690 # Slide with a pause

2691

2692 content before the pause

2693

2694 . . .

2695

2696 content after the pause

2697

2698Styling the slides

2699------------------

2700

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

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

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

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

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

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

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

2708

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

2710be modified there.

2711

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

2713for example:

2714

2715 -V theme=moon

2716

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

2718

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

2720using the `-V` option:

2721

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

2723

2724Note that header attributes will turn into slide attributes

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

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

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

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

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

2730bibliographies:

2731

2732 # References {.allowframebreaks}

2733

2734Literate Haskell support

2735========================

2736

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

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

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

2740literate Haskell source. This means that

2741

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

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

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

2745

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

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

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

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

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

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

2752

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

2754 as Haskell code.

2755

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

2757 be rendered using bird tracks.

2758

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

2760 Haskell code.

2761

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

2763 inside `code` environments.

2764

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

2766 with class `literatehaskell` and bird tracks.

2767

2768Examples:

2769

2770 pandoc -f markdown+lhs -t html

2771

2772reads literate Haskell source formatted with markdown conventions and writes

2773ordinary HTML (without bird tracks).

2774

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

2776

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

2778and pasted as literate Haskell source.

2779

2780Custom writers

2781==============

2782

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

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

2785

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

2787in place of the output format. For example:

2788

2789 pandoc -t data/sample.lua

2790

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

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

2793which you can modify according to your needs, do

2794

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

2796

2797Authors

2798=======

2799

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

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

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

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

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

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

2807Christopher Sawicki, Kelsey Hightower, Masayoshi Takahashi, Antoine

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

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

2810Jamie F. Olson.

2811

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

2844[lua]: http://www.lua.org

2845