\HeaderA{Rdutils}{Rd Utilities}{Rdutils}
\aliasA{Rd\_db}{Rdutils}{Rd.Rul.db}
\aliasA{Rd\_parse}{Rdutils}{Rd.Rul.parse}
\keyword{utilities}{Rdutils}
\keyword{documentation}{Rdutils}
\begin{Description}\relax
Utilities for computing on the information in Rd objects.
\end{Description}
\begin{Usage}
\begin{verbatim}
Rd_db(package, dir, lib.loc = NULL)
Rd_parse(file, text = NULL)
\end{verbatim}
\end{Usage}
\begin{Arguments}
\begin{ldescription}
\item[\code{package}] a character string naming an installed package.
\item[\code{dir}] a character string specifying the path to a package's root
source directory.  This should contain the subdirectory \file{man}
with \R{} documentation sources (in Rd format).  Only used if
\code{package} is not given.
\item[\code{lib.loc}] a character vector of directory names of \R{} libraries,
or \code{NULL}.  The default value of \code{NULL} corresponds to all
libraries currently known.  The specified library trees are used to
to search for \code{package}.
\item[\code{file}] a connection, or a character string giving the name of a
file or a URL to read documentation in Rd format from.
\item[\code{text}] character vector with documentation in Rd format.
Elements are treated as if they were lines of a file.
\end{ldescription}
\end{Arguments}
\begin{Details}\relax
\code{Rd\_db} builds a simple \dQuote{data base} of all Rd sources in a
package, as a list of character vectors with the lines of the Rd files
in the package.  This is particularly useful for working on installed
packages, where the individual Rd files in the sources are no longer
available.

\code{Rd\_parse} is a simple top-level Rd parser/analyzer.  It returns
a list with components
\describe{
\item[\code{meta}] a list containing the Rd metadata (aliases,
concepts, keywords, and documentation type);

\item[\code{data}] a data frame with the names (\code{tags}) and
corresponding text (\code{vals}) of the top-level sections in the
R documentation object;

\item[\code{rest}] top-level text not accounted for (currently,
silently discarded by Rdconv, and hence usually the indication of
a problem).

}
Note that at least for the time being, only the top-level structure is
analyzed.
\end{Details}
\begin{Section}{Warning}
These functions are still experimental.  Names, interfaces and values
might change in future versions.
\end{Section}
\begin{Examples}
\begin{ExampleCode}
## Build the Rd db for the (installed) base package.
db <- Rd_db("base")
## Run Rd_parse on all entries in the Rd db.
db <- lapply(db, function(txt) Rd_parse(text = txt))
## Extract the metadata.
meta <- lapply(db, "[[", "meta")

## Keyword metadata per Rd file.
keywords <- lapply(meta, "[[", "keywords")
## Tabulate the keyword entries.
kw_table <- sort(table(unlist(keywords)))
## The 5 most frequent ones:
rev(kw_table)[1 : 5]
## The "most informative" ones:
kw_table[kw_table == 1]

## Concept metadata per Rd file.
concepts <- lapply(meta, "[[", "concepts")
## How many files already have \concept metadata?
sum(sapply(concepts, length) > 0)
## How many concept entries altogether?
length(unlist(concepts))
\end{ExampleCode}
\end{Examples}

