render_latex: Set output hooks for different output formats

Description

These functions set built-in output hooks for LaTeX, HTML, Markdown and reStructuredText.

Usage

render_latex()
render_sweave()
render_listings()
render_html()
render_markdown(strict = FALSE)
render_jekyll(highlight = c("pygments", "prettify", "none"), extra = "")
render_rst(strict = FALSE)

Arguments

strict

whether to use strict markdown or reST syntax; for markdown: if TRUE, code blocks will be indented by 4 spaces, otherwise they are put in fences made by three backticks; for reST, if TRUE, code is put under two colons and

highlight

which code highlighting engine to use: for pygments, the Liquid syntax is used (default approach Jekyll); for prettify, the output is prepared for the JavaScript library prettify.js; for none, no

extra

extra tags for the highlighting engine; for pygments, it can be 'linenos'; for prettify, it can be 'linenums'

Value

NULL; corresponding hooks are set as a side effect

Details

There are three variants of markdown documents: ordinary markdown (render_markdown(strict = TRUE)), extended markdown (e.g. GitHub Flavored Markdown and pandoc; render_markdown(strict = FALSE)), and Jekyll (a blogging system on GitHub; render_jekyll()). For LaTeX output, there are three variants as well: knitr's default style (render_latex(); use the LaTeX framed package), Sweave style (render_sweave(); use Sweave.sty) and listings style (render_listings(); use LaTeX listings package). Default HTML output hooks are set by render_html(), and reStructuredText uses render_rst().

These functions can be used before knit() or in the first chunk of the input document (ideally this chunk has options include = FALSE and cache = FALSE) so that all the following chunks will be formatted as expected.

You can use knit_hooks to further customize output hooks; see references.

References

See output hooks in http://yihui.name/knitr/hooks.

Jekyll and Liquid: https://github.com/mojombo/jekyll/wiki/Liquid-Extensions; prettify.js: http://code.google.com/p/google-code-prettify/