[latex3-commits] [latex2e-public] r1349 - more edits from Karl

noreply at latex-project.org noreply at latex-project.org
Mon Jan 23 22:04:26 CET 2017

Author: carlisle
Date: 2017-01-23 22:04:26 +0100 (Mon, 23 Jan 2017)
New Revision: 1349

more edits from Karl

Modified: trunk/doc/ltnews26.tex
--- trunk/doc/ltnews26.tex	2017-01-23 12:05:02 UTC (rev 1348)
+++ trunk/doc/ltnews26.tex	2017-01-23 21:04:26 UTC (rev 1349)
@@ -75,7 +75,7 @@
 The team expect to make wider use of \eTeX{} within the kernel in future;
 details will be announced where they impact on end users in a visible way.
-\section{Default Encodings in \hologo{XeLaTeX} and \hologo{LuaLaTeX}}
+\section{Default encodings in \hologo{XeLaTeX} and \hologo{LuaLaTeX}}
 The default encoding in \LaTeX\ has always been the original
 128-character encoding \texttt{OT1}.  For Unicode based \TeX\ engines, this
 is not really suitable, and is especially problematic with
@@ -136,18 +136,18 @@
 this change will be undone if an earlier
 release is specified using the \textsf{latexrelease} package.
-\section{The \textsf{fixltx2e} Package}
+\section{The \textsf{fixltx2e} package}
 As described in \LaTeX{} News~22, the \textsf{fixltx2e} package has become
 obsolete with the new update policy. Since 2015 it has just made a
 warning and exited.  In this release we have re-introduced all
 the code from the original fixes in the 2014 \LaTeX\ but guarded by
-So for current releases \textsf{fixltx2e} still just makes a warning
+So for current releases \textsf{fixltx2e} still just displays a warning
 but for old releases, whether that is an old format, or a format with
 the version date reset via  the \textsf{latexrelease} package, the
 fixes in the original \textsf{fixltx2e} will be applied.
-This improves the ability to run old documents in a way compatible
+This improves the ability to run old documents in a way that is compatible
 with contemporary formats. If you have a 2014 document that used
 \verb|\usepackage{fixltx2e}| and you add
 \verb|\RequirePackage[2014/01/01]{latexrelease}| and process it with the
@@ -166,7 +166,7 @@
 This is being published separately to CTAN at the same time as this
 release. By using the \textsf{latexbug} package you can easily check
 that the packages involved in the test are all part of the core
-release. The \LaTeX\ project can not handle bug reports on contributed
+release. The \LaTeX\ project cannot handle bug reports on contributed
 packages, which should be directed to the package maintainer as given
 in the package documentation.
@@ -200,7 +200,7 @@
 There is also an update to the \hologo{LuaTeX} support in \textsf{bm}.
-\section{An addendum to the release changes in 2015}
+\section{An addendum to the release changes in 2015:  page breaks and vertical spacing}
 In 2015 we announced the introduction of the roll-back\slash
 roll-forward concept to manage bug fixes and additions to core

More information about the latex3-commits mailing list