Markup.

git-svn-id: https://svn.r-project.org/R/trunk@85660 00db46b3-68df-0310-9c12-caf00c1e9a41

doc/manual/R-exts.texi

@@ -1178,7 +1178,7 @@ allowed in the @file{R} directory to allow a @file{configure} script to
 generate suitable files.
 
 Only @acronym{ASCII} characters (and the control characters tab,
-formfeed, LF and CR) should be used in code files.  Other characters are
+formfeed, @abbr{LF} and @abbr{CR}) should be used in code files.  Other characters are
 accepted in comments@footnote{but they should be in the encoding
 declared in the @file{DESCRIPTION} file.}, but then the comments may not
 be readable in e.g.@: a UTF-8 locale.  Non-@acronym{ASCII} characters in
@@ -3511,7 +3511,7 @@ and for the use of reasonable levels of compression.
 @item
 C, C++ and Fortran source and header files@footnote{An exception is made
 for subdirectories with names starting @samp{win} or @samp{Win}.} are
-tested for portable (LF-only) line endings.  If there is a
+tested for portable (@abbr{LF}-only) line endings.  If there is a
 @file{Makefile} or @file{Makefile.in} or @file{Makevars} or
 @file{Makevars.in} file under the @file{src} directory, it is checked
 for portable line endings and the correct use of @samp{$(BLAS_LIBS)} and
@@ -3731,7 +3731,7 @@ Prior to actually building the package in the standard gzipped tar file
 format, a few diagnostic checks and cleanups are performed.  In
 particular, it is tested whether object indices exist and can be assumed
 to be up-to-date, and C, C++ and Fortran source files and relevant
-makefiles in a @file{src} directory are tested and converted to LF
+makefiles in a @file{src} directory are tested and converted to @abbr{LF}
 line-endings if necessary.
 
 Run-time checks whether the package works correctly should be performed
@@ -4000,7 +4000,7 @@ Finally, if there is a @file{Makefile} and it has a @samp{clean:}
 target, @command{make clean} is run.
 
 All the usual @emph{caveats} about including a @file{Makefile} apply.
-It must be portable (no @acronym{GNU} extensions), use LF line endings
+It must be portable (no @acronym{GNU} extensions), use @abbr{LF} line endings
 and must work correctly with a parallel @command{make}: too many authors
 have written things like
 
@@ -4886,8 +4886,8 @@ empty @file{configure.win} file if no actions are needed).
 @item
 If your package has a @file{Makevars} or @file{Makefile} file, make sure
 that you use only portable make features.  Such files should be
-LF-terminated@footnote{Solaris @command{make} did not accept
-CRLF-terminated Makefiles; Solaris warned about and some other
+@abbr{LF}-terminated@footnote{Solaris @command{make} did not accept
+@abbr{CRLF}-terminated Makefiles; Solaris warned about and some other
 @command{make}s ignore incomplete final lines.} (including the final
 line of the file) and not make use of GNU extensions.  (The POSIX
 specification is available at
@@ -9637,7 +9637,7 @@ will be some small memory leaks from @code{readline} and @R{} itself ---
 these are memory areas that are in use right up to the end of the @R{}
 session.  Expect this to run around 20x slower than without
 @code{valgrind}, and in some cases much slower than that.  Several
-versions of @code{valgrind} were not happy with some optimized BLASes
+versions of @code{valgrind} were not happy with some optimized BLAS libraries
 that use @acronym{CPU}-specific instructions so you may need to build a
 version of @R{} specifically to use with @code{valgrind}.
 
@@ -11948,7 +11948,7 @@ system and so the two interworked successfully.  This was true of
 @command{gcc} 4 and later.  In particular, any package that makes use of
 Fortran I/O will when compiled on Windows interfere with C I/O: when the
 Fortran I/O support code is initialized (typically when the package is
-loaded) the C @code{stdout} and @code{stderr} are switched to LF line
+loaded) the C @code{stdout} and @code{stderr} are switched to @abbr{LF} line
 endings.  (Function @code{init} in file
 @file{src/modules/lapack/init_win.c} shows how to mitigate this.  In a
 package this would look something like

doc/manual/R-ints.texi

@@ -1148,7 +1148,7 @@ their earlier `internal' dot-name versions) and
 serialize to (a file, a connection, a raw vector) and whether they are
 intended to serialize a single object or a collection of objects
 (typically the workspace).  @code{save} writes a header at the beginning
-of the file (a single LF-terminated line) which the lower-level versions
+of the file (a single @abbr{LF}-terminated line) which the lower-level versions
 do not.
 
 @code{save} and @code{saveRDS} allow various forms of compression, and

doc/manual/rw-FAQ.texi

@@ -845,7 +845,7 @@ or their use suppressed by @code{options(useFancyQuotes=FALSE)}.
 @section There is no tilde on my keyboard!
 
 Where tilde does not appear on the main keyboard, it can normally be
-accessed by pressing AltGr (the right Alt key) plus some other key.
+accessed by pressing @key{AltGr} (the right @key{Alt} key) plus some other key.
 This is @code{]} in Canadian (multilingual), German and Scandinavian
 layouts, @code{1} in Eastern Europe, @code{[} in Portuguese, @code{4} or
 @code{5} in Spanish, @code{/} in Francophone Belgian, and so on.  You

src/library/grid/vignettes/nonfinite.Rnw

@@ -50,7 +50,7 @@ For all of these primitives, non-finite values for locations or
 sizes result in the corresponding primitive not being drawn.
 The following image provides a simple demonstration.  Each primitive
 is drawn at seven x-locations, with the fourth location made non-finite
- (as indicated by a grey \texttt{"NA"}).
+ (as indicated by a grey \code{"NA"}).
 
 <<prim1, echo=FALSE, fig=TRUE, results=hide, width=4, height=2, include=FALSE>>=
 pushViewport(viewport(layout = grid.layout(1, 2,
@@ -85,8 +85,8 @@ new location are both not non-finite.
 \textbf{polygon} {~} \\
 A non-finite value breaks the polygon into two separate polygons.
 NOTE that this break happens within the current polygon as specified
-by the \texttt{id} argument.  All polygons with the same \texttt{id}
-receive the same \texttt{gp} settings.
+by the \code{id} argument.  All polygons with the same \code{id}
+receive the same \code{gp} settings.
 
 \textbf{arrows} {~} \\
 An arrow head is only drawn if the first or last line segment is

src/library/utils/R/aspell.R

@@ -426,6 +426,7 @@ aspell_control_R_manuals <-
            "--add-texinfo-ignore=include",
            "--add-texinfo-ignore=ifclear",
            "--add-texinfo-ignore=ifset",
+           "--add-texinfo-ignore=key",
            "--add-texinfo-ignore=math",
            "--add-texinfo-ignore=multitable",
            "--add-texinfo-ignore=node",