[latexrefman-commits] [SCM] latexrefman updated: r574 - trunk

[karl at gnu.org.ua]

Author: karl
Date: 2017-08-01 00:50:22 +0300 (Tue, 01 Aug 2017)
New Revision: 574

Modified:
   trunk/latex2e.texi
Log:
latex209 frozen, not retired; clarify usrguide status and \NeedsTeXFormat; typos

Modified: trunk/latex2e.texi
===================================================================
--- trunk/latex2e.texi	2017-07-31 11:12:28 UTC (rev 573)
+++ trunk/latex2e.texi	2017-07-31 21:50:22 UTC (rev 574)
@@ -188,10 +188,7 @@
 @cindex @LaTeX{} vs.@: @LaTeX{}2e
 In this document, we will mostly just use `@LaTeX{}' rather than
 `@LaTeX{}2e', since the previous version of @LaTeX{}@tie{}(2.09) was
- at c xxx vincentb1: is `retired' saracastic, meaning that LaTeX 2.09 after
- at c many years of good services needs some rest now, or is it more
- at c neutral, just a synonym of withdrawn ?
-retired many years ago.
+frozen decades ago.
 
 @cindex unofficial nature of this manual
 @cindex @LaTeX{} Project team
@@ -221,9 +218,9 @@
 
 @item http://ctan.org/pkg/usrguide
 @findex usrguide @r{official documentation}
-The guide for document authors that is maintained as part of @LaTeX{};
- at c xxx vincentb1 What does ``others'' refer to ?
-there are plenty of others available elsewhere.
+The guide for document authors that is maintained as part of @LaTeX{}.
+Many other guides by many other people are also available, independent
+of @LaTeX{} itself; one such is the next item:
 
 @item http://ctan.org/pkg/lshort
 @findex lshort @r{document}
@@ -965,7 +962,7 @@
 
 
 @node Class and package structure
- at subsection  Class and package structure
+ at subsection Class and package structure
 
 @cindex class and package structure
 @cindex class file layout 
@@ -1173,13 +1170,13 @@
 @code{\providerobustcmd}, and @code{\providrobustcmd*} which are similar
 to @code{\newcommand}, @code{\newcommand*}, @code{\renewcommand},
 @code{\renewcommand*}, @code{\providecommand}, and
- at code{\providecommand*}, but define a robust @var{cmd} with two advanges
+ at code{\providecommand*}, but define a robust @var{cmd} with two advantages
 as compared to @code{\DeclareRobustCommand} :
 @enumerate
 @item
-They use a low level e- at TeX{} protection mechanism rather than the
-higher level @LaTeX{} @code{\protect} mechanism, so they do not incurr
-the slight loss of perfomance mentioned above, and
+They use the low-level e- at TeX{} protection mechanism rather than the
+higher level @LaTeX{} @code{\protect} mechanism, so they do not incur
+the slight loss of performance mentioned above, and
 @item
 They make the same distinction between @code{\new at dots{}},
 @code{\renew at dots{}}, and @code{\provide at dots{}}, as the standard
@@ -1248,14 +1245,13 @@
 
 @item \NeedsTeXFormat@{@var{format}@}[@var{format date}]
 @findex \NeedsTeXFormat
-Specifies the format that this class should be run under.  Often issued
+Specifies the format that this class must be run under.  Often issued
 as the first line of a class file, and most often used as:
- at code{\NeedsTeXFormat@{LaTeX2e@}}.  The format that you specify must
-exactly match the one installed on your system that you invoked,
- at c xxx vincentb1 What does ``that you invoked'' mean here ?
-including that the @var{format} string is case sensitive.  If it does
-not match then execution stops with an error like @samp{This file needs
-format `xxx' but this is `LaTeX2e'.}
+ at code{\NeedsTeXFormat@{LaTeX2e@}}.  When a document is processed using
+that class, the format name given here must match the format that is
+actually being run (including that the @var{format} string is case
+sensitive).  If it does not match then execution stops with an error
+like @samp{This file needs format `LaTeX2e' but this is `xxx'.}
 
 To specify a version of the format that you know to have certain
 features, include the optional @var{format date} on which those features
@@ -1263,8 +1259,7 @@
 If the format version installed on your system is earlier than
 @var{format date} then you get a warning like @samp{You have requested
 release `2038/01/20' of LaTeX, but only release `2016/02/01' is
-available.}  (The @LaTeX{} kernel has been frozen for many years so you
-probably do not not need to specify the format date.)
+available.}
 
 @item \OptionNotUsed
 @findex \OptionNotUsed
@@ -2599,7 +2594,7 @@
 unit's title.  This space will be discarded if the sectioning unit
 happens to start at the top of a fresh page.  If this number is negative
 then the first paragraph following the header is not indented, if it is
-nonnegative then the first paragraph is indented.  (Note that the
+non-negative then the first paragraph is indented.  (Note that the
 negative of @code{1pt plus 2pt minus 3pt} is @code{-1pt plus -2pt minus
 -3pt}.)
 
@@ -2621,7 +2616,7 @@
 
 @item afterskip
 @anchor{\@@startsection/afterskip} This is a length.  If @var{afterskip}
-is nonnegative then this is the vertical space inserted after the
+is non-negative then this is the vertical space inserted after the
 sectioning unit's title header.  If it is negative then the title header
 becomes a run-in header, so that it becomes part of the next paragraph.
 In this case the absolute value of the length gives the horizontal space
@@ -2633,7 +2628,7 @@
 @code{minus} components is good practice here since it gives @LaTeX{}
 more flexibility in putting the page together.
 
-If @code{afterskip} is nonnegative then the full accounting of the
+If @code{afterskip} is non-negative then the full accounting of the
 vertical space between the baseline of the sectioning unit's header and
 the baseline of the first line of the following paragraph is that it is
 the sum of the @code{\parskip} of the heading font, the