# 1 "src/Text/Pandoc/Data.hsb" {-# LANGUAGE OverloadedStrings #-} -- to be processed using hsb2hs module Text.Pandoc.Data (dataFiles) where import qualified Data.ByteString as B dataFiles :: [(FilePath, B.ByteString)] dataFiles = ("README", "% Pandoc User's Guide\n% John MacFarlane\n% May 27, 2015\n\nSynopsis\n========\n\n`pandoc` [*options*] [*input-file*]...\n\nDescription\n===========\n\nPandoc is a [Haskell] library for converting from one markup format to\nanother, and a command-line tool that uses this library. It can read\n[Markdown], [CommonMark], and (subsets of) [Textile],\n[reStructuredText], [HTML], [LaTeX], [MediaWiki markup], [TWiki\nmarkup], [Haddock markup], [OPML], [Emacs Org-mode], [DocBook],\n[txt2tags], [EPUB] and [Word docx]; and it can write plain text,\n[Markdown], [reStructuredText], [XHTML], [HTML 5], [LaTeX] (including\n[beamer] slide shows), [ConTeXt], [RTF], [OPML], [DocBook],\n[OpenDocument], [ODT], [Word docx], [GNU Texinfo], [MediaWiki markup],\n[DokuWiki markup], [Haddock markup], [EPUB] (v2 or v3),\n[FictionBook2], [Textile], [groff man] pages, [Emacs Org-Mode],\n[AsciiDoc], [InDesign ICML], and [Slidy], [Slideous], [DZSlides],\n[reveal.js] or [S5] HTML slide shows. It can also produce [PDF] output\non systems where LaTeX is installed.\n\nPandoc's enhanced version of markdown includes syntax for footnotes,\ntables, flexible ordered lists, definition lists, fenced code blocks,\nsuperscript, subscript, strikeout, title blocks, automatic tables of\ncontents, embedded LaTeX math, citations, and markdown inside HTML block\nelements. (These enhancements, described below under\n[Pandoc's markdown](#pandocs-markdown), can be disabled using the\n`markdown_strict` input or output format.)\n\nIn contrast to most existing tools for converting markdown to HTML, which\nuse regex substitutions, Pandoc has a modular design: it consists of a\nset of readers, which parse text in a given format and produce a native\nrepresentation of the document, and a set of writers, which convert\nthis native representation into a target format. Thus, adding an input\nor output format requires only adding a reader or writer.\n\nUsing `pandoc`\n--------------\n\nIf no *input-file* is specified, input is read from *stdin*.\nOtherwise, the *input-files* are concatenated (with a blank\nline between each) and used as input. Output goes to *stdout* by\ndefault (though output to *stdout* is disabled for the `odt`, `docx`,\n`epub`, and `epub3` output formats). For output to a file, use the\n`-o` option:\n\n pandoc -o output.html input.txt\n\nBy default, pandoc produces a document fragment, not a standalone\ndocument with a proper header and footer. To produce a standalone\ndocument, use the `-s` or `--standalone` flag:\n\n pandoc -s -o output.html input.txt\n\nFor more information on how standalone documents are produced, see\n[Templates](#templates), below.\n\nInstead of a file, an absolute URI may be given. In this case\npandoc will fetch the content using HTTP:\n\n pandoc -f html -t markdown http://www.fsf.org\n\nIf multiple input files are given, `pandoc` will concatenate them all (with\nblank lines between them) before parsing. This feature is disabled for\n binary input formats such as `EPUB` and `docx`.\n\nThe format of the input and output can be specified explicitly using\ncommand-line options. The input format can be specified using the\n`-r/--read` or `-f/--from` options, the output format using the\n`-w/--write` or `-t/--to` options. Thus, to convert `hello.txt` from\nmarkdown to LaTeX, you could type:\n\n pandoc -f markdown -t latex hello.txt\n\nTo convert `hello.html` from html to markdown:\n\n pandoc -f html -t markdown hello.html\n\nSupported output formats are listed below under the `-t/--to` option.\nSupported input formats are listed below under the `-f/--from` option. Note\nthat the `rst`, `textile`, `latex`, and `html` readers are not complete;\nthere are some constructs that they do not parse.\n\nIf the input or output format is not specified explicitly, `pandoc`\nwill attempt to guess it from the extensions of\nthe input and output filenames. Thus, for example,\n\n pandoc -o hello.tex hello.txt\n\nwill convert `hello.txt` from markdown to LaTeX. If no output file\nis specified (so that output goes to *stdout*), or if the output file's\nextension is unknown, the output format will default to HTML.\nIf no input file is specified (so that input comes from *stdin*), or\nif the input files' extensions are unknown, the input format will\nbe assumed to be markdown unless explicitly specified.\n\nPandoc uses the UTF-8 character encoding for both input and output.\nIf your local character encoding is not UTF-8, you\nshould pipe input and output through `iconv`:\n\n iconv -t utf-8 input.txt | pandoc | iconv -f utf-8\n\nNote that in some output formats (such as HTML, LaTeX, ConTeXt,\nRTF, OPML, DocBook, and Texinfo), information about\nthe character encoding is included in the document header, which\nwill only be included if you use the `-s/--standalone` option.\n\nCreating a PDF\n--------------\n\nEarlier versions of pandoc came with a program, `markdown2pdf`, that\nused pandoc and pdflatex to produce a PDF. This is no longer needed,\nsince `pandoc` can now produce `pdf` output itself. To produce a PDF, simply\nspecify an output file with a `.pdf` extension. Pandoc will create a latex\nfile and use pdflatex (or another engine, see `--latex-engine`) to convert it\nto PDF:\n\n pandoc test.txt -o test.pdf\n\nProduction of a PDF requires that a LaTeX engine be installed (see\n`--latex-engine`, below), and assumes that the following LaTeX packages are\navailable: `amssymb`, `amsmath`, `ifxetex`, `ifluatex`, `listings` (if the\n`--listings` option is used), `fancyvrb`, `longtable`, `booktabs`, `url`,\n`graphicx` and `grffile` (if the document contains images),\n `hyperref`, `ulem`, `babel` (if the `lang` variable is set),\n`fontspec` (if `xelatex` or `lualatex` is used as the LaTeX engine), `xltxtra`\nand `xunicode` (if `xelatex` is used).\n\n`hsmarkdown`\n------------\n\nA user who wants a drop-in replacement for `Markdown.pl` may create\na symbolic link to the `pandoc` executable called `hsmarkdown`. When\ninvoked under the name `hsmarkdown`, `pandoc` will behave as if\ninvoked with `-f markdown_strict --email-obfuscation=references`,\nand all command-line options will be treated as regular arguments.\nHowever, this approach does not work under Cygwin, due to problems with\nits simulation of symbolic links.\n\n[Cygwin]: http://www.cygwin.com/\n[`iconv`]: http://www.gnu.org/software/libiconv/\n[CTAN]: http://www.ctan.org \"Comprehensive TeX Archive Network\"\n[TeX Live]: http://www.tug.org/texlive/\n[MacTeX]: http://www.tug.org/mactex/\n\nOptions\n=======\n\nGeneral options\n---------------\n\n`-f` *FORMAT*, `-r` *FORMAT*, `--from=`*FORMAT*, `--read=`*FORMAT*\n\n: Specify input format. *FORMAT* can be `native` (native Haskell),\n `json` (JSON version of native AST), `markdown` (pandoc's\n extended markdown), `markdown_strict` (original unextended\n markdown), `markdown_phpextra` (PHP Markdown Extra extended\n markdown), `markdown_github` (github extended markdown),\n `commonmark` (CommonMark markdown), `textile` (Textile), `rst`\n (reStructuredText), `html` (HTML), `docbook` (DocBook), `t2t`\n (txt2tags), `docx` (docx), `epub` (EPUB), `opml` (OPML), `org`\n (Emacs Org-mode), `mediawiki` (MediaWiki markup), `twiki` (TWiki\n markup), `haddock` (Haddock markup), or `latex` (LaTeX). If\n `+lhs` is appended to `markdown`, `rst`, `latex`, or `html`, the\n input will be treated as literate Haskell source: see [Literate\n Haskell support](#literate-haskell-support), below. Markdown\n syntax extensions can be individually enabled or disabled by\n appending `+EXTENSION` or `-EXTENSION` to the format name. So, for\n example, `markdown_strict+footnotes+definition_lists` is strict\n markdown with footnotes and definition lists enabled, and\n `markdown-pipe_tables+hard_line_breaks` is pandoc's markdown\n without pipe tables and with hard line breaks. See [Pandoc's\n markdown](#pandocs-markdown), below, for a list of extensions and\n their names.\n\n`-t` *FORMAT*, `-w` *FORMAT*, `--to=`*FORMAT*, `--write=`*FORMAT*\n\n: Specify output format. *FORMAT* can be `native` (native Haskell),\n `json` (JSON version of native AST), `plain` (plain text),\n `markdown` (pandoc's extended markdown), `markdown_strict`\n (original unextended markdown), `markdown_phpextra` (PHP Markdown\n extra extended markdown), `markdown_github` (github extended\n markdown), `commonmark` (CommonMark markdown), `rst`\n (reStructuredText), `html` (XHTML 1), `html5` (HTML 5), `latex`\n (LaTeX), `beamer` (LaTeX beamer slide show), `context` (ConTeXt),\n `man` (groff man), `mediawiki` (MediaWiki markup), `dokuwiki`\n (DokuWiki markup), `textile` (Textile), `org` (Emacs Org-Mode),\n `texinfo` (GNU Texinfo), `opml` (OPML), `docbook` (DocBook),\n `opendocument` (OpenDocument), `odt` (OpenOffice text document),\n `docx` (Word docx), `haddock` (Haddock markup), `rtf` (rich text\n format), `epub` (EPUB v2 book), `epub3` (EPUB v3), `fb2`\n (FictionBook2 e-book), `asciidoc` (AsciiDoc), `icml` (InDesign\n ICML), `slidy` (Slidy HTML and javascript slide show), `slideous`\n (Slideous HTML and javascript slide show), `dzslides` (DZSlides\n HTML5 + javascript slide show), `revealjs` (reveal.js HTML5 +\n javascript slide show), `s5` (S5 HTML and javascript slide show),\n or the path of a custom lua writer (see [Custom\n writers](#custom-writers), below). Note that `odt`, `epub`, and\n `epub3` output will not be directed to *stdout*; an output\n filename must be specified using the `-o/--output` option. If\n `+lhs` is appended to `markdown`, `rst`, `latex`, `beamer`,\n `html`, or `html5`, the output will be rendered as literate\n Haskell source: see [Literate Haskell\n support](#literate-haskell-support), below. Markdown syntax\n extensions can be individually enabled or disabled by appending\n `+EXTENSION` or `-EXTENSION` to the format name, as described\n above under `-f`.\n\n`-o` *FILE*, `--output=`*FILE*\n\n: Write output to *FILE* instead of *stdout*. If *FILE* is\n `-`, output will go to *stdout*. (Exception: if the output\n format is `odt`, `docx`, `epub`, or `epub3`, output to stdout is disabled.)\n\n`--data-dir=`*DIRECTORY*\n\n: Specify the user data directory to search for pandoc data files.\n If this option is not specified, the default user data directory\n will be used. This is\n\n $HOME/.pandoc\n\n in unix,\n\n C:\\Documents And Settings\\USERNAME\\Application Data\\pandoc\n\n in Windows XP, and\n\n C:\\Users\\USERNAME\\AppData\\Roaming\\pandoc\n\n in Windows 7. (You can find the default user data directory\n on your system by looking at the output of `pandoc --version`.)\n A `reference.odt`, `reference.docx`, `default.csl`,\n `epub.css`, `templates`, `slidy`, `slideous`, or `s5` directory\n placed in this directory will override pandoc's normal defaults.\n\n`--verbose`\n\n: Give verbose debugging output. Currently this only has an effect\n with PDF output.\n\n`-v`, `--version`\n\n: Print version.\n\n`-h`, `--help`\n\n: Show usage message.\n\nReader options\n--------------\n\n`-R`, `--parse-raw`\n\n: Parse untranslatable HTML codes and LaTeX environments as raw HTML\n or LaTeX, instead of ignoring them. Affects only HTML and LaTeX\n input. Raw HTML can be printed in markdown, reStructuredText, HTML,\n Slidy, Slideous, DZSlides, reveal.js, and S5 output; raw LaTeX\n can be printed in markdown, reStructuredText, LaTeX, and ConTeXt output.\n The default is for the readers to omit untranslatable HTML codes and\n LaTeX environments. (The LaTeX reader does pass through untranslatable\n LaTeX *commands*, even if `-R` is not specified.)\n\n`-S`, `--smart`\n\n: Produce typographically correct output, converting straight quotes\n to curly quotes, `---` to em-dashes, `--` to en-dashes, and\n `...` to ellipses. Nonbreaking spaces are inserted after certain\n abbreviations, such as \"Mr.\" (Note: This option is significant only when\n the input format is `markdown`, `markdown_strict`, `textile` or `twiki`.\n It is selected automatically when the input format is `textile` or the\n output format is `latex` or `context`, unless `--no-tex-ligatures`\n is used.)\n\n`--old-dashes`\n\n: Selects the pandoc <= 1.8.2.1 behavior for parsing smart dashes: `-` before\n a numeral is an en-dash, and `--` is an em-dash. This option is selected\n automatically for `textile` input.\n\n`--base-header-level=`*NUMBER*\n\n: Specify the base level for headers (defaults to 1).\n\n`--indented-code-classes=`*CLASSES*\n\n: Specify classes to use for indented code blocks--for example,\n `perl,numberLines` or `haskell`. Multiple classes may be separated\n by spaces or commas.\n\n`--default-image-extension=`*EXTENSION*\n\n: Specify a default extension to use when image paths/URLs have no\n extension. This allows you to use the same source for formats that\n require different kinds of images. Currently this option only affects\n the markdown and LaTeX readers.\n\n`--filter=`*EXECUTABLE*\n\n: Specify an executable to be used as a filter transforming the\n Pandoc AST after the input is parsed and before the output is\n written. The executable should read JSON from stdin and write\n JSON to stdout. The JSON must be formatted like pandoc's own\n JSON input and output. The name of the output format will be\n passed to the filter as the first argument. Hence,\n\n pandoc --filter ./caps.py -t latex\n\n is equivalent to\n\n pandoc -t json | ./caps.py latex | pandoc -f json -t latex\n\n The latter form may be useful for debugging filters.\n\n Filters may be written in any language. `Text.Pandoc.JSON`\n exports `toJSONFilter` to facilitate writing filters in Haskell.\n Those who would prefer to write filters in python can use the\n module `pandocfilters`, installable from PyPI. See\n for the module and several\n examples. There are also pandoc filter libraries in\n [PHP](https://github.com/vinai/pandocfilters-php),\n [perl](https://metacpan.org/pod/Pandoc::Filter), and\n [javascript/node.js](https://github.com/mvhenderson/pandoc-filter-node).\n\n Note that the *EXECUTABLE* will be sought in the user's\n `PATH`, and not in the working directory, if no directory is\n provided. If you want to run a script in the working directory,\n preface the filename with `./`.\n\n`-M` *KEY*[`=`*VAL*], `--metadata=`*KEY*[`:`*VAL*]\n\n: Set the metadata field *KEY* to the value *VAL*. A value specified\n on the command line overrides a value specified in the document.\n Values will be parsed as YAML boolean or string values. If no value is\n specified, the value will be treated as Boolean true. Like\n `--variable`, `--metadata` causes template variables to be set.\n But unlike `--variable`, `--metadata` affects the metadata of the\n underlying document (which is accessible from filters and may be\n printed in some output formats).\n\n`--normalize`\n\n: Normalize the document after reading: merge adjacent\n `Str` or `Emph` elements, for example, and remove repeated `Space`s.\n\n`-p`, `--preserve-tabs`\n\n: Preserve tabs instead of converting them to spaces (the default).\n Note that this will only affect tabs in literal code spans and code\n blocks; tabs in regular text will be treated as spaces.\n\n`--tab-stop=`*NUMBER*\n\n: Specify the number of spaces per tab (default is 4).\n\n`--track-changes=accept`|`reject`|`all`\n\n: Specifies what to do with insertions and deletions produced by the MS\n Word \"track-changes\" feature. `accept` (the default), inserts all\n insertions, and ignores all deletions. `reject` inserts all\n deletions and ignores insertions. `all` puts in both insertions\n and deletions, wrapped in spans with `insertion` and `deletion`\n classes, respectively. The author and time of change is\n included. `all` is useful for scripting: only accepting changes\n from a certain reviewer, say, or before a certain date. This\n option only affects the docx reader.\n\n`--extract-media=`*DIR*\n\n: Extract images and other media contained in a docx or epub container\n to the path *DIR*, creating it if necessary, and adjust the images\n references in the document so they point to the extracted files.\n This option only affects the docx and epub readers.\n\nGeneral writer options\n----------------------\n\n`-s`, `--standalone`\n\n: Produce output with an appropriate header and footer (e.g. a\n standalone HTML, LaTeX, or RTF file, not a fragment). This option\n is set automatically for `pdf`, `epub`, `epub3`, `fb2`, `docx`, and `odt`\n output.\n\n`--template=`*FILE*\n\n: Use *FILE* as a custom template for the generated document. Implies\n `--standalone`. See [Templates](#templates) below for a description\n of template syntax. If no extension is specified, an extension\n corresponding to the writer will be added, so that `--template=special`\n looks for `special.html` for HTML output. If the template is not\n found, pandoc will search for it in the user data directory\n (see `--data-dir`). If this option is not used, a default\n template appropriate for the output format will be used (see\n `-D/--print-default-template`).\n\n`-V` *KEY*[`=`*VAL*], `--variable=`*KEY*[`:`*VAL*]\n\n: Set the template variable *KEY* to the value *VAL* when rendering the\n document in standalone mode. This is generally only useful when the\n `--template` option is used to specify a custom template, since\n pandoc automatically sets the variables used in the default\n templates. If no *VAL* is specified, the key will be given the\n value `true`.\n\n`-D` *FORMAT*, `--print-default-template=`*FORMAT*\n\n: Print the default template for an output *FORMAT*. (See `-t`\n for a list of possible *FORMAT*s.)\n\n`--print-default-data-file=`*FILE*\n\n: Print a default data file.\n\n`--no-wrap`\n\n: Disable text wrapping in output. By default, text is wrapped\n appropriately for the output format.\n\n`--columns=`*NUMBER*\n\n: Specify length of lines in characters (for text wrapping).\n\n`--toc`, `--table-of-contents`\n\n: Include an automatically generated table of contents (or, in\n the case of `latex`, `context`, and `rst`, an instruction to create\n one) in the output document. This option has no effect on `man`,\n `docbook`, `slidy`, `slideous`, `s5`, `docx`, or `odt` output.\n\n`--toc-depth=`*NUMBER*\n\n: Specify the number of section levels to include in the table\n of contents. The default is 3 (which means that level 1, 2, and 3\n headers will be listed in the contents).\n\n`--no-highlight`\n\n: Disables syntax highlighting for code blocks and inlines, even when\n a language attribute is given.\n\n`--highlight-style=`*STYLE*\n\n: Specifies the coloring style to be used in highlighted source code.\n Options are `pygments` (the default), `kate`, `monochrome`,\n `espresso`, `zenburn`, `haddock`, and `tango`. For more information\n on syntax highlighting in pandoc, see [Syntax highlighting], below.\n\n`-H` *FILE*, `--include-in-header=`*FILE*\n\n: Include contents of *FILE*, verbatim, at the end of the header.\n This can be used, for example, to include special\n CSS or javascript in HTML documents. This option can be used\n repeatedly to include multiple files in the header. They will be\n included in the order specified. Implies `--standalone`.\n\n`-B` *FILE*, `--include-before-body=`*FILE*\n\n: Include contents of *FILE*, verbatim, at the beginning of the\n document body (e.g. after the `` tag in HTML, or the\n `\\begin{document}` command in LaTeX). This can be used to include\n navigation bars or banners in HTML documents. This option can be\n used repeatedly to include multiple files. They will be included in\n the order specified. Implies `--standalone`.\n\n`-A` *FILE*, `--include-after-body=`*FILE*\n\n: Include contents of *FILE*, verbatim, at the end of the document\n body (before the `` tag in HTML, or the\n `\\end{document}` command in LaTeX). This option can be be used\n repeatedly to include multiple files. They will be included in the\n order specified. Implies `--standalone`.\n\nOptions affecting specific writers\n----------------------------------\n\n`--self-contained`\n\n: Produce a standalone HTML file with no external dependencies, using\n `data:` URIs to incorporate the contents of linked scripts, stylesheets,\n images, and videos. The resulting file should be \"self-contained,\"\n in the sense that it needs no external files and no net access to be\n displayed properly by a browser. This option works only with HTML output\n formats, including `html`, `html5`, `html+lhs`, `html5+lhs`, `s5`,\n `slidy`, `slideous`, `dzslides`, and `revealjs`. Scripts, images, and\n stylesheets at absolute URLs will be downloaded; those at relative URLs\n will be sought relative to the working directory (if the first source\n file is local) or relative to the base URL (if the first source\n file is remote). `--self-contained` does not work with `--mathjax`.\n\n`--offline`\n\n: Deprecated synonym for `--self-contained`.\n\n`-5`, `--html5`\n\n: Produce HTML5 instead of HTML4. This option has no effect for writers\n other than `html`. (*Deprecated:* Use the `html5` output format instead.)\n\n`--html-q-tags`\n\n: Use `` tags for quotes in HTML.\n\n`--ascii`\n\n: Use only ascii characters in output. Currently supported only\n for HTML output (which uses numerical entities instead of\n UTF-8 when this option is selected).\n\n`--reference-links`\n\n: Use reference-style links, rather than inline links, in writing markdown\n or reStructuredText. By default inline links are used.\n\n`--atx-headers`\n\n: Use ATX style headers in markdown and asciidoc output. The default is\n to use setext-style headers for levels 1-2, and then ATX headers.\n\n`--chapters`\n\n: Treat top-level headers as chapters in LaTeX, ConTeXt, and DocBook\n output. When the LaTeX template uses the report, book, or\n memoir class, this option is implied. If `beamer` is the output\n format, top-level headers will become `\\part{..}`.\n\n`-N`, `--number-sections`\n\n: Number section headings in LaTeX, ConTeXt, HTML, or EPUB output.\n By default, sections are not numbered. Sections with class\n `unnumbered` will never be numbered, even if `--number-sections`\n is specified.\n\n`--number-offset=`*NUMBER*[`,`*NUMBER*`,`*...*]\n\n: Offset for section headings in HTML output (ignored in other\n output formats). The first number is added to the section number for\n top-level headers, the second for second-level headers, and so on.\n So, for example, if you want the first top-level header in your\n document to be numbered \"6\", specify `--number-offset=5`.\n If your document starts with a level-2 header which you want to\n be numbered \"1.5\", specify `--number-offset=1,4`.\n Offsets are 0 by default. Implies `--number-sections`.\n\n`--no-tex-ligatures`\n\n: Do not convert quotation marks, apostrophes, and dashes to\n the TeX ligatures when writing LaTeX or ConTeXt. Instead, just\n use literal unicode characters. This is needed for using advanced\n OpenType features with XeLaTeX and LuaLaTeX. Note: normally\n `--smart` is selected automatically for LaTeX and ConTeXt\n output, but it must be specified explicitly if `--no-tex-ligatures`\n is selected. If you use literal curly quotes, dashes, and ellipses\n in your source, then you may want to use `--no-tex-ligatures`\n without `--smart`.\n\n`--listings`\n\n: Use listings package for LaTeX code blocks\n\n`-i`, `--incremental`\n\n: Make list items in slide shows display incrementally (one by one).\n The default is for lists to be displayed all at once.\n\n`--slide-level=`*NUMBER*\n\n: Specifies that headers with the specified level create\n slides (for `beamer`, `s5`, `slidy`, `slideous`, `dzslides`). Headers\n above this level in the hierarchy are used to divide the\n slide show into sections; headers below this level create\n subheads within a slide. The default is to set the slide level\n based on the contents of the document; see\n [Structuring the slide show](#structuring-the-slide-show), below.\n\n`--section-divs`\n\n: Wrap sections in `
` tags (or `
` tags in HTML5),\n and attach identifiers to the enclosing `
` (or `
`)\n rather than the header itself.\n See [Section identifiers](#header-identifiers-in-html-latex-and-context), below.\n\n`--email-obfuscation=none`|`javascript`|`references`\n\n: Specify a method for obfuscating `mailto:` links in HTML documents.\n `none` leaves `mailto:` links as they are. `javascript` obfuscates\n them using javascript. `references` obfuscates them by printing their\n letters as decimal or hexadecimal character references.\n\n`--id-prefix=`*STRING*\n\n: Specify a prefix to be added to all automatically generated identifiers\n in HTML and DocBook output, and to footnote numbers in markdown output.\n This is useful for preventing duplicate identifiers when generating\n fragments to be included in other pages.\n\n`-T` *STRING*, `--title-prefix=`*STRING*\n\n: Specify *STRING* as a prefix at the beginning of the title\n that appears in the HTML header (but not in the title as it\n appears at the beginning of the HTML body). Implies\n `--standalone`.\n\n`-c` *URL*, `--css=`*URL*\n\n: Link to a CSS style sheet. This option can be be used repeatedly to\n include multiple files. They will be included in the order specified.\n\n`--reference-odt=`*FILE*\n\n: Use the specified file as a style reference in producing an ODT.\n For best results, the reference ODT should be a modified version\n of an ODT produced using pandoc. The contents of the reference ODT\n are ignored, but its stylesheets are used in the new ODT. If no\n reference ODT is specified on the command line, pandoc will look\n for a file `reference.odt` in the user data directory (see\n `--data-dir`). If this is not found either, sensible defaults will be\n used.\n\n`--reference-docx=`*FILE*\n\n: Use the specified file as a style reference in producing a docx file.\n For best results, the reference docx should be a modified version\n of a docx file produced using pandoc. The contents of the reference docx\n are ignored, but its stylesheets and document properties (including\n margins, page size, header, and footer) are used in the new docx. If no\n reference docx is specified on the command line, pandoc will look\n for a file `reference.docx` in the user data directory (see\n `--data-dir`). If this is not found either, sensible defaults will be\n used. The following styles are used by pandoc: [paragraph]\n Normal, Compact, Title, Subtitle, Authors, Date, Abstract, Heading 1,\n Heading 2, Heading 3, Heading 4, Heading 5, Block Text, Definition Term,\n Definition, Bibliography, Body Text, Table Caption, Image Caption,\n Figure, FigureWithCaption;\n [character] Default Paragraph Font, Body Text Char, Verbatim Char,\n Footnote Reference, Hyperlink.\n\n`--epub-stylesheet=`*FILE*\n\n: Use the specified CSS file to style the EPUB. If no stylesheet\n is specified, pandoc will look for a file `epub.css` in the\n user data directory (see `--data-dir`). If it is not\n found there, sensible defaults will be used.\n\n`--epub-cover-image=`*FILE*\n\n: Use the specified image as the EPUB cover. It is recommended\n that the image be less than 1000px in width and height. Note that\n in a markdown source document you can also specify `cover-image`\n in a YAML metadata block (see [EPUB Metadata], below).\n\n`--epub-metadata=`*FILE*\n\n: Look in the specified XML file for metadata for the EPUB.\n The file should contain a series of Dublin Core elements,\n as documented at .\n For example:\n\n Creative Commons\n es-AR\n\n By default, pandoc will include the following metadata elements:\n `` (from the document title), `` (from the\n document authors), `` (from the document date, which should\n be in [ISO 8601 format]), `` (from the `lang`\n variable, or, if is not set, the locale), and `` (a randomly generated UUID). Any of these may be\n overridden by elements in the metadata file.\n\n Note: if the source document is markdown, a YAML metadata block\n in the document can be used instead. See below under\n [EPUB Metadata].\n\n`--epub-embed-font=`*FILE*\n\n: Embed the specified font in the EPUB. This option can be repeated\n to embed multiple fonts. Wildcards can also be used: for example,\n `DejaVuSans-*.ttf`. However, if you use wildcards on the command\n line, be sure to escape them or put the whole filename in single quotes,\n to prevent them from being interpreted by the shell. To use the\n embedded fonts, you will need to add declarations like the following\n to your CSS (see `--epub-stylesheet`):\n\n @font-face {\n font-family: DejaVuSans;\n font-style: normal;\n font-weight: normal;\n src:url(\"DejaVuSans-Regular.ttf\");\n }\n @font-face {\n font-family: DejaVuSans;\n font-style: normal;\n font-weight: bold;\n src:url(\"DejaVuSans-Bold.ttf\");\n }\n @font-face {\n font-family: DejaVuSans;\n font-style: italic;\n font-weight: normal;\n src:url(\"DejaVuSans-Oblique.ttf\");\n }\n @font-face {\n font-family: DejaVuSans;\n font-style: italic;\n font-weight: bold;\n src:url(\"DejaVuSans-BoldOblique.ttf\");\n }\n body { font-family: \"DejaVuSans\"; }\n\n`--epub-chapter-level=`*NUMBER*\n\n: Specify the header level at which to split the EPUB into separate\n \"chapter\" files. The default is to split into chapters at level 1\n headers. This option only affects the internal composition of the\n EPUB, not the way chapters and sections are displayed to users. Some\n readers may be slow if the chapter files are too large, so for large\n documents with few level 1 headers, one might want to use a chapter\n level of 2 or 3.\n\n`--latex-engine=pdflatex`|`lualatex`|`xelatex`\n\n: Use the specified LaTeX engine when producing PDF output.\n The default is `pdflatex`. If the engine is not in your PATH,\n the full path of the engine may be specified here.\n\n`--latex-engine-opt=`*STRING*\n\n: Use the given string as a command-line argument to the `latex-engine`.\n If used multiple times, the arguments are provided with spaces between\n them. Note that no check for duplicate options is done.\n\nCitation rendering\n------------------\n\n`--bibliography=`*FILE*\n\n: Set the `bibliography` field in the document's metadata to *FILE*,\n overriding any value set in the metadata, and process citations\n using `pandoc-citeproc`. (This is equivalent to\n `--metadata bibliography=FILE --filter pandoc-citeproc`.)\n If `--natbib` or `--biblatex` is also supplied, `pandoc-citeproc` is not\n used, making this equivalent to `--metadata bibliography=FILE`.\n If you supply this argument multiple times, each *FILE* will be added\n to bibliography.\n\n`--csl=`*FILE*\n\n: Set the `csl` field in the document's metadata to *FILE*,\n overriding any value set in the metadata. (This is equivalent to\n `--metadata csl=FILE`.)\n This option is only relevant with `pandoc-citeproc`.\n\n`--citation-abbreviations=`*FILE*\n\n: Set the `citation-abbreviations` field in the document's metadata to\n *FILE*, overriding any value set in the metadata. (This is equivalent to\n `--metadata citation-abbreviations=FILE`.)\n This option is only relevant with `pandoc-citeproc`.\n\n`--natbib`\n\n: Use natbib for citations in LaTeX output. This option is not for use\n with the `pandoc-citeproc` filter or with PDF output. It is intended for\n use in producing a LaTeX file that can be processed with pdflatex and\n bibtex.\n\n`--biblatex`\n\n: Use biblatex for citations in LaTeX output. This option is not for use\n with the `pandoc-citeproc` filter or with PDF output. It is intended for\n use in producing a LaTeX file that can be processed with pdflatex and\n bibtex or biber.\n\nMath rendering in HTML\n----------------------\n\n`-m` [*URL*], `--latexmathml`[`=`*URL*]\n\n: Use the [LaTeXMathML] script to display embedded TeX math in HTML output.\n To insert a link to a local copy of the `LaTeXMathML.js` script,\n provide a *URL*. If no *URL* is provided, the contents of the\n script will be inserted directly into the HTML header, preserving\n portability at the price of efficiency. If you plan to use math on\n several pages, it is much better to link to a copy of the script,\n so it can be cached.\n\n`--mathml`[`=`*URL*]\n\n: Convert TeX math to MathML (in `docbook` as well as `html` and `html5`).\n In standalone `html` output, a small javascript (or a link to such a\n script if a *URL* is supplied) will be inserted that allows the MathML to\n be viewed on some browsers.\n\n`--jsmath`[`=`*URL*]\n\n: Use [jsMath] to display embedded TeX math in HTML output.\n The *URL* should point to the jsMath load script (e.g.\n `jsMath/easy/load.js`); if provided, it will be linked to in\n the header of standalone HTML documents. If a *URL* is not provided,\n no link to the jsMath load script will be inserted; it is then\n up to the author to provide such a link in the HTML template.\n\n`--mathjax`[`=`*URL*]\n\n: Use [MathJax] to display embedded TeX math in HTML output.\n The *URL* should point to the `MathJax.js` load script.\n If a *URL* is not provided, a link to the MathJax CDN will\n be inserted.\n\n`--gladtex`\n\n: Enclose TeX math in `` tags in HTML output. These can then\n be processed by [gladTeX] to produce links to images of the typeset\n formulas.\n\n`--mimetex`[`=`*URL*]\n\n: Render TeX math using the [mimeTeX] CGI script. If *URL* is not\n specified, it is assumed that the script is at `/cgi-bin/mimetex.cgi`.\n\n`--webtex`[`=`*URL*]\n\n: Render TeX formulas using an external script that converts TeX\n formulas to images. The formula will be concatenated with the URL\n provided. If *URL* is not specified, the Google Chart API will be used.\n\n`--katex`[`=`*URL*]\n\n: Use [KaTeX] to display embedded TeX math in HTML output.\n The *URL* should point to the `katex.js` load script. If a *URL* is\n not provided, a link to the KaTeX CDN will be inserted.\n\n`--katex-stylesheet=`*URL*\n\n: The *URL* should point to the `katex.css` stylesheet. If this option is\n not specified, a link to the KaTeX CDN will be inserted. Note that this\n option does not imply `--katex`.\n\nOptions for wrapper scripts\n---------------------------\n\n`--dump-args`\n\n: Print information about command-line arguments to *stdout*, then exit.\n This option is intended primarily for use in wrapper scripts.\n The first line of output contains the name of the output file specified\n with the `-o` option, or `-` (for *stdout*) if no output file was\n specified. The remaining lines contain the command-line arguments,\n one per line, in the order they appear. These do not include regular\n Pandoc options and their arguments, but do include any options appearing\n after a `--` separator at the end of the line.\n\n`--ignore-args`\n\n: Ignore command-line arguments (for use in wrapper scripts).\n Regular Pandoc options are not ignored. Thus, for example,\n\n pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1\n\n is equivalent to\n\n pandoc -o foo.html -s\n\n[LaTeXMathML]: http://math.etsu.edu/LaTeXMathML/\n[jsMath]: http://www.math.union.edu/~dpvc/jsmath/\n[MathJax]: http://www.mathjax.org/\n[gladTeX]: http://ans.hsh.no/home/mgg/gladtex/\n[mimeTeX]: http://www.forkosh.com/mimetex.html\n[CSL]: http://CitationStyles.org\n\nTemplates\n=========\n\nWhen the `-s/--standalone` option is used, pandoc uses a template to\nadd header and footer material that is needed for a self-standing\ndocument. To see the default template that is used, just type\n\n pandoc -D FORMAT\n\nwhere `FORMAT` is the name of the output format. A custom template\ncan be specified using the `--template` option. You can also override\nthe system default templates for a given output format `FORMAT`\nby putting a file `templates/default.FORMAT` in the user data\ndirectory (see `--data-dir`, above). *Exceptions:* For `odt` output,\ncustomize the `default.opendocument` template. For `pdf` output,\ncustomize the `default.latex` template.\n\nTemplates may contain *variables*. Variable names are sequences of\nalphanumerics, `-`, and `_`, starting with a letter. A variable name\nsurrounded by `$` signs will be replaced by its value. For example,\nthe string `$title$` in\n\n $title$\n\nwill be replaced by the document title.\n\nTo write a literal `$` in a template, use `$$`.\n\nSome variables are set automatically by pandoc. These vary somewhat\ndepending on the output format, but include metadata fields (such\nas `title`, `author`, and `date`) as well as the following:\n\n`header-includes`\n: contents specified by `-H/--include-in-header` (may have multiple\n values)\n\n`toc`\n: non-null value if `--toc/--table-of-contents` was specified\n\n`include-before`\n: contents specified by `-B/--include-before-body` (may have\n multiple values)\n\n`include-after`\n: contents specified by `-A/--include-after-body` (may have\n multiple values)\n\n`body`\n: body of document\n\n`lang`\n: language code for HTML or LaTeX documents\n\n`slidy-url`\n: base URL for Slidy documents (defaults to\n `http://www.w3.org/Talks/Tools/Slidy2`)\n\n`slideous-url`\n: base URL for Slideous documents (defaults to `slideous`)\n\n`s5-url`\n: base URL for S5 documents (defaults to `s5/default`)\n\n`revealjs-url`\n: base URL for reveal.js documents (defaults to `reveal.js`)\n\n`theme`\n: reveal.js or LaTeX beamer theme\n\n`transition`\n: reveal.js transition\n\n`fontsize`\n: font size (10pt, 11pt, 12pt) for LaTeX documents\n\n`documentclass`\n: document class for LaTeX documents\n\n`classoption`\n: option for LaTeX documentclass, e.g. `oneside`; may be repeated\n for multiple options\n\n`geometry`\n: options for LaTeX `geometry` class, e.g. `margin=1in`;\n may be repeated for multiple options\n\n`linestretch`\n: adjusts line spacing (requires the `setspace` package)\n\n`fontfamily`\n: font package to use for LaTeX documents (with pdflatex):\n TeXLive has `bookman` (Bookman), `utopia` or `fourier` (Utopia),\n `fouriernc` (New Century Schoolbook), `times` or `txfonts` (Times),\n `mathpazo` or `pxfonts` or `mathpple` (Palatino),\n `libertine` (Linux Libertine), `arev` (Arev Sans),\n and the default `lmodern`, among others.\n\n`mainfont`, `sansfont`, `monofont`, `mathfont`, `CJKmainfont`\n: fonts for LaTeX documents (works only with xelatex\n and lualatex). Note that if `CJKmainfont` is used,\n the `xeCJK` package must be available.\n\n`colortheme`\n: colortheme for LaTeX beamer documents\n\n`fonttheme`\n: fonttheme for LaTeX beamer documents\n\n`linkcolor`\n: color for internal links in LaTeX documents (`red`, `green`,\n `magenta`, `cyan`, `blue`, `black`)\n\n`toccolor`\n: color for links in table of contents in LaTeX documents\n\n`urlcolor`\n: color for external links in LaTeX documents\n\n`citecolor`\n: color for citation links in LaTeX documents\n\n`links-as-notes`\n: causes links to be printed as footnotes in LaTeX documents\n\n`toc`\n: include table of contents in LaTeX documents\n\n`toc-depth`\n: level of section to include in table of contents in LaTeX documents\n\n`toc-title`\n: title of table of contents (works only with EPUB and docx)\n\n`lof`\n: include list of figures in LaTeX documents\n\n`lot`\n: include list of tables in LaTeX documents\n\n`bibliography`\n: bibliography to use for resolving references\n\n`biblio-style`\n: bibliography style in LaTeX, when used with `--natbib`\n\n`section`\n: section number in man pages\n\n`header`\n: header in man pages\n\n`footer`\n: footer in man pages\n\nVariables may be set at the command line using the `-V/--variable`\noption. Variables set in this way override metadata fields with\nthe same name.\n\nTemplates may contain conditionals. The syntax is as follows:\n\n $if(variable)$\n X\n $else$\n Y\n $endif$\n\nThis will include `X` in the template if `variable` has a non-null\nvalue; otherwise it will include `Y`. `X` and `Y` are placeholders for\nany valid template text, and may include interpolated variables or other\nconditionals. The `$else$` section may be omitted.\n\nWhen variables can have multiple values (for example, `author` in\na multi-author document), you can use the `$for$` keyword:\n\n $for(author)$\n \n $endfor$\n\nYou can optionally specify a separator to be used between\nconsecutive items:\n\n $for(author)$$author$$sep$, $endfor$\n\nA dot can be used to select a field of a variable that takes\nan object as its value. So, for example:\n\n $author.name$ ($author.affiliation$)\n\nIf you use custom templates, you may need to revise them as pandoc\nchanges. We recommend tracking the changes in the default templates,\nand modifying your custom templates accordingly. An easy way to do this\nis to fork the pandoc-templates repository\n() and merge in changes after each\npandoc release.\n\nPandoc's markdown\n=================\n\nPandoc understands an extended and slightly revised version of\nJohn Gruber's [markdown] syntax. This document explains the syntax,\nnoting differences from standard markdown. Except where noted, these\ndifferences can be suppressed by using the `markdown_strict` format instead\nof `markdown`. An extensions can be enabled by adding `+EXTENSION`\nto the format name and disabled by adding `-EXTENSION`. For example,\n`markdown_strict+footnotes` is strict markdown with footnotes\nenabled, while `markdown-footnotes-pipe_tables` is pandoc's\nmarkdown without footnotes or pipe tables.\n\nPhilosophy\n----------\n\nMarkdown is designed to be easy to write, and, even more importantly,\neasy to read:\n\n> A Markdown-formatted document should be publishable as-is, as plain\n> text, without looking like it's been marked up with tags or formatting\n> instructions.\n> -- [John Gruber](http://daringfireball.net/projects/markdown/syntax#philosophy)\n\nThis principle has guided pandoc's decisions in finding syntax for\ntables, footnotes, and other extensions.\n\nThere is, however, one respect in which pandoc's aims are different\nfrom the original aims of markdown. Whereas markdown was originally\ndesigned with HTML generation in mind, pandoc is designed for multiple\noutput formats. Thus, while pandoc allows the embedding of raw HTML,\nit discourages it, and provides other, non-HTMLish ways of representing\nimportant document elements like definition lists, tables, mathematics, and\nfootnotes.\n\nParagraphs\n----------\n\nA paragraph is one or more lines of text followed by one or more blank lines.\nNewlines are treated as spaces, so you can reflow your paragraphs as you like.\nIf you need a hard line break, put two or more spaces at the end of a line.\n\n#### Extension: `escaped_line_breaks` ####\n\nA backslash followed by a newline is also a hard line break.\nNote: in multiline and grid table cells, this is the only way\nto create a hard line break, since trailing spaces in the cells\nare ignored.\n\nHeaders\n-------\n\nThere are two kinds of headers, Setext and atx.\n\n### Setext-style headers ###\n\nA setext-style header is a line of text \"underlined\" with a row of `=` signs\n(for a level one header) or `-` signs (for a level two header):\n\n A level-one header\n ==================\n\n A level-two header\n ------------------\n\nThe header text can contain inline formatting, such as emphasis (see\n[Inline formatting](#inline-formatting), below).\n\n\n### Atx-style headers ###\n\nAn Atx-style header consists of one to six `#` signs and a line of\ntext, optionally followed by any number of `#` signs. The number of\n`#` signs at the beginning of the line is the header level:\n\n ## A level-two header\n\n ### A level-three header ###\n\nAs with setext-style headers, the header text can contain formatting:\n\n # A level-one header with a [link](/url) and *emphasis*\n\n#### Extension: `blank_before_header` ####\n\nStandard markdown syntax does not require a blank line before a header.\nPandoc does require this (except, of course, at the beginning of the\ndocument). The reason for the requirement is that it is all too easy for a\n`#` to end up at the beginning of a line by accident (perhaps through line\nwrapping). Consider, for example:\n\n I like several of their flavors of ice cream:\n #22, for example, and #5.\n\n\n### Header identifiers in HTML, LaTeX, and ConTeXt ###\n\n#### Extension: `header_attributes` ####\n\nHeaders can be assigned attributes using this syntax at the end\nof the line containing the header text:\n\n {#identifier .class .class key=value key=value}\n\nThus, for example, the following headers will all be assigned the identifier\n`foo`:\n\n # My header {#foo}\n\n ## My header ## {#foo}\n\n My other header {#foo}\n ---------------\n\n(This syntax is compatible with [PHP Markdown Extra].)\n\nNote that although this syntax allows assignment of classes and key/value\nattributes, writers generally don't use all of this information. Identifiers,\nclasses, and key/value attributes are used in HTML and HTML-based formats such\nas EPUB and slidy. Identifiers are used for labels and link anchors in the\nLaTeX, ConTeXt, Textile, and AsciiDoc writers.\n\nHeaders with the class `unnumbered` will not be numbered, even if\n`--number-sections` is specified. A single hyphen (`-`) in an attribute\ncontext is equivalent to `.unnumbered`, and preferable in non-English\ndocuments. So,\n\n # My header {-}\n\nis just the same as\n\n # My header {.unnumbered}\n\n#### Extension: `auto_identifiers` ####\n\nA header without an explicitly specified identifier will be\nautomatically assigned a unique identifier based on the header text.\nTo derive the identifier from the header text,\n\n - Remove all formatting, links, etc.\n - Remove all footnotes.\n - Remove all punctuation, except underscores, hyphens, and periods.\n - Replace all spaces and newlines with hyphens.\n - Convert all alphabetic characters to lowercase.\n - Remove everything up to the first letter (identifiers may\n not begin with a number or punctuation mark).\n - If nothing is left after this, use the identifier `section`.\n\nThus, for example,\n\n Header Identifier\n ------------------------------- ----------------------------\n Header identifiers in HTML `header-identifiers-in-html`\n *Dogs*?--in *my* house? `dogs--in-my-house`\n [HTML], [S5], or [RTF]? `html-s5-or-rtf`\n 3. Applications `applications`\n 33 `section`\n\nThese rules should, in most cases, allow one to determine the identifier\nfrom the header text. The exception is when several headers have the\nsame text; in this case, the first will get an identifier as described\nabove; the second will get the same identifier with `-1` appended; the\nthird with `-2`; and so on.\n\nThese identifiers are used to provide link targets in the table of\ncontents generated by the `--toc|--table-of-contents` option. They\nalso make it easy to provide links from one section of a document to\nanother. A link to this section, for example, might look like this:\n\n See the section on\n [header identifiers](#header-identifiers-in-html-latex-and-context).\n\nNote, however, that this method of providing links to sections works\nonly in HTML, LaTeX, and ConTeXt formats.\n\nIf the `--section-divs` option is specified, then each section will\nbe wrapped in a `div` (or a `section`, if `--html5` was specified),\nand the identifier will be attached to the enclosing `
`\n(or `
`) tag rather than the header itself. This allows entire\nsections to be manipulated using javascript or treated differently in\nCSS.\n\n#### Extension: `implicit_header_references` ####\n\nPandoc behaves as if reference links have been defined for each header.\nSo, instead of\n\n [header identifiers](#header-identifiers-in-html)\n\nyou can simply write\n\n [header identifiers]\n\nor\n\n [header identifiers][]\n\nor\n\n [the section on header identifiers][header identifiers]\n\nIf there are multiple headers with identical text, the corresponding\nreference will link to the first one only, and you will need to use explicit\nlinks to link to the others, as described above.\n\nLike regular reference links, these references are case-insensitive.\n\nExplicit link reference definitions always take priority over\nimplicit header references. So, in the following example, the\nlink will point to `bar`, not to `#foo`:\n\n # Foo\n\n [foo]: bar\n\n See [foo]\n\nBlock quotations\n----------------\n\nMarkdown uses email conventions for quoting blocks of text.\nA block quotation is one or more paragraphs or other block elements\n(such as lists or headers), with each line preceded by a `>` character\nand a space. (The `>` need not start at the left margin, but it should\nnot be indented more than three spaces.)\n\n > This is a block quote. This\n > paragraph has two lines.\n >\n > 1. This is a list inside a block quote.\n > 2. Second item.\n\nA \"lazy\" form, which requires the `>` character only on the first\nline of each block, is also allowed:\n\n > This is a block quote. This\n paragraph has two lines.\n\n > 1. This is a list inside a block quote.\n 2. Second item.\n\nAmong the block elements that can be contained in a block quote are\nother block quotes. That is, block quotes can be nested:\n\n > This is a block quote.\n >\n > > A block quote within a block quote.\n\n#### Extension: `blank_before_blockquote` ####\n\nStandard markdown syntax does not require a blank line before a block\nquote. Pandoc does require this (except, of course, at the beginning of the\ndocument). The reason for the requirement is that it is all too easy for a\n`>` to end up at the beginning of a line by accident (perhaps through line\nwrapping). So, unless the `markdown_strict` format is used, the following does\nnot produce a nested block quote in pandoc:\n\n > This is a block quote.\n >> Nested.\n\n\nVerbatim (code) blocks\n----------------------\n\n### Indented code blocks ###\n\nA block of text indented four spaces (or one tab) is treated as verbatim\ntext: that is, special characters do not trigger special formatting,\nand all spaces and line breaks are preserved. For example,\n\n if (a > 3) {\n moveShip(5 * gravity, DOWN);\n }\n\nThe initial (four space or one tab) indentation is not considered part\nof the verbatim text, and is removed in the output.\n\nNote: blank lines in the verbatim text need not begin with four spaces.\n\n\n### Fenced code blocks ###\n\n#### Extension: `fenced_code_blocks` ####\n\nIn addition to standard indented code blocks, Pandoc supports\n*fenced* code blocks. These begin with a row of three or more\ntildes (`~`) and end with a row of tildes that must be at least as long as\nthe starting row. Everything between these lines is treated as code. No\nindentation is necessary:\n\n ~~~~~~~\n if (a > 3) {\n moveShip(5 * gravity, DOWN);\n }\n ~~~~~~~\n\nLike regular code blocks, fenced code blocks must be separated\nfrom surrounding text by blank lines.\n\nIf the code itself contains a row of tildes or backticks, just use a longer\nrow of tildes or backticks at the start and end:\n\n ~~~~~~~~~~~~~~~~\n ~~~~~~~~~~\n code including tildes\n ~~~~~~~~~~\n ~~~~~~~~~~~~~~~~\n\n#### Extension: `backtick_code_blocks` ####\n\nSame as `fenced_code_blocks`, but uses backticks (`` ` ``) instead of tildes\n(`~`).\n\n#### Extension: `fenced_code_attributes` ####\n\nOptionally, you may attach attributes to fenced or backtick code block using\nthis syntax:\n\n ~~~~ {#mycode .haskell .numberLines startFrom=\"100\"}\n qsort [] = []\n qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++\n qsort (filter (>= x) xs)\n ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~\n\nHere `mycode` is an identifier, `haskell` and `numberLines` are classes, and\n`startFrom` is an attribute with value `100`. Some output formats can use this\ninformation to do syntax highlighting. Currently, the only output formats\nthat uses this information are HTML and LaTeX. If highlighting is supported\nfor your output format and language, then the code block above will appear\nhighlighted, with numbered lines. (To see which languages are supported, do\n`pandoc --version`.) Otherwise, the code block above will appear as follows:\n\n 
\n      \n      ...\n      \n
\n\nA shortcut form can also be used for specifying the language of\nthe code block:\n\n ```haskell\n qsort [] = []\n ```\n\nThis is equivalent to:\n\n ``` {.haskell}\n qsort [] = []\n ```\n\nIf the `fenced_code_attributes` extension is disabled, but\ninput contains class attribute(s) for the codeblock, the first\nclass attribute will be printed after the opening fence as a bare\nword.\n\nTo prevent all highlighting, use the `--no-highlight` flag.\nTo set the highlighting style, use `--highlight-style`.\nFor more information on highlighting, see [Syntax highlighting],\nbelow.\n\nLine blocks\n-----------\n\n#### Extension: `line_blocks` ####\n\nA line block is a sequence of lines beginning with a vertical bar (`|`)\nfollowed by a space. The division into lines will be preserved in\nthe output, as will any leading spaces; otherwise, the lines will\nbe formatted as markdown. This is useful for verse and addresses:\n\n | The limerick packs laughs anatomical\n | In space that is quite economical.\n | But the good ones I've seen\n | So seldom are clean\n | And the clean ones so seldom are comical\n\n | 200 Main St.\n | Berkeley, CA 94718\n\nThe lines can be hard-wrapped if needed, but the continuation\nline must begin with a space.\n\n | The Right Honorable Most Venerable and Righteous Samuel L.\n Constable, Jr.\n | 200 Main St.\n | Berkeley, CA 94718\n\nThis syntax is borrowed from [reStructuredText].\n\nLists\n-----\n\n### Bullet lists ###\n\nA bullet list is a list of bulleted list items. A bulleted list\nitem begins with a bullet (`*`, `+`, or `-`). Here is a simple\nexample:\n\n * one\n * two\n * three\n\nThis will produce a \"compact\" list. If you want a \"loose\" list, in which\neach item is formatted as a paragraph, put spaces between the items:\n\n * one\n\n * two\n\n * three\n\nThe bullets need not be flush with the left margin; they may be\nindented one, two, or three spaces. The bullet must be followed\nby whitespace.\n\nList items look best if subsequent lines are flush with the first\nline (after the bullet):\n\n * here is my first\n list item.\n * and my second.\n\nBut markdown also allows a \"lazy\" format:\n\n * here is my first\n list item.\n * and my second.\n\n### The four-space rule ###\n\nA list item may contain multiple paragraphs and other block-level\ncontent. However, subsequent paragraphs must be preceded by a blank line\nand indented four spaces or a tab. The list will look better if the first\nparagraph is aligned with the rest:\n\n * First paragraph.\n\n Continued.\n\n * Second paragraph. With a code block, which must be indented\n eight spaces:\n\n { code }\n\nList items may include other lists. In this case the preceding blank\nline is optional. The nested list must be indented four spaces or\none tab:\n\n * fruits\n + apples\n - macintosh\n - red delicious\n + pears\n + peaches\n * vegetables\n + broccoli\n + chard\n\nAs noted above, markdown allows you to write list items \"lazily,\" instead of\nindenting continuation lines. However, if there are multiple paragraphs or\nother blocks in a list item, the first line of each must be indented.\n\n + A lazy, lazy, list\n item.\n\n + Another one; this looks\n bad but is legal.\n\n Second paragraph of second\n list item.\n\n**Note:** Although the four-space rule for continuation paragraphs\ncomes from the official [markdown syntax guide], the reference implementation,\n`Markdown.pl`, does not follow it. So pandoc will give different results than\n`Markdown.pl` when authors have indented continuation paragraphs fewer than\nfour spaces.\n\nThe [markdown syntax guide] is not explicit whether the four-space\nrule applies to *all* block-level content in a list item; it only\nmentions paragraphs and code blocks. But it implies that the rule\napplies to all block-level content (including nested lists), and\npandoc interprets it that way.\n\n [markdown syntax guide]:\n http://daringfireball.net/projects/markdown/syntax#list\n\n### Ordered lists ###\n\nOrdered lists work just like bulleted lists, except that the items\nbegin with enumerators rather than bullets.\n\nIn standard markdown, enumerators are decimal numbers followed\nby a period and a space. The numbers themselves are ignored, so\nthere is no difference between this list:\n\n 1. one\n 2. two\n 3. three\n\nand this one:\n\n 5. one\n 7. two\n 1. three\n\n#### Extension: `fancy_lists` ####\n\nUnlike standard markdown, Pandoc allows ordered list items to be marked\nwith uppercase and lowercase letters and roman numerals, in addition to\narabic numerals. List markers may be enclosed in parentheses or followed by a\nsingle right-parentheses or period. They must be separated from the\ntext that follows by at least one space, and, if the list marker is a\ncapital letter with a period, by at least two spaces.[^2]\n\n[^2]: The point of this rule is to ensure that normal paragraphs\n starting with people's initials, like\n\n B. Russell was an English philosopher.\n\n do not get treated as list items.\n\n This rule will not prevent\n\n (C) 2007 Joe Smith\n\n from being interpreted as a list item. In this case, a backslash\n escape can be used:\n\n (C\\) 2007 Joe Smith\n\nThe `fancy_lists` extension also allows '`#`' to be used as an\nordered list marker in place of a numeral:\n\n #. one\n #. two\n\n#### Extension: `startnum` ####\n\nPandoc also pays attention to the type of list marker used, and to the\nstarting number, and both of these are preserved where possible in the\noutput format. Thus, the following yields a list with numbers followed\nby a single parenthesis, starting with 9, and a sublist with lowercase\nroman numerals:\n\n 9) Ninth\n 10) Tenth\n 11) Eleventh\n i. subone\n ii. subtwo\n iii. subthree\n\nPandoc will start a new list each time a different type of list\nmarker is used. So, the following will create three lists:\n\n (2) Two\n (5) Three\n 1. Four\n * Five\n\nIf default list markers are desired, use `#.`:\n\n #. one\n #. two\n #. three\n\n\n### Definition lists ###\n\n#### Extension: `definition_lists` ####\n\nPandoc supports definition lists, using the syntax of\n[PHP Markdown Extra] with some extensions.[^3]\n\n Term 1\n\n : Definition 1\n\n Term 2 with *inline markup*\n\n : Definition 2\n\n { some code, part of Definition 2 }\n\n Third paragraph of definition 2.\n\nEach term must fit on one line, which may optionally be followed by\na blank line, and must be followed by one or more definitions.\nA definition begins with a colon or tilde, which may be indented one\nor two spaces.\n\nA term may have multiple definitions, and each definition may consist of one or\nmore block elements (paragraph, code block, list, etc.), each indented four\nspaces or one tab stop. The body of the definition (including the first line,\naside from the colon or tilde) should be indented four spaces. However,\nas with other markdown lists, you can \"lazily\" omit indentation except\nat the beginning of a paragraph or other block element:\n\n Term 1\n\n : Definition\n with lazy continuation.\n\n Second paragraph of the definition.\n\nIf you leave space before the definition (as in the example above),\nthe text of the definition will be treated as a paragraph. In some\noutput formats, this will mean greater spacing between term/definition\npairs. For a more compact definition list, omit the space before the\ndefinition:\n\n Term 1\n ~ Definition 1\n\n Term 2\n ~ Definition 2a\n ~ Definition 2b\n\nNote that space between items in a definition list is required.\n(A variant that loosens this requirement, but disallows \"lazy\"\nhard wrapping, can be activated with `compact_definition_lists`: see\n[Non-pandoc extensions](#non-pandoc-extensions), below.)\n\n[^3]: I have been influenced by the suggestions of [David Wheeler](http://www.justatheory.com/computers/markup/modest-markdown-proposal.html).\n\n[PHP Markdown Extra]: http://www.michelf.com/projects/php-markdown/extra/\n\n\n### Numbered example lists ###\n\n#### Extension: `example_lists` ####\n\nThe special list marker `@` can be used for sequentially numbered\nexamples. The first list item with a `@` marker will be numbered '1',\nthe next '2', and so on, throughout the document. The numbered examples\nneed not occur in a single list; each new list using `@` will take up\nwhere the last stopped. So, for example:\n\n (@) My first example will be numbered (1).\n (@) My second example will be numbered (2).\n\n Explanation of examples.\n\n (@) My third example will be numbered (3).\n\nNumbered examples can be labeled and referred to elsewhere in the\ndocument:\n\n (@good) This is a good example.\n\n As (@good) illustrates, ...\n\nThe label can be any string of alphanumeric characters, underscores,\nor hyphens.\n\n\n### Compact and loose lists ###\n\nPandoc behaves differently from `Markdown.pl` on some \"edge\ncases\" involving lists. Consider this source:\n\n + First\n + Second:\n \t- Fee\n \t- Fie\n \t- Foe\n\n + Third\n\nPandoc transforms this into a \"compact list\" (with no `

