`` tags (or ``

`` tags for ``html4``), and attach identifiers to the enclosing ``

`` (or ``

``) rather than the heading itself (see `Heading identifiers <#heading-identifiers>`__, below). This option only affects HTML output (and does not affect HTML slide formats). ``--email-obfuscation=none``\ \|\ ``javascript``\ \|\ ``references`` Specify a method for obfuscating ``mailto:`` links in HTML documents. ``none`` leaves ``mailto:`` links as they are. ``javascript`` obfuscates them using JavaScript. ``references`` obfuscates them by printing their letters as decimal or hexadecimal character references. The default is ``none``. ``--id-prefix=``\ *STRING* Specify a prefix to be added to all identifiers and internal links in HTML and DocBook output, and to footnote numbers in Markdown and Haddock output. This is useful for preventing duplicate identifiers when generating fragments to be included in other pages. ``-T`` *STRING*, ``--title-prefix=``\ *STRING* Specify *STRING* as a prefix at the beginning of the title that appears in the HTML header (but not in the title as it appears at the beginning of the HTML body). Implies ``--standalone``. ``-c`` *URL*, ``--css=``\ *URL* Link to a CSS style sheet. This option can be used repeatedly to include multiple files. They will be included in the order specified. This option only affects HTML (including HTML slide shows) and EPUB output. It should be used together with ``-s/--standalone``, because the link to the stylesheet goes in the document header. A stylesheet is required for generating EPUB. If none is provided using this option (or the ``css`` or ``stylesheet`` metadata fields), pandoc will look for a file ``epub.css`` in the user data directory (see ``--data-dir``). If it is not found there, sensible defaults will be used. ``--reference-doc=``\ *FILE*\ \|\ *URL* Use the specified file as a style reference in producing a docx or ODT file. Docx For best results, the reference docx should be a modified version of a docx file produced using pandoc. The contents of the reference docx are ignored, but its stylesheets and document properties (including margins, page size, header, and footer) are used in the new docx. If no reference docx is specified on the command line, pandoc will look for a file ``reference.docx`` in the user data directory (see ``--data-dir``). If this is not found either, sensible defaults will be used. To produce a custom ``reference.docx``, first get a copy of the default ``reference.docx``: ``pandoc -o custom-reference.docx --print-default-data-file reference.docx``. Then open ``custom-reference.docx`` in Word, modify the styles as you wish, and save the file. For best results, do not make changes to this file other than modifying the styles used by pandoc: Paragraph styles: - Normal - Body Text - First Paragraph - Compact - Title - Subtitle - Author - Date - Abstract - AbstractTitle - Bibliography - Heading 1 - Heading 2 - Heading 3 - Heading 4 - Heading 5 - Heading 6 - Heading 7 - Heading 8 - Heading 9 - Block Text [for block quotes] - Footnote Block Text [for block quotes in footnotes] - Source Code - Footnote Text - Definition Term - Definition - Caption - Table Caption - Image Caption - Figure - Captioned Figure - TOC Heading Character styles: - Default Paragraph Font - Verbatim Char - Footnote Reference - Hyperlink - Section Number Table style: - Table ODT For best results, the reference ODT should be a modified version of an ODT produced using pandoc. The contents of the reference ODT are ignored, but its stylesheets are used in the new ODT. If no reference ODT is specified on the command line, pandoc will look for a file ``reference.odt`` in the user data directory (see ``--data-dir``). If this is not found either, sensible defaults will be used. To produce a custom ``reference.odt``, first get a copy of the default ``reference.odt``: ``pandoc -o custom-reference.odt --print-default-data-file reference.odt``. Then open ``custom-reference.odt`` in LibreOffice, modify the styles as you wish, and save the file. PowerPoint Templates included with Microsoft PowerPoint 2013 (either with ``.pptx`` or ``.potx`` extension) are known to work, as are most templates derived from these. The specific requirement is that the template should contain layouts with the following names (as seen within PowerPoint): - Title Slide - Title and Content - Section Header - Two Content - Comparison - Content with Caption - Blank For each name, the first layout found with that name will be used. If no layout is found with one of the names, pandoc will output a warning and use the layout with that name from the default reference doc instead. (How these layouts are used is described in `PowerPoint layout choice <#powerpoint-layout-choice>`__.) All templates included with a recent version of MS PowerPoint will fit these criteria. (You can click on ``Layout`` under the ``Home`` menu to check.) You can also modify the default ``reference.pptx``: first run ``pandoc -o custom-reference.pptx --print-default-data-file reference.pptx``, and then modify ``custom-reference.pptx`` in MS PowerPoint (pandoc will use the layouts with the names listed above). ``--split-level=``\ *NUMBER* Specify the heading level at which to split an EPUB or chunked HTML document into separate files. The default is to split into chapters at level-1 headings. In the case of EPUB, this option only affects the internal composition of the EPUB, not the way chapters and sections are displayed to users. Some readers may be slow if the chapter files are too large, so for large documents with few level-1 headings, one might want to use a chapter level of 2 or 3. For chunked HTML, this option determines how much content goes in each â€œchunk.â€ ``--chunk-template=``\ *PATHTEMPLATE* Specify a template for the filenames in a ``chunkedhtml`` document. In the template, ``%n`` will be replaced by the chunk number (padded with leading 0s to 3 digits), ``%s`` with the section number of the chunk, ``%h`` with the heading text (with formatting removed), ``%i`` with the section identifier. For example, ``%section-%s-%i.html`` might be resolved to ``section-1.1-introduction.html``. The characters ``/`` and ``\`` are not allowed in chunk templates and will be ignored. The default is ``%s-%i.html``. ``--epub-chapter-level=``\ *NUMBER* *Deprecated synonym for ``--split-level``.* ``--epub-cover-image=``\ *FILE* Use the specified image as the EPUB cover. It is recommended that the image be less than 1000px in width and height. Note that in a Markdown source document you can also specify ``cover-image`` in a YAML metadata block (see `EPUB Metadata <#epub-metadata>`__, below). ``--epub-title-page=true``\ \|\ ``false`` Determines whether a the title page is included in the EPUB (default is ``true``). ``--epub-metadata=``\ *FILE* Look in the specified XML file for metadata for the EPUB. The file should contain a series of `Dublin Core elements `__. For example: :: Creative Commons es-AR By default, pandoc will include the following metadata elements: ```` (from the document title), ```` (from the document authors), ```` (from the document date, which should be in `ISO 8601 format `__), ```` (from the ``lang`` variable, or, if is not set, the locale), and ```` (a randomly generated UUID). Any of these may be overridden by elements in the metadata file. Note: if the source document is Markdown, a YAML metadata block in the document can be used instead. See below under `EPUB Metadata <#epub-metadata>`__. ``--epub-embed-font=``\ *FILE* Embed the specified font in the EPUB. This option can be repeated to embed multiple fonts. Wildcards can also be used: for example, ``DejaVuSans-*.ttf``. However, if you use wildcards on the command line, be sure to escape them or put the whole filename in single quotes, to prevent them from being interpreted by the shell. To use the embedded fonts, you will need to add declarations like the following to your CSS (see ``--css``): :: @font-face { font-family: DejaVuSans; font-style: normal; font-weight: normal; src:url("/fonts/DejaVuSans-Regular.ttf"); } @font-face { font-family: DejaVuSans; font-style: normal; font-weight: bold; src:url("/fonts/DejaVuSans-Bold.ttf"); } @font-face { font-family: DejaVuSans; font-style: italic; font-weight: normal; src:url("/fonts/DejaVuSans-Oblique.ttf"); } @font-face { font-family: DejaVuSans; font-style: italic; font-weight: bold; src:url("/fonts/DejaVuSans-BoldOblique.ttf"); } body { font-family: "DejaVuSans"; } ``--epub-subdirectory=``\ *DIRNAME* Specify the subdirectory in the OCF container that is to hold the EPUB-specific contents. The default is ``EPUB``. To put the EPUB contents in the top level, use an empty string. ``--ipynb-output=all|none|best`` Determines how ipynb output cells are treated. ``all`` means that all of the data formats included in the original are preserved. ``none`` means that the contents of data cells are omitted. ``best`` causes pandoc to try to pick the richest data block in each output cell that is compatible with the output format. The default is ``best``. ``--pdf-engine=``\ *PROGRAM* Use the specified engine when producing PDF output. Valid values are ``pdflatex``, ``lualatex``, ``xelatex``, ``latexmk``, ``tectonic``, ``wkhtmltopdf``, ``weasyprint``, ``pagedjs-cli``, ``prince``, ``context``, ``groff``, ``pdfroff``, and ``typst``. If the engine is not in your PATH, the full path of the engine may be specified here. If this option is not specified, pandoc uses the following defaults depending on the output format specified using ``-t/--to``: - ``-t latex`` or none: ``pdflatex`` (other options: ``xelatex``, ``lualatex``, ``tectonic``, ``latexmk``) - ``-t context``: ``context`` - ``-t html``: ``weasyprint`` (other options: ``prince``, ``wkhtmltopdf``, ``pagedjs-cli``; see `print-css.rocks `__ for a good introduction to PDF generation from HTML/CSS) - ``-t ms``: ``pdfroff`` - ``-t typst``: ``typst`` This option is normally intended to be used when a PDF file is specified as ``-o/--output``. However, it may still have an effect when other output formats are requested. For example, ``ms`` output will include ``.pdfhref`` macros only if a ``--pdf-engine`` is selected, and the macros will be differently encoded depending on whether ``groff`` or ``pdfroff`` is specified. ``--pdf-engine-opt=``\ *STRING* Use the given string as a command-line argument to the ``pdf-engine``. For example, to use a persistent directory ``foo`` for ``latexmk``\ â€™s auxiliary files, use ``--pdf-engine-opt=-outdir=foo``. Note that no check for duplicate options is done. Citation rendering ------------------ ``-C``, ``--citeproc`` Process the citations in the file, replacing them with rendered citations and adding a bibliography. Citation processing will not take place unless bibliographic data is supplied, either through an external file specified using the ``--bibliography`` option or the ``bibliography`` field in metadata, or via a ``references`` section in metadata containing a list of citations in CSL YAML format with Markdown formatting. The style is controlled by a `CSL `__ stylesheet specified using the ``--csl`` option or the ``csl`` field in metadata. (If no stylesheet is specified, the ``chicago-author-date`` style will be used by default.) The citation processing transformation may be applied before or after filters or Lua filters (see ``--filter``, ``--lua-filter``): these transformations are applied in the order they appear on the command line. For more information, see the section on `Citations <#citations>`__. Note: if this option is specified, the ``citations`` extension will be disabled automatically in the writer, to ensure that the citeproc-generated citations will be rendered instead of the formatâ€™s own citation syntax. ``--bibliography=``\ *FILE* Set the ``bibliography`` field in the documentâ€™s metadata to *FILE*, overriding any value set in the metadata. If you supply this argument multiple times, each *FILE* will be added to bibliography. If *FILE* is a URL, it will be fetched via HTTP. If *FILE* is not found relative to the working directory, it will be sought in the resource path (see ``--resource-path``). ``--csl=``\ *FILE* Set the ``csl`` field in the documentâ€™s metadata to *FILE*, overriding any value set in the metadata. (This is equivalent to ``--metadata csl=FILE``.) If *FILE* is a URL, it will be fetched via HTTP. If *FILE* is not found relative to the working directory, it will be sought in the resource path (see ``--resource-path``) and finally in the ``csl`` subdirectory of the pandoc user data directory. ``--citation-abbreviations=``\ *FILE* Set the ``citation-abbreviations`` field in the documentâ€™s metadata to *FILE*, overriding any value set in the metadata. (This is equivalent to ``--metadata citation-abbreviations=FILE``.) If *FILE* is a URL, it will be fetched via HTTP. If *FILE* is not found relative to the working directory, it will be sought in the resource path (see ``--resource-path``) and finally in the ``csl`` subdirectory of the pandoc user data directory. ``--natbib`` Use ```natbib`` `__ for citations in LaTeX output. This option is not for use with the ``--citeproc`` option or with PDF output. It is intended for use in producing a LaTeX file that can be processed with ```bibtex`` `__. ``--biblatex`` Use ```biblatex`` `__ for citations in LaTeX output. This option is not for use with the ``--citeproc`` option or with PDF output. It is intended for use in producing a LaTeX file that can be processed with ```bibtex`` `__ or ```biber`` `__. Math rendering in HTML ---------------------- The default is to render TeX math as far as possible using Unicode characters. Formulas are put inside a ``span`` with ``class="math"``, so that they may be styled differently from the surrounding text if needed. However, this gives acceptable results only for basic math, usually you will want to use ``--mathjax`` or another of the following options. ``--mathjax``\ [``=``\ *URL*] Use `MathJax `__ to display embedded TeX math in HTML output. TeX math will be put between ``$...$`` (for inline math) or ``\[...\]`` (for display math) and wrapped in ```` tags with class ``math``. Then the MathJax JavaScript will render it. The *URL* should point to the ``MathJax.js`` load script. If a *URL* is not provided, a link to the Cloudflare CDN will be inserted. ``--mathml`` Convert TeX math to `MathML `__ (in ``epub3``, ``docbook4``, ``docbook5``, ``jats``, ``html4`` and ``html5``). This is the default in ``odt`` output. MathML is supported natively by the main web browsers and select e-book readers. ``--webtex``\ [``=``\ *URL*] Convert TeX formulas to ```` tags that link to an external script that converts formulas to images. The formula will be URL-encoded and concatenated with the URL provided. For SVG images you can for example use ``--webtex https://latex.codecogs.com/svg.latex?``. If no URL is specified, the CodeCogs URL generating PNGs will be used (``https://latex.codecogs.com/png.latex?``). Note: the ``--webtex`` option will affect Markdown output as well as HTML, which is useful if youâ€™re targeting a version of Markdown without native math support. ``--katex``\ [``=``\ *URL*] Use `KaTeX `__ to display embedded TeX math in HTML output. The *URL* is the base URL for the KaTeX library. That directory should contain a ``katex.min.js`` and a ``katex.min.css`` file. If a *URL* is not provided, a link to the KaTeX CDN will be inserted. ``--gladtex`` Enclose TeX math in ```` tags in HTML output. The resulting HTML can then be processed by `GladTeX `__ to produce SVG images of the typeset formulas and an HTML file with these images embedded. :: pandoc -s --gladtex input.md -o myfile.htex gladtex -d image_dir myfile.htex # produces myfile.html and images in image_dir Options for wrapper scripts --------------------------- ``--dump-args[=true|false]`` Print information about command-line arguments to *stdout*, then exit. This option is intended primarily for use in wrapper scripts. The first line of output contains the name of the output file specified with the ``-o`` option, or ``-`` (for *stdout*) if no output file was specified. The remaining lines contain the command-line arguments, one per line, in the order they appear. These do not include regular pandoc options and their arguments, but do include any options appearing after a ``--`` separator at the end of the line. ``--ignore-args[=true|false]`` Ignore command-line arguments (for use in wrapper scripts). Regular pandoc options are not ignored. Thus, for example, :: pandoc --ignore-args -o foo.html -s foo.txt -- -e latin1 is equivalent to :: pandoc -o foo.html -s Exit codes ========== If pandoc completes successfully, it will return exit code 0. Nonzero exit codes have the following meanings: ==== =================================== Code Error ==== =================================== 1 PandocIOError 3 PandocFailOnWarningError 4 PandocAppError 5 PandocTemplateError 6 PandocOptionError 21 PandocUnknownReaderError 22 PandocUnknownWriterError 23 PandocUnsupportedExtensionError 24 PandocCiteprocError 25 PandocBibliographyError 31 PandocEpubSubdirectoryError 43 PandocPDFError 44 PandocXMLError 47 PandocPDFProgramNotFoundError 61 PandocHttpError 62 PandocShouldNeverHappenError 63 PandocSomeError 64 PandocParseError 66 PandocMakePDFError 67 PandocSyntaxMapError 83 PandocFilterError 84 PandocLuaError 89 PandocNoScriptingEngine 91 PandocMacroLoop 92 PandocUTF8DecodingError 93 PandocIpynbDecodingError 94 PandocUnsupportedCharsetError 95 PandocInputNotTextError 97 PandocCouldNotFindDataFileError 98 PandocCouldNotFindMetadataFileError 99 PandocResourceNotFound ==== =================================== Defaults files ============== The ``--defaults`` option may be used to specify a package of options, in the form of a YAML file. Fields that are omitted will just have their regular default values. So a defaults file can be as simple as one line: .. code:: yaml verbosity: INFO In fields that expect a file path (or list of file paths), the following syntax may be used to interpolate environment variables: .. code:: yaml csl: ${HOME}/mycsldir/special.csl ``${USERDATA}`` may also be used; this will always resolve to the user data directory that is current when the defaults file is parsed, regardless of the setting of the environment variable ``USERDATA``. ``${.}`` will resolve to the directory containing the defaults file itself. This allows you to refer to resources contained in that directory: .. code:: yaml epub-cover-image: ${.}/cover.jpg epub-metadata: ${.}/meta.xml resource-path: - . # the working directory from which pandoc is run - ${.}/images # the images subdirectory of the directory # containing this defaults file This environment variable interpolation syntax *only* works in fields that expect file paths. Defaults files can be placed in the ``defaults`` subdirectory of the user data directory and used from any directory. For example, one could create a file specifying defaults for writing letters, save it as ``letter.yaml`` in the ``defaults`` subdirectory of the user data directory, and then invoke these defaults from any directory using ``pandoc --defaults letter`` or ``pandoc -dletter``. When multiple defaults are used, their contents will be combined. Note that, where command-line arguments may be repeated (``--metadata-file``, ``--css``, ``--include-in-header``, ``--include-before-body``, ``--include-after-body``, ``--variable``, ``--metadata``, ``--syntax-definition``), the values specified on the command line will combine with values specified in the defaults file, rather than replacing them. The following tables show the mapping between the command line and defaults file entries. +----------------------------------+-----------------------------------+ | command line | defaults file | +==================================+===================================+ | :: | .. code:: yaml | | | | | foo.md | input-file: foo.md | +----------------------------------+-----------------------------------+ | :: | .. code:: yaml | | | | | foo.md bar.md | input-files: | | | - foo.md | | | - bar.md | +----------------------------------+-----------------------------------+ The value of ``input-files`` may be left empty to indicate input from stdin, and it can be an empty sequence ``[]`` for no input. .. _general-options-1: General options --------------- +-----------------------------------+--------------------------------------+ | command line | defaults file | +===================================+======================================+ | :: | .. code:: yaml | | | | | --from markdown+emoji | from: markdown+emoji | | | | | | .. code:: yaml | | | | | | reader: markdown+emoji | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --to markdown+hard_line_breaks | to: markdown+hard_line_breaks | | | | | | .. code:: yaml | | | | | | writer: markdown+hard_line_breaks | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --output foo.pdf | output-file: foo.pdf | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --output - | output-file: | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --data-dir dir | data-dir: dir | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --defaults file | defaults: | | | - file | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --verbose | verbosity: INFO | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --quiet | verbosity: ERROR | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --fail-if-warnings | fail-if-warnings: true | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --sandbox | sandbox: true | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --log=FILE | log-file: FILE | +-----------------------------------+--------------------------------------+ Options specified in a defaults file itself always have priority over those in another file included with a ``defaults:`` entry. ``verbosity`` can have the values ``ERROR``, ``WARNING``, or ``INFO``. .. _reader-options-1: Reader options -------------- +-------------------------------------+------------------------------------+ | command line | defaults file | +=====================================+====================================+ | :: | .. code:: yaml | | | | | --shift-heading-level-by -1 | shift-heading-level-by: -1 | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --indented-code-classes python | indented-code-classes: | | | - python | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --default-image-extension ".jpg" | default-image-extension: '.jpg' | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --file-scope | file-scope: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --citeproc \ | filters: | | --lua-filter count-words.lua \ | - citeproc | | --filter special.lua | - count-words.lua | | | - type: json | | | path: special.lua | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --metadata key=value \ | metadata: | | --metadata key2 | key: value | | | key2: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --metadata-file meta.yaml | metadata-files: | | | - meta.yaml | | | | | | .. code:: yaml | | | | | | metadata-file: meta.yaml | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --preserve-tabs | preserve-tabs: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --tab-stop 8 | tab-stop: 8 | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --track-changes accept | track-changes: accept | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --extract-media dir | extract-media: dir | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --abbreviations abbrevs.txt | abbreviations: abbrevs.txt | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --trace | trace: true | +-------------------------------------+------------------------------------+ Metadata values specified in a defaults file are parsed as literal string text, not Markdown. Filters will be assumed to be Lua filters if they have the ``.lua`` extension, and JSON filters otherwise. But the filter type can also be specified explicitly, as shown. Filters are run in the order specified. To include the built-in citeproc filter, use either ``citeproc`` or ``{type: citeproc}``. .. _general-writer-options-1: General writer options ---------------------- +-----------------------------------+--------------------------------------+ | command line | defaults file | +===================================+======================================+ | :: | .. code:: yaml | | | | | --standalone | standalone: true | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --template letter | template: letter | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --variable key=val \ | variables: | | --variable key2 | key: val | | | key2: true | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --eol nl | eol: nl | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --dpi 300 | dpi: 300 | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --wrap 60 | wrap: 60 | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --columns 72 | columns: 72 | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --table-of-contents | table-of-contents: true | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --toc | toc: true | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --toc-depth 3 | toc-depth: 3 | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --strip-comments | strip-comments: true | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --no-highlight | syntax-highlighting: 'none' | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --syntax-highlighting kate | syntax-highlighting: kate | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --syntax-definition mylang.xml | syntax-definitions: | | | - mylang.xml | | | | | | .. code:: yaml | | | | | | syntax-definition: mylang.xml | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --include-in-header inc.tex | include-in-header: | | | - inc.tex | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --include-before-body inc.tex | include-before-body: | | | - inc.tex | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --include-after-body inc.tex | include-after-body: | | | - inc.tex | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --resource-path .:foo | resource-path: ['.','foo'] | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --request-header foo:bar | request-headers: | | | - ["User-Agent", "Mozilla/5.0"] | +-----------------------------------+--------------------------------------+ | :: | .. code:: yaml | | | | | --no-check-certificate | no-check-certificate: true | +-----------------------------------+--------------------------------------+ .. _options-affecting-specific-writers-1: Options affecting specific writers ---------------------------------- +-------------------------------------+------------------------------------+ | command line | defaults file | +=====================================+====================================+ | :: | .. code:: yaml | | | | | --self-contained | self-contained: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --link-images | link-images: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --html-q-tags | html-q-tags: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --ascii | ascii: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --reference-links | reference-links: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --reference-location block | reference-location: block | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --figure-caption-position=above | figure-caption-position: above | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --table-caption-position=below | table-caption-position: below | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --markdown-headings atx | markdown-headings: atx | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --list-tables | list-tables: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --top-level-division chapter | top-level-division: chapter | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --number-sections | number-sections: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --number-offset=1,4 | number-offset: \[1,4\] | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --listings | listings: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --list-of-figures | list-of-figures: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --lof | lof: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --list-of-tables | list-of-tables: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --lot | lot: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --incremental | incremental: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --slide-level 2 | slide-level: 2 | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --section-divs | section-divs: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --email-obfuscation references | email-obfuscation: references | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --id-prefix ch1 | identifier-prefix: ch1 | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --title-prefix MySite | title-prefix: MySite | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --css styles/screen.css \ | css: | | --css styles/special.css | - styles/screen.css | | | - styles/special.css | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --reference-doc my.docx | reference-doc: my.docx | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --epub-cover-image cover.jpg | epub-cover-image: cover.jpg | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --epub-title-page=false | epub-title-page: false | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --epub-metadata meta.xml | epub-metadata: meta.xml | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --epub-embed-font special.otf \ | epub-fonts: | | --epub-embed-font headline.otf | - special.otf | | | - headline.otf | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --split-level 2 | split-level: 2 | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --chunk-template="%i.html" | chunk-template: "%i.html" | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --epub-subdirectory="" | epub-subdirectory: '' | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --ipynb-output best | ipynb-output: best | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --pdf-engine xelatex | pdf-engine: xelatex | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --pdf-engine-opt=--shell-escape | pdf-engine-opts: | | | - '-shell-escape' | | | | | | .. code:: yaml | | | | | | pdf-engine-opt: '-shell-escape' | +-------------------------------------+------------------------------------+ .. _citation-rendering-1: Citation rendering ------------------ +-------------------------------------+------------------------------------+ | command line | defaults file | +=====================================+====================================+ | :: | .. code:: yaml | | | | | --citeproc | citeproc: true | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --bibliography logic.bib | bibliography: logic.bib | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --csl ieee.csl | csl: ieee.csl | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --citation-abbreviations ab.json | citation-abbreviations: ab.json | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --natbib | cite-method: natbib | +-------------------------------------+------------------------------------+ | :: | .. code:: yaml | | | | | --biblatex | cite-method: biblatex | +-------------------------------------+------------------------------------+ ``cite-method`` can be ``citeproc``, ``natbib``, or ``biblatex``. This only affects LaTeX output. If you want to use citeproc to format citations, you should also set â€˜citeproc: trueâ€™. If you need control over when the citeproc processing is done relative to other filters, you should instead use ``citeproc`` in the list of ``filters`` (see `Reader options <#reader-options-1>`__). .. _math-rendering-in-html-1: Math rendering in HTML ---------------------- +----------------------------------+-----------------------------------+ | command line | defaults file | +==================================+===================================+ | :: | .. code:: yaml | | | | | --mathjax | html-math-method: | | | method: mathjax | +----------------------------------+-----------------------------------+ | :: | .. code:: yaml | | | | | --mathml | html-math-method: | | | method: mathml | +----------------------------------+-----------------------------------+ | :: | .. code:: yaml | | | | | --webtex | html-math-method: | | | method: webtex | +----------------------------------+-----------------------------------+ | :: | .. code:: yaml | | | | | --katex | html-math-method: | | | method: katex | +----------------------------------+-----------------------------------+ | :: | .. code:: yaml | | | | | --gladtex | html-math-method: | | | method: gladtex | +----------------------------------+-----------------------------------+ In addition to the values listed above, ``method`` can have the value ``plain``. If the command line option accepts a URL argument, an ``url:`` field can be added to ``html-math-method:``. .. _options-for-wrapper-scripts-1: Options for wrapper scripts --------------------------- +----------------------------------+-----------------------------------+ | command line | defaults file | +==================================+===================================+ | :: | .. code:: yaml | | | | | --dump-args | dump-args: true | +----------------------------------+-----------------------------------+ | :: | .. code:: yaml | | | | | --ignore-args | ignore-args: true | +----------------------------------+-----------------------------------+ Templates ========= When the ``-s/--standalone`` option is used, pandoc uses a template to add header and footer material that is needed for a self-standing document. To see the default template that is used, just type :: pandoc -D *FORMAT* where *FORMAT* is the name of the output format. A custom template can be specified using the ``--template`` option. You can also override the system default templates for a given output format *FORMAT* by putting a file ``templates/default.*FORMAT*`` in the user data directory (see ``--data-dir``, above). *Exceptions:* - For ``odt`` output, customize the ``default.opendocument`` template. - For ``docx`` output, customize the ``default.openxml`` template. - For ``pdf`` output, customize the ``default.latex`` template (or the ``default.context`` template, if you use ``-t context``, or the ``default.ms`` template, if you use ``-t ms``, or the ``default.html`` template, if you use ``-t html``). - ``pptx`` has no template. Note that ``docx``, ``odt``, and ``pptx`` output can also be customized using ``--reference-doc``. Use a reference doc to adjust the styles in your document; use a template to handle variable interpolation and customize the presentation of metadata, the position of the table of contents, boilerplate text, etc. Templates contain *variables*, which allow for the inclusion of arbitrary information at any point in the file. They may be set at the command line using the ``-V/--variable`` option. If a variable is not set, pandoc will look for the key in the documentâ€™s metadata, which can be set using either `YAML metadata blocks <#extension-yaml_metadata_block>`__ or with the ``-M/--metadata`` option. In addition, some variables are given default values by pandoc. See `Variables <#variables>`__ below for a list of variables used in pandocâ€™s default templates. If you use custom templates, you may need to revise them as pandoc changes. We recommend tracking the changes in the default templates, and modifying your custom templates accordingly. An easy way to do this is to fork the `pandoc-templates `__ repository and merge in changes after each pandoc release. Template syntax --------------- Comments ~~~~~~~~ Anything between the sequence ``$--`` and the end of the line will be treated as a comment and omitted from the output. Delimiters ~~~~~~~~~~ To mark variables and control structures in the template, either ``$``\ â€¦\ ``$`` or ``${``\ â€¦\ ``}`` may be used as delimiters. The styles may also be mixed in the same template, but the opening and closing delimiter must match in each case. The opening delimiter may be followed by one or more spaces or tabs, which will be ignored. The closing delimiter may be preceded by one or more spaces or tabs, which will be ignored. To include a literal ``$`` in the document, use ``$$``. Interpolated variables ~~~~~~~~~~~~~~~~~~~~~~ A slot for an interpolated variable is a variable name surrounded by matched delimiters. Variable names must begin with a letter and can contain letters, numbers, ``_``, ``-``, and ``.``. The keywords ``it``, ``if``, ``else``, ``endif``, ``for``, ``sep``, and ``endfor`` may not be used as variable names. Examples: :: $foo$ $foo.bar.baz$ $foo_bar.baz-bim$ $ foo $ ${foo} ${foo.bar.baz} ${foo_bar.baz-bim} ${ foo } Variable names with periods are used to get at structured variable values. So, for example, ``employee.salary`` will return the value of the ``salary`` field of the object that is the value of the ``employee`` field. - If the value of the variable is a simple value, it will be rendered verbatim. (Note that no escaping is done; the assumption is that the calling program will escape the strings appropriately for the output format.) - If the value is a list, the values will be concatenated. - If the value is a map, the string ``true`` will be rendered. - Every other value will be rendered as the empty string. Conditionals ~~~~~~~~~~~~ A conditional begins with ``if(variable)`` (enclosed in matched delimiters) and ends with ``endif`` (enclosed in matched delimiters). It may optionally contain an ``else`` (enclosed in matched delimiters). The ``if`` section is used if ``variable`` has a true value, otherwise the ``else`` section is used (if present). The following values count as true: - any map - any array containing at least one true value - any nonempty string - boolean True Note that in YAML metadata (and metadata specified on the command line using ``-M/--metadata``), unquoted ``true`` and ``false`` will be interpreted as Boolean values. But a variable specified on the command line using ``-V/--variable`` will always be given a string value. Hence a conditional ``if(foo)`` will be triggered if you use ``-V foo=false``, but not if you use ``-M foo=false``. Examples: :: $if(foo)$bar$endif$ $if(foo)$ $foo$ $endif$ $if(foo)$ part one $else$ part two $endif$ ${if(foo)}bar${endif} ${if(foo)} ${foo} ${endif} ${if(foo)} ${ foo.bar } ${else} no foo! ${endif} The keyword ``elseif`` may be used to simplify complex nested conditionals: :: $if(foo)$ XXX $elseif(bar)$ YYY $else$ ZZZ $endif$ For loops ~~~~~~~~~ A for loop begins with ``for(variable)`` (enclosed in matched delimiters) and ends with ``endfor`` (enclosed in matched delimiters). - If ``variable`` is an array, the material inside the loop will be evaluated repeatedly, with ``variable`` being set to each value of the array in turn, and concatenated. - If ``variable`` is a map, the material inside will be set to the map. - If the value of the associated variable is not an array or a map, a single iteration will be performed on its value. Examples: :: $for(foo)$$foo$$sep$, $endfor$ $for(foo)$ - $foo.last$, $foo.first$ $endfor$ ${ for(foo.bar) } - ${ foo.bar.last }, ${ foo.bar.first } ${ endfor } $for(mymap)$ $it.name$: $it.office$ $endfor$ You may optionally specify a separator between consecutive values using ``sep`` (enclosed in matched delimiters). The material between ``sep`` and the ``endfor`` is the separator. :: ${ for(foo) }${ foo }${ sep }, ${ endfor } Instead of using ``variable`` inside the loop, the special anaphoric keyword ``it`` may be used. :: ${ for(foo.bar) } - ${ it.last }, ${ it.first } ${ endfor } Partials ~~~~~~~~ Partials (subtemplates stored in different files) may be included by using the name of the partial, followed by ``()``, for example: :: ${ styles() } Partials will be sought in the directory containing the main template. The file name will be assumed to have the same extension as the main template if it lacks an extension. When calling the partial, the full name including file extension can also be used: :: ${ styles.html() } (If a partial is not found in the directory of the template and the template path is given as a relative path, it will also be sought in the ``templates`` subdirectory of the user data directory.) Partials may optionally be applied to variables using a colon: :: ${ date:fancy() } ${ articles:bibentry() } If ``articles`` is an array, this will iterate over its values, applying the partial ``bibentry()`` to each one. So the second example above is equivalent to :: ${ for(articles) } ${ it:bibentry() } ${ endfor } Note that the anaphoric keyword ``it`` must be used when iterating over partials. In the above examples, the ``bibentry`` partial should contain ``it.title`` (and so on) instead of ``articles.title``. Final newlines are omitted from included partials. Partials may include other partials. A separator between values of an array may be specified in square brackets, immediately after the variable name or partial: :: ${months[, ]} ${articles:bibentry()[; ]} The separator in this case is literal and (unlike with ``sep`` in an explicit ``for`` loop) cannot contain interpolated variables or other template directives. Nesting ~~~~~~~ To ensure that content is â€œnested,â€ that is, subsequent lines indented, use the ``^`` directive: :: $item.number$ $^$$item.description$ ($item.price$) In this example, if ``item.description`` has multiple lines, they will all be indented to line up with the first line: :: 00123 A fine bottle of 18-year old Oban whiskey. ($148) To nest multiple lines to the same level, align them with the ``^`` directive in the template. For example: :: $item.number$ $^$$item.description$ ($item.price$) (Available til $item.sellby$.) will produce :: 00123 A fine bottle of 18-year old Oban whiskey. ($148) (Available til March 30, 2020.) If a variable occurs by itself on a line, preceded by whitespace and not followed by further text or directives on the same line, and the variableâ€™s value contains multiple lines, it will be nested automatically. Breakable spaces ~~~~~~~~~~~~~~~~ Normally, spaces in the template itself (as opposed to values of the interpolated variables) are not breakable, but they can be made breakable in part of the template by using the ``~`` keyword (ended with another ``~``). :: $~$This long line may break if the document is rendered with a short line length.$~$ Pipes ~~~~~ A pipe transforms the value of a variable or partial. Pipes are specified using a slash (``/``) between the variable name (or partial) and the pipe name. Example: :: $for(name)$ $name/uppercase$ $endfor$ $for(metadata/pairs)$ - $it.key$: $it.value$ $endfor$ $employee:name()/uppercase$ Pipes may be chained: :: $for(employees/pairs)$ $it.key/alpha/uppercase$. $it.name$ $endfor$ Some pipes take parameters: :: |----------------------|------------| $for(employee)$ $it.name.first/uppercase/left 20 "| "$$it.name.salary/right 10 " | " " |"$ $endfor$ |----------------------|------------| Currently the following pipes are predefined: - ``pairs``: Converts a map or array to an array of maps, each with ``key`` and ``value`` fields. If the original value was an array, the ``key`` will be the array index, starting with 1. - ``uppercase``: Converts text to uppercase. - ``lowercase``: Converts text to lowercase. - ``length``: Returns the length of the value: number of characters for a textual value, number of elements for a map or array. - ``reverse``: Reverses a textual value or array, and has no effect on other values. - ``first``: Returns the first value of an array, if applied to a non-empty array; otherwise returns the original value. - ``last``: Returns the last value of an array, if applied to a non-empty array; otherwise returns the original value. - ``rest``: Returns all but the first value of an array, if applied to a non-empty array; otherwise returns the original value. - ``allbutlast``: Returns all but the last value of an array, if applied to a non-empty array; otherwise returns the original value. - ``chomp``: Removes trailing newlines (and breakable space). - ``nowrap``: Disables line wrapping on breakable spaces. - ``alpha``: Converts textual values that can be read as an integer into lowercase alphabetic characters ``a..z`` (mod 26). This can be used to get lettered enumeration from array indices. To get uppercase letters, chain with ``uppercase``. - ``roman``: Converts textual values that can be read as an integer into lowercase roman numerals. This can be used to get lettered enumeration from array indices. To get uppercase roman, chain with ``uppercase``. - ``left n "leftborder" "rightborder"``: Renders a textual value in a block of width ``n``, aligned to the left, with an optional left and right border. Has no effect on other values. This can be used to align material in tables. Widths are positive integers indicating the number of characters. Borders are strings inside double quotes; literal ``"`` and ``\`` characters must be backslash-escaped. - ``right n "leftborder" "rightborder"``: Renders a textual value in a block of width ``n``, aligned to the right, and has no effect on other values. - ``center n "leftborder" "rightborder"``: Renders a textual value in a block of width ``n``, aligned to the center, and has no effect on other values. Variables --------- Metadata variables ~~~~~~~~~~~~~~~~~~ ``title``, ``author``, ``date`` allow identification of basic aspects of the document. Included in PDF metadata through LaTeX and ConTeXt. These can be set through a `pandoc title block <#extension-pandoc_title_block>`__, which allows for multiple authors, or through a `YAML metadata block <#extension-yaml_metadata_block>`__: :: --- author: - Aristotle - Peter Abelard ... Note that if you just want to set PDF or HTML metadata, without including a title block in the document itself, you can set the ``title-meta``, ``author-meta``, and ``date-meta`` variables. (By default these are set automatically, based on ``title``, ``author``, and ``date``.) The page title in HTML is set by ``pagetitle``, which is equal to ``title`` by default. ``subtitle`` document subtitle, included in HTML, EPUB, LaTeX, ConTeXt, and docx documents ``abstract`` document summary, included in HTML, LaTeX, ConTeXt, AsciiDoc, and docx documents ``abstract-title`` title of abstract, currently used only in HTML, EPUB, docx, and Typst. This will be set automatically to a localized value, depending on ``lang``, but can be manually overridden. ``keywords`` list of keywords to be included in HTML, PDF, ODT, pptx, docx and AsciiDoc metadata; repeat as for ``author``, above ``subject`` document subject, included in ODT, PDF, docx, EPUB, and pptx metadata ``description`` document description, included in ODT, docx and pptx metadata. Some applications show this as ``Comments`` metadata. ``category`` document category, included in docx and pptx metadata Additionally, any root-level string metadata, not included in ODT, docx or pptx metadata is added as a *custom property*. The following `YAML `__ metadata block for instance: :: --- title: 'This is the title' subtitle: "This is the subtitle" author: - Author One - Author Two description: | This is a long description. It consists of two paragraphs ... will include ``title``, ``author`` and ``description`` as standard document properties and ``subtitle`` as a custom property when converting to docx, ODT or pptx. Language variables ~~~~~~~~~~~~~~~~~~ ``lang`` identifies the main language of the document using IETF language tags (following the `BCP 47 `__ standard), such as ``en`` or ``en-GB``. The `Language subtag lookup `__ tool can look up or verify these tags. This affects most formats, and controls hyphenation in PDF output when using LaTeX (through ```babel`` `__ and ```polyglossia`` `__) or ConTeXt. Use native pandoc `Divs and Spans <#divs-and-spans>`__ with the ``lang`` attribute to switch the language: :: --- lang: en-GB ... Text in the main document language (British English). ::: {lang=fr-CA} > Cette citation est Ã©crite en franÃ§ais canadien. ::: More text in English. ['Zitat auf Deutsch.']{lang=de} ``dir`` the base script direction, either ``rtl`` (right-to-left) or ``ltr`` (left-to-right). For bidirectional documents, native pandoc ``span``\ s and ``div``\ s with the ``dir`` attribute (value ``rtl`` or ``ltr``) can be used to override the base direction in some output formats. This may not always be necessary if the final renderer (e.g.Â the browser, when generating HTML) supports the `Unicode Bidirectional Algorithm `__. When using LaTeX for bidirectional documents, only the ``xelatex`` engine is fully supported (use ``--pdf-engine=xelatex``). Variables for HTML ~~~~~~~~~~~~~~~~~~ ``document-css`` Enables inclusion of most of the `CSS `__ in the ``styles.html`` `partial <#partials>`__ (have a look with ``pandoc --print-default-data-file=templates/styles.html``). Unless you use ``--css``, this variable is set to ``true`` by default. You can disable it with e.g.Â ``pandoc -M document-css=false``. ``mainfont`` sets the CSS ``font-family`` property on the ``html`` element. ``fontsize`` sets the base CSS ``font-size``, which youâ€™d usually set to e.g.Â ``20px``, but it also accepts ``pt`` (12pt = 16px in most browsers). ``fontcolor`` sets the CSS ``color`` property on the ``html`` element. ``linkcolor`` sets the CSS ``color`` property on all links. ``monofont`` sets the CSS ``font-family`` property on ``code`` elements. ``monobackgroundcolor`` sets the CSS ``background-color`` property on ``code`` elements and adds extra padding. ``linestretch`` sets the CSS ``line-height`` property on the ``html`` element, which is preferred to be unitless. ``maxwidth`` sets the CSS ``max-width`` property (default is 36em). ``backgroundcolor`` sets the CSS ``background-color`` property on the ``html`` element. ``margin-left``, ``margin-right``, ``margin-top``, ``margin-bottom`` sets the corresponding CSS ``padding`` properties on the ``body`` element. To override or extend some `CSS `__ for just one document, include for example: :: --- header-includes: | --- Variables for HTML math ~~~~~~~~~~~~~~~~~~~~~~~ ``classoption`` when using ``--katex``, you can render display math equations flush left using `YAML metadata <#layout>`__ or with ``-M classoption=fleqn``. Variables for HTML slides ~~~~~~~~~~~~~~~~~~~~~~~~~ These affect HTML output when `producing slide shows with pandoc <#slide-shows>`__. ``institute`` author affiliations: can be a list when there are multiple authors ``revealjs-url`` base URL for reveal.js documents (defaults to ``https://unpkg.com/reveal.js@^5``) ``s5-url`` base URL for S5 documents (defaults to ``s5/default``) ``slidy-url`` base URL for Slidy documents (defaults to ``https://www.w3.org/Talks/Tools/Slidy2``) ``slideous-url`` base URL for Slideous documents (defaults to ``slideous``) ``title-slide-attributes`` additional attributes for the title slide of reveal.js slide shows. See `background in reveal.js, beamer, and pptx <#background-in-reveal.js-beamer-and-pptx>`__ for an example. All `reveal.js configuration options `__ are available as variables. To turn off boolean flags that default to true in reveal.js, use ``0``. Variables for Beamer slides ~~~~~~~~~~~~~~~~~~~~~~~~~~~ These variables change the appearance of PDF slides using ```beamer`` `__. ``aspectratio`` slide aspect ratio (``43`` for 4:3 [default], ``169`` for 16:9, ``1610`` for 16:10, ``149`` for 14:9, ``141`` for 1.41:1, ``54`` for 5:4, ``32`` for 3:2) ``beameroption`` add extra beamer option with ``\setbeameroption{}`` ``institute`` author affiliations: can be a list when there are multiple authors ``logo`` logo image for slides ``navigation`` controls navigation symbols (default is ``empty`` for no navigation symbols; other valid values are ``frame``, ``vertical``, and ``horizontal``) ``section-titles`` enables â€œtitle pagesâ€ for new sections (default is true) ``theme``, ``colortheme``, ``fonttheme``, ``innertheme``, ``outertheme`` beamer themes ``themeoptions``, ``colorthemeoptions``, ``fontthemeoptions``, ``innerthemeoptions``, ``outerthemeoptions`` options for LaTeX beamer themes (lists) ``titlegraphic`` image for title slide: can be a list ``titlegraphicoptions`` options for title slide image ``shorttitle``, ``shortsubtitle``, ``shortauthor``, ``shortinstitute``, ``shortdate`` some beamer themes use short versions of the title, subtitle, author, institute, date Variables for PowerPoint ~~~~~~~~~~~~~~~~~~~~~~~~ These variables control the visual aspects of a slide show that are not easily controlled via templates. ``monofont`` font to use for code. Variables for LaTeX ~~~~~~~~~~~~~~~~~~~ Pandoc uses these variables when `creating a PDF <#creating-a-pdf>`__ with a LaTeX engine. Layout ^^^^^^ ``block-headings`` make ``\paragraph`` and ``\subparagraph`` (fourth- and fifth-level headings, or fifth- and sixth-level with book classes) free-standing rather than run-in; requires further formatting to distinguish from ``\subsubsection`` (third- or fourth-level headings). Instead of using this option, `KOMA-Script `__ can adjust headings more extensively: :: --- documentclass: scrartcl header-includes: | \RedeclareSectionCommand[ beforeskip=-10pt plus -2pt minus -1pt, afterskip=1sp plus -1sp minus 1sp, font=\normalfont\itshape]{paragraph} \RedeclareSectionCommand[ beforeskip=-10pt plus -2pt minus -1pt, afterskip=1sp plus -1sp minus 1sp, font=\normalfont\scshape, indent=0pt]{subparagraph} ... ``classoption`` option for document class, e.g.Â ``oneside``; repeat for multiple options: :: --- classoption: - twocolumn - landscape ... ``documentclass`` document class: usually one of the standard classes, ```article`` `__, ```book`` `__, and ```report`` `__; the `KOMA-Script `__ equivalents, ``scrartcl``, ``scrbook``, and ``scrreprt``, which default to smaller margins; or ```memoir`` `__ ``geometry`` option for ```geometry`` `__ package, e.g.Â ``margin=1in``; repeat for multiple options: :: --- geometry: - top=30mm - left=20mm - heightrounded ... ``shorthands`` Enable language-specific shorthands when loading ``babel``. (By default, pandoc includes ``shorthands=off`` when loading ``babel``, disabling language-specific shorthands.) ``hyperrefoptions`` option for ```hyperref`` `__ package, e.g.Â ``linktoc=all``; repeat for multiple options: :: --- hyperrefoptions: - linktoc=all - pdfwindowui - pdfpagemode=FullScreen ... ``indent`` if true, pandoc will use document class settings for indentation (the default LaTeX template otherwise removes indentation and adds space between paragraphs) ``linestretch`` adjusts line spacing using the ```setspace`` `__ package, e.g.Â ``1.25``, ``1.5`` ``margin-left``, ``margin-right``, ``margin-top``, ``margin-bottom`` sets margins if ``geometry`` is not used (otherwise ``geometry`` overrides these) ``pagestyle`` control ``\pagestyle{}``: the default article class supports ``plain`` (default), ``empty`` (no running heads or page numbers), and ``headings`` (section titles in running heads) ``papersize`` paper size, e.g.Â ``letter``, ``a4`` ``secnumdepth`` numbering depth for sections (with ``--number-sections`` option or ``numbersections`` variable) ``beamerarticle`` produce an article from Beamer slides. Note: if you set this variable, you must specify the beamer writer but use the default *LaTeX* template: for example, ``pandoc -Vbeamerarticle -t beamer --template default.latex``. ``handout`` produce a handout version of Beamer slides (with overlays condensed into single slides) ``csquotes`` load ``csquotes`` package and use ``\enquote`` or ``\enquote*`` for quoted text. ``csquotesoptions`` options to use for ``csquotes`` package (repeat for multiple options). ``babeloptions`` options to pass to the babel package (may be repeated for multiple options). This defaults to ``provide=*`` if the main language isnâ€™t a European language written with Latin or Cyrillic script or Vietnamese. Most users will not need to adjust the default setting. Fonts ^^^^^ ``fontenc`` allows font encoding to be specified through ``fontenc`` package (with ``pdflatex``); default is ``T1`` (see `LaTeX font encodings guide `__) ``fontfamily`` font package for use with ``pdflatex``: `TeX Live `__ includes many options, documented in the `LaTeX Font Catalogue `__. The default is `Latin Modern `__. ``fontfamilyoptions`` options for package used as ``fontfamily``; repeat for multiple options. For example, to use the Libertine font with proportional lowercase (old-style) figures through the ```libertinus`` `__ package: :: --- fontfamily: libertinus fontfamilyoptions: - osf - p ... ``fontsize`` font size for body text. The standard classes allow 10pt, 11pt, and 12pt. To use another size, set ``documentclass`` to one of the `KOMA-Script `__ classes, such as ``scrartcl`` or ``scrbook``. ``mainfont``, ``sansfont``, ``monofont``, ``mathfont``, ``CJKmainfont``, ``CJKsansfont``, ``CJKmonofont`` font families for use with ``xelatex`` or ``lualatex``: take the name of any system font, using the ```fontspec`` `__ package. ``CJKmainfont`` uses the ```xecjk`` `__ package if ``xelatex`` is used, or the ```luatexja`` `__ package if ``lualatex`` is used. ``mainfontoptions``, ``sansfontoptions``, ``monofontoptions``, ``mathfontoptions``, ``CJKoptions``, ``luatexjapresetoptions`` options to use with ``mainfont``, ``sansfont``, ``monofont``, ``mathfont``, ``CJKmainfont`` in ``xelatex`` and ``lualatex``. Allow for any choices available through ```fontspec`` `__; repeat for multiple options. For example, to use the `TeX Gyre `__ version of Palatino with lowercase figures: :: --- mainfont: TeX Gyre Pagella mainfontoptions: - Numbers=Lowercase - Numbers=Proportional ... ``mainfontfallback``, ``sansfontfallback``, ``monofontfallback`` fonts to try if a glyph isnâ€™t found in ``mainfont``, ``sansfont``, or ``monofont`` respectively. These are lists. The font name must be followed by a colon and optionally a set of options, for example: :: --- mainfontfallback: - "FreeSans:" - "NotoColorEmoji:mode=harf" ... Font fallbacks currently only work with ``lualatex``. ``babelfonts`` a map of Babel language names (e.g.Â ``chinese``) to the font to be used with the language: :: --- babelfonts: chinese-hant: "Noto Serif CJK TC" russian: "Noto Serif" ... ``microtypeoptions`` options to pass to the microtype package Links ^^^^^ ``colorlinks`` add color to link text; automatically enabled if any of ``linkcolor``, ``filecolor``, ``citecolor``, ``urlcolor``, or ``toccolor`` are set ``boxlinks`` add visible box around links (has no effect if ``colorlinks`` is set) ``linkcolor``, ``filecolor``, ``citecolor``, ``urlcolor``, ``toccolor`` color for internal links, external links, citation links, linked URLs, and links in table of contents, respectively: uses options allowed by ```xcolor`` `__, including the ``dvipsnames``, ``svgnames``, and ``x11names`` lists ``links-as-notes`` causes links to be printed as footnotes ``urlstyle`` style for URLs (e.g., ``tt``, ``rm``, ``sf``, and, the default, ``same``) Front matter ^^^^^^^^^^^^ ``lof``, ``lot`` include list of figures, list of tables (can also be set using ``--lof/--list-of-figures``, ``--lot/--list-of-tables``) ``thanks`` contents of acknowledgments footnote after document title ``toc`` include table of contents (can also be set using ``--toc/--table-of-contents``) ``toc-depth`` level of section to include in table of contents BibLaTeX Bibliographies ^^^^^^^^^^^^^^^^^^^^^^^ These variables function when using BibLaTeX for `citation rendering <#citation-rendering>`__. ``biblatexoptions`` list of options for biblatex ``biblio-style`` bibliography style, when used with ``--natbib`` and ``--biblatex`` ``biblio-title`` bibliography title, when used with ``--natbib`` and ``--biblatex`` ``bibliography`` bibliography to use for resolving references ``natbiboptions`` list of options for natbib Other ^^^^^ ``pdf-trailer-id`` the PDF trailer ID; must be two PDF byte strings if set, conventionally with 16 bytes each. E.g., ``<00112233445566778899aabbccddeeff> <00112233445566778899aabbccddeeff>``. See the section on `reproducible builds <#reproducible-builds>`__. Variables for ConTeXt ~~~~~~~~~~~~~~~~~~~~~ Pandoc uses these variables when `creating a PDF <#creating-a-pdf>`__ with ConTeXt. ``fontsize`` font size for body text (e.g.Â ``10pt``, ``12pt``) ``headertext``, ``footertext`` text to be placed in running header or footer (see `ConTeXt Headers and Footers `__); repeat up to four times for different placement ``indenting`` controls indentation of paragraphs, e.g.Â ``yes,small,next`` (see `ConTeXt Indentation `__); repeat for multiple options ``interlinespace`` adjusts line spacing, e.g.Â ``4ex`` (using ```setupinterlinespace`` `__); repeat for multiple options ``layout`` options for page margins and text arrangement (see `ConTeXt Layout `__); repeat for multiple options ``linkcolor``, ``contrastcolor`` color for links outside and inside a page, e.g.Â ``red``, ``blue`` (see `ConTeXt Color `__) ``linkstyle`` typeface style for links, e.g.Â ``normal``, ``bold``, ``slanted``, ``boldslanted``, ``type``, ``cap``, ``small`` ``lof``, ``lot`` include list of figures, list of tables ``mainfont``, ``sansfont``, ``monofont``, ``mathfont`` font families: take the name of any system font (see `ConTeXt Font Switching `__) ``mainfontfallback``, ``sansfontfallback``, ``monofontfallback`` list of fonts to try, in order, if a glyph is not found in the main font. Use ``\definefallbackfamily``-compatible font name syntax. Emoji fonts are unsupported. ``margin-left``, ``margin-right``, ``margin-top``, ``margin-bottom`` sets margins, if ``layout`` is not used (otherwise ``layout`` overrides these) ``pagenumbering`` page number style and location (using ```setuppagenumbering`` `__); repeat for multiple options ``papersize`` paper size, e.g.Â ``letter``, ``A4``, ``landscape`` (see `ConTeXt Paper Setup `__); repeat for multiple options ``pdfa`` adds to the preamble the setup necessary to generate PDF/A of the type specified, e.g.Â ``1a:2005``, ``2a``. If no type is specified (i.e.Â the value is set to True, by e.g. ``--metadata=pdfa`` or ``pdfa: true`` in a YAML metadata block), ``1b:2005`` will be used as default, for reasons of backwards compatibility. Using ``--variable=pdfa`` without specified value is not supported. To successfully generate PDF/A the required ICC color profiles have to be available and the content and all included files (such as images) have to be standard-conforming. The ICC profiles and output intent may be specified using the variables ``pdfaiccprofile`` and ``pdfaintent``. See also `ConTeXt PDFA `__ for more details. ``pdfaiccprofile`` when used in conjunction with ``pdfa``, specifies the ICC profile to use in the PDF, e.g.Â ``default.cmyk``. If left unspecified, ``sRGB.icc`` is used as default. May be repeated to include multiple profiles. Note that the profiles have to be available on the system. They can be obtained from `ConTeXt ICC Profiles `__. ``pdfaintent`` when used in conjunction with ``pdfa``, specifies the output intent for the colors, e.g.Â ``ISO coated v2 300\letterpercent\space (ECI)`` If left unspecified, ``sRGB IEC61966-2.1`` is used as default. ``toc`` include table of contents (can also be set using ``--toc/--table-of-contents``) ``urlstyle`` typeface style for links without link text, e.g.Â ``normal``, ``bold``, ``slanted``, ``boldslanted``, ``type``, ``cap``, ``small`` ``whitespace`` spacing between paragraphs, e.g.Â ``none``, ``small`` (using ```setupwhitespace`` `__) ``includesource`` include all source documents as file attachments in the PDF file Variables for ``wkhtmltopdf`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Pandoc uses these variables when `creating a PDF <#creating-a-pdf>`__ with ```wkhtmltopdf`` `__. The ``--css`` option also affects the output. ``footer-html``, ``header-html`` add information to the header and footer ``margin-left``, ``margin-right``, ``margin-top``, ``margin-bottom`` set the page margins ``papersize`` sets the PDF paper size Variables for man pages ~~~~~~~~~~~~~~~~~~~~~~~ ``adjusting`` adjusts text to left (``l``), right (``r``), center (``c``), or both (``b``) margins ``footer`` footer in man pages ``header`` header in man pages ``section`` section number in man pages Variables for Texinfo ~~~~~~~~~~~~~~~~~~~~~ ``version`` version of software (used in title and title page) ``filename`` name of info file to be generated (defaults to a name based on the texi filename) Variables for Typst ~~~~~~~~~~~~~~~~~~~ ``template`` Typst template to use. ``margin`` A dictionary with the fields defined in the Typst documentation: ``x``, ``y``, ``top``, ``bottom``, ``left``, ``right``. ``papersize`` Paper size: ``a4``, ``us-letter``, etc. ``mainfont`` Name of system font to use for the main font. ``fontsize`` Font size (e.g., ``12pt``). ``section-numbering`` Schema to use for numbering sections, e.g.Â ``1.A.1``. ``page-numbering`` Schema to use for numbering pages, e.g.Â ``1`` or ``i``, or an empty string to omit page numbering. ``columns`` Number of columns for body text. ``thanks`` contents of acknowledgments footnote after document title ``mathfont``, ``codefont`` Name of system font to use for math and code, respectively. ``linestretch`` adjusts line spacing, e.g.Â ``1.25``, ``1.5`` ``linkcolor``, ``filecolor``, ``citecolor`` color for external links, internal links, and citation links, respectively: expects a hexadecimal color code Variables for ms ~~~~~~~~~~~~~~~~ ``fontfamily`` ``A`` (Avant Garde), ``B`` (Bookman), ``C`` (Helvetica), ``HN`` (Helvetica Narrow), ``P`` (Palatino), or ``T`` (Times New Roman). This setting does not affect source code, which is always displayed using monospace Courier. These built-in fonts are limited in their coverage of characters. Additional fonts may be installed using the script ```install-font.sh`` `__ provided by Peter Schaffter and documented in detail on `his web site `__. ``indent`` paragraph indent (e.g.Â ``2m``) ``lineheight`` line height (e.g.Â ``12p``) ``pointsize`` point size (e.g.Â ``10p``) Variables set automatically ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Pandoc sets these variables automatically in response to `options <#options>`__ or document contents; users can also modify them. These vary depending on the output format, and include the following: ``body`` body of document ``date-meta`` the ``date`` variable converted to ISO 8601 YYYY-MM-DD, included in all HTML based formats (dzslides, epub, html, html4, html5, revealjs, s5, slideous, slidy). The recognized formats for ``date`` are: ``mm/dd/yyyy``, ``mm/dd/yy``, ``yyyy-mm-dd`` (ISO 8601), ``dd MM yyyy`` (e.g.Â either ``02 Apr 2018`` or ``02 April 2018``), ``MM dd, yyyy`` (e.g.Â ``Apr. 02, 2018`` or ``April 02, 2018),``\ yyyy[mm[dd]]\ ``(e.g.``\ 20180402, ``201804`` or ``2018``). ``header-includes`` contents specified by ``-H/--include-in-header`` (may have multiple values) ``include-before`` contents specified by ``-B/--include-before-body`` (may have multiple values) ``include-after`` contents specified by ``-A/--include-after-body`` (may have multiple values) ``meta-json`` JSON representation of all of the documentâ€™s metadata. Field values are transformed to the selected output format. ``numbersections`` non-null value if ``-N/--number-sections`` was specified ``sourcefile``, ``outputfile`` source and destination filenames, as given on the command line. ``sourcefile`` can also be a list if input comes from multiple files, or empty if input is from stdin. You can use the following snippet in your template to distinguish them: :: $if(sourcefile)$ $for(sourcefile)$ $sourcefile$ $endfor$ $else$ (stdin) $endif$ Similarly, ``outputfile`` can be ``-`` if output goes to the terminal. If you need absolute paths, use e.g.Â ``$curdir$/$sourcefile$``. ``pdf-engine`` name of PDF engine if provided using ``--pdf-engine``, or the default engine for the format if PDF output is requested. ``curdir`` working directory from which pandoc is run. ``pandoc-version`` pandoc version. ``toc`` non-null value if ``--toc/--table-of-contents`` was specified ``toc-title`` title of table of contents (works only with EPUB, HTML, revealjs, opendocument, odt, docx, pptx, beamer, LaTeX). Note that in docx and pptx a custom ``toc-title`` will be picked up from metadata, but cannot be set as a variable. Extensions ========== The behavior of some of the readers and writers can be adjusted by enabling or disabling various extensions. An extension can be enabled by adding ``+EXTENSION`` to the format name and disabled by adding ``-EXTENSION``. For example, ``--from markdown_strict+footnotes`` is strict Markdown with footnotes enabled, while ``--from markdown-footnotes-pipe_tables`` is pandocâ€™s Markdown without footnotes or pipe tables. The Markdown reader and writer make by far the most use of extensions. Extensions only used by them are therefore covered in the section `Pandocâ€™s Markdown <#pandocs-markdown>`__ below (see `Markdown variants <#markdown-variants>`__ for ``commonmark`` and ``gfm``). In the following, extensions that also work for other formats are covered. Note that Markdown extensions added to the ``ipynb`` format affect Markdown cells in Jupyter notebooks (as do command-line options like ``--markdown-headings``). Typography ---------- Extension: ``smart`` ~~~~~~~~~~~~~~~~~~~~ Interpret straight quotes as curly quotes, ``---`` as em-dashes, ``--`` as en-dashes, and ``...`` as ellipses. Nonbreaking spaces are inserted after certain abbreviations, such as â€œMr.â€ This extension can be enabled/disabled for the following formats: input formats ``markdown``, ``commonmark``, ``latex``, ``mediawiki``, ``org``, ``rst``, ``twiki``, ``html`` output formats ``markdown``, ``latex``, ``context``, ``org``, ``rst`` enabled by default in ``markdown``, ``latex``, ``context`` (both input and output) Note: If you are *writing* Markdown, then the ``smart`` extension has the reverse effect: what would have been curly quotes comes out straight. In LaTeX, ``smart`` means to use the standard TeX ligatures for quotation marks (:literal:`\`\`` and ``''`` for double quotes, :literal:`\`` and ``'`` for single quotes) and dashes (``--`` for en-dash and ``---`` for em-dash). If ``smart`` is disabled, then in reading LaTeX pandoc will parse these characters literally. In writing LaTeX, enabling ``smart`` tells pandoc to use the ligatures when possible; if ``smart`` is disabled pandoc will use unicode quotation mark and dash characters. Headings and sections --------------------- Extension: ``auto_identifiers`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A heading without an explicitly specified identifier will be automatically assigned a unique identifier based on the heading text. This extension can be enabled/disabled for the following formats: input formats ``markdown``, ``latex``, ``rst``, ``mediawiki``, ``textile`` output formats ``markdown``, ``muse`` enabled by default in ``markdown``, ``muse`` The default algorithm used to derive the identifier from the heading text is: - Remove all formatting, links, etc. - Remove all footnotes. - Remove all non-alphanumeric characters, except underscores, hyphens, and periods. - Replace all spaces and newlines with hyphens. - Convert all alphabetic characters to lowercase. - Remove everything up to the first letter (identifiers may not begin with a number or punctuation mark). - If nothing is left after this, use the identifier ``section``. Thus, for example, =============================== =============================== Heading Identifier =============================== =============================== ``Heading identifiers in HTML`` ``heading-identifiers-in-html`` ``MaÃ®tre d'hÃ´tel`` ``maÃ®tre-dhÃ´tel`` ``*Dogs*?--in *my* house?`` ``dogs--in-my-house`` ``[HTML], [S5], or [RTF]?`` ``html-s5-or-rtf`` ``3. Applications`` ``applications`` ``33`` ``section`` =============================== =============================== These rules should, in most cases, allow one to determine the identifier from the heading text. The exception is when several headings have the same text; in this case, the first will get an identifier as described above; the second will get the same identifier with ``-1`` appended; the third with ``-2``; and so on. (However, a different algorithm is used if ``gfm_auto_identifiers`` is enabled; see below.) These identifiers are used to provide link targets in the table of contents generated by the ``--toc|--table-of-contents`` option. They also make it easy to provide links from one section of a document to another. A link to this section, for example, might look like this: :: See the section on [heading identifiers](#heading-identifiers-in-html-latex-and-context). Note, however, that this method of providing links to sections works only in HTML, LaTeX, and ConTeXt formats. If the ``--section-divs`` option is specified, then each section will be wrapped in a ``section`` (or a ``div``, if ``html4`` was specified), and the identifier will be attached to the enclosing ``

