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

Karl Berry INVALID.NOREPLY at gnu.org.ua
Tue Dec 27 00:41:58 CET 2022


Author: karl
Date: 2022-12-26 23:41:57 +0000 (Mon, 26 Dec 2022)
New Revision: 1140

Modified:
   trunk/ChangeLog
   trunk/NEWS
   trunk/latex2e.texi
Log:
expand on \dots issues; Texinfo 7.0 @microtype on; other

Modified: trunk/ChangeLog
===================================================================
--- trunk/ChangeLog	2022-11-19 21:47:20 UTC (rev 1139)
+++ trunk/ChangeLog	2022-12-26 23:41:57 UTC (rev 1140)
@@ -1,3 +1,10 @@
+2022-12-26  Karl Berry  <karl at freefriends.org>
+
+	* latex2e.texi (Dots): say more about amsmath's overwriting of the
+	kernel's \dots, and about Unicode vs. traditional output.
+	(@microtype on): use this, per Texinfo 7.0.
+	(thoughout): avoid some use of "very", fix under/overfull boxes.
+
 2022-11-19  Karl Berry  <karl at freefriends.org>
 
 	* latex2e.texi (\frame): "is put" typo, from Pieter van Oostrum.

Modified: trunk/NEWS
===================================================================
--- trunk/NEWS	2022-11-19 21:47:20 UTC (rev 1139)
+++ trunk/NEWS	2022-12-26 23:41:57 UTC (rev 1140)
@@ -15,7 +15,13 @@
 * description of definition and use of optional arguments somewhat clarified.
 * \texttt{\textbackslash} (and \textbraceleft and \textbraceright)
 require T1 or other non-default encoding to produce typewriter characters.
+* \dots description extended, with more about the amsmath redefinition,
+and Unicode vs. traditional typesetting.
 
+Formatting:
+* For the TeX output, enable microtype, since Texinfo now supports it.
+
+
 
 Notable changes in January 2022 release:
 
 New sections:

Modified: trunk/latex2e.texi
===================================================================
--- trunk/latex2e.texi	2022-11-19 21:47:20 UTC (rev 1139)
+++ trunk/latex2e.texi	2022-12-26 23:41:57 UTC (rev 1140)
@@ -2,7 +2,7 @@
 @c $Id$
 @comment %**start of header (This is for running Texinfo on a region.)
 @setfilename latex2e.info
- at set UPDATED September 2022
+ at set UPDATED December 2022
 @include common.texi
 @settitle @LaTeX{}2e unofficial reference manual (@value{UPDATED})
 @comment %**end of header (This is for running Texinfo on a region.)
@@ -21,6 +21,7 @@
 @c xx check recent ltnews for (lots of) changes
 @c xx \write of non-ASCII chars (vincent mail of 14 Mar 2020 21:39:41)
 @c xx \nonstopmode etc., if they are officially supported by LaTeX?
+ at c xx LaTeX defines \do at \begin{document} even though it is not documented
 @c xx JH explain nfss somewhere
 @c xx JH expand BiBTeX
 @c xx JH expand theorem, AMS math
@@ -93,6 +94,8 @@
 \global\hbadness=4444 % don't complain much
 @end tex
 
+ at microtype on
+
 @html
 <div class='intro'> <p>This is an unofficial reference manual for
 LaTeX.  See below for the <a href='#SEC_Overview'>Table of Contents</a>. 
@@ -3082,24 +3085,25 @@
 between lines can approach zero but if it becomes zero (or less than
 zero) then the lines jump to 1 at dmn{pt} 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
-distance is via @code{\baselinestretch}.  It scales
- at code{\baselineskip}, and has a default value of 1.0.  It is a command,
-not a length, so change the scale factor as in
+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 distance is via @code{\baselinestretch}.  It scales
+ at code{\baselineskip}, and has a default value of 1.0.  It is a
+command, not a length, and does not take effect until a font change
+happens, so set the scale factor like this:
 @code{\renewcommand@{\baselinestretch@}@{1.5@}\selectfont}.
 
 The most straightforward way to change the line spacing for an entire
 document is to put @code{\linespread@{@var{factor}@}} in the preamble.
 For double spacing, take @var{factor} to be 1.6 and for one-and-a-half