` tags around\n\"First\", \"Second\", or \"Third\"), while markdown puts `

` tags around\n\"Second\" and \"Third\" (but not \"First\"), because of the blank space\naround \"Third\". Pandoc follows a simple rule: if the text is followed by\na blank line, it is treated as a paragraph. Since \"Second\" is followed\nby a list, and not a blank line, it isn't treated as a paragraph. The\nfact that the list is followed by a blank line is irrelevant. (Note:\nPandoc works this way even when the `markdown_strict` format is specified. This\nbehavior is consistent with the official markdown syntax description,\neven though it is different from that of `Markdown.pl`.)\n\n\n### Ending a list ###\n\nWhat if you want to put an indented code block after a list?\n\n - item one\n - item two\n\n { my code block }\n\nTrouble! Here pandoc (like other markdown implementations) will treat\n`{ my code block }` as the second paragraph of item two, and not as\na code block.\n\nTo \"cut off\" the list after item two, you can insert some non-indented\ncontent, like an HTML comment, which won't produce visible output in\nany format:\n\n - item one\n - item two\n\n \n\n { my code block }\n\nYou can use the same trick if you want two consecutive lists instead\nof one big list:\n\n 1. one\n 2. two\n 3. three\n\n \n\n 1. uno\n 2. dos\n 3. tres\n\nHorizontal rules\n----------------\n\nA line containing a row of three or more `*`, `-`, or `_` characters\n(optionally separated by spaces) produces a horizontal rule:\n\n * * * *\n\n ---------------\n\n\nTables\n------\n\nFour kinds of tables may be used. The first three kinds presuppose the use of\na fixed-width font, such as Courier. The fourth kind can be used with\nproportionally spaced fonts, as it does not require lining up columns.\n\n#### Extension: `table_captions` ####\n\nA caption may optionally be provided with all 4 kinds of tables (as\nillustrated in the examples below). A caption is a paragraph beginning\nwith the string `Table:` (or just `:`), which will be stripped off.\nIt may appear either before or after the table.\n\n#### Extension: `simple_tables` ####\n\nSimple tables look like this:\n\n Right Left Center Default\n ------- ------ ---------- -------\n 12 12 12 12\n 123 123 123 123\n 1 1 1 1\n\n Table: Demonstration of simple table syntax.\n\nThe headers and table rows must each fit on one line. Column\nalignments are determined by the position of the header text relative\nto the dashed line below it:[^4]\n\n - If the dashed line is flush with the header text on the right side\n but extends beyond it on the left, the column is right-aligned.\n - If the dashed line is flush with the header text on the left side\n but extends beyond it on the right, the column is left-aligned.\n - If the dashed line extends beyond the header text on both sides,\n the column is centered.\n - If the dashed line is flush with the header text on both sides,\n the default alignment is used (in most cases, this will be left).\n\n[^4]: This scheme is due to Michel Fortin, who proposed it on the\n [Markdown discussion list](http://six.pairlist.net/pipermail/markdown-discuss/2005-March/001097.html).\n\nThe table must end with a blank line, or a line of dashes followed by\na blank line.\n\nThe column headers may be omitted, provided a dashed line is used\nto end the table. For example:\n\n ------- ------ ---------- -------\n 12 12 12 12\n 123 123 123 123\n 1 1 1 1\n ------- ------ ---------- -------\n\nWhen headers are omitted, column alignments are determined on the basis\nof the first line of the table body. So, in the tables above, the columns\nwould be right, left, center, and right aligned, respectively.\n\n#### Extension: `multiline_tables` ####\n\nMultiline tables allow headers and table rows to span multiple lines\nof text (but cells that span multiple columns or rows of the table are\nnot supported). Here is an example:\n\n -------------------------------------------------------------\n Centered Default Right Left\n Header Aligned Aligned Aligned\n ----------- ------- --------------- -------------------------\n First row 12.0 Example of a row that\n spans multiple lines.\n\n Second row 5.0 Here's another one. Note\n the blank line between\n rows.\n -------------------------------------------------------------\n\n Table: Here's the caption. It, too, may span\n multiple lines.\n\nThese work like simple tables, but with the following differences:\n\n - They must begin with a row of dashes, before the header text\n (unless the headers are omitted).\n - They must end with a row of dashes, then a blank line.\n - The rows must be separated by blank lines.\n\nIn multiline tables, the table parser pays attention to the widths of\nthe columns, and the writers try to reproduce these relative widths in\nthe output. So, if you find that one of the columns is too narrow in the\noutput, try widening it in the markdown source.\n\nHeaders may be omitted in multiline tables as well as simple tables:\n\n ----------- ------- --------------- -------------------------\n First row 12.0 Example of a row that\n spans multiple lines.\n\n Second row 5.0 Here's another one. Note\n the blank line between\n rows.\n ----------- ------- --------------- -------------------------\n\n : Here's a multiline table without headers.\n\nIt is possible for a multiline table to have just one row, but the row\nshould be followed by a blank line (and then the row of dashes that ends\nthe table), or the table may be interpreted as a simple table.\n\n#### Extension: `grid_tables` ####\n\nGrid tables look like this:\n\n : Sample grid table.\n\n +---------------+---------------+--------------------+\n | Fruit | Price | Advantages |\n +===============+===============+====================+\n | Bananas | $1.34 | - built-in wrapper |\n | | | - bright color |\n +---------------+---------------+--------------------+\n | Oranges | $2.10 | - cures scurvy |\n | | | - tasty |\n +---------------+---------------+--------------------+\n\nThe row of `=`s separates the header from the table body, and can be\nomitted for a headerless table. The cells of grid tables may contain\narbitrary block elements (multiple paragraphs, code blocks, lists,\netc.). Alignments are not supported, nor are cells that span multiple\ncolumns or rows. Grid tables can be created easily using [Emacs table mode].\n\n [Emacs table mode]: http://table.sourceforge.net/\n\n#### Extension: `pipe_tables` ####\n\nPipe tables look like this:\n\n | Right | Left | Default | Center |\n |------:|:-----|---------|:------:|\n | 12 | 12 | 12 | 12 |\n | 123 | 123 | 123 | 123 |\n | 1 | 1 | 1 | 1 |\n\n : Demonstration of pipe table syntax.\n\nThe syntax is [the same as in PHP markdown extra]. The beginning and\nending pipe characters are optional, but pipes are required between all\ncolumns. The colons indicate column alignment as shown. The header\ncannot be omitted. To simulate a headerless table, include a header\nwith blank cells.\n\nSince the pipes indicate column boundaries, columns need not be vertically\naligned, as they are in the above example. So, this is a perfectly\nlegal (though ugly) pipe table:\n\n fruit| price\n -----|-----:\n apple|2.05\n pear|1.37\n orange|3.09\n\nThe cells of pipe tables cannot contain block elements like paragraphs\nand lists, and cannot span multiple lines. Note also that in LaTeX/PDF\noutput, the cells produced by pipe tables will not wrap, since there\nis no information available about relative widths. If you want content\nto wrap within cells, use multiline or grid tables.\n\n [the same as in PHP markdown extra]:\n http://michelf.ca/projects/php-markdown/extra/#table\n\nNote: Pandoc also recognizes pipe tables of the following\nform, as can be produced by Emacs' orgtbl-mode:\n\n | One | Two |\n |-----+-------|\n | my | table |\n | is | nice |\n\nThe difference is that `+` is used instead of `|`. Other orgtbl features\nare not supported. In particular, to get non-default column alignment,\nyou'll need to add colons as above.\n\nMetadata blocks\n---------------\n\n#### Extension: `pandoc_title_block` ####\n\nIf the file begins with a title block\n\n % title\n % author(s) (separated by semicolons)\n % date\n\nit will be parsed as bibliographic information, not regular text. (It\nwill be used, for example, in the title of standalone LaTeX or HTML\noutput.) The block may contain just a title, a title and an author,\nor all three elements. If you want to include an author but no\ntitle, or a title and a date but no author, you need a blank line:\n\n %\n % Author\n\n % My title\n %\n % June 15, 2006\n\nThe title may occupy multiple lines, but continuation lines must\nbegin with leading space, thus:\n\n % My title\n on multiple lines\n\nIf a document has multiple authors, the authors may be put on\nseparate lines with leading space, or separated by semicolons, or\nboth. So, all of the following are equivalent:\n\n % Author One\n Author Two\n\n % Author One; Author Two\n\n % Author One;\n Author Two\n\nThe date must fit on one line.\n\nAll three metadata fields may contain standard inline formatting\n(italics, links, footnotes, etc.).\n\nTitle blocks will always be parsed, but they will affect the output only\nwhen the `--standalone` (`-s`) option is chosen. In HTML output, titles\nwill appear twice: once in the document head -- this is the title that\nwill appear at the top of the window in a browser -- and once at the\nbeginning of the document body. The title in the document head can have\nan optional prefix attached (`--title-prefix` or `-T` option). The title\nin the body appears as an H1 element with class \"title\", so it can be\nsuppressed or reformatted with CSS. If a title prefix is specified with\n`-T` and no title block appears in the document, the title prefix will\nbe used by itself as the HTML title.\n\nThe man page writer extracts a title, man page section number, and\nother header and footer information from the title line. The title\nis assumed to be the first word on the title line, which may optionally\nend with a (single-digit) section number in parentheses. (There should\nbe no space between the title and the parentheses.) Anything after\nthis is assumed to be additional footer and header text. A single pipe\ncharacter (`|`) should be used to separate the footer text from the header\ntext. Thus,\n\n % PANDOC(1)\n\nwill yield a man page with the title `PANDOC` and section 1.\n\n % PANDOC(1) Pandoc User Manuals\n\nwill also have \"Pandoc User Manuals\" in the footer.\n\n % PANDOC(1) Pandoc User Manuals | Version 4.0\n\nwill also have \"Version 4.0\" in the header.\n\n#### Extension: `yaml_metadata_block` ####\n\nA YAML metadata block is a valid YAML object, delimited by a line of three\nhyphens (`---`) at the top and a line of three hyphens (`---`) or three dots\n(`...`) at the bottom. A YAML metadata block may occur anywhere in the\ndocument, but if it is not at the beginning, it must be preceded by a blank\nline. (Note that, because of the way pandoc concatenates input files when\nseveral are provided, you may also keep the metadata in a separate YAML file\nand pass it to pandoc as an argument, along with your markdown files:\n\n pandoc chap1.md chap2.md chap3.md metadata.yaml -s -o book.html\n\nJust be sure that the YAML file begins with `---` and ends with `---` or\n`...`.)\n\nMetadata will be taken from the fields of the YAML object and added to any\nexisting document metadata. Metadata can contain lists and objects (nested\narbitrarily), but all string scalars will be interpreted as markdown. Fields\nwith names ending in an underscore will be ignored by pandoc. (They may be\ngiven a role by external processors.)\n\nA document may contain multiple metadata blocks. The metadata fields will\nbe combined through a *left-biased union*: if two metadata blocks attempt\nto set the same field, the value from the first block will be taken.\n\nWhen pandoc is used with `-t markdown` to create a markdown document,\na YAML metadata block will be produced only if the `-s/--standalone`\noption is used. All of the metadata will appear in a single block\nat the beginning of the document.\n\nNote that YAML escaping rules must be followed. Thus, for example,\nif a title contains a colon, it must be quoted. The pipe character\n(`|`) can be used to begin an indented block that will be interpreted\nliterally, without need for escaping. This form is necessary\nwhen the field contains blank lines:\n\n ---\n title: 'This is the title: it contains a colon'\n author:\n - name: Author One\n affiliation: University of Somewhere\n - name: Author Two\n affiliation: University of Nowhere\n tags: [nothing, nothingness]\n abstract: |\n This is the abstract.\n\n It consists of two paragraphs.\n ...\n\nTemplate variables will be set automatically from the metadata. Thus, for\nexample, in writing HTML, the variable `abstract` will be set to the HTML\nequivalent of the markdown in the `abstract` field:\n\n

This is the abstract.

\n

It consists of two paragraphs.

\n\nNote: The `author` variable in the default templates expects a simple list or\nstring. To use the structured authors in the example, you would need a\ncustom template. For example:\n\n $for(author)$\n $if(author.name)$\n $author.name$$if(author.affiliation)$ ($author.affiliation$)$endif$\n $else$\n $author$\n $endif$\n $endfor$\n\n\nBackslash escapes\n-----------------\n\n#### Extension: `all_symbols_escapable` ####\n\nExcept inside a code block or inline code, any punctuation or space\ncharacter preceded by a backslash will be treated literally, even if it\nwould normally indicate formatting. Thus, for example, if one writes\n\n *\\*hello\\**\n\none will get\n\n *hello*\n\ninstead of\n\n hello\n\nThis rule is easier to remember than standard markdown's rule,\nwhich allows only the following characters to be backslash-escaped:\n\n \\`*_{}[]()>#+-.!\n\n(However, if the `markdown_strict` format is used, the standard markdown rule\nwill be used.)\n\nA backslash-escaped space is parsed as a nonbreaking space. It will\nappear in TeX output as `~` and in HTML and XML as `\\ ` or\n`\\ `.\n\nA backslash-escaped newline (i.e. a backslash occurring at the end of\na line) is parsed as a hard line break. It will appear in TeX output as\n`\\\\` and in HTML as `
`. This is a nice alternative to\nmarkdown's \"invisible\" way of indicating hard line breaks using\ntwo trailing spaces on a line.\n\nBackslash escapes do not work in verbatim contexts.\n\nSmart punctuation\n-----------------\n\n#### Extension ####\n\nIf the `--smart` option is specified, pandoc will produce typographically\ncorrect output, converting straight quotes to curly quotes, `---` to\nem-dashes, `--` to en-dashes, and `...` to ellipses. Nonbreaking spaces\nare inserted after certain abbreviations, such as \"Mr.\"\n\nNote: if your LaTeX template uses the `csquotes` package, pandoc will\ndetect automatically this and use `\\enquote{...}` for quoted text.\n\nInline formatting\n-----------------\n\n### Emphasis ###\n\nTo *emphasize* some text, surround it with `*`s or `_`, like this:\n\n This text is _emphasized with underscores_, and this\n is *emphasized with asterisks*.\n\nDouble `*` or `_` produces **strong emphasis**:\n\n This is **strong emphasis** and __with underscores__.\n\nA `*` or `_` character surrounded by spaces, or backslash-escaped,\nwill not trigger emphasis:\n\n This is * not emphasized *, and \\*neither is this\\*.\n\n#### Extension: `intraword_underscores` ####\n\nBecause `_` is sometimes used inside words and identifiers,\npandoc does not interpret a `_` surrounded by alphanumeric\ncharacters as an emphasis marker. If you want to emphasize\njust part of a word, use `*`:\n\n feas*ible*, not feas*able*.\n\n\n### Strikeout ###\n\n#### Extension: `strikeout` ####\n\nTo strikeout a section of text with a horizontal line, begin and end it\nwith `~~`. Thus, for example,\n\n This ~~is deleted text.~~\n\n\n### Superscripts and subscripts ###\n\n#### Extension: `superscript`, `subscript` ####\n\nSuperscripts may be written by surrounding the superscripted text by `^`\ncharacters; subscripts may be written by surrounding the subscripted\ntext by `~` characters. Thus, for example,\n\n H~2~O is a liquid. 2^10^ is 1024.\n\nIf the superscripted or subscripted text contains spaces, these spaces\nmust be escaped with backslashes. (This is to prevent accidental\nsuperscripting and subscripting through the ordinary use of `~` and `^`.)\nThus, if you want the letter P with 'a cat' in subscripts, use\n`P~a\\ cat~`, not `P~a cat~`.\n\n\n### Verbatim ###\n\nTo make a short span of text verbatim, put it inside backticks:\n\n What is the difference between `>>=` and `>>`?\n\nIf the verbatim text includes a backtick, use double backticks:\n\n Here is a literal backtick `` ` ``.\n\n(The spaces after the opening backticks and before the closing\nbackticks will be ignored.)\n\nThe general rule is that a verbatim span starts with a string\nof consecutive backticks (optionally followed by a space)\nand ends with a string of the same number of backticks (optionally\npreceded by a space).\n\nNote that backslash-escapes (and other markdown constructs) do not\nwork in verbatim contexts:\n\n This is a backslash followed by an asterisk: `\\*`.\n\n#### Extension: `inline_code_attributes` ####\n\nAttributes can be attached to verbatim text, just as with\n[fenced code blocks](#fenced-code-blocks):\n\n `<$>`{.haskell}\n\n### Small caps ###\n\nTo write small caps, you can use an HTML span tag:\n\n Small caps\n\n(The semicolon is optional and there may be space after the\ncolon.) This will work in all output formats that support small caps.\n\nMath\n----\n\n#### Extension: `tex_math_dollars` ####\n\nAnything between two `$` characters will be treated as TeX math. The\nopening `$` must have a non-space character immediately to its right,\nwhile the closing `$` must have a non-space character immediately to its\nleft, and must not be followed immediately by a digit. Thus,\n`$20,000 and $30,000` won't parse as math. If for some reason\nyou need to enclose text in literal `$` characters, backslash-escape\nthem and they won't be treated as math delimiters.\n\nTeX math will be printed in all output formats. How it is rendered\ndepends on the output format:\n\nMarkdown, LaTeX, Org-Mode, ConTeXt\n ~ It will appear verbatim between `$` characters.\n\nreStructuredText\n ~ It will be rendered using an interpreted text role `:math:`, as described\n [here](http://docutils.sourceforge.net/docs/ref/rst/roles.html#math)\n\nAsciiDoc\n ~ It will be rendered as `latexmath:[...]`.\n\nTexinfo\n ~ It will be rendered inside a `@math` command.\n\ngroff man\n ~ It will be rendered verbatim without `$`'s.\n\nMediaWiki, DokuWiki\n ~ It will be rendered inside `` tags.\n\nTextile\n ~ It will be rendered inside `` tags.\n\nRTF, OpenDocument, ODT\n ~ It will be rendered, if possible, using unicode characters,\n and will otherwise appear verbatim.\n\nDocbook\n ~ If the `--mathml` flag is used, it will be rendered using mathml\n in an `inlineequation` or `informalequation` tag. Otherwise it\n will be rendered, if possible, using unicode characters.\n\nDocx\n ~ It will be rendered using OMML math markup.\n\nFictionBook2\n ~ If the `--webtex` option is used, formulas are rendered as images\n using Google Charts or other compatible web service, downloaded\n and embedded in the e-book. Otherwise, they will appear verbatim.\n\nHTML, Slidy, DZSlides, S5, EPUB\n ~ The way math is rendered in HTML will depend on the\n command-line options selected:\n\n 1. The default is to render TeX math as far as possible using unicode\n characters, as with RTF, DocBook, and OpenDocument output. Formulas\n are put inside a `span` with `class=\"math\"`, so that they may be\n styled differently from the surrounding text if needed.\n\n 2. If the `--latexmathml` option is used, TeX math will be displayed\n between `$` or `$$` characters and put in `` tags with class `LaTeX`.\n The [LaTeXMathML] script will be used to render it as formulas.\n (This trick does not work in all browsers, but it works in Firefox.\n In browsers that do not support LaTeXMathML, TeX math will appear\n verbatim between `$` characters.)\n\n 3. If the `--jsmath` option is used, TeX math will be put inside\n `` tags (for inline math) or `
` tags (for display math)\n with class `math`. The [jsMath] script will be used to render\n it.\n\n 4. If the `--mimetex` option is used, the [mimeTeX] CGI script will\n be called to generate images for each TeX formula. This should\n work in all browsers. The `--mimetex` option takes an optional URL\n as argument. If no URL is specified, it will be assumed that the\n mimeTeX CGI script is at `/cgi-bin/mimetex.cgi`.\n\n 5. If the `--gladtex` option is used, TeX formulas will be enclosed\n in `` tags in the HTML output. The resulting `htex` file may then\n be processed by [gladTeX], which will produce image files for each\n formula and an `html` file with links to these images. So, the\n procedure is:\n\n pandoc -s --gladtex myfile.txt -o myfile.htex\n gladtex -d myfile-images myfile.htex\n # produces myfile.html and images in myfile-images\n\n 6. If the `--webtex` option is used, TeX formulas will be converted\n to `` tags that link to an external script that converts\n formulas to images. The formula will be URL-encoded and concatenated\n with the URL provided. If no URL is specified, the Google Chart\n API will be used (`http://chart.apis.google.com/chart?cht=tx&chl=`).\n\n 7. If the `--mathjax` option is used, TeX math will be displayed\n between `\\(...\\)` (for inline math) or `\\[...\\]` (for display\n math) and put in `` tags with class `math`.\n The [MathJax] script will be used to render it as formulas.\n\nRaw HTML\n--------\n\n#### Extension: `raw_html` ####\n\nMarkdown allows you to insert raw HTML (or DocBook) anywhere in a document\n(except verbatim contexts, where `<`, `>`, and `&` are interpreted\nliterally). (Technically this is not an extension, since standard\nmarkdown allows it, but it has been made an extension so that it can\nbe disabled if desired.)\n\nThe raw HTML is passed through unchanged in HTML, S5, Slidy, Slideous,\nDZSlides, EPUB, Markdown, and Textile output, and suppressed in other\nformats.\n\n#### Extension: `markdown_in_html_blocks` ####\n\nStandard markdown allows you to include HTML \"blocks\": blocks\nof HTML between balanced tags that are separated from the surrounding text\nwith blank lines, and start and end at the left margin. Within\nthese blocks, everything is interpreted as HTML, not markdown;\nso (for example), `*` does not signify emphasis.\n\nPandoc behaves this way when the `markdown_strict` format is used; but\nby default, pandoc interprets material between HTML block tags as markdown.\nThus, for example, Pandoc will turn\n\n \n \n \n \n \n
*one*[a link](http://google.com)
\n\ninto\n\n \n \n \n \n \n
onea link
\n\nwhereas `Markdown.pl` will preserve it as is.\n\nThere is one exception to this rule: text between `\n$if(math)$\n $math$\n$endif$\n$for(header-includes)$\n $header-includes$\n$endfor$\n\n\n$for(include-before)$\n$include-before$\n$endfor$\n
\n
\n
\n
\n
\n

$date$

\n

$title$

\n
\n
\n
\n$if(title)$\n
\n

$title$

\n$if(subtitle)$\n

$subtitle$

\n$endif$\n

$for(author)$$author$$sep$
$endfor$

\n

$date$

\n
\n$endif$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n
\n\n\n"),("templates/default.asciidoc","$if(titleblock)$\n$title$\n$for(author)$\n:author: $author$\n$endfor$\n$if(date)$\n:date: $date$\n$endif$\n$if(toc)$\n:toc:\n$endif$\n\n$endif$\n$for(header-includes)$\n$header-includes$\n\n$endfor$\n$for(include-before)$\n$include-before$\n\n$endfor$\n$body$\n$for(include-after)$\n\n$include-after$\n$endfor$\n"),("templates/default.rtf","{\\rtf1\\ansi\\deff0{\\fonttbl{\\f0 \\fswiss Helvetica;}{\\f1 Courier;}}\n{\\colortbl;\\red255\\green0\\blue0;\\red0\\green0\\blue255;}\n\\widowctrl\\hyphauto\n$for(header-includes)$\n$header-includes$\n$endfor$\n\n$if(title)$\n{\\pard \\qc \\f0 \\sa180 \\li0 \\fi0 \\b \\fs36 $title$\\par}\n$endif$\n$for(author)$\n{\\pard \\qc \\f0 \\sa180 \\li0 \\fi0 $author$\\par}\n$endfor$\n$if(date)$\n{\\pard \\qc \\f0 \\sa180 \\li0 \\fi0 $date$\\par}\n$endif$\n$if(spacer)$\n{\\pard \\ql \\f0 \\sa180 \\li0 \\fi0 \\par}\n$endif$\n$if(toc)$\n$toc$\n$endif$\n$for(include-before)$\n$include-before$\n$endfor$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n}\n"),("templates/default.html","\n\n\n \n \n \n$for(author-meta)$\n \n$endfor$\n$if(date-meta)$\n \n$endif$\n $if(title-prefix)$$title-prefix$ - $endif$$pagetitle$\n \n$if(quotes)$\n \n$endif$\n$if(highlighting-css)$\n \n$endif$\n$for(css)$\n \n$endfor$\n$if(math)$\n $math$\n$endif$\n$for(header-includes)$\n $header-includes$\n$endfor$\n\n\n$for(include-before)$\n$include-before$\n$endfor$\n$if(title)$\n
\n

$title$

\n$if(subtitle)$\n

$subtitle$

\n$endif$\n$for(author)$\n

$author$

\n$endfor$\n$if(date)$\n

$date$

\n$endif$\n
\n$endif$\n$if(toc)$\n
\n$toc$\n
\n$endif$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n\n\n"),("templates/default.markdown","$if(titleblock)$\n$titleblock$\n\n$endif$\n$for(header-includes)$\n$header-includes$\n\n$endfor$\n$for(include-before)$\n$include-before$\n\n$endfor$\n$if(toc)$\n$toc$\n\n$endif$\n$body$\n$for(include-after)$\n\n$include-after$\n$endfor$\n"),("templates/default.dzslides","\n\n\n$for(author-meta)$\n \n$endfor$\n$if(date-meta)$\n \n$endif$\n $if(title-prefix)$$title-prefix$ - $endif$$pagetitle$\n \n$if(highlighting-css)$\n \n$endif$\n$if(css)$\n$for(css)$\n \n$endfor$\n$else$\n\n$endif$\n$if(math)$\n $math$\n$endif$\n$for(header-includes)$\n $header-includes$\n$endfor$\n\n\n$if(title)$\n
\n

$title$

\n$if(subtitle)$\n

$subtitle$

\n$endif$\n$for(author)$\n

$author$

\n$endfor$\n

$date$

\n
\n$endif$\n$for(include-before)$\n$include-before$\n$endfor$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n$dzslides-core$\n\n\n"),("templates/default.epub3","\n\n\n\n \n \n $pagetitle$\n$if(quotes)$\n \n$endif$\n$if(highlighting-css)$\n \n$endif$\n$for(css)$\n \n$endfor$\n$for(header-includes)$\n $header-includes$\n$endfor$\n\n\n$if(titlepage)$\n
\n$for(title)$\n$if(title.type)$\n

$title.text$

\n$else$\n

$title$

\n$endif$\n$endfor$\n$if(subtitle)$\n

$subtitle$

\n$endif$\n$for(author)$\n

$author$

\n$endfor$\n$for(creator)$\n

$creator.text$

\n$endfor$\n$if(publisher)$\n

$publisher$

\n$endif$\n$if(date)$\n

$date$

\n$endif$\n$if(rights)$\n
$rights$
\n$endif$\n
\n$else$\n$for(include-before)$\n$include-before$\n$endfor$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n$endif$\n\n\n\n"),("templates/default.html5","\n\n\n \n \n \n$for(author-meta)$\n \n$endfor$\n$if(date-meta)$\n \n$endif$\n $if(title-prefix)$$title-prefix$ - $endif$$pagetitle$\n \n \n$if(quotes)$\n \n$endif$\n$if(highlighting-css)$\n \n$endif$\n$for(css)$\n \n$endfor$\n$if(math)$\n $math$\n$endif$\n$for(header-includes)$\n $header-includes$\n$endfor$\n\n\n$for(include-before)$\n$include-before$\n$endfor$\n$if(title)$\n
\n

$title$

\n$if(subtitle)$\n

$subtitle$

\n$endif$\n$for(author)$\n

$author$

\n$endfor$\n$if(date)$\n

$date$

\n$endif$\n
\n$endif$\n$if(toc)$\n\n$endif$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n\n\n"),("templates/default.commonmark","$if(titleblock)$\n$titleblock$\n\n$endif$\n$for(header-includes)$\n$header-includes$\n\n$endfor$\n$for(include-before)$\n$include-before$\n\n$endfor$\n$if(toc)$\n$toc$\n\n$endif$\n$body$\n$for(include-after)$\n\n$include-after$\n$endfor$\n"),("templates/default.man","$if(has-tables)$\n.\\\"t\n$endif$\n.TH \"$title$\" \"$section$\" \"$date$\" \"$footer$\" \"$header$\"\n$for(header-includes)$\n$header-includes$\n$endfor$\n$for(include-before)$\n$include-before$\n$endfor$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n$if(author)$\n.SH AUTHORS\n$for(author)$$author$$sep$; $endfor$.\n$endif$\n"),("templates/default.rst","$if(title)$\n$title$\n\n$endif$\n$for(author)$\n:Author: $author$\n$endfor$\n$if(date)$\n:Date: $date$\n$endif$\n$if(author)$\n\n$else$\n$if(date)$\n\n$endif$\n$endif$\n$if(math)$\n.. role:: math(raw)\n :format: html latex\n..\n\n$endif$\n$if(rawtex)$\n.. role:: raw-latex(raw)\n :format: latex\n..\n\n$endif$\n$for(include-before)$\n$include-before$\n\n$endfor$\n$if(toc)$\n.. contents::\n :depth: $toc-depth$\n..\n\n$endif$\n$for(header-includes)$\n$header-includes$\n\n$endfor$\n$body$\n$for(include-after)$\n\n$include-after$\n$endfor$\n"),("templates/default.slidy","\n\n\n\n \n \n \n$for(author-meta)$\n \n$endfor$\n$if(date-meta)$\n \n$endif$\n $if(title-prefix)$$title-prefix$ - $endif$$pagetitle$\n \n$if(highlighting-css)$\n \n$endif$\n \n$for(css)$\n \n$endfor$\n$if(math)$\n $math$\n$endif$\n$for(header-includes)$\n $header-includes$\n$endfor$\n \n$if(duration)$\n \n$endif$\n\n\n$for(include-before)$\n$include-before$\n$endfor$\n$if(title)$\n
\n

$title$

\n$if(subtitle)$\n

$subtitle$

\n$endif$\n

\n$for(author)$$author$$sep$
$endfor$\n

\n$if(date)$\n

$date$

\n$endif$\n
\n$endif$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n\n\n"),("templates/default.opendocument","\n\n \n \n \n $automatic-styles$\n$for(header-includes)$\n $header-includes$\n$endfor$\n\n\n$if(title)$\n$title$\n$endif$\n$for(author)$\n$author$\n$endfor$\n$if(date)$\n$date$\n$endif$\n$for(include-before)$\n$include-before$\n$endfor$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n\n\n\n"),("templates/default.haddock","$body$\n"),("templates/default.org","$if(title)$\n#+TITLE: $title$\n\n$endif$\n$if(author)$\n#+AUTHOR: $for(author)$$author$$sep$; $endfor$\n$endif$\n$if(date)$\n#+DATE: $date$\n\n$endif$\n$for(header-includes)$\n$header-includes$\n\n$endfor$\n$for(include-before)$\n$include-before$\n\n$endfor$\n$body$\n$for(include-after)$\n\n$include-after$\n$endfor$\n"),("templates/default.latex","\\documentclass[$if(fontsize)$$fontsize$,$endif$$if(lang)$$lang$,$endif$$if(papersize)$$papersize$,$endif$$for(classoption)$$classoption$$sep$,$endfor$]{$documentclass$}\n$if(fontfamily)$\n\\usepackage{$fontfamily$}\n$else$\n\\usepackage{lmodern}\n$endif$\n$if(linestretch)$\n\\usepackage{setspace}\n\\setstretch{$linestretch$}\n$endif$\n\\usepackage{amssymb,amsmath}\n\\usepackage{ifxetex,ifluatex}\n\\usepackage{fixltx2e} % provides \\textsubscript\n\\ifnum 0\\ifxetex 1\\fi\\ifluatex 1\\fi=0 % if pdftex\n \\usepackage[T1]{fontenc}\n \\usepackage[utf8]{inputenc}\n$if(euro)$\n \\usepackage{eurosym}\n$endif$\n\\else % if luatex or xelatex\n \\ifxetex\n \\usepackage{mathspec}\n \\usepackage{xltxtra,xunicode}\n \\else\n \\usepackage{fontspec}\n \\fi\n \\defaultfontfeatures{Mapping=tex-text,Scale=MatchLowercase}\n \\newcommand{\\euro}{\226\130\172}\n$if(mainfont)$\n \\setmainfont{$mainfont$}\n$endif$\n$if(sansfont)$\n \\setsansfont{$sansfont$}\n$endif$\n$if(monofont)$\n \\setmonofont[Mapping=tex-ansi]{$monofont$}\n$endif$\n$if(mathfont)$\n \\setmathfont(Digits,Latin,Greek){$mathfont$}\n$endif$\n$if(CJKmainfont)$\n \\usepackage{xeCJK}\n \\setCJKmainfont[$CJKoptions$]{$CJKmainfont$}\n$endif$\n\\fi\n% use upquote if available, for straight quotes in verbatim environments\n\\IfFileExists{upquote.sty}{\\usepackage{upquote}}{}\n% use microtype if available\n\\IfFileExists{microtype.sty}{%\n\\usepackage{microtype}\n\\UseMicrotypeSet[protrusion]{basicmath} % disable protrusion for tt fonts\n}{}\n$if(geometry)$\n\\usepackage[$for(geometry)$$geometry$$sep$,$endfor$]{geometry}\n$endif$\n\\ifxetex\n \\usepackage[setpagesize=false, % page size defined by xetex\n unicode=false, % unicode breaks when used with xetex\n xetex]{hyperref}\n\\else\n \\usepackage[unicode=true]{hyperref}\n\\fi\n\\usepackage[usenames,dvipsnames]{color}\n\\hypersetup{breaklinks=true,\n bookmarks=true,\n pdfauthor={$author-meta$},\n pdftitle={$title-meta$},\n colorlinks=true,\n citecolor=$if(citecolor)$$citecolor$$else$blue$endif$,\n urlcolor=$if(urlcolor)$$urlcolor$$else$blue$endif$,\n linkcolor=$if(linkcolor)$$linkcolor$$else$magenta$endif$,\n pdfborder={0 0 0}}\n\\urlstyle{same} % don't use monospace font for urls\n$if(lang)$\n\\ifxetex\n \\usepackage{polyglossia}\n \\setmainlanguage{$mainlang$}\n \\setotherlanguages{$for(otherlang)$$otherlang$$sep$,$endfor$}\n\\else\n \\usepackage[shorthands=off,$lang$]{babel}\n\\fi\n$endif$\n$if(natbib)$\n\\usepackage{natbib}\n\\bibliographystyle{$if(biblio-style)$$biblio-style$$else$plainnat$endif$}\n$endif$\n$if(biblatex)$\n\\usepackage{biblatex}\n$for(bibliography)$\n\\addbibresource{$bibliography$}\n$endfor$\n$endif$\n$if(listings)$\n\\usepackage{listings}\n$endif$\n$if(lhs)$\n\\lstnewenvironment{code}{\\lstset{language=Haskell,basicstyle=\\small\\ttfamily}}{}\n$endif$\n$if(highlighting-macros)$\n$highlighting-macros$\n$endif$\n$if(verbatim-in-note)$\n\\usepackage{fancyvrb}\n\\VerbatimFootnotes\n$endif$\n$if(tables)$\n\\usepackage{longtable,booktabs}\n$endif$\n$if(graphics)$\n\\usepackage{graphicx,grffile}\n\\makeatletter\n\\def\\maxwidth{\\ifdim\\Gin@nat@width>\\linewidth\\linewidth\\else\\Gin@nat@width\\fi}\n\\def\\maxheight{\\ifdim\\Gin@nat@height>\\textheight\\textheight\\else\\Gin@nat@height\\fi}\n\\makeatother\n% Scale images if necessary, so that they will not overflow the page\n% margins by default, and it is still possible to overwrite the defaults\n% using explicit options in \\includegraphics[width, height, ...]{}\n\\setkeys{Gin}{width=\\maxwidth,height=\\maxheight,keepaspectratio}\n$endif$\n$if(links-as-notes)$\n% Make links footnotes instead of hotlinks:\n\\renewcommand{\\href}[2]{#2\\footnote{\\url{#1}}}\n$endif$\n$if(strikeout)$\n\\usepackage[normalem]{ulem}\n% avoid problems with \\sout in headers with hyperref:\n\\pdfstringdefDisableCommands{\\renewcommand{\\sout}{}}\n$endif$\n\\setlength{\\parindent}{0pt}\n\\setlength{\\parskip}{6pt plus 2pt minus 1pt}\n\\setlength{\\emergencystretch}{3em} % prevent overfull lines\n\\providecommand{\\tightlist}{%\n \\setlength{\\itemsep}{0pt}\\setlength{\\parskip}{0pt}}\n$if(numbersections)$\n\\setcounter{secnumdepth}{5}\n$else$\n\\setcounter{secnumdepth}{0}\n$endif$\n$if(verbatim-in-note)$\n\\VerbatimFootnotes % allows verbatim text in footnotes\n$endif$\n\n$if(title)$\n\\title{$title$$if(subtitle)$\\\\\\vspace{0.5em}{\\large $subtitle$}$endif$}\n$endif$\n$if(author)$\n\\author{$for(author)$$author$$sep$ \\and $endfor$}\n$endif$\n\\date{$date$}\n$for(header-includes)$\n$header-includes$\n$endfor$\n\n% Redefines (sub)paragraphs to behave more like sections\n\\ifx\\paragraph\\undefined\\else\n\\let\\oldparagraph\\paragraph\n\\renewcommand{\\paragraph}[1]{\\oldparagraph{#1}\\mbox{}}\n\\fi\n\\ifx\\subparagraph\\undefined\\else\n\\let\\oldsubparagraph\\subparagraph\n\\renewcommand{\\subparagraph}[1]{\\oldsubparagraph{#1}\\mbox{}}\n\\fi\n\n\\begin{document}\n$if(title)$\n\\maketitle\n$endif$\n$if(abstract)$\n\\begin{abstract}\n$abstract$\n\\end{abstract}\n$endif$\n\n$for(include-before)$\n$include-before$\n\n$endfor$\n$if(toc)$\n{\n\\hypersetup{linkcolor=$if(toccolor)$$toccolor$$else$black$endif$}\n\\setcounter{tocdepth}{$toc-depth$}\n\\tableofcontents\n}\n$endif$\n$if(lot)$\n\\listoftables\n$endif$\n$if(lof)$\n\\listoffigures\n$endif$\n$body$\n\n$if(natbib)$\n$if(bibliography)$\n$if(biblio-title)$\n$if(book-class)$\n\\renewcommand\\bibname{$biblio-title$}\n$else$\n\\renewcommand\\refname{$biblio-title$}\n$endif$\n$endif$\n\\bibliography{$for(bibliography)$$bibliography$$sep$,$endfor$}\n\n$endif$\n$endif$\n$if(biblatex)$\n\\printbibliography$if(biblio-title)$[title=$biblio-title$]$endif$\n\n$endif$\n$for(include-after)$\n$include-after$\n\n$endfor$\n\\end{document}\n"),("templates/default.dokuwiki","$for(include-before)$\n$include-before$\n\n$endfor$\n$if(toc)$\n__TOC__\n\n$endif$\n$body$\n$for(include-after)$\n\n$include-after$\n$endfor$\n"),("templates/default.icml","\n\n\n\n \n \n $charStyles$ \n \n \n \n \n \n \n LeftAlign\n .\n \n 10 \n \n \n \n \n $parStyles$ \n \n \n \n \n \n \n \n \n \n\n\n$body$\n\n \n $hyperlinks$\n\n"),("templates/default.opml","\n\n \n $title$\n $date$\n $for(author)$$author$$sep$; $endfor$\n \n \n$body$\n \n\n"),("templates/README.markdown","Templates for [pandoc](http://github.com/jgm/pandoc).\n\nIf you use custom templates, we recommend forking this repository,\nso that you can integrate changes to the default templates in future\npandoc releases.\n\nAll of the templates in this repository are dual licensed, under both\nthe GPL (v2 or higher, same as pandoc) and the BSD 3-clause license\n(included below).\n\n----\n\nCopyright (c) 2014, John MacFarlane\n\nAll rights reserved.\n\nRedistribution and use in source and binary forms, with or without\nmodification, are permitted provided that the following conditions are met:\n\n * Redistributions of source code must retain the above copyright\n notice, this list of conditions and the following disclaimer.\n\n * Redistributions in binary form must reproduce the above\n copyright notice, this list of conditions and the following\n disclaimer in the documentation and/or other materials provided\n with the distribution.\n\n * Neither the name of John MacFarlane nor the names of other\n contributors may be used to endorse or promote products derived\n from this software without specific prior written permission.\n\nTHIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS\n\"AS IS\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT\nLIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR\nA PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT\nOWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,\nSPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT\nLIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,\nDATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY\nTHEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT\n(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE\nOF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.\n"),("templates/default.texinfo","\\input texinfo\n@documentencoding UTF-8\n$for(header-includes)$\n$header-includes$\n$endfor$\n\n$if(strikeout)$\n@macro textstrikeout{text}\n~~\\text\\~~\n@end macro\n\n$endif$\n$if(subscript)$\n@macro textsubscript{text}\n@iftex\n@textsubscript{\\text\\}\n@end iftex\n@ifnottex\n_@{\\text\\@}\n@end ifnottex\n@end macro\n\n$endif$\n$if(superscript)$\n@macro textsuperscript{text}\n@iftex\n@textsuperscript{\\text\\}\n@end iftex\n@ifnottex\n^@{\\text\\@}\n@end ifnottex\n@end macro\n\n$endif$\n@ifnottex\n@paragraphindent 0\n@end ifnottex\n$if(titlepage)$\n@titlepage\n@title $title$\n$for(author)$\n@author $author$\n$endfor$\n$if(date)$\n$date$\n$endif$\n@end titlepage\n\n$endif$\n$for(include-before)$\n$include-before$\n\n$endfor$\n$if(toc)$\n@contents\n\n$endif$\n$body$\n$for(include-after)$\n\n$include-after$\n$endfor$\n\n@bye\n"),("templates/default.context","\\startmode[*mkii]\n \\enableregime[utf-8] \n \\setupcolors[state=start]\n\\stopmode\n$if(mainlang)$\n\\mainlanguage[$mainlang$]\n$endif$\n\n% Enable hyperlinks\n\\setupinteraction[state=start, color=middleblue]\n\n\\setuppapersize [$if(papersize)$$papersize$$else$letter$endif$][$if(papersize)$$papersize$$else$letter$endif$]\n\\setuplayout [width=middle, backspace=1.5in, cutspace=1.5in,\n height=middle, topspace=0.75in, bottomspace=0.75in]\n\n\\setuppagenumbering[location={footer,center}]\n\n\\setupbodyfont[11pt]\n\n\\setupwhitespace[medium]\n\n\\setuphead[chapter] [style=\\tfd]\n\\setuphead[section] [style=\\tfc]\n\\setuphead[subsection] [style=\\tfb]\n\\setuphead[subsubsection][style=\\bf]\n\n$if(number-sections)$\n$else$\n\\setuphead[chapter, section, subsection, subsubsection][number=no]\n$endif$\n\n\\definedescription\n [description]\n [headstyle=bold, style=normal, location=hanging, width=broad, margin=1cm]\n\n\\setupitemize[autointro] % prevent orphan list intro\n\\setupitemize[indentnext=no]\n\n\\setupfloat[figure][default={here,nonumber}]\n\\setupfloat[table][default={here,nonumber}]\n\n\\setupthinrules[width=15em] % width of horizontal rules\n\n\\setupdelimitedtext\n [blockquote]\n [before={\\blank[medium]},\n after={\\blank[medium]},\n indentnext=no,\n ]\n\n$if(toc)$\n\\setupcombinedlist[content][list={$placelist$}]\n\n$endif$\n$for(header-includes)$\n$header-includes$\n$endfor$\n\n\\starttext\n$if(title)$\n\\startalignment[center]\n \\blank[2*big]\n {\\tfd $title$}\n$if(author)$\n \\blank[3*medium]\n {\\tfa $for(author)$$author$$sep$\\crlf $endfor$}\n$endif$\n$if(date)$\n \\blank[2*medium]\n {\\tfa $date$}\n$endif$\n \\blank[3*medium]\n\\stopalignment\n$endif$\n$for(include-before)$\n$include-before$\n$endfor$\n$if(toc)$\n\\placecontent\n$endif$\n\n$body$\n\n$for(include-after)$\n$include-after$\n$endfor$\n\\stoptext\n"),("templates/default.plain","$if(titleblock)$\n$titleblock$\n\n$endif$\n$for(header-includes)$\n$header-includes$\n\n$endfor$\n$for(include-before)$\n$include-before$\n\n$endfor$\n$if(toc)$\n$toc$\n\n$endif$\n$body$\n$for(include-after)$\n\n$include-after$\n$endfor$\n"),("templates/default.epub","\n\n\n\n \n \n \n $pagetitle$\n$if(highlighting-css)$\n \n$endif$\n$for(css)$\n \n$endfor$\n$for(header-includes)$\n $header-includes$\n$endfor$\n\n\n$if(titlepage)$\n$for(title)$\n$if(title.text)$\n

$title.text$

\n$else$\n

$title$

\n$endif$\n$endfor$\n$if(subtitle)$\n

$subtitle$

\n$endif$\n$for(author)$\n

$author$

\n$endfor$\n$for(creator)$\n

$creator.text$

\n$endfor$\n$if(publisher)$\n

$publisher$

\n$endif$\n$if(date)$\n

$date$

\n$endif$\n$if(rights)$\n
$rights$
\n$endif$\n$else$\n$for(include-before)$\n$include-before$\n$endfor$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n$endif$\n\n\n\n"),("templates/default.docbook","\n$if(mathml)$\n\n$else$\n\n$endif$\n
\n \n $title$\n$if(author)$\n \n$for(author)$\n \n $author$\n \n$endfor$\n \n$endif$\n$if(date)$\n $date$\n$endif$\n \n$for(include-before)$\n$include-before$\n$endfor$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n
\n"),("templates/default.slideous","\n\n\n\n \n \n \n$for(author-meta)$\n \n$endfor$\n$if(date-meta)$\n \n$endif$\n $if(title-prefix)$$title-prefix$ - $endif$$pagetitle$\n \n$if(highlighting-css)$\n \n$endif$\n \n$for(css)$\n \n$endfor$\n$if(math)$\n $math$\n$endif$\n$for(header-includes)$\n $header-includes$\n$endfor$\n \n$if(duration)$\n \n$endif$\n\n\n$for(include-before)$\n$include-before$\n$endfor$\n
\n\n of {$$slidecount}\n\n\n\n\n\n\n\n\n\n\n½\n{$$title}, {$$author}\n
\n$if(title)$\n
\n

$title$

\n$if(subtitle)$\n

$subtitle$

\n$endif$\n

\n$for(author)$$author$$sep$
$endfor$\n

\n$if(date)$\n

$date$

\n$endif$\n
\n$endif$\n$body$\n$for(include-after)$\n$include-after$\n$endfor$\n\n\n"),("templates/default.mediawiki","$for(include-before)$\n$include-before$\n\n$endfor$\n$if(toc)$\n__TOC__\n\n$endif$\n$body$\n$for(include-after)$\n\n$include-after$\n$endfor$\n"),("templates/default.revealjs","\n\n\n \n \n$for(author-meta)$\n \n$endfor$\n$if(date-meta)$\n \n$endif$\n $if(title-prefix)$$title-prefix$ - $endif$$pagetitle$\n \n \n \n \n \n$if(highlighting-css)$\n \n$endif$\n$if(theme)$\n \n$else$\n \n$endif$\n$for(css)$\n \n$endfor$\n \n \n \n$if(math)$\n $math$\n$endif$\n$for(header-includes)$\n $header-includes$\n$endfor$\n\n\n$for(include-before)$\n$include-before$\n$endfor$\n
\n
\n\n$if(title)$\n
\n

$title$

\n$if(subtitle)$\n

$subtitle$

\n$endif$\n$for(author)$\n

$author$

\n$endfor$\n

$date$

\n
\n$endif$\n$if(toc)$\n
\n$toc$\n
\n$endif$\n\n$body$\n
\n
\n\n\n \n \n\n \n $for(include-after)$\n $include-after$\n $endfor$\n \n\n"),("templates/default.beamer","\\documentclass[$if(fontsize)$$fontsize$,$endif$$if(handout)$handout,$endif$$if(beamer)$ignorenonframetext,$endif$$for(classoption)$$classoption$$sep$,$endfor$]{$documentclass$}\n$if(theme)$\n\\usetheme{$theme$}\n$endif$\n$if(colortheme)$\n\\usecolortheme{$colortheme$}\n$endif$\n$if(fonttheme)$\n\\usefonttheme{$fonttheme$}\n$endif$\n\\setbeamertemplate{caption}[numbered]\n\\setbeamertemplate{caption label separator}{:}\n\\setbeamercolor{caption name}{fg=normal text.fg}\n\\usepackage{amssymb,amsmath}\n\\usepackage{ifxetex,ifluatex}\n\\usepackage{fixltx2e} % provides \\textsubscript\n\\usepackage{lmodern}\n\\ifxetex\n \\usepackage{fontspec,xltxtra,xunicode}\n \\defaultfontfeatures{Mapping=tex-text,Scale=MatchLowercase}\n \\newcommand{\\euro}{\226\130\172}\n\\else\n \\ifluatex\n \\usepackage{fontspec}\n \\defaultfontfeatures{Mapping=tex-text,Scale=MatchLowercase}\n \\newcommand{\\euro}{\226\130\172}\n \\else\n \\usepackage[T1]{fontenc}\n \\usepackage[utf8]{inputenc}\n $if(euro)$\n \\usepackage{eurosym}\n $endif$\n \\fi\n\\fi\n% use upquote if available, for straight quotes in verbatim environments\n\\IfFileExists{upquote.sty}{\\usepackage{upquote}}{}\n% use microtype if available\n\\IfFileExists{microtype.sty}{\\usepackage{microtype}}{}\n$if(natbib)$\n\\usepackage{natbib}\n\\bibliographystyle{plainnat}\n$endif$\n$if(biblatex)$\n\\usepackage{biblatex}\n$for(bibliography)$\n\\addbibresource{$bibliography$}\n$endfor$\n$endif$\n$if(listings)$\n\\usepackage{listings}\n$endif$\n$if(lhs)$\n\\lstnewenvironment{code}{\\lstset{language=Haskell,basicstyle=\\small\\ttfamily}}{}\n$endif$\n$if(highlighting-macros)$\n$highlighting-macros$\n$endif$\n$if(verbatim-in-note)$\n\\usepackage{fancyvrb}\n$endif$\n$if(tables)$\n\\usepackage{longtable,booktabs}\n\\usepackage{caption}\n% These lines are needed to make table captions work with longtable:\n\\makeatletter\n\\def\\fnum@table{\\tablename~\\thetable}\n\\makeatother\n$endif$\n$if(url)$\n\\usepackage{url}\n$endif$\n$if(graphics)$\n\\usepackage{graphicx}\n\\makeatletter\n\\def\\maxwidth{\\ifdim\\Gin@nat@width>\\linewidth\\linewidth\\else\\Gin@nat@width\\fi}\n\\def\\maxheight{\\ifdim\\Gin@nat@height>\\textheight0.8\\textheight\\else\\Gin@nat@height\\fi}\n\\makeatother\n% Scale images if necessary, so that they will not overflow the page\n% margins by default, and it is still possible to overwrite the defaults\n% using explicit options in \\includegraphics[width, height, ...]{}\n\\setkeys{Gin}{width=\\maxwidth,height=\\maxheight,keepaspectratio}\n$endif$\n\n% Comment these out if you don't want a slide with just the\n% part/section/subsection/subsubsection title:\n\\AtBeginPart{\n \\let\\insertpartnumber\\relax\n \\let\\partname\\relax\n \\frame{\\partpage}\n}\n\\AtBeginSection{\n \\let\\insertsectionnumber\\relax\n \\let\\sectionname\\relax\n \\frame{\\sectionpage}\n}\n\\AtBeginSubsection{\n \\let\\insertsubsectionnumber\\relax\n \\let\\subsectionname\\relax\n \\frame{\\subsectionpage}\n}\n\n$if(strikeout)$\n\\usepackage[normalem]{ulem}\n% avoid problems with \\sout in headers with hyperref:\n\\pdfstringdefDisableCommands{\\renewcommand{\\sout}{}}\n$endif$\n\\setlength{\\parindent}{0pt}\n\\setlength{\\parskip}{6pt plus 2pt minus 1pt}\n\\setlength{\\emergencystretch}{3em} % prevent overfull lines\n\\providecommand{\\tightlist}{%\n \\setlength{\\itemsep}{0pt}\\setlength{\\parskip}{0pt}}\n$if(numbersections)$\n$else$\n\\setcounter{secnumdepth}{0}\n$endif$\n$if(verbatim-in-note)$\n\\VerbatimFootnotes % allows verbatim text in footnotes\n$endif$\n$if(lang)$\n\\ifxetex\n \\usepackage{polyglossia}\n \\setmainlanguage{$mainlang$}\n \\setotherlanguages{$for(otherlang)$$otherlang$$sep$,$endfor$}\n\\else\n \\usepackage[shorthands=off,$lang$]{babel}\n\\fi\n$endif$\n$for(header-includes)$\n$header-includes$\n$endfor$\n\n$if(title)$\n\\title{$title$}\n$endif$\n$if(subtitle)$\n\\subtitle{$subtitle$}\n$endif$\n$if(author)$\n\\author{$for(author)$$author$$sep$ \\and $endfor$}\n$endif$\n\\date{$date$}\n\n\\begin{document}\n$if(title)$\n\\frame{\\titlepage}\n$endif$\n\n$for(include-before)$\n$include-before$\n\n$endfor$\n$if(toc)$\n\\begin{frame}\n\\tableofcontents[hideallsubsections]\n\\end{frame}\n\n$endif$\n$body$\n\n$if(natbib)$\n$if(bibliography)$\n$if(biblio-title)$\n$if(book-class)$\n\\renewcommand\\bibname{$biblio-title$}\n$else$\n\\renewcommand\\refname{$biblio-title$}\n$endif$\n$endif$\n\\begin{frame}[allowframebreaks]{$biblio-title$}\n\\bibliography{$for(bibliography)$$bibliography$$sep$,$endfor$}\n\\end{frame}\n\n$endif$\n$endif$\n$if(biblatex)$\n\\begin{frame}[allowframebreaks]{$biblio-title$}\n\\printbibliography[heading=none]\n\\end{frame}\n\n$endif$\n$for(include-after)$\n$include-after$\n\n$endfor$\n\\end{document}\n"),("odt/meta.xml","\n\n \n \n Pandoc\n \n\n"),("odt/styles.xml","\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n 1\n \n \n \n \n\n"),("odt/manifest.rdf","\n\n \n \n \n \n \n \n \n \n \n \n \n \n \n \n \n\n"),("odt/mimetype","application/vnd.oasis.opendocument.text"),("odt/settings.xml","\n002174710874truefalseview23041304100217451087300false100falsetruefalsefalse1473719falsetruefalsefalsetruefalsefalsefalsefalsefalsefalsefalsefalsetruefalse0falsefalsefalsefalsefalsefalsefalsefalsefalsefalsetruetruefalsefalsetruetruetruefalsehigh-resolution147371910falsefalsefalsetruefalsefalsetruefalsetruetruefalsefalsefalsefalsetruetruefalsetruetruetruefalsefalsefalse0falsefalsetruetrue"),("odt/content.xml","\nHello World!"),("odt/Thumbnails/thumbnail.png","\137PNG\r\n\SUB\n\NUL\NUL\NUL\rIHDR\NUL\NUL\NUL\198\NUL\NUL\SOH\NUL\b\STX\NUL\NUL\NULg?\158\ETB\NUL\NUL\STX\216IDATx\156\237\214A\n\194\&0\DC4\NULQ\ETX\222\255\202_\161 E\DLE\186\CANQ\235{\139\240\179j\SYNC\210\235\204\\\160s\253\244\SOH8\ESCI\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC4\177,\169\181\214\204\220\215m\251\152\183\225i\173>\202\ETB*o\169GO\251y\ESC\246+\231\246\222\135o\DELo\241'\178\164^=g\158\185\DEL\227\247\156\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\138\152\164\136I\234\144\181\214\204|\250\DC4\191AR\135\232\233\&8I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC41I\DC1\147\DC4\177\ESC\b\SUB(\EOTp\211\ESCp\NUL\NUL\NUL\NULIEND\174B`\130"),("odt/Configurations2/accelerator/current.xml",""),("odt/META-INF/manifest.xml","\n\n \n \n \n \n \n \n \n \n \n"),("dzslides/template.html","\n\n\nThe Title Of Your Presentation\n\n\n\n\n
\n \n

My Presentation

\n
by John Doe
\n
\n\n
\n

Some random text: But I've never been to the moon! You can see how I lived before I met you. Also Zoidberg.\n I could if you hadn't turned on the light and shut off my stereo.

\n
\n\n
\n

An incremental list

\n
    \n
  • Item 1\n
  • Item 2\n
  • Item 3\n
\n
Some notes. They are only visible using onstage shell.
\n
\n\n
\n \n Who's brave enough to fly into something we all keep calling a death sphere?\n \n
\n\n
\n

Part two

\n
\n\n
\n
\n \n
An image
\n
\n
Kittens are so cute!
\n
\n\n
\n
\n \n
A video
\n
\n
\n\n
\n

End!

\n
\n\n\n\n\n\n\n\n\n\n\n\n
\n\n\n\n\n\n\n\n\n\n")]