`` (or ``

``) tag rather than the heading itself. This allows entire sections to be manipulated using JavaScript or treated differently in CSS. Extension: ``ascii_identifiers`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Causes the identifiers produced by ``auto_identifiers`` to be pure ASCII. Accents are stripped off of accented Latin letters, and non-Latin letters are omitted. Extension: ``gfm_auto_identifiers`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Changes the algorithm used by ``auto_identifiers`` to conform to GitHubâ€™s method. Spaces are converted to dashes (``-``), uppercase characters to lowercase characters, and punctuation characters other than ``-`` and ``_`` are removed. Emojis are replaced by their names. Math Input ---------- The extensions ```tex_math_dollars`` <#extension-tex_math_dollars>`__, ```tex_math_gfm`` <#extension-tex_math_gfm>`__, ```tex_math_single_backslash`` <#extension-tex_math_single_backslash>`__, and ```tex_math_double_backslash`` <#extension-tex_math_double_backslash>`__ are described in the section about Pandocâ€™s Markdown. However, they can also be used with HTML input. This is handy for reading web pages formatted using MathJax, for example. Raw HTML/TeX ------------ The following extensions are described in more detail in their respective sections of `Pandocâ€™s Markdown <#pandocs-markdown>`__: - ```raw_html`` <#extension-raw_html>`__ allows HTML elements which are not representable in pandocâ€™s AST to be parsed as raw HTML. By default, this is disabled for HTML input. - ```raw_tex`` <#extension-raw_tex>`__ allows raw LaTeX, TeX, and ConTeXt to be included in a document. This extension can be enabled/disabled for the following formats (in addition to ``markdown``): input formats ``latex``, ``textile``, ``html`` (environments, ``\ref``, and ``\eqref`` only), ``ipynb`` output formats ``textile``, ``commonmark`` Note: as applied to ``ipynb``, ``raw_html`` and ``raw_tex`` affect not only raw TeX in Markdown cells, but data with mime type ``text/html`` in output cells. Since the ``ipynb`` reader attempts to preserve the richest possible outputs when several options are given, you will get best results if you disable ``raw_html`` and ``raw_tex`` when converting to formats like ``docx`` which donâ€™t allow raw ``html`` or ``tex``. - ```native_divs`` <#extension-native_divs>`__ causes HTML ``div`` elements to be parsed as native pandoc Div blocks. If you want them to be parsed as raw HTML, use ``-f html-native_divs+raw_html``. - ```native_spans`` <#extension-native_spans>`__ causes HTML ``span`` elements to be parsed as native pandoc Span inlines. If you want them to be parsed as raw HTML, use ``-f html-native_spans+raw_html``. If you want to drop all ``div``\ s and ``span``\ s when converting HTML to Markdown, you can use ``pandoc -f html-native_divs-native_spans -t markdown``. Literate Haskell support ------------------------ Extension: ``literate_haskell`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Treat the document as literate Haskell source. This extension can be enabled/disabled for the following formats: input formats ``markdown``, ``rst``, ``latex`` output formats ``markdown``, ``rst``, ``latex``, ``html`` If you append ``+lhs`` (or ``+literate_haskell``) to one of the formats above, pandoc will treat the document as literate Haskell source. This means that - In Markdown input, â€œbird trackâ€ sections will be parsed as Haskell code rather than block quotations. Text between ``\begin{code}`` and ``\end{code}`` will also be treated as Haskell code. For ATX-style headings the character â€˜=â€™ will be used instead of â€˜#â€™. - In Markdown output, code blocks with classes ``haskell`` and ``literate`` will be rendered using bird tracks, and block quotations will be indented one space, so they will not be treated as Haskell code. In addition, headings will be rendered setext-style (with underlines) rather than ATX-style (with â€˜#â€™ characters). (This is because ghc treats â€˜#â€™ characters in column 1 as introducing line numbers.) - In restructured text input, â€œbird trackâ€ sections will be parsed as Haskell code. - In restructured text output, code blocks with class ``haskell`` will be rendered using bird tracks. - In LaTeX input, text in ``code`` environments will be parsed as Haskell code. - In LaTeX output, code blocks with class ``haskell`` will be rendered inside ``code`` environments. - In HTML output, code blocks with class ``haskell`` will be rendered with class ``literatehaskell`` and bird tracks. Examples: :: pandoc -f markdown+lhs -t html reads literate Haskell source formatted with Markdown conventions and writes ordinary HTML (without bird tracks). :: pandoc -f markdown+lhs -t html+lhs writes HTML with the Haskell code in bird tracks, so it can be copied and pasted as literate Haskell source. Note that GHC expects the bird tracks in the first column, so indented literate code blocks (e.g.Â inside an itemized environment) will not be picked up by the Haskell compiler. Other extensions ---------------- Extension: ``empty_paragraphs`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Allows empty paragraphs. By default empty paragraphs are omitted. This extension can be enabled/disabled for the following formats: input formats ``docx``, ``html`` output formats ``docx``, ``odt``, ``opendocument``, ``html``, ``latex`` Extension: ``native_numbering`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Enables native numbering of figures and tables. Enumeration starts at 1. This extension can be enabled/disabled for the following formats: output formats ``odt``, ``opendocument``, ``docx`` Extension: ``xrefs_name`` ~~~~~~~~~~~~~~~~~~~~~~~~~ Links to headings, figures and tables inside the document are substituted with cross-references that will use the name or caption of the referenced item. The original link text is replaced once the generated document is refreshed. This extension can be combined with ``xrefs_number`` in which case numbers will appear before the name. Text in cross-references is only made consistent with the referenced item once the document has been refreshed. This extension can be enabled/disabled for the following formats: output formats ``odt``, ``opendocument`` Extension: ``xrefs_number`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Links to headings, figures and tables inside the document are substituted with cross-references that will use the number of the referenced item. The original link text is discarded. This extension can be combined with ``xrefs_name`` in which case the name or caption numbers will appear after the number. For the ``xrefs_number`` to be useful heading numbers must be enabled in the generated document, also table and figure captions must be enabled using for example the ``native_numbering`` extension. Numbers in cross-references are only visible in the final document once it has been refreshed. This extension can be enabled/disabled for the following formats: output formats ``odt``, ``opendocument`` .. _ext-styles: Extension: ``styles`` ~~~~~~~~~~~~~~~~~~~~~ When converting from docx, add ``custom-styles`` attributes for all docx styles, regardless of whether pandoc understands the meanings of these styles. Because attributes cannot be added directly to paragraphs or text in the pandoc AST, paragraph styles will cause Divs to be created and character styles will cause Spans to be created to hold the attributes. (Table styles will be added to the Table elements directly.) This extension can be used with `docx custom styles <#custom-styles>`__. input formats ``docx`` Extension: ``amuse`` ~~~~~~~~~~~~~~~~~~~~ In the ``muse`` input format, this enables Text::Amuse extensions to Emacs Muse markup. Extension: ``raw_markdown`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~ In the ``ipynb`` input format, this causes Markdown cells to be included as raw Markdown blocks (allowing lossless round-tripping) rather than being parsed. Use this only when you are targeting ``ipynb`` or a Markdown-based output format. .. _typst-citations: Extension: ``citations`` (typst) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When the ``citations`` extension is enabled in ``typst`` (as it is by default), ``typst`` citations will be parsed as native pandoc citations, and native pandoc citations will be rendered as ``typst`` citations. .. _org-citations: Extension: ``citations`` (org) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When the ``citations`` extension is enabled in ``org``, org-cite and org-ref style citations will be parsed as native pandoc citations, and org-cite citations will be used to render native pandoc citations. .. _docx-citations: Extension: ``citations`` (docx) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ When ``citations`` is enabled in ``docx``, citations inserted by Zotero or Mendeley or EndNote plugins will be parsed as native pandoc citations. (Otherwise, the formatted citations generated by the bibliographic software will be parsed as regular text.) .. _org-fancy-lists: Extension: ``fancy_lists`` (org) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Some aspects of `Pandocâ€™s Markdown fancy lists <#extension-fancy_lists>`__ are also accepted in ``org`` input, mimicking the option ``org-list-allow-alphabetical`` in Emacs. As in Org Mode, enabling this extension allows lowercase and uppercase alphabetical markers for ordered lists to be parsed in addition to arabic ones. Note that for Org, this does not include roman numerals or the ``#`` placeholder that are enabled by the extension in Pandocâ€™s Markdown. Extension: ``element_citations`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In the ``jats`` output formats, this causes reference items to be replaced with ```` elements. These elements are not influenced by CSL styles, but all information on the item is included in tags. Extension: ``ntb`` ~~~~~~~~~~~~~~~~~~ In the ``context`` output format this enables the use of `Natural Tables (TABLE) `__ instead of the default `Extreme Tables (xtables) `__. Natural tables allow more fine-grained global customization but come at a performance penalty compared to extreme tables. Extension: ``smart_quotes`` (org) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Interpret straight quotes as curly quotes during parsing. When *writing* Org, then the ``smart_quotes`` extension has the reverse effect: what would have been curly quotes comes out straight. This extension is implied if ``smart`` is enabled. Extension: ``special_strings`` (org) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Interpret ``---`` as em-dashes, ``--`` as en-dashes, ``\-`` as shy hyphen, and ``...`` as ellipses. This extension is implied if ``smart`` is enabled. .. _extension--tagging: Extension: ``tagging`` ~~~~~~~~~~~~~~~~~~~~~~ Enabling this extension with ``context`` output will produce markup suitable for the production of tagged PDFs. This includes additional markers for paragraphs and alternative markup for emphasized text. The ``emphasis-command`` template variable is set if the extension is enabled. Pandocâ€™s Markdown ================= Pandoc understands an extended and slightly revised version of John Gruberâ€™s `Markdown `__ syntax. This document explains the syntax, noting differences from original Markdown. Except where noted, these differences can be suppressed by using the ``markdown_strict`` format instead of ``markdown``. Extensions can be enabled or disabled to specify the behavior more granularly. They are described in the following. See also `Extensions <#extensions>`__ above, for extensions that work also on other formats. Philosophy ---------- Markdown is designed to be easy to write, and, even more importantly, easy to read: | A Markdown-formatted document should be publishable as-is, as plain text, without looking like itâ€™s been marked up with tags or formatting instructions. | â€“ `John Gruber `__ This principle has guided pandocâ€™s decisions in finding syntax for tables, footnotes, and other extensions. There is, however, one respect in which pandocâ€™s aims are different from the original aims of Markdown. Whereas Markdown was originally designed with HTML generation in mind, pandoc is designed for multiple output formats. Thus, while pandoc allows the embedding of raw HTML, it discourages it, and provides other, non-HTMLish ways of representing important document elements like definition lists, tables, mathematics, and footnotes. Paragraphs ---------- A paragraph is one or more lines of text followed by one or more blank lines. Newlines are treated as spaces, so you can reflow your paragraphs as you like. If you need a hard line break, put two or more spaces at the end of a line. Extension: ``escaped_line_breaks`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A backslash followed by a newline is also a hard line break. Note: in multiline and grid table cells, this is the only way to create a hard line break, since trailing spaces in the cells are ignored. Headings -------- There are two kinds of headings: Setext and ATX. Setext-style headings ~~~~~~~~~~~~~~~~~~~~~ A setext-style heading is a line of text â€œunderlinedâ€ with a row of ``=`` signs (for a level-one heading) or ``-`` signs (for a level-two heading): :: A level-one heading =================== A level-two heading ------------------- The heading text can contain inline formatting, such as emphasis (see `Inline formatting <#inline-formatting>`__, below). ATX-style headings ~~~~~~~~~~~~~~~~~~ An ATX-style heading consists of one to six ``#`` signs and a line of text, optionally followed by any number of ``#`` signs. The number of ``#`` signs at the beginning of the line is the heading level: :: ## A level-two heading ### A level-three heading ### As with setext-style headings, the heading text can contain formatting: :: # A level-one heading with a [link](/url) and *emphasis* Extension: ``blank_before_header`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Original Markdown syntax does not require a blank line before a heading. Pandoc does require this (except, of course, at the beginning of the document). The reason for the requirement is that it is all too easy for a ``#`` to end up at the beginning of a line by accident (perhaps through line wrapping). Consider, for example: :: I like several of their flavors of ice cream: #22, for example, and #5. Extension: ``space_in_atx_header`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Many Markdown implementations do not require a space between the opening ``#``\ s of an ATX heading and the heading text, so that ``#5 bolt`` and ``#hashtag`` count as headings. With this extension, pandoc does require the space. Heading identifiers ~~~~~~~~~~~~~~~~~~~ See also the ```auto_identifiers`` extension <#extension-auto_identifiers>`__ above. Extension: ``header_attributes`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Headings can be assigned attributes using this syntax at the end of the line containing the heading text: :: {#identifier .class .class key=value key=value} Thus, for example, the following headings will all be assigned the identifier ``foo``: :: # My heading {#foo} ## My heading ## {#foo} My other heading {#foo} --------------- (This syntax is compatible with `PHP Markdown Extra `__.) Note that although this syntax allows assignment of classes and key/value attributes, writers generally donâ€™t use all of this information. Identifiers, classes, and key/value attributes are used in HTML and HTML-based formats such as EPUB and slidy. Identifiers are used for labels and link anchors in the LaTeX, ConTeXt, Textile, Jira markup, and AsciiDoc writers. Headings with the class ``unnumbered`` will not be numbered, even if ``--number-sections`` is specified. A single hyphen (``-``) in an attribute context is equivalent to ``.unnumbered``, and preferable in non-English documents. So, :: # My heading {-} is just the same as :: # My heading {.unnumbered} If the ``unlisted`` class is present in addition to ``unnumbered``, the heading will not be included in a table of contents. (Currently this feature is only implemented for certain formats: those based on LaTeX and HTML, PowerPoint, and RTF.) Extension: ``implicit_header_references`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Pandoc behaves as if reference links have been defined for each heading. So, to link to a heading :: # Heading identifiers in HTML you can simply write :: [Heading identifiers in HTML] or :: [Heading identifiers in HTML][] or :: [the section on heading identifiers][heading identifiers in HTML] instead of giving the identifier explicitly: :: [Heading identifiers in HTML](#heading-identifiers-in-html) If there are multiple headings with identical text, the corresponding reference will link to the first one only, and you will need to use explicit links to link to the others, as described above. Like regular reference links, these references are case-insensitive. Explicit link reference definitions always take priority over implicit heading references. So, in the following example, the link will point to ``bar``, not to ``#foo``: :: # Foo [foo]: bar See [foo] Block quotations ---------------- Markdown uses email conventions for quoting blocks of text. A block quotation is one or more paragraphs or other block elements (such as lists or headings), with each line preceded by a ``>`` character and an optional space. (The ``>`` need not start at the left margin, but it should not be indented more than three spaces.) :: > This is a block quote. This > paragraph has two lines. > > 1. This is a list inside a block quote. > 2. Second item. A â€œlazyâ€ form, which requires the ``>`` character only on the first line of each block, is also allowed: :: > This is a block quote. This paragraph has two lines. > 1. This is a list inside a block quote. 2. Second item. Among the block elements that can be contained in a block quote are other block quotes. That is, block quotes can be nested: :: > This is a block quote. > > > A block quote within a block quote. If the ``>`` character is followed by an optional space, that space will be considered part of the block quote marker and not part of the indentation of the contents. Thus, to put an indented code block in a block quote, you need five spaces after the ``>``: :: > code Extension: ``blank_before_blockquote`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Original Markdown syntax does not require a blank line before a block quote. Pandoc does require this (except, of course, at the beginning of the document). The reason for the requirement is that it is all too easy for a ``>`` to end up at the beginning of a line by accident (perhaps through line wrapping). So, unless the ``markdown_strict`` format is used, the following does not produce a nested block quote in pandoc: :: > This is a block quote. >> Not nested, since `blank_before_blockquote` is enabled by default Verbatim (code) blocks ---------------------- Indented code blocks ~~~~~~~~~~~~~~~~~~~~ A block of text indented four spaces (or one tab) is treated as verbatim text: that is, special characters do not trigger special formatting, and all spaces and line breaks are preserved. For example, :: if (a > 3) { moveShip(5 * gravity, DOWN); } The initial (four space or one tab) indentation is not considered part of the verbatim text, and is removed in the output. Note: blank lines in the verbatim text need not begin with four spaces. Fenced code blocks ~~~~~~~~~~~~~~~~~~ Extension: ``fenced_code_blocks`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ In addition to standard indented code blocks, pandoc supports *fenced* code blocks. These begin with a row of three or more tildes (``~``) and end with a row of tildes that must be at least as long as the starting row. Everything between these lines is treated as code. No indentation is necessary: :: ~~~~~~~ if (a > 3) { moveShip(5 * gravity, DOWN); } ~~~~~~~ Like regular code blocks, fenced code blocks must be separated from surrounding text by blank lines. If the code itself contains a row of tildes or backticks, just use a longer row of tildes or backticks at the start and end: :: ~~~~~~~~~~~~~~~~ ~~~~~~~~~~ code including tildes ~~~~~~~~~~ ~~~~~~~~~~~~~~~~ Extension: ``backtick_code_blocks`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Same as ``fenced_code_blocks``, but uses backticks (:literal:`\``) instead of tildes (``~``). Extension: ``fenced_code_attributes`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Optionally, you may attach attributes to fenced or backtick code block using this syntax: :: ~~~~ {#mycode .haskell .numberLines startFrom="100"} qsort [] = [] qsort (x:xs) = qsort (filter (< x) xs) ++ [x] ++ qsort (filter (>= x) xs) ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Here ``mycode`` is an identifier, ``haskell`` and ``numberLines`` are classes, and ``startFrom`` is an attribute with value ``100``. Some output formats can use this information to do syntax highlighting. Currently, the only output formats that use this information are HTML, LaTeX, Docx, Ms, and PowerPoint. If highlighting is supported for your output format and language, then the code block above will appear highlighted, with numbered lines. (To see which languages are supported, type ``pandoc --list-highlight-languages``.) Otherwise, the code block above will appear as follows: ::

