compileAsciiDoc.default

compileAsciiDoc

The filename and (optional) path of the
     document to be compiled.

filename, path

Additional arguments passed to executable <code>ascii</code>
    (which must be on the system search path)
    called via <code><a rd-options="base" href="/link/system2?package=R.rsp&version=0.30.0&to=base" data-mini-rdoc="base::system2">system2</a></code>().

outPath

Should the generated document be post processed or not?

postprocess

See <code><a rd-options="R.utils" href="/link/Verbose?package=R.rsp&version=0.30.0&to=R.utils" data-mini-rdoc="R.utils::Verbose">Verbose</a></code>.

verbose

internal

file

The RSP markup language makes any text-based document come alive.  RSP provides a powerful markup for controlling the content and output of LaTeX, HTML, Markdown, AsciiDoc, Sweave and knitr documents (and more), e.g. 'Today's date is <%=Sys.Date()%>'.  Contrary to many other literate programming languages, with RSP it is straightforward to loop over mixtures of code and text sections, e.g. in month-by-month summaries.  RSP has also several preprocessing directives for incorporating static and dynamic contents of external files (local or online) among other things.  Functions rstring() and rcat() make it easy to process RSP strings, rsource() sources an RSP file as it was an R script, while rfile() compiles it (even online) into its final output format, e.g. rfile('report.tex.rsp') generates 'report.pdf' and rfile('report.md.rsp') generates 'report.html'.  RSP is ideal for self-contained scientific reports and R package vignettes.  It's easy to use - if you know how to write an R script, you'll be up and running within minutes.

compileAsciiDoc: Compiles an AsciiDoc file

Description

Usage

Arguments

Value