[latex3-commits] [latex2e-public] r1337 - shock news: barbara found some typos

[noreply at latex-project.org]

Author: carlisle
Date: 2017-01-13 22:23:51 +0100 (Fri, 13 Jan 2017)
New Revision: 1337

Modified:
   trunk/doc/ltnews26.tex
Log:
shock news: barbara found some typos

Modified: trunk/doc/ltnews26.tex
===================================================================
--- trunk/doc/ltnews26.tex	2017-01-13 09:16:14 UTC (rev 1336)
+++ trunk/doc/ltnews26.tex	2017-01-13 21:23:51 UTC (rev 1337)
@@ -34,8 +34,8 @@
 \usepackage[T1]{fontenc}
 
 \usepackage{lmodern,url,hologo}
+\usepackage{hyperref}
 
-
 \publicationmonth{January}
 \publicationyear{2017}
 
@@ -70,7 +70,7 @@
 Practically, modern \TeX{} distributions provide the extensions in all engines
 other than the ``pure'' Knuth \texttt{tex}, and indeed parts of the
 format-building process already require \eTeX{}, most notably some of the UTF-8
-hyphenation patterns. As such, there should be no noticeable affect on users of
+hyphenation patterns. As such, there should be no noticeable effect on users of
 this change.
 
 The team expect to make wider use of \eTeX{} within the kernel in future;
@@ -78,18 +78,18 @@
 
 \section{Default Encodings in \hologo{XeLaTeX} and \hologo{LuaLaTeX}}
 The default encoding in \LaTeX\ has always been the original
-127-character encoding OT1.  For Unicode based \TeX\ engines, this
+128-character encoding \texttt{OT1}.  For Unicode based \TeX\ engines, this
 is not really suitable, and is especially problematic with
 \hologo{XeLaTeX} as in the major distributions this is built with
-Unicode base hyphenation patterns in the format.  In practice this has
+Unicode based hyphenation patterns in the format.  In practice this has
 not been a major problem as documents use the contributed
 \textsf{fontspec} package in order to switch to a
 Unicode encoded font.
 
-In this release we are adding TU as a new supported
-encoding in addition to the previously supported encodings such as OT1
-and T1. This denotes a Unicode based font encoding. It is essentially
-the same as the TU encoding that has been on trial with the
+In this release we are adding \texttt{TU} as a new supported
+encoding in addition to the previously supported encodings such as \texttt{OT1}
+and \texttt{T1}. This denotes a Unicode based font encoding. It is essentially
+the same as the \texttt{TU} encoding that has been on trial with the
 experimental \texttt{tuenc} option to \textsf{fontspec} for the past
 year.
 
@@ -103,21 +103,21 @@
 to recognise the new encoding default arrangements.
 
 Note that in practice no font supports the full Unicode range, and so
-TU encoded fonts, unlike fonts specified for T1, may be expected to be
-incomplete in various ways. In the current release the file
-\texttt{tuenc.def} that implements the TU encoding-specific commands
+\texttt{TU} encoded fonts, unlike fonts specified for \texttt{T1}, may be
+expected to be incomplete in various ways. In the current release the file
+\texttt{tuenc.def} that implements the \texttt{TU} encoding-specific commands
 has made some basic assumptions for (for example) default handling of
 accent commands, and the set of command names is derived from the
-command names used for the UTF-8 support in the inputenc package,
+command names used for the UTF-8 support in the \textsf{inputenc} package,
 restricted roughly to the character ranges classically provided by
-the T1 and TS1 encodings, but is part of a longer term plan seen over
-recent releases to increase support for Unicode based \TeX\ engines into
-the core \LaTeX\ support.
+the \texttt{T1} and \texttt{TS1} encodings, but is part of a longer term plan
+seen over recent releases to increase support for Unicode based \TeX\ engines
+into the core \LaTeX\ support.
 
 
 
 If for any reason you need to process a document with the previous
-default OT1 encoding, you may switch encoding in the usual ways, for
+default \texttt{OT1} encoding, you may switch encoding in the usual ways, for
 example
 \begin{verbatim}
 \usepackage[OT1]{fontenc}
@@ -132,7 +132,7 @@
 Due to the way \hologo{XeLaTeX} interfaces to font libraries, the
 standard definition of \cs{showhyphens} does not work.  A variant
 definition has been available in the contributed \textsf{xltxtra}
-package however a (slightly different) definition for \cs{showhyphens}
+package, however a (slightly different) definition for \cs{showhyphens}
 is now included in \hologo{XeLaTeX} by default. As usual
 this change will be undone if an earlier
 release is specified using the \textsf{latexrelease} package.
@@ -175,19 +175,19 @@
 The \textsf{amsmath} package has two updates at this release.
 \begin{itemize}
 \item The spacing to the left of the \texttt{aligned} and
-  \texttt{gathered} environments has been fixed, the spurious thin
+  \texttt{gathered} environments has been fixed: the spurious thin
   space is no longer added by default. Package options control this
-  to revert to the original behaviour where required, see the
+  to revert to the original behaviour where required; see the
   \textsf{amsldoc} guide for further details. 
 \item The large delimiters around generalised fractions (for example
-  in the \verb|\binom| construct) did not work in previous releases if
-  using Lua\TeX or Xe\TeX\ with OpenType math fonts. This is releated
-  to the lack of specific metrcs for this use in the OpenType Math
-  table. In principle Lua\TeX\ has two additional named metrics
+  in the \cs{binom} construct) did not work in previous releases if
+  using \hologo{LuaTeX} or \hologo{XeTeX} with OpenType math fonts. This is
+  related to the lack of specific metrics for this use in the OpenType Math
+  table. In principle \hologo{LuaTeX} has two additional named metrics
   to control the delimiters but these are not initialised by default,
-  and in Xe\TeX\ it does not seem possible to make them work at all.
+  and in \hologo{XeTeX} it does not seem possible to make them work at all.
   So for Unicode \TeX\ systems, a new implementation of
-  \verb|\genfrac| is used at this release that uses \verb|\left\right|
+  \cs{genfrac} is used at this release that uses \verb|\left\right|
   internally but parameterised to give spacing as close to the
   original as possible. The implementation in (pdf)\TeX\ is
   unaffected.
@@ -196,7 +196,7 @@
 \section{Updates to \textsf{tools}}
 The \textsf{array} package has been updated to fix a longstanding but
 previously unreported issue with unwanted interactions between tables
-in the page head or foot and the body of the page. As reported in
+in the page head or foot and the body of the page, as reported in
 \href{http://www.latex-project.org/cgi-bin/ltxbugs2html?pr=tools/4488}{PR
   tools/4488}.
 
@@ -222,7 +222,7 @@
 Starting with release 2015/01/01 this is now finally corrected already
 in the kernel and not only in \textsf{fixltx2e}.  In nearly all
 circumstances this will either make no difference to existing
-documents or, it will locally impove the visual appearence of that
+documents, or it will locally improve the visual appearence of that
 document without changing anything on other pages.  However, by the
 nature of the change it is also possible that there are further
 non-local changes to the page breaks due to the different break