...

The ``numberLines`` (or ``number-lines``) class will cause the lines of the code block to be numbered, starting with ``1`` or the value of the ``startFrom`` attribute. The ``lineAnchors`` (or ``line-anchors``) class will cause the lines to be clickable anchors in HTML output. A shortcut form can also be used for specifying the language of the code block: :: ```haskell qsort [] = [] ``` This is equivalent to: :: ``` {.haskell} qsort [] = [] ``` This shortcut form may be combined with attributes: :: ```haskell {.numberLines} qsort [] = [] ``` Which is equivalent to: :: ``` {.haskell .numberLines} qsort [] = [] ``` If the ``fenced_code_attributes`` extension is disabled, but input contains class attribute(s) for the code block, the first class attribute will be printed after the opening fence as a bare word. To prevent all highlighting, use the ``--syntax-highlighting=none`` option. To set the highlighting style or method, use ``--syntax-highlighting``. For more information on highlighting, see `Syntax highlighting <#syntax-highlighting>`__, below. Line blocks ----------- Extension: ``line_blocks`` ~~~~~~~~~~~~~~~~~~~~~~~~~~ A line block is a sequence of lines beginning with a vertical bar (``|``) followed by a space. The division into lines will be preserved in the output, as will any leading spaces; otherwise, the lines will be formatted as Markdown. This is useful for verse and addresses: :: | The limerick packs laughs anatomical | In space that is quite economical. | But the good ones I've seen | So seldom are clean | And the clean ones so seldom are comical | 200 Main St. | Berkeley, CA 94718 The lines can be hard-wrapped if needed, but the continuation line must begin with a space. :: | The Right Honorable Most Venerable and Righteous Samuel L. Constable, Jr. | 200 Main St. | Berkeley, CA 94718 Inline formatting (such as emphasis) is allowed in the content (though it canâ€™t cross line boundaries). Block-level formatting (such as block quotes or lists) is not recognized. This syntax is borrowed from `reStructuredText `__. Lists ----- Bullet lists ~~~~~~~~~~~~ A bullet list is a list of bulleted list items. A bulleted list item begins with a bullet (``*``, ``+``, or ``-``). Here is a simple example: :: * one * two * three This will produce a â€œcompactâ€ list. If you want a â€œlooseâ€ list, in which each item is formatted as a paragraph, put spaces between the items: :: * one * two * three The bullets need not be flush with the left margin; they may be indented one, two, or three spaces. The bullet must be followed by whitespace. List items look best if subsequent lines are flush with the first line (after the bullet): :: * here is my first list item. * and my second. But Markdown also allows a â€œlazyâ€ format: :: * here is my first list item. * and my second. Block content in list items ~~~~~~~~~~~~~~~~~~~~~~~~~~~ A list item may contain multiple paragraphs and other block-level content. However, subsequent paragraphs must be preceded by a blank line and indented to line up with the first non-space content after the list marker. :: * First paragraph. Continued. * Second paragraph. With a code block, which must be indented eight spaces: { code } Exception: if the list marker is followed by an indented code block, which must begin 5 spaces after the list marker, then subsequent paragraphs must begin two columns after the last character of the list marker: :: * code continuation paragraph List items may include other lists. In this case the preceding blank line is optional. The nested list must be indented to line up with the first non-space character after the list marker of the containing list item. :: * fruits + apples - macintosh - red delicious + pears + peaches * vegetables + broccoli + chard As noted above, Markdown allows you to write list items â€œlazily,â€ instead of indenting continuation lines. However, if there are multiple paragraphs or other blocks in a list item, the first line of each must be indented. :: + A lazy, lazy, list item. + Another one; this looks bad but is legal. Second paragraph of second list item. Ordered lists ~~~~~~~~~~~~~ Ordered lists work just like bulleted lists, except that the items begin with enumerators rather than bullets. In original Markdown, enumerators are decimal numbers followed by a period and a space. The numbers themselves are ignored, so there is no difference between this list: :: 1. one 2. two 3. three and this one: :: 5. one 7. two 1. three Extension: ``fancy_lists`` ~~~~~~~~~~~~~~~~~~~~~~~~~~ Unlike original Markdown, pandoc allows ordered list items to be marked with uppercase and lowercase letters and roman numerals, in addition to Arabic numerals. List markers may be enclosed in parentheses or followed by a single right-parenthesis or period. They must be separated from the text that follows by at least one space, and, if the list marker is a capital letter with a period, by at least two spaces. [1]_ The ``fancy_lists`` extension also allows â€˜``#``â€™ to be used as an ordered list marker in place of a numeral: :: #. one #. two Note: the â€˜``#``â€™ ordered list marker doesnâ€™t work with ``commonmark``. Extension: ``startnum`` ~~~~~~~~~~~~~~~~~~~~~~~ Pandoc also pays attention to the type of list marker used, and to the starting number, and both of these are preserved where possible in the output format. Thus, the following yields a list with numbers followed by a single parenthesis, starting with 9, and a sublist with lowercase roman numerals: :: 9) Ninth 10) Tenth 11) Eleventh i. subone ii. subtwo iii. subthree Pandoc will start a new list each time a different type of list marker is used. So, the following will create three lists: :: (2) Two (5) Three 1. Four * Five If default list markers are desired, use ``#.``: :: #. one #. two #. three Extension: ``task_lists`` ~~~~~~~~~~~~~~~~~~~~~~~~~ Pandoc supports task lists, using the syntax of GitHub-Flavored Markdown. :: - [ ] an unchecked task list item - [x] checked item Definition lists ~~~~~~~~~~~~~~~~ Extension: ``definition_lists`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Pandoc supports definition lists, using the syntax of `PHP Markdown Extra `__ with some extensions. [2]_ :: Term 1 : Definition 1 Term 2 with *inline markup* : Definition 2 { some code, part of Definition 2 } Third paragraph of definition 2. Each term must fit on one line, which may optionally be followed by a blank line, and must be followed by one or more definitions. A definition begins with a colon or tilde, which may be indented one or two spaces. A term may have multiple definitions, and each definition may consist of one or more block elements (paragraph, code block, list, etc.), each indented four spaces or one tab stop. The body of the definition (not including the first line) should be indented four spaces. However, as with other Markdown lists, you can â€œlazilyâ€ omit indentation except at the beginning of a paragraph or other block element: :: Term 1 : Definition with lazy continuation. Second paragraph of the definition. If you leave space before the definition (as in the example above), the text of the definition will be treated as a paragraph. In some output formats, this will mean greater spacing between term/definition pairs. For a more compact definition list, omit the space before the definition: :: Term 1 ~ Definition 1 Term 2 ~ Definition 2a ~ Definition 2b Note that space between items in a definition list is required. Numbered example lists ~~~~~~~~~~~~~~~~~~~~~~ Extension: ``example_lists`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ The special list marker ``@`` can be used for sequentially numbered examples. The first list item with a ``@`` marker will be numbered â€˜1â€™, the next â€˜2â€™, and so on, throughout the document. The numbered examples need not occur in a single list; each new list using ``@`` will take up where the last stopped. So, for example: :: (@) My first example will be numbered (1). (@) My second example will be numbered (2). Explanation of examples. (@) My third example will be numbered (3). Numbered examples can be labeled and referred to elsewhere in the document: :: (@good) This is a good example. As (@good) illustrates, ... The label can be any string of alphanumeric characters, underscores, or hyphens. Continuation paragraphs in example lists must always be indented four spaces, regardless of the length of the list marker. That is, example lists always behave as if the ``four_space_rule`` extension is set. This is because example labels tend to be long, and indenting content to the first non-space character after the label would be awkward. You can repeat an earlier numbered example by re-using its label: :: (@foo) Sample sentence. Intervening text... This theory can explain the case we saw earlier (repeated): (@foo) Sample sentence. This only works reliably, though, if the repeated item is in a list by itself, because each numbered example list will be numbered continuously from its starting number. Ending a list ~~~~~~~~~~~~~ What if you want to put an indented code block after a list? :: - item one - item two { my code block } Trouble! Here pandoc (like other Markdown implementations) will treat ``{ my code block }`` as the second paragraph of item two, and not as a code block. To â€œcut offâ€ the list after item two, you can insert some non-indented content, like an HTML comment, which wonâ€™t produce visible output in any format: :: - item one - item two { my code block } You can use the same trick if you want two consecutive lists instead of one big list: :: 1. one 2. two 3. three 1. uno 2. dos 3. tres Horizontal rules ---------------- A line containing a row of three or more ``*``, ``-``, or ``_`` characters (optionally separated by spaces) produces a horizontal rule: :: * * * * --------------- We strongly recommend that horizontal rules be separated from surrounding text by blank lines. If a horizontal rule is not followed by a blank line, pandoc may try to interpret the lines that follow as a YAML metadata block or a table. Tables ------ Four kinds of tables may be used. The first three kinds presuppose the use of a fixed-width font, such as Courier. The fourth kind can be used with proportionally spaced fonts, as it does not require lining up columns. Extension: ``table_captions`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A caption may optionally be provided with all 4 kinds of tables (as illustrated in the examples below). A caption is a paragraph beginning with the string ``Table:`` (or ``table:`` or just ``:``), which will be stripped off. It may appear either before or after the table. Extension: ``simple_tables`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Simple tables look like this: :: Right Left Center Default ------- ------ ---------- ------- 12 12 12 12 123 123 123 123 1 1 1 1 Table: Demonstration of simple table syntax. The header and table rows must each fit on one line. Column alignments are determined by the position of the header text relative to the dashed line below it: [3]_ - If the dashed line is flush with the header text on the right side but extends beyond it on the left, the column is right-aligned. - If the dashed line is flush with the header text on the left side but extends beyond it on the right, the column is left-aligned. - If the dashed line extends beyond the header text on both sides, the column is centered. - If the dashed line is flush with the header text on both sides, the default alignment is used (in most cases, this will be left). The table must end with a blank line, or a line of dashes followed by a blank line. The column header row may be omitted, provided a dashed line is used to end the table. For example: :: ------- ------ ---------- ------- 12 12 12 12 123 123 123 123 1 1 1 1 ------- ------ ---------- ------- When the header row is omitted, column alignments are determined on the basis of the first line of the table body. So, in the tables above, the columns would be right, left, center, and right aligned, respectively. Extension: ``multiline_tables`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Multiline tables allow header and table rows to span multiple lines of text (but cells that span multiple columns or rows of the table are not supported). Here is an example: :: ------------------------------------------------------------- Centered Default Right Left Header Aligned Aligned Aligned ----------- ------- --------------- ------------------------- First row 12.0 Example of a row that spans multiple lines. Second row 5.0 Here's another one. Note the blank line between rows. ------------------------------------------------------------- Table: Here's the caption. It, too, may span multiple lines. These work like simple tables, but with the following differences: - They must begin with a row of dashes, before the header text (unless the header row is omitted). - They must end with a row of dashes, then a blank line. - The rows must be separated by blank lines. In multiline tables, the table parser pays attention to the widths of the columns, and the writers try to reproduce these relative widths in the output. So, if you find that one of the columns is too narrow in the output, try widening it in the Markdown source. The header may be omitted in multiline tables as well as simple tables: :: ----------- ------- --------------- ------------------------- First row 12.0 Example of a row that spans multiple lines. Second row 5.0 Here's another one. Note the blank line between rows. ----------- ------- --------------- ------------------------- : Here's a multiline table without a header. It is possible for a multiline table to have just one row, but the row should be followed by a blank line (and then the row of dashes that ends the table), or the table may be interpreted as a simple table. Extension: ``grid_tables`` ~~~~~~~~~~~~~~~~~~~~~~~~~~ Grid tables look like this: :: : Sample grid table. +---------------+---------------+--------------------+ | Fruit | Price | Advantages | +===============+===============+====================+ | Bananas | $1.34 | - built-in wrapper | | | | - bright color | +---------------+---------------+--------------------+ | Oranges | $2.10 | - cures scurvy | | | | - tasty | +---------------+---------------+--------------------+ The row of ``=``\ s separates the header from the table body, and can be omitted for a headerless table. The cells of grid tables may contain arbitrary block elements (multiple paragraphs, code blocks, lists, etc.). Cells can span multiple columns or rows: :: +---------------------+----------+ | Property | Earth | +=============+=======+==========+ | | min | -89.2 Â°C | | Temperature +-------+----------+ | 1961-1990 | mean | 14 Â°C | | +-------+----------+ | | max | 56.7 Â°C | +-------------+-------+----------+ A table header may contain more than one row: :: +---------------------+-----------------------+ | Location | Temperature 1961-1990 | | | in degree Celsius | | +-------+-------+-------+ | | min | mean | max | +=====================+=======+=======+=======+ | Antarctica | -89.2 | N/A | 19.8 | +---------------------+-------+-------+-------+ | Earth | -89.2 | 14 | 56.7 | +---------------------+-------+-------+-------+ Alignments can be specified as with pipe tables, by putting colons at the boundaries of the separator line after the header: :: +---------------+---------------+--------------------+ | Right | Left | Centered | +==============:+:==============+:==================:+ | Bananas | $1.34 | built-in wrapper | +---------------+---------------+--------------------+ For headerless tables, the colons go on the top line instead: :: +--------------:+:--------------+:------------------:+ | Right | Left | Centered | +---------------+---------------+--------------------+ A table foot can be defined by enclosing it with separator lines that use ``=`` instead of ``-``: :: +---------------+---------------+ | Fruit | Price | +===============+===============+ | Bananas | $1.34 | +---------------+---------------+ | Oranges | $2.10 | +===============+===============+ | Sum | $3.44 | +===============+===============+ The foot must always be placed at the very bottom of the table. Grid tables can be created easily using Emacsâ€™ table-mode (``M-x table-insert``). Extension: ``pipe_tables`` ~~~~~~~~~~~~~~~~~~~~~~~~~~ Pipe tables look like this: :: | Right | Left | Default | Center | |------:|:-----|---------|:------:| | 12 | 12 | 12 | 12 | | 123 | 123 | 123 | 123 | | 1 | 1 | 1 | 1 | : Demonstration of pipe table syntax. The syntax is identical to `PHP Markdown Extra tables `__. The beginning and ending pipe characters are optional, but pipes are required between all columns. The colons indicate column alignment as shown. The header cannot be omitted. To simulate a headerless table, include a header with blank cells. Since the pipes indicate column boundaries, columns need not be vertically aligned, as they are in the above example. So, this is a perfectly legal (though ugly) pipe table: :: fruit| price -----|-----: apple|2.05 pear|1.37 orange|3.09 The cells of pipe tables cannot contain block elements like paragraphs and lists, and cannot span multiple lines. If any line of the Markdown source is longer than the column width (see ``--columns``), then the table will take up the full text width and the cell contents will wrap, with the relative cell widths determined by the number of dashes in the line separating the table header from the table body. (For example ``---|-`` would make the first column 3/4 and the second column 1/4 of the full text width.) On the other hand, if no lines are wider than column width, then cell contents will not be wrapped, and the cells will be sized to their contents. Note: pandoc also recognizes pipe tables of the following form, as can be produced by Emacsâ€™ orgtbl-mode: :: | One | Two | |-----+-------| | my | table | | is | nice | The difference is that ``+`` is used instead of ``|``. Other orgtbl features are not supported. In particular, to get non-default column alignment, youâ€™ll need to add colons as above. Metadata blocks --------------- Extension: ``pandoc_title_block`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ If the file begins with a title block :: % title % author(s) (separated by semicolons) % date it will be parsed as bibliographic information, not regular text. (It will be used, for example, in the title of standalone LaTeX or HTML output.) The block may contain just a title, a date and an author, or all three elements. If you want to include an author but no title, or a title and a date but no author, you need a blank line: :: % % Author :: % My title % % June 15, 2006 The title may occupy multiple lines, but continuation lines must begin with leading space, thus: :: % My title on multiple lines If a document has multiple authors, the authors may be put on separate lines with leading space, or separated by semicolons, or both. So, all of the following are equivalent: :: % Author One Author Two :: % Author One; Author Two :: % Author One; Author Two The date must fit on one line. All three metadata fields may contain standard inline formatting (italics, links, footnotes, etc.). Title blocks will always be parsed, but they will affect the output only when the ``--standalone`` (``-s``) option is chosen. In HTML output, titles will appear twice: once in the document headâ€”this is the title that will appear at the top of the window in a browserâ€”and once at the beginning of the document body. The title in the document head can have an optional prefix attached (``--title-prefix`` or ``-T`` option). The title in the body appears as an H1 element with class â€œtitleâ€, so it can be suppressed or reformatted with CSS. If a title prefix is specified with ``-T`` and no title block appears in the document, the title prefix will be used by itself as the HTML title. The man page writer extracts a title, man page section number, and other header and footer information from the title line. The title is assumed to be the first word on the title line, which may optionally end with a (single-digit) section number in parentheses. (There should be no space between the title and the parentheses.) Anything after this is assumed to be additional footer and header text. A single pipe character (``|``) should be used to separate the footer text from the header text. Thus, :: % PANDOC(1) will yield a man page with the title ``PANDOC`` and section 1. :: % PANDOC(1) Pandoc User Manuals will also have â€œPandoc User Manualsâ€ in the footer. :: % PANDOC(1) Pandoc User Manuals | Version 4.0 will also have â€œVersion 4.0â€ in the header. Extension: ``yaml_metadata_block`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ A `YAML `__ metadata block is a valid YAML object, delimited by a line of three hyphens (``---``) at the top and a line of three hyphens (``---``) or three dots (``...``) at the bottom. The initial line ``---`` must not be followed by a blank line. A YAML metadata block may occur anywhere in the document, but if it is not at the beginning, it must be preceded by a blank line. Note that, because of the way pandoc concatenates input files when several are provided, you may also keep the metadata in a separate YAML file and pass it to pandoc as an argument, along with your Markdown files: :: pandoc chap1.md chap2.md chap3.md metadata.yaml -s -o book.html Just be sure that the YAML file begins with ``---`` and ends with ``---`` or ``...``. Alternatively, you can use the ``--metadata-file`` option. Using that approach however, you cannot reference content (like footnotes) from the main Markdown input document. Metadata will be taken from the fields of the YAML object and added to any existing document metadata. Metadata can contain lists and objects (nested arbitrarily), but all string scalars will be interpreted as Markdown. Fields with names ending in an underscore will be ignored by pandoc. (They may be given a role by external processors.) Field names must not be interpretable as YAML numbers or boolean values (so, for example, ``yes``, ``True``, and ``15`` cannot be used as field names). A document may contain multiple metadata blocks. If two metadata blocks attempt to set the same field, the value from the second block will be taken. Each metadata block is handled internally as an independent YAML document. This means, for example, that any YAML anchors defined in a block cannot be referenced in another block. When pandoc is used with ``-t markdown`` to create a Markdown document, a YAML metadata block will be produced only if the ``-s/--standalone`` option is used. All of the metadata will appear in a single block at the beginning of the document. Note that `YAML `__ escaping rules must be followed. Thus, for example, if a title contains a colon, it must be quoted, and if it contains a backslash escape, then it must be ensured that it is not treated as a `YAML escape sequence `__. The pipe character (``|``) can be used to begin an indented block that will be interpreted literally, without need for escaping. This form is necessary when the field contains blank lines or block-level formatting: :: --- title: 'This is the title: it contains a colon' author: - Author One - Author Two keywords: [nothing, nothingness] abstract: | This is the abstract. It consists of two paragraphs. ... The literal block after the ``|`` must be indented relative to the line containing the ``|``. If it is not, the YAML will be invalid and pandoc will not interpret it as metadata. For an overview of the complex rules governing YAML, see the `Wikipedia entry on YAML syntax `__. Template variables will be set automatically from the metadata. Thus, for example, in writing HTML, the variable ``abstract`` will be set to the HTML equivalent of the Markdown in the ``abstract`` field: ::

