% Generated by roxygen2: do not edit by hand
% Please edit documentation in R/hooks-html.R, R/hooks-asciidoc.R,
%   R/hooks-latex.R, R/hooks-md.R, R/hooks-rst.R, R/hooks-textile.R
\name{render_html}
\alias{render_html}
\alias{render_asciidoc}
\alias{render_latex}
\alias{render_sweave}
\alias{render_listings}
\alias{render_markdown}
\alias{render_jekyll}
\alias{render_rst}
\alias{render_textile}
\title{Set output hooks for different output formats}
\usage{
render_html()

render_asciidoc()

render_latex()

render_sweave()

render_listings()

render_markdown(strict = FALSE, fence_char = "`")

render_jekyll(highlight = c("pygments", "prettify", "none"), extra = "")

render_rst(strict = FALSE)

render_textile()
}
\arguments{
\item{strict}{Boolean; whether to use strict markdown or reST syntax. For markdown, if
\code{TRUE}, code blocks will be indented by 4 spaces, otherwise they are
put in fences made by three backticks. For reST, if \code{TRUE}, code is
put under two colons and indented by 4 spaces, otherwise it is put under the
\samp{sourcecode} directive (this is useful for e.g. Sphinx).}

\item{fence_char}{A single character to be used in the code blocks fence.
This can be e.g. a backtick or a tilde, depending on your Markdown rendering
engine.}

\item{highlight}{Which code highlighting engine to use: if \code{pygments},
the Liquid syntax is used (default approach Jekyll); if \code{prettify},
the output is prepared for the JavaScript library \file{prettify.js}; if
\code{none}, no highlighting engine will be used, and code blocks are simply
indented by 4 spaces).}

\item{extra}{Extra tags for the highlighting engine. For \code{pygments}, this
can be \code{'linenos'}; for \code{prettify}, it can be \code{'linenums'}.}
}
\value{
\code{NULL}; corresponding hooks are set as a side effect
}
\description{
These functions set built-in output hooks for LaTeX, HTML, Markdown,
reStructuredText, AsciiDoc and Textile.
}
\details{
There are three variants of markdown documents: ordinary markdown
(\code{render_markdown(strict = TRUE)}), extended markdown (e.g. GitHub
Flavored Markdown and pandoc; \code{render_markdown(strict = FALSE)}), and
Jekyll (a blogging system on GitHub; \code{render_jekyll()}). For LaTeX
output, there are three variants as well: \pkg{knitr}'s default style
(\code{render_latex()}; use the LaTeX \pkg{framed} package), Sweave style
(\code{render_sweave()}; use \file{Sweave.sty}) and listings style
(\code{render_listings()}; use LaTeX \pkg{listings} package). Default HTML
output hooks are set by \code{render_html()}; \code{render_rst()} and
\code{render_asciidoc()} are for reStructuredText and AsciiDoc respectively.

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

You can use \code{\link{knit_hooks}} to further customize output hooks; see
references.
}
\references{
See output hooks in \url{https://yihui.org/knitr/hooks/}.

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