-spacing use 1.3.  These number are rough: for instance, since the
+spacing use 1.3.  These numbers are rough: for instance, since the
 @code{\baselineskip} is about 1.2 times the font size, multiplying by
 1.6 gives a baseline skip to font size ratio of about 2.  (The
 @code{\linespread} command is defined as
- at code{\renewcommand@{\baselinestretch@}@{@var{factor}@}} so it won't
-take effect until a font setting happens. But that always takes place at
-the start of a document, so there you don't need to follow it with
- at code{\selectfont}.)
+ at code{\renewcommand@{\baselinestretch@}@{@var{factor}@}} so it also
+won't take effect until a font setting happens. But that always takes
+place at the start of a document, so there you don't need to follow it
+with @code{\selectfont}.)
 
 @PkgIndex{setspace}
 A simpler approach is the @package{setspace} package.  The basic example:
@@ -3501,9 +3505,10 @@
 
 @PkgIndex{titlesec}
 @LaTeX{} lets you change the appearance of the sectional units.  As a
-simple example, you can change the section numbering to upper-case
-letters with @code{\renewcommand\thesection@{\Alph@{section@}@}} in the
-preamble (@pxref{\alph \Alph \arabic \roman \Roman \fnsymbol}).  CTAN
+simple example, you can change the section numbering to uppercase
+letters with this (in the preamble):@*
+ at code{\renewcommand\thesection@{\Alph@{section@}@}} .
+(@xref{\alph \Alph \arabic \roman \Roman \fnsymbol}.)  CTAN
 has many packages that make this adjustment easier, notably
 @package{titlesec}.
 
@@ -5609,10 +5614,10 @@
 scope of the declaration must contain the blank line or @code{\end}
 command that ends the paragraph unit.
 
-Here @code{\raggedright} in each second column keeps @LaTeX{} from doing
-very awkward typesetting to fit the text into the narrow column.  Note
-that @code{\raggedright} is inside the curly braces @code{@{...@}} to
-delimit its effect.
+Here @code{\raggedright} in each second column keeps @LaTeX{} from
+doing awkward typesetting to fit the text into the narrow column.
+Note that @code{\raggedright} is inside the curly braces
+ at code{@{...@}} to delimit its effect.
 
 @example
 \begin@{tabular@}@{rp@{2in@}@}
@@ -8802,10 +8807,10 @@
 better fit.
 
 The @code{\-} command only allows @LaTeX{} to break there, it does not
-require that it break there.  You can force a split with something like
- at code{Hef-\linebreak feron}.  Of course, if you later change the text
-then this forced break may look very odd, so this approach requires
-care.
+require that it break there.  You can force a split with something
+like @code{Hef-\linebreak feron}.  Of course, if you later change the
+text then this forced break may look out of place, so this approach
+requires care.
 
 
 @node \discretionary
@@ -10749,7 +10754,7 @@
 @code{\ } for this.  @xref{\(SPACE)}.)
 
 The @package{xspace} package provides @code{\xspace}.  It is for writing
-commands which are designed to be used mainly in text.  It must be place
+commands which are designed to be used mainly in text.  It must be placed
 at the very end of the definition of these commands. It inserts a space
 after that command unless what immediately follows is in a list of
 exceptions.  In this example, the empty braces are not needed.
@@ -13717,14 +13722,15 @@
 
 @anchor{ellipses ldots}
 @item \ldots
+ at itemx \mathellipsis
+ at itemx \dots
 Ellipsis on the baseline, @BES{2026,\ldots}.  Used as: @code{\(
-x_0,\ldots x_@{n-1@} \)}.  Another example is the above array example. A
-synonym is @code{\mathellipsis}.  A synonym from the @package{amsmath}
-package is @code{\hdots}.
+x_0,\ldots x_@{n-1@} \)}.  Another example is the above array example.
+Synonyms are @code{\mathellipsis} and @code{\dots}.  A synonym from
+the @package{amsmath} package is @code{\hdots}.
 
 You can also use this command outside of mathematical text, as in
- at code{The gears, brakes, \ldots@{@} are all broken}.  (In a paragraph
-mode or LR mode a synonym for @code{\ldots} is @code{\dots}.)
+ at code{The gears, brakes, \ldots@{@} are all broken}.
 
 @anchor{ellipses vdots}
 @item \vdots
@@ -13747,6 +13753,10 @@
 Conclusion: there are infinitely many primes \( p_0, p_1, \dotsc \).
 @end example
 
+ at findex \dotsc
+ at findex \dotsb
+ at findex \dotsi
+ at findex \dots
 @noindent
 In the first line @LaTeX{} looks to the comma following @code{\dots} to
 determine that it should output an ellipsis on the baseline.  The second
@@ -13759,7 +13769,26 @@
 or relation symbol, @code{\dotsi} for dots with integrals, or
 @code{\dotso} for others.
 