This is the abstract.

It consists of two paragraphs.

Variables can contain arbitrary YAML structures, but the template must match this structure. The ``author`` variable in the default templates expects a simple list or string, but can be changed to support more complicated structures. The following combination, for example, would add an affiliation to the author if one is given: :: --- title: The document title author: - name: Author One affiliation: University of Somewhere - name: Author Two affiliation: University of Nowhere ... To use the structured authors in the example above, you would need a custom template: :: $for(author)$ $if(author.name)$ $author.name$$if(author.affiliation)$ ($author.affiliation$)$endif$ $else$ $author$ $endif$ $endfor$ Raw content to include in the documentâ€™s header may be specified using ``header-includes``; however, it is important to mark up this content as raw code for a particular output format, using the ```raw_attribute`` extension <#extension-raw_attribute>`__, or it will be interpreted as Markdown. For example: :: header-includes: - | ```{=latex} \let\oldsection\section \renewcommand{\section}[1]{\clearpage\oldsection{#1}} ``` Note: the ``yaml_metadata_block`` extension works with ``commonmark`` as well as ``markdown`` (and it is enabled by default in ``gfm`` and ``commonmark_x``). However, in these formats the following restrictions apply: - The YAML metadata block must occur at the beginning of the document (and there can be only one). If multiple files are given as arguments to pandoc, only the first can be a YAML metadata block. - The leaf nodes of the YAML structure are parsed in isolation from each other and from the rest of the document. So, for example, you canâ€™t use a reference link in these contexts if the link definition is somewhere else in the document. Backslash escapes ----------------- Extension: ``all_symbols_escapable`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Except inside a code block or inline code, any punctuation or space character preceded by a backslash will be treated literally, even if it would normally indicate formatting. Thus, for example, if one writes :: *\*hello\** one will get :: *hello* instead of :: hello This rule is easier to remember than original Markdownâ€™s rule, which allows only the following characters to be backslash-escaped: :: \`*_{}[]()>#+-.! (However, if the ``markdown_strict`` format is used, the original Markdown rule will be used.) A backslash-escaped space is parsed as a nonbreaking space. In TeX output, it will appear as ``~``. In HTML and XML output, it will appear as a literal unicode nonbreaking space character (note that it will thus actually look â€œinvisibleâ€ in the generated HTML source; you can still use the ``--ascii`` command-line option to make it appear as an explicit entity). A backslash-escaped newline (i.e.Â a backslash occurring at the end of a line) is parsed as a hard line break. It will appear in TeX output as ``\\`` and in HTML as ``
``. This is a nice alternative to Markdownâ€™s â€œinvisibleâ€ way of indicating hard line breaks using two trailing spaces on a line. Backslash escapes do not work in verbatim contexts. Inline formatting ----------------- Emphasis ~~~~~~~~ To *emphasize* some text, surround it with ``*``\ s or ``_``, like this: :: This text is _emphasized with underscores_, and this is *emphasized with asterisks*. Double ``*`` or ``_`` produces **strong emphasis**: :: This is **strong emphasis** and __with underscores__. A ``*`` or ``_`` character surrounded by spaces, or backslash-escaped, will not trigger emphasis: :: This is * not emphasized *, and \*neither is this\*. Extension: ``intraword_underscores`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Because ``_`` is sometimes used inside words and identifiers, pandoc does not interpret a ``_`` surrounded by alphanumeric characters as an emphasis marker. If you want to emphasize just part of a word, use ``*``: :: feas*ible*, not feas*able*. Strikeout ~~~~~~~~~ Extension: ``strikeout`` ~~~~~~~~~~~~~~~~~~~~~~~~ To strike out a section of text with a horizontal line, begin and end it with ``~~``. Thus, for example, :: This ~~is deleted text.~~ Superscripts and subscripts ~~~~~~~~~~~~~~~~~~~~~~~~~~~ Extension: ``superscript``, ``subscript`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Superscripts may be written by surrounding the superscripted text by ``^`` characters; subscripts may be written by surrounding the subscripted text by ``~`` characters. Thus, for example, :: H~2~O is a liquid. 2^10^ is 1024. The text between ``^...^`` or ``~...~`` may not contain spaces or newlines. If the superscripted or subscripted text contains spaces, these spaces must be escaped with backslashes. (This is to prevent accidental superscripting and subscripting through the ordinary use of ``~`` and ``^``, and also bad interactions with footnotes.) Thus, if you want the letter P with â€˜a catâ€™ in subscripts, use ``P~a\ cat~``, not ``P~a cat~``. Verbatim ~~~~~~~~ To make a short span of text verbatim, put it inside backticks: :: What is the difference between `>>=` and `>>`? If the verbatim text includes a backtick, use double backticks: :: Here is a literal backtick `` ` ``. (The spaces after the opening backticks and before the closing backticks will be ignored.) The general rule is that a verbatim span starts with a string of consecutive backticks (optionally followed by a space) and ends with a string of the same number of backticks (optionally preceded by a space). Note that backslash-escapes (and other Markdown constructs) do not work in verbatim contexts: :: This is a backslash followed by an asterisk: `\*`. Extension: ``inline_code_attributes`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Attributes can be attached to verbatim text, just as with `fenced code blocks <#fenced-code-blocks>`__: :: `<$>`{.haskell} Underline ~~~~~~~~~ To underline text, use the ``underline`` class: :: [Underline]{.underline} Or, without the ``bracketed_spans`` extension (but with ``native_spans``): :: Underline This will work in all output formats that support underline. Small caps ~~~~~~~~~~ To write small caps, use the ``smallcaps`` class: :: [Small caps]{.smallcaps} Or, without the ``bracketed_spans`` extension: :: Small caps For compatibility with other Markdown flavors, CSS is also supported: :: Small caps This will work in all output formats that support small caps. Highlighting ~~~~~~~~~~~~ To highlight text, use the ``mark`` class: :: [Mark]{.mark} Or, without the ``bracketed_spans`` extension (but with ``native_spans``): :: Mark This will work in all output formats that support highlighting. Math ---- Extension: ``tex_math_dollars`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Anything between two ``$`` characters will be treated as TeX math. The opening ``$`` must have a non-space character immediately to its right, while the closing ``$`` must have a non-space character immediately to its left, and must not be followed immediately by a digit. Thus, ``$20,000 and $30,000`` wonâ€™t parse as math. If for some reason you need to enclose text in literal ``$`` characters, backslash-escape them and they wonâ€™t be treated as math delimiters. For display math, use ``$$`` delimiters. (In this case, the delimiters may be separated from the formula by whitespace. However, there can be no blank lines between the opening and closing ``$$`` delimiters.) TeX math will be printed in all output formats. How it is rendered depends on the output format: LaTeX It will appear verbatim surrounded by ``$...$`` (for inline math) or ``\[...\]`` (for display math). Markdown, Emacs Org mode, ConTeXt, ZimWiki It will appear verbatim surrounded by ``$...$`` (for inline math) or ``$$...$$`` (for display math). XWiki It will appear verbatim surrounded by ``{{formula}}..{{/formula}}``. reStructuredText It will be rendered using an `interpreted text role ``:math:`` `__. AsciiDoc For AsciiDoc output math will appear verbatim surrounded by ``latexmath:[...]``. For ``asciidoc_legacy`` the bracketed material will also include inline or display math delimiters. Texinfo It will be rendered inside a ``@math`` command. roff man, Jira markup It will be rendered verbatim without ``$``\ â€™s. MediaWiki, DokuWiki It will be rendered inside ``

