markup

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

Author: smeyer

doc/manual/R-exts.texi

@@ -7385,7 +7385,8 @@ E.g., @file{abline.Rd} contains
 @group
 \details@{
   Typical usages are
-\preformatted@{abline(a, b, ...)
+\preformatted@{
+abline(a, b, ...)
 ......
 @}
 @end group

src/library/base/man/Arithmetic.Rd

@@ -58,9 +58,8 @@ x \%/\% y
   integer division, i.e., \code{q <- x \%/\% y := floor(x/y)}, as promoted
   by Donald Knuth, see the Wikipedia page on \sQuote{Modulo operation},
   and hence \code{sign(r) == sign(y)}.  It is guaranteed that
-  \describe{
-    \item{\code{ x == (x \%\% y) + y * (x \%/\% y) }}{\sspace (up to rounding error)}
-  }
+  (up to rounding error)
+  \preformatted{    x == (x \%\% y) + y * (x \%/\% y)    }
   unless \code{y == 0} where the result of \code{\%\%} is
   \code{\link{NA_integer_}} or \code{\link{NaN}} (depending on the
   \code{\link{typeof}} of the arguments) or for some non-\link{finite}

src/library/graphics/man/abline.Rd

@@ -28,7 +28,8 @@ abline(a = NULL, b = NULL, h = NULL, v = NULL, reg = NULL,
 }
 \details{
   Typical usages are
-\preformatted{abline(a, b, ...)
+\preformatted{
+abline(a, b, ...)
 abline(h =, ...)
 abline(v =, ...)
 abline(coef =, ...)

src/library/graphics/man/par.Rd

@@ -347,10 +347,10 @@ par(\dots, no.readonly = FALSE)
     \item{\code{lend}}{The line end style.  This can be specified as an
       integer or string:
       \describe{
-        \item{\code{0}}{and \code{"round"} mean rounded line caps
+        \item{\code{0} and \code{"round"}}{mean rounded line caps
           [\emph{default}];}
-        \item{\code{1}}{and \code{"butt"} mean butt line caps;}
-        \item{\code{2}}{and \code{"square"} mean square line caps.}
+        \item{\code{1} and \code{"butt"}}{mean butt line caps;}
+        \item{\code{2} and \code{"square"}}{mean square line caps.}
       }
     }
     \item{\code{lheight}}{The line height multiplier.
@@ -362,10 +362,10 @@ par(\dots, no.readonly = FALSE)
     \item{\code{ljoin}}{The line join style.
       This can be specified as an integer or string:
       \describe{
-        \item{\code{0}}{and \code{"round"} mean rounded line joins
+        \item{\code{0} and \code{"round"}}{mean rounded line joins
           [\emph{default}];}
-        \item{\code{1}}{and \code{"mitre"} mean mitred line joins;}
-        \item{\code{2}}{and \code{"bevel"} mean bevelled line joins.}
+        \item{\code{1} and \code{"mitre"}}{mean mitred line joins;}
+        \item{\code{2} and \code{"bevel"}}{mean bevelled line joins.}
       }
     }
     \item{\code{lmitre}}{The line mitre limit.  This controls when

src/library/methods/man/Methods_for_S3.Rd

@@ -44,9 +44,9 @@ For details, see \link{S3Methods}.
 In modern \R, a function \code{meth} in a package is registered as an S3 method
 for function \code{fun} and class \code{Class} by
 including in the package's \code{NAMESPACE} file the directive
-
-\code{S3method(fun, Class, meth)}
-
+\preformatted{
+    S3method(fun, Class, meth)
+}
 By default (and traditionally), the third argument is taken to be the
 function \code{fun.Class}; that is,
 the name of the
@@ -63,9 +63,9 @@ register S3 methods rather than requiring the package to be attached.
 
 \section{Methods for S4 Classes}{
 
-Two possible mechanisms for implementing a method  corresponding to an
-S4 class, there are two possibilities are to register it as an S3 method with the
-S4 class name or to define and set an S4 method, which will have the
+There are two possible mechanisms for implementing a method
+corresponding to an S4 class: register it as an S3 method with the
+S4 class name or define and set an S4 method, which will have the
 side effect of creating an S4 generic version of this function.
 
 For most situations either works, but
@@ -79,20 +79,17 @@ extending \code{"character"} and intending to ignore upper- and
 lower-case.
 The base function \code{\link{unique}} dispatches S3 methods.
 To define the class and a method for this function:
-
-\code{setClass("uncased", contains = "character")}
-
-\code{unique.uncased <- function(x, incomparables = FALSE, ...)
-  nextMethod(tolower(x))}
-
-\code{setMethod("unique", "uncased", unique.uncased)}
-
+\preformatted{
+    setClass("uncased", contains = "character")
+    unique.uncased <- function(x, incomparables = FALSE, ...)
+        NextMethod(tolower(x))
+    setMethod("unique", "uncased", unique.uncased)
+}
 In addition, the \code{NAMESPACE} for the package should contain:
-
-\code{S3method(unique, uncased)}
-
-\code{exportMethods(unique)}
-
+\preformatted{
+    S3method(unique, uncased)
+    exportMethods(unique)
+}
 The result is to define identical S3 and S4 methods and ensure that all
 calls to \code{unique} will dispatch that method when appropriate.
 }