diff options
author | John MacFarlane <fiddlosopher@gmail.com> | 2012-03-09 10:32:32 -0800 |
---|---|---|
committer | John MacFarlane <fiddlosopher@gmail.com> | 2012-03-09 10:32:32 -0800 |
commit | 9766b532f38266d0606520fcbfb0c13fd5b09a2f (patch) | |
tree | 9357603e8e3ad600e75dc72bd93d2731f61f1b6d /README | |
parent | 6787cf2fbf32a59fcf70d09ed2f2ffe12f642d0a (diff) | |
download | pandoc-9766b532f38266d0606520fcbfb0c13fd5b09a2f.tar.gz |
Added beamer+lhs as output format.
Diffstat (limited to 'README')
-rw-r--r-- | README | 11 |
1 files changed, 6 insertions, 5 deletions
@@ -138,7 +138,7 @@ General options `json` (JSON version of native AST), `markdown` (markdown), `textile` (Textile), `rst` (reStructuredText), `html` (HTML), or `latex` (LaTeX). If `+lhs` is appended to `markdown`, `rst`, - or `latex`, the input will be treated as literate Haskell source: + `latex`, the input will be treated as literate Haskell source: see [Literate Haskell support](#literate-haskell-support), below. @@ -156,8 +156,8 @@ General options slide show), or `rtf` (rich text format). Note that `odt` and `epub` output will not be directed to *stdout*; an output filename must be specified using the `-o/--output` option. If `+lhs` is appended - to `markdown`, `rst`, `latex`, `html`, or `html5`, the output will - be rendered as literate Haskell source: see [Literate Haskell + to `markdown`, `rst`, `latex`, `beamer`, `html`, or `html5`, the output + will be rendered as literate Haskell source: see [Literate Haskell support](#literate-haskell-support), below. `-o` *FILE*, `--output=`*FILE* @@ -2168,8 +2168,9 @@ Literate Haskell support ======================== If you append `+lhs` to an appropriate input or output format (`markdown`, -`rst`, or `latex` for input or output; `html` or `html5` for output only), -pandoc will treat the document as literate Haskell source. This means that +`rst`, or `latex` for input or output; `beamer`, `html` or `html5` for +output only), 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}` |