`` tags.
Textile
   It will be rendered inside ``

`` tags. RTF, OpenDocument It will be rendered, if possible, using Unicode characters, and will otherwise appear verbatim. ODT It will be rendered, if possible, using MathML. DocBook If the ``--mathml`` flag is used, it will be rendered using MathML in an ``inlineequation`` or ``informalequation`` tag. Otherwise it will be rendered, if possible, using Unicode characters. Docx and PowerPoint It will be rendered using OMML math markup. FictionBook2 If the ``--webtex`` option is used, formulas are rendered as images using CodeCogs or other compatible web service, downloaded and embedded in the e-book. Otherwise, they will appear verbatim. HTML, Slidy, DZSlides, S5, EPUB The way math is rendered in HTML will depend on the command-line options selected. Therefore see `Math rendering in HTML <#math-rendering-in-html>`__ above. Raw HTML -------- Extension: ``raw_html`` ~~~~~~~~~~~~~~~~~~~~~~~ Markdown allows you to insert raw HTML (or DocBook) anywhere in a document (except verbatim contexts, where ``<``, ``>``, and ``&`` are interpreted literally). (Technically this is not an extension, since standard Markdown allows it, but it has been made an extension so that it can be disabled if desired.) The raw HTML is passed through unchanged in HTML, S5, Slidy, Slideous, DZSlides, EPUB, Markdown, CommonMark, Emacs Org mode, and Textile output, and suppressed in other formats. For a more explicit way of including raw HTML in a Markdown document, see the ```raw_attribute`` extension <#extension-raw_attribute>`__. In the CommonMark format, if ``raw_html`` is enabled, superscripts, subscripts, strikeouts and small capitals will be represented as HTML. Otherwise, plain-text fallbacks will be used. Note that even if ``raw_html`` is disabled, tables will be rendered with HTML syntax if they cannot use pipe syntax. Extension: ``markdown_in_html_blocks`` ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Original Markdown allows you to include HTML â€œblocksâ€: blocks of HTML between balanced tags that are separated from the surrounding text with blank lines, and start and end at the left margin. Within these blocks, everything is interpreted as HTML, not Markdown; so (for example), ``*`` does not signify emphasis. Pandoc behaves this way when the ``markdown_strict`` format is used; but by default, pandoc interprets material between HTML block tags as Markdown. Thus, for example, pandoc will turn ::

