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

[karl at gnu.org.ua]

Author: karl
Date: 2021-06-05 21:50:20 +0000 (Sat, 05 Jun 2021)
New Revision: 922

Modified:
   trunk/latex2e.texi
Log:
\lineskip index, etc.

Modified: trunk/latex2e.texi
===================================================================
--- trunk/latex2e.texi	2021-06-04 17:09:44 UTC (rev 921)
+++ trunk/latex2e.texi	2021-06-05 21:50:20 UTC (rev 922)
@@ -3030,7 +3030,7 @@
 unit.  So if a document contains this paragraph then its lines will be
 scrunched together, compared to lines in surrounding paragraphs.
 
- at c Adapted from B Beeton's "Lapses in TeX" TB 42,1 p 13.
+ at c Adapted from B Beeton's "Lapses in TeX" TB 42:1 p 13.
 @example
 Many people see a page break between text and a displayed equation as 
 bad style, so in effect the display is part of the paragraph.
@@ -3039,6 +3039,9 @@
 @{\footnotesize $$a+b = c$$@}
 @end example
 
+ at findex \lineskip
+ at findex \lineskiplimit
+ at findex \prevdepth
 The process for making paragraphs is that when a new line is added, if
 the depth of the previous line plus the height of the new line is less
 than @code{\baselineskip} then @TeX{} inserts vertical glue to make up
@@ -3047,14 +3050,15 @@
 then @TeX{} instead uses @code{\lineskip} as the interline glue.  The
 second is that @TeX{} doesn't actually use the depth of the previous
 line.  Instead it uses @code{\prevdepth}, which usually contains that
-depth.  But at the beginning of the paragraph (or any vertical list) or
-just after a rule, @code{\prevdepth} has the value -1000pt and that
-keeps @TeX{} from inserting any interline glue at the paragraph start.
+depth.  But at the beginning of the paragraph (or any vertical list)
+or just after a rule, @code{\prevdepth} has the value -1000pt and this
+special value tells @TeX{} not to insert any interline glue at the
+paragraph start.
 
 In the standard classes @code{\lineskiplimit} is 0pt and
 @code{\lineskip} is 1pt.  By the prior paragraph then, the distance
-between lines can approach zero but if it equals zero then the lines
-jump to 1pt apart.
+between lines can approach zero but if it becomes zero (or less than
+zero) then the lines jump to 1pt apart.
 
 Sometimes authors must, for editing purposes, put the document in double
 space or one-and-a-half space.  The right way to influence the interline
@@ -3075,17 +3079,19 @@
 the start of a document, so there you don't need to follow it with
 @code{\selectfont}.)
 
-A more flexible approach is the @file{setspace} package.  After the
+ at PkgIndex{setspace}
+A simpler approach is the @file{setspace} package.  After the
 @code{\usepackage@{setspace@}}, use @code{\doublespacing}, or
- at code{\onehalfspacing} or one-an-a-half.  In the preamble these will
+ at code{\onehalfspacing} for one-and-a-half.  In the preamble these will
 start the document off with that sizing.  But you can also use these
-declarations in the document body to change the spacing from that point
-forward, and consequently there is @code{\singlespacing} to return the
-spacing to normal.  In the document body, a better practice than using
-the declarations is to use environments, such as
- at code{\begin@{doublespace@} ... \end@{doublespace@}}.  The package also
-has commands to do arbitrary spacing: @code{\setstretch@{@var{factor}@}}
-and @code{\begin@{spacing@}@{@var{factor}@} ... \end@{spacing@}}.
+declarations in the document body to change the spacing from that
+point forward, and consequently there is @code{\singlespacing} to
+return the spacing to normal.  In the document body, a better practice
+than using the declarations is to use environments, such as
+ at code{\begin@{doublespace@} ... \end@{doublespace@}}.  The package
+also has commands to do arbitrary spacing:
+ at code{\setstretch@{@var{factor}@}} and
+ at code{\begin@{spacing@}@{@var{factor}@} ... \end@{spacing@}}.
 
 
 @node Floats
@@ -18288,8 +18294,10 @@
 \usepackage[@var{encoding-name}]@{inputenc@}
 @end example
 
-Declare the input file's text encoding. The default, if this package
-is not loaded, is UTF-8.
+Declare the input file's text encoding to be @var{encoding-name}. The
+default, if this package is not loaded, is UTF-8.  Technically,
+specifying the encoding name is optional, but in practice it is not
+useful to omit it.
 
 @cindex encoding, of input files
 @cindex character encoding