I found some trivial typos, mostly unmatched parentheses, in the R
manuals. More information and suggested fixes are in the attached diff file.
--
Mikko Korpela
Department of Geosciences and Geography
University of Helsinki
Index: doc/manual/R-admin.texi
===================================================================
--- doc/manual/R-admin.texi (revision 72066)
+++ doc/manual/R-admin.texi (working copy)
@@ -571,7 +571,7 @@
@noindent
This requires @command{ebook-convert} from @command{Calibre}
(@uref{http://calibre-ebook.com/download}), or from most Linux
-distributions). If necessary the path to @command{ebook-convert} can be
+distributions. If necessary the path to @command{ebook-convert} can be
set as make macro @env{EBOOK} to by editing @file{doc/manual/Makefile}
(which contains a commented value suitable for macOS).
@@ -2973,7 +2973,7 @@
distributions.)
Even on 64-bit builds of @R{} there are limits on the size of @R{}
-objects (see @code{help("Memory-limits")}, some of which stem from the
+objects (see @code{help("Memory-limits")}), some of which stem from the
use of 32-bit integers (especially in FORTRAN code). For example, the
dimensions of an array are limited to @math{2^{31} - 1}.
@@ -4566,7 +4566,7 @@
designed for use in terminals). In such locales @emph{fontsets} are
used, made up of fonts encoded in other encodings. If the locale you
are using has an entry in the @samp{XLC_LOCALE} directory (typically
-@file{/usr/share/X11/locale}, it is likely that all you need to do is to
+@file{/usr/share/X11/locale}), it is likely that all you need to do is to
pick a suitable font specification that has fonts in the encodings
specified there. If not, you may have to get hold of a suitable locale
entry for X11. This may mean that, for example, Japanese text can be
Index: doc/manual/R-data.texi
===================================================================
--- doc/manual/R-data.texi (revision 72066)
+++ doc/manual/R-data.texi (working copy)
@@ -345,7 +345,7 @@
By default strings are quoted (including the row and column names).
Argument @code{quote} controls if character and factor variables are
quoted: some programs, for example @pkg{Mondrian}
-(@uref{https://en.wikipedia.org/wiki/Mondrian_(software)}, do not accept
+(@uref{https://en.wikipedia.org/wiki/Mondrian_(software)}), do not accept
quoted strings.
Some care is needed if the strings contain embedded quotes. Three
Index: doc/manual/R-exts.texi
===================================================================
--- doc/manual/R-exts.texi (revision 72066)
+++ doc/manual/R-exts.texi (working copy)
@@ -463,9 +463,9 @@
suitable @samp{Authors@@R} field is given. This field can be used to
provide a refined and machine-readable description of the package
``authors'' (in particular specifying their precise @emph{roles}), via
-suitable @R{} code. It should create an object of class @code{"person'},
+suitable @R{} code. It should create an object of class @code{"person"},
by either a call to @code{person} or a series of calls (one per
-``author'') concatenated by @code{c()}): see the example
+``author'') concatenated by @code{c()}: see the example
@file{DESCRIPTION} file above. The roles can include @samp{"aut"}
(author) for full authors, @samp{"cre"} (creator) for the package
maintainer, and @samp{"ctb"} (contributor) for other contributors,
@@ -1553,7 +1553,7 @@
@group
foo <- function(x) @{
if(!@@HAVE_FOO@@)
- stop("Sorry, library 'foo' is not available"))
+ stop("Sorry, library 'foo' is not available")
...
@end group
@end example
@@ -1566,7 +1566,7 @@
@group
foo <- function(x) @{
if(!FALSE)
- stop("Sorry, library 'foo' is not available"))
+ stop("Sorry, library 'foo' is not available")
...
@end group
@end example
@@ -3351,7 +3351,7 @@
to the encoding of the current @R{} session.
@code{Stangle()} will produce an @R{} code file in the current locale's
-encoding: for a non-@acronym{ASCII} vignette what that is recorded in a
+encoding: for a non-@acronym{ASCII} vignette what that is is recorded in a
comment at the top of the file.
@code{Sweave()} will produce a @file{.tex} file in the current
@@ -4214,7 +4214,7 @@
@R{} has tested that @code{DOUBLE COMPLEX} works (although an extension
to the Fortran standards) and so is preferred to @code{COMPLEX*16}.
(Fortran 9x code can use something like
-@code{COMPLEX(KIND=KIND(0.0D0)}@footnote{See
+@code{COMPLEX(KIND=KIND(0.0D0))}@footnote{See
@uref{http://people.ds.cam.ac.uk/nmm1/fortran/paper_07.pdf}.}.)
@@ -5179,7 +5179,7 @@
and mark strings by
@example
-dngettext(("@var{pkg}", @var{<singular string>}, @var{<plural string>}, n)
+dngettext("@var{pkg}", @var{<singular string>}, @var{<plural string>}, n)
@end example
@item
@@ -6484,8 +6484,8 @@
The ``comment'' character @samp{%} and unpaired braces@footnote{See the
examples section in the file @file{Paren.Rd} for an example.}
@emph{almost always} need to be escaped by @samp{\}, and @samp{\\} can
-be used for backslash and needs to be when there two or more adjacent
-backslashes). In @R{}-like code quoted strings are handled slightly
+be used for backslash and needs to be when there are two or more adjacent
+backslashes. In @R{}-like code quoted strings are handled slightly
differently; see @uref{https://developer.r-project.org/parseRd.pdf,
``Parsing Rd files''} for details -- in particular braces should not be
escaped in quoted strings.
@@ -12003,7 +12003,7 @@
Package @CRANpkg{RODBC} uses external pointers to maintain its
@emph{channels}, connections to databases. There can be several
connections open at once, and the status information for each is stored
-in a C structure (pointed to by @code{this_handle}) in the code extract
+in a C structure (pointed to by @code{thisHandle} in the code extract
below) that is returned @emph{via} an external pointer as part of the RODBC
`channel' (as the @code{"handle_ptr"} attribute). The external pointer
is created by
@@ -12838,7 +12838,7 @@
The Gamma function, the natural logarithm of its absolute value and
first four derivatives and the n-th derivative of Psi, the digamma
function, which is the derivative of @code{lgammafn}. In other words,
-@code{digamma(x)} is the same as @code{(psigamma(x,0)},
+@code{digamma(x)} is the same as @code{psigamma(x,0)},
@code{trigamma(x) == psigamma(x,1)}, etc.
@end deftypefun
Index: doc/manual/R-intro.texi
===================================================================
--- doc/manual/R-intro.texi (revision 72066)
+++ doc/manual/R-intro.texi (working copy)
@@ -6674,7 +6674,7 @@
File @emph{permissions} are a related topic. @R{} has support for the
POSIX concepts of read/write/execute permission for owner/group/all but
-this may be only partially supported on the filesystem (so for example
+this may be only partially supported on the filesystem, so for example
on Windows only read-only files (for the account running the @R{}
session) are recognized. Access Control Lists (ACLs) are employed on
several filesystems, but do not have an agreed standard and @R{} has no
Index: doc/manual/R-ints.texi
===================================================================
--- doc/manual/R-ints.texi (revision 72066)
+++ doc/manual/R-ints.texi (working copy)
@@ -1051,7 +1051,7 @@
`Special' primitive and internal functions evaluate their arguments
internally @emph{after} @code{R_Visible} has been set, and evaluation of
-the arguments (e.g.@: an assignment as in PR#9263)) can change the value
+the arguments (e.g.@: an assignment as in PR#9263) can change the value
of the flag.
The @code{R_Visible} flag can also get altered during the evaluation of
@@ -2261,7 +2261,7 @@
@noindent
). One could argue about @code{~}, but it is known to the parser and has
semantics quite unlike a normal function. And @code{:} is documented
-with different argument names in its two meanings.)
+with different argument names in its two meanings.
The QC functions @code{codoc} and @code{checkS3methods} also make use of
these environments (effectively placing them in front of base in the
@@ -2652,7 +2652,7 @@
roots for each physical or logical file system (`volume'), organized
under @emph{drives} (with file paths starting @code{D:} for an
@acronym{ASCII} letter, case-insensitively) and @emph{network shares}
-(with paths like @code{\netname\topdir\myfiles\a file}. There is a
+(with paths like @code{\netname\topdir\myfiles\a file}). There is a
current drive, and path names without a drive part are relative to the
current drive. Further, each drive has a current directory, and
relative paths are relative to that current directory, on a particular
Index: doc/manual/R-lang.texi
===================================================================
--- doc/manual/R-lang.texi (revision 72066)
+++ doc/manual/R-lang.texi (working copy)
@@ -1838,7 +1838,7 @@
The most important example of a class method for @code{[} is that used
for data frames. It is not described in detail here (see the help
-page for @code{[.data.frame}, but in broad terms, if two indices are
+page for @code{[.data.frame}), but in broad terms, if two indices are
supplied (even if one is empty) it creates matrix-like indexing for a
structure that is basically a list of vectors of the same length. If a
single index is supplied, it is interpreted as indexing the list of
______________________________________________
R-devel@r-project.org mailing list
https://stat.ethz.ch/mailman/listinfo/r-devel