+ at PkgIndex{unicode-math} The @code{\dots} command from
+ at package{amsmath} differs from the @LaTeX{} kernel's @code{\dots}
+command in another way: it outputs a thin space after the
+ellipsis. Furthermore, the @package{unicode-math} package
+automatically loads @package{amsmath}, so @package{amsmath}'s
+ at code{\dots} may be active even when you did not explicitly load it,
+thus changing the output from @code{\dots} in both text and math mode.
 
+ at cindex ellipsis, in Unicode (U+2026)
+ at cindex ellipsis, traditional (three periods)
+Yet more about the ellipsis commands: when running under Unicode
+engines (@code{lualatex}, @code{xelatex}), @LaTeX{} will use the
+Unicode ellipsis character (U+2026) in the font if it's available;
+under traditional @TeX{} engines (@code{pdflatex}, @code{latex}), it
+will typeset three spaced periods. Generally, the Unicode
+single-character ellipsis has almost no space between the three
+periods, while the spacing of the non-Unicode ellipsis is looser, more
+in accordance with traditional typography.
+
+
 @node Greek letters
 @subsection Greek letters
 
@@ -14827,7 +14856,7 @@
 in paragraph mode, in LR mode @LaTeX{} never starts a new line, it just
 keeps going from left to right.  (Although @LaTeX{} will not complain
 that the LR box is too long, when it is finished and next tries to put
-that box into a line, it could very well complain that the finished LR
+that box into a line, it might well complain that the finished LR
 box won't fit there.)
 
 @item
@@ -14923,8 +14952,8 @@
 the first page of an article.
 
 @PkgIndex{fancyhdr}
-The package @package{fancyhdr} is very helpful for constructing page
-styles.  See its documentation on CTAN.
+The package @package{fancyhdr} is commonly used for constructing page
+styles.  See its documentation.
 
 @menu
 * \maketitle::          Generate a title page.
@@ -16410,9 +16439,10 @@
 The soviet tank \mbox@{T-34@} is a symbol of victory against nazism.
 @end example
 
-The first two command synopsis versions, @code{\mbox} and @code{\makebox}, are
-roughly equivalent.  They create a box just wide enough to contain the
- at var{text}.  (They are like plain @TeX{}'s @code{\hbox}.)
+The first two command invocations shown, @code{\mbox} and
+ at code{\makebox}, are roughly the same.  They create a box just wide
+enough to contain the @var{text}.  (They are like plain @TeX{}'s
+ at code{\hbox}.)
 
 In the third version the optional argument @var{width} specifies the
 width of the box.  Note that the space occupied by the text need not
@@ -16768,13 +16798,13 @@
 @code{\newcommand} macro variable is efficiency, that @LaTeX{} need not
 repeatedly retypeset the contents.  See the example below.
 
-The first two command invocations,
+The first two command invocations shown above,
 @code{\sbox@{@var{box-cmd}@}@{@var{text}@}} and
- at code{\savebox@{@var{box-cmd}@}@{@var{text}@}}, are roughly equivalent.
-As to the third and fourth, the optional arguments allow you to specify
-the box width as @var{width}, and the position of the text inside that
-box as @var{position}.  @xref{\mbox & \makebox}, for the full
-description.
+ at code{\savebox@{@var{box-cmd}@}@{@var{text}@}}, are roughly the same.
+As to the third and fourth, the optional arguments allow you to
+specify the box width as @var{width}, and the position of the text
+inside that box as @var{position}.  @xref{\mbox & \makebox}, for the
+full description.
 
 In the @code{\sbox} and @code{\savebox} commands the @var{text} is
 typeset in LR mode so it does not have line breaks (@pxref{Modes}).  If
@@ -17606,9 +17636,8 @@
 other format is available.)
 
 @item command
-A command that will be applied to the
-file. This is very often left empty. This command must start with a
-single backward quote.  Thus,
+A command that will be applied to the file. This is often left
+empty. This command must start with a single backward quote.  Thus,
 @code{\DeclareGraphicsRule@{.eps.gz@}@{eps@}@{.eps.bb@}@{`gunzip -c
 #1@}} specifies that any file with the extension @file{.eps.gz} should
 be treated as an @code{eps} file, with the BoundingBox information
@@ -18435,11 +18464,12 @@
 Double and single angle quotation marks, commonly used in French.
 
 @item \ldots
+ at itemx \textellipsis
 @itemx \dots
- at itemx \textellipsis
 @cindex ellipsis
- at dots{}  An ellipsis (three dots at the baseline):  @code{\ldots}
-and @code{\dots} also work in math mode.
+ at dots{} An ellipsis (three dots at the baseline): @code{\ldots} and
+ at code{\dots} also work in math mode (@pxref{Dots}).  See that math
+mode ellipsis description for additional general information.
 
 @item \lq
 @cindex left quote



More information about the latexrefman-commits mailing list.