*one*

[a link](https://google.com)

into ::

one

a link

whereas ``Markdown.pl`` will preserve it as is. There is one exception to this rule: text between `` HTML """) ``` ## Image This image ![image](myimage.png) will be included as a cell attachment. If you want to add cell attributes, group cells differently, or add output to code cells, then you need to include divs to indicate the structure. You can use either `fenced divs <#extension-fenced_divs>`__ or `native divs <#extension-native_divs>`__ for this. Here is an example: :: :::::: {.cell .markdown} # Lorem **Lorem ipsum** dolor sit amet, consectetur adipiscing elit. Nunc luctus bibendum felis dictum sodales. :::::: :::::: {.cell .code execution_count=1} ``` {.python} print("hello") ``` ::: {.output .stream .stdout} ``` hello ``` ::: :::::: :::::: {.cell .code execution_count=2} ``` {.python} from IPython.display import HTML HTML(""" HTML """) ``` ::: {.output .execute_result execution_count=2} ```{=html} HTML hello ``` ::: :::::: If you include raw HTML or TeX in an output cell, use the `raw attribute <#extension-raw_attribute>`__, as shown in the last cell of the example above. Although pandoc can process â€œbareâ€ raw HTML and TeX, the result is often interspersed raw elements and normal textual elements, and in an output cell pandoc expects a single, connected raw block. To avoid using raw HTML or TeX except when marked explicitly using raw attributes, we recommend specifying the extensions ``-raw_html-raw_tex+raw_attribute`` when translating between Markdown and ipynb notebooks. Note that options and extensions that affect reading and writing of Markdown will also affect Markdown cells in ipynb notebooks. For example, ``--wrap=preserve`` will preserve soft line breaks in Markdown cells; ``--markdown-headings=setext`` will cause Setext-style headings to be used; and ``--preserve-tabs`` will prevent tabs from being turned to spaces. Vimdoc ====== Vimdoc writer generates Vim help files and makes use of the following metadata variables: .. code:: yaml abstract: "A short description" author: Author title: Title # Vimdoc-specific filename: "definition-lists.txt" vimdoc-prefix: pandoc Complete header requires ``abstract``, ``author``, ``title`` and ``filename`` to be set. Compiling file with such metadata produces the following file (assumes ``--standalone``, see `Templates <#templates>`__): .. code:: vimdoc *definition-lists.txt* A short description Title by Author Type |gO| to see the table of contents. [...] vim:tw=72:sw=4:ts=4:ft=help:norl:et: If ``vimdoc-prefix`` is set, all non-command tags are prefixed with its value, it is used to prevent tag collision: all headers have a tag (either inferred or explicit) and multiple help pages can have the same header names, therefore collision is to be expected. Let our input be the following markdown file: .. code:: markdown ## Header `:[range]Fnl {expr}`{#:Fnl} : Evaluates {expr} or range `vim.b`{#vim.b} : Buffer-scoped (`:h b:`) variables for the current buffer. Invalid or unset key returns `nil`. Can be indexed with an integer to access variables for a specific buffer. [Span]{#span} : generic inline container for phrasing content, which does not inherently represent anything. Convert it to vimdoc: .. code:: vimdoc ------------------------------------------------------------------------ Header *header* :[range]Fnl {expr} *:Fnl* Evaluates {expr} or range `vim.b` *vim.b* Buffer-scoped (|b:|) variables for the current buffer. Invalid or unset key returns `nil`. Can be indexed with an integer to access variables for a specific buffer. Span *span* generic inline container for phrasing content, which does not inherently represent anything. Convert it to vimdoc with metadata variable set (e.g.Â with ``-M vimdoc-prefix=pandoc``) .. code:: vimdoc ------------------------------------------------------------------------ Header *pandoc-header* :[range]Fnl {expr} *:Fnl* Evaluates {expr} or range `vim.b` *pandoc-vim.b* Buffer-scoped (|b:|) variables for the current buffer. Invalid or unset key returns `nil`. Can be indexed with an integer to access variables for a specific buffer. Span *pandoc-span* generic inline container for phrasing content, which does not inherently represent anything. ``vim.b`` and ``Span`` got their prefixes but not ``:Fnl`` because ex-commands (those starting with ``:``) donâ€™t get a prefix, since they are considered unique across help pages. In both cases ``:help b:`` became reference ``|b:|`` (also works with ``:h b:``). Links pointing to either https://vimhelp.org/ or https://neovim.io/doc/user become references too. Vim traditionally wraps at 78, but Pandoc defaults to 72. Use ``--columns 78`` to match Vim. Syntax highlighting =================== Pandoc will automatically highlight syntax in `fenced code blocks <#fenced-code-blocks>`__ that are marked with a language name. The Haskell library `skylighting `__ is used for highlighting. Currently highlighting is supported only for HTML, EPUB, Docx, Ms, Man, Typst, and LaTeX/PDF output. To see a list of language names that pandoc will recognize, type ``pandoc --list-highlight-languages``. The color scheme can be selected using the ``--syntax-highlighting`` option. The default color scheme is ``pygments``, which imitates the default color scheme used by the Python library pygments (though pygments is not actually used to do the highlighting). To see a list of highlight styles, type ``pandoc --list-highlight-styles``. If you are not satisfied with the predefined styles, you can use ``--print-highlight-style`` to generate a JSON ``.theme`` file which can be modified and used as the argument to ``--syntax-highlighting``. To get a JSON version of the ``pygments`` style, for example: :: pandoc -o my.theme --print-highlight-style pygments Then edit ``my.theme`` and use it like this: :: pandoc --syntax-highlighting my.theme If you are not satisfied with the built-in highlighting, or you want to highlight a language that isnâ€™t supported, you can use the ``--syntax-definition`` option to load a `KDE-style XML syntax definition file `__. Before writing your own, have a look at KDEâ€™s `repository of syntax definitions `__. If you receive an error that pandoc â€œCould not read highlighting themeâ€, check that the JSON file is encoded with UTF-8 and has no Byte-Order Mark (BOM). To disable highlighting, use ``--syntax-highlighting=none``. Custom Styles ============= Custom styles can be used in the docx, odt and ICML formats. Output ------ By default, pandocâ€™s odt, docx and ICML output applies a predefined set of styles for blocks such as paragraphs and block quotes, and uses largely default formatting (italics, bold) for inlines. This will work for most purposes, especially alongside a `reference doc <#option--reference-doc>`__ file. However, if you need to apply your own styles to blocks, or match a preexisting set of styles, pandoc allows you to define custom styles for blocks and text using ``div``\ s and ``span``\ s, respectively. If you define a Div, Span, or Table with the attribute ``custom-style``, pandoc will apply your specified style to the contained elements (with the exception of elements whose function depends on a style, like headings, code blocks, block quotes, or links). So, for example, using the ``bracketed_spans`` syntax, :: [Get out]{custom-style="Emphatically"}, he said. would produce a file with â€œGet outâ€ styled with character style ``Emphatically``. Similarly, using the ``fenced_divs`` syntax, :: Dickinson starts the poem simply: ::: {custom-style="Poetry"} | A Bird came down the Walk--- | He did not know I saw--- ::: would style the two contained lines with the ``Poetry`` paragraph style. Styles will be defined in the output file as inheriting from normal text (docx) or Default Paragraph Style (odt), if the styles are not yet in your `reference doc <#option--reference-doc>`__. If they are already defined, pandoc will not alter the definition. This feature allows for greatest customization in conjunction with `pandoc filters `__. If you want all paragraphs after block quotes to be indented, you can write a filter to apply the styles necessary. If you want all italics to be transformed to the ``Emphasis`` character style (perhaps to change their color), you can write a filter which will transform all italicized inlines to inlines within an ``Emphasis`` custom-style ``span``. For docx or odt output, you donâ€™t need to enable any extensions for custom styles to work. Input ----- The docx reader, by default, only reads those styles that it can convert into pandoc elements, either by direct conversion or interpreting the derivation of the input documentâ€™s styles. By enabling the ```styles`` extension <#ext-styles>`__ in the docx reader (``-f docx+styles``), you can produce output that maintains the styles of the input document, using the ``custom-style`` class. A ``custom-style`` attribute will be added for each style. Divs will be created to hold the paragraph styles, and Spans to hold the character styles. Table styles will be applied directly to the Table. For example, using the ``custom-style-reference.docx`` file in the test directory, we have the following different outputs: Without the ``+styles`` extension: :: $ pandoc test/docx/custom-style-reference.docx -f docx -t markdown This is some text. This is text with an *emphasized* text style. And this is text with a **strengthened** text style. > Here is a styled paragraph that inherits from Block Text. And with the extension: :: $ pandoc test/docx/custom-style-reference.docx -f docx+styles -t markdown ::: {custom-style="First Paragraph"} This is some text. ::: ::: {custom-style="Body Text"} This is text with an [emphasized]{custom-style="Emphatic"} text style. And this is text with a [strengthened]{custom-style="Strengthened"} text style. ::: ::: {custom-style="My Block Style"} > Here is a styled paragraph that inherits from Block Text. ::: With these custom styles, you can use your input document as a reference-doc while creating docx output (see below), and maintain the same styles in your input and output files. Custom readers and writers ========================== Pandoc can be extended with custom readers and writers written in `Lua `__. (Pandoc includes a Lua interpreter, so Lua need not be installed separately.) To use a custom reader or writer, simply specify the path to the Lua script in place of the input or output format. For example: :: pandoc -t data/sample.lua pandoc -f my_custom_markup_language.lua -t latex -s If the script is not found relative to the working directory, it will be sought in the ``custom`` subdirectory of the user data directory (see ``--data-dir``). A custom reader is a Lua script that defines one function, Reader, which takes a string as input and returns a Pandoc AST. See the `Lua filters documentation `__ for documentation of the functions that are available for creating pandoc AST elements. For parsing, the `lpeg `__ parsing library is available by default. To see a sample custom reader: :: pandoc --print-default-data-file creole.lua If you want your custom reader to have access to reader options (e.g.Â the tab stop setting), you give your Reader function a second ``options`` parameter. A custom writer is a Lua script that defines a function that specifies how to render each element in a Pandoc AST. See the `djot-writer.lua `__ for a full-featured example. Note that custom writers have no default template. If you want to use ``--standalone`` with a custom writer, you will need to specify a template manually using ``--template`` or add a new default template with the name ``default.NAME_OF_CUSTOM_WRITER.lua`` to the ``templates`` subdirectory of your user data directory (see `Templates <#templates>`__). Reproducible builds =================== Some of the document formats pandoc targets (such as EPUB, docx, and ODT) include build timestamps in the generated document. That means that the files generated on successive builds will differ, even if the source does not. To avoid this, set the ``SOURCE_DATE_EPOCH`` environment variable, and the timestamp will be taken from it instead of the current time. ``SOURCE_DATE_EPOCH`` should contain an integer unix timestamp (specifying the number of seconds since midnight UTC January 1, 1970). For reproducible builds with LaTeX, you can either specify the ``pdf-trailer-id`` in the metadata or leave it undefined, in which case pandoc will create a trailer-id based on a hash of the ``SOURCE_DATE_EPOCH`` and the documentâ€™s contents. Some document formats also include a unique identifier. For EPUB, this can be set explicitly by setting the ``identifier`` metadata field (see `EPUB Metadata <#epub-metadata>`__, above). Accessible PDFs and PDF archiving standards =========================================== PDF is a flexible format, and using PDF in certain contexts requires additional conventions. For example, PDFs are not accessible by default; they define how characters are placed on a page but do not contain semantic information on the content. However, it is possible to generate accessible PDFs, which use tagging to add semantic information to the document. Pandoc defaults to LaTeX to generate PDF. Tagging support in LaTeX is in development and not readily available, so PDFs generated in this way will always be untagged and not accessible. This means that alternative engines must be used to generate accessible PDFs. The PDF standards PDF/A and PDF/UA define further restrictions intended to optimize PDFs for archiving and accessibility. Tagging is commonly used in combination with these standards to ensure best results. Note, however, that standard compliance depends on many things, including the colorspace of embedded images. Pandoc cannot check this, and external programs must be used to ensure that generated PDFs are in compliance. ConTeXt ------- ConTeXt always produces tagged PDFs, but the quality depends on the input. The default ConTeXt markup generated by pandoc is optimized for readability and reuse, not tagging. Enable the ```tagging`` <#extension--tagging>`__ format extension to force markup that is optimized for tagging. For example: :: pandoc -t context+tagging doc.md -o doc.pdf A recent ``context`` version should be used, as older versions contained a bug that lead to invalid PDF metadata. WeasyPrint ---------- The HTML-based engine WeasyPrint includes experimental support for PDF/A and PDF/UA since version 57. Tagged PDFs can created with :: pandoc --pdf-engine=weasyprint \ --pdf-engine-opt=--pdf-variant=pdf/ua-1 ... The feature is experimental and standard compliance should not be assumed. Prince XML ---------- The non-free HTML-to-PDF converter ``prince`` has extensive support for various PDF standards as well as tagging. E.g.: :: pandoc --pdf-engine=prince \ --pdf-engine-opt=--tagged-pdf ... See the prince documentation for more info. Typst ----- Typst 0.12 can produce PDF/A-2b: :: pandoc --pdf-engine=typst --pdf-engine-opt=--pdf-standard=a-2b ... Word Processors --------------- Word processors like LibreOffice and MS Word can also be used to generate standardized and tagged PDF output. Pandoc does not support direct conversions via these tools. However, pandoc can convert a document to a ``docx`` or ``odt`` file, which can then be opened and converted to PDF with the respective word processor. See the documentation for `Word `__ and `LibreOffice `__. Running pandoc as a web server ============================== If you rename (or symlink) the pandoc executable to ``pandoc-server``, or if you call pandoc with ``server`` as the first argument, it will start up a web server with a JSON API. This server exposes most of the conversion functionality of pandoc. For full documentation, see the `pandoc-server `__ man page. If you rename (or symlink) the pandoc executable to ``pandoc-server.cgi``, it will function as a CGI program exposing the same API as ``pandoc-server``. ``pandoc-server`` is designed to be maximally secure; it uses Haskellâ€™s type system to provide strong guarantees that no I/O will be performed on the server during pandoc conversions. Running pandoc as a Lua interpreter =================================== Calling the pandoc executable under the name ``pandoc-lua`` or with ``lua`` as the first argument will make it function as a standalone Lua interpreter. The behavior is mostly identical to that of the `standalone ``lua`` executable `__, version 5.4. All ``pandoc.*`` packages, as well as the packages ``re`` and ``lpeg``, are available via global variables. Furthermore, the globals ``PANDOC_VERSION``, ``PANDOC_STATE``, and ``PANDOC_API_VERSION`` are set at startup. For full documentation, see the `pandoc-lua `__ man page. A note on security ================== 1. Although pandoc itself will not create or modify any files other than those you explicitly ask it create (with the exception of temporary files used in producing PDFs), a filter or custom writer could in principle do anything on your file system. Please audit filters and custom writers very carefully before using them. 2. Several input formats (including LaTeX, Org, RST, and Typst) support ``include`` directives that allow the contents of a file to be included in the output. An untrusted attacker could use these to view the contents of files on the file system. (Using the ``--sandbox`` option can protect against this threat.) 3. Several output formats (including RTF, FB2, HTML with ``--self-contained``, EPUB, Docx, and ODT) will embed encoded or raw images into the output file. An untrusted attacker could exploit this to view the contents of non-image files on the file system. (Using the ``--sandbox`` option can protect against this threat, but will also prevent including images in these formats.) 4. In reading HTML files, pandoc will attempt to include the contents of ``iframe`` elements by fetching content from the local file or URL specified by ``src``. If untrusted HTML is processed on a server, this has the potential to reveal anything readable by the process running the server. Using the ``-f html+raw_html`` will mitigate this threat by causing the whole ``iframe`` to be parsed as a raw HTML block. Using \`â€“sandbox will also protect against the threat. 5. If your application uses pandoc as a Haskell library (rather than shelling out to the executable), it is possible to use it in a mode that fully isolates pandoc from your file system, by running the pandoc operations in the ``PandocPure`` monad. See the document `Using the pandoc API `__ for more details. (This corresponds to the use of the ``--sandbox`` option on the command line.) 6. Pandocâ€™s parsers can exhibit pathological performance on some corner cases. It is wise to put any pandoc operations under a timeout, to avoid DOS attacks that exploit these issues. If you are using the pandoc executable, you can add the command line options ``+RTS -M512M -RTS`` (for example) to limit the heap size to 512MB. Note that the ``commonmark`` parser (including ``commonmark_x`` and ``gfm``) is much less vulnerable to pathological performance than the ``markdown`` parser, so it is a better choice when processing untrusted input. 7. The HTML generated by pandoc is not guaranteed to be safe. If ``raw_html`` is enabled for the Markdown input, users can inject arbitrary HTML. Even if ``raw_html`` is disabled, users can include dangerous content in URLs and attributes. To be safe, you should run all HTML generated from untrusted user input through an HTML sanitizer. Authors ======= Copyright 2006â€“2024 John MacFarlane (jgm@berkeley.edu). Released under the `GPL `__, version 2 or greater. This software carries no warranty of any kind. (See COPYRIGHT for full copyright and warranty notices.) For a full list of contributors, see the file AUTHORS.md in the pandoc source code. .. [1] The point of this rule is to ensure that normal paragraphs starting with peopleâ€™s initials, like :: B. Russell won a Nobel Prize (but not for "On Denoting"). do not get treated as list items. This rule will not prevent :: (C) 2007 Joe Smith from being interpreted as a list item. In this case, a backslash escape can be used: :: (C\) 2007 Joe Smith .. [2] I have been influenced by the suggestions of `David Wheeler `__. .. [3] This scheme is due to Michel Fortin, who proposed it on the `Markdown discussion list `__. .. [4] Note that if ``--file-scope`` is used, a div written this way will be given an identifier of the form ``FILE__refs``, to avoid duplicate identifiers (see ``--file-scope``). In view of this possibility, pandoc will place the bibliography in any div whose identifier is ``refs`` *or* ends with ``__refs``. "I think I'll go down to Holloway and see Ren¨¦ Lalage," Prout said thoughtfully. "I dare say I shall be able to advise him to tell me something as to the past of the Countess. If only he were not secure, that woman would have to look to herself. He believes that the woman betrayed and murdered his brother, and he is a Corsican. Give him a few hours' start, and the law would be rid of Leona Lalage." Were the vines ranked and trimmed with pruning-knives, Further yet lay the artificial lake of Meer Alam, reflecting the palace of Baradari and the russet plain, infinite as far as the eye could reach towards the north, where other superb mausoleums were visible in their whiteness. ¡°Son, turn that preserver over¡ªlet me see the other side.¡± The Chiricahuas could see that there was trouble between the officials, both military and civil, and the government. They did not know what it was. They did not understand that the harassed general, whose word¡ªand his alone¡ªhad their entire belief, nagged and thwarted, given authority and then prevented from enforcing it, had rebelled at last, had asked to be relieved, and had been refused. But they drew in with delight the air of strife and unrest. It was the one they loved best, there could and can be no doubt about that. And Cairness himself was startled and utterly unprepared when the Reverend Taylor opened the door of the room where he lay and let her pass in. The little parson uttered no word, but there was a look on his face which said that now the questions he had put with no result were answered. It was for this that Cairness had given the best of his life. [70] "Let's go away," she whispered, half nervously and half angrily, "I hate standing here." In spite of the farm's new activities, he found that he could still manage without engaging fresh labour. The odds and ends of work which his boys took off him and[Pg 123] Beatup left them free to attack the bigger enterprises. And as Odiam grew the children would grow. Even now they were all impressed for service, except little George, who was delicate and, moreover, subject to fits. Their work was varied¡ªthey scared birds from the crops, fed the poultry, collected the eggs, drove the cows to and from pasture, fed the pigs, ran errands to the neighbouring farms. In course of time Albert learned milking, and could saddle old Crump the roan, or put him into the gig. Soon the rumour spread round Peasmarsh that Backfield was going to buy some more land. Reuben himself had started it. Tyler and the other leaders, followed by hundreds, now rushed on to the palace;¡ªthe massive gates yielded to their blows, and the assailants, pouring in through the arched passages, ran along gallery and window, and through seemingly countless apartments. Yet, even amidst their eagerness to capture Lancaster, they paused a moment, casting glances of astonishment and pleasure at the beautifully inlaid cabinets, rich tapestries, and embroidered cushions, which every where met their gaze. The galleyman, however, was perhaps the only one among all the gazers who knew the value of the things he looked upon; and he could not repress a feeling of regret, as he glanced at the damask hangings, and the gold cords and fringes, and remembered that all these would be speedily feeding the flames. As he was thus occupied, and thinking what a fortune these articles would be to a pedling merchant, he saw Jack Straw in the act of whispering in Harvey's ear (who, by some strange sort of moral attraction, was standing by his side), and he noticed them linger until the group they had accompanied passed on to the inspection of other apartments. Oakley then opened a door in a recess in the corridor, which, when they entered, they closed hastily after them. HoME ¾©ÏãÃÀ½ÅÔÚÏß²¥·Å ENTER NUMBET 0016jduigr.com.cn
www.lianpei.org.cn
kqchain.com.cn
www.kimkim.com.cn
px8news.com.cn
www.taqqq.com.cn
www.todaycode.com.cn
www.uhfjwz.com.cn
www.pesyun.com.cn
wyzwck.com.cn