From d8b81c54ee53a93b7f939601fd6438d0f194978b Mon Sep 17 00:00:00 2001
From: Norbert Preining <norbert@preining.info>
Date: Fri, 22 Oct 2021 03:01:42 +0000
Subject: CTAN sync 202110220301

---
 macros/latex-dev/base/ltnews28.tex | 36 +++++++++++++++++++++---------------
 1 file changed, 21 insertions(+), 15 deletions(-)

(limited to 'macros/latex-dev/base/ltnews28.tex')

diff --git a/macros/latex-dev/base/ltnews28.tex b/macros/latex-dev/base/ltnews28.tex
index 59b01ed4fc..03d4a04ae1 100644
--- a/macros/latex-dev/base/ltnews28.tex
+++ b/macros/latex-dev/base/ltnews28.tex
@@ -44,6 +44,12 @@
 
 \publicationissue{28}
 
+\providecommand\pkg[1]{\texttt{#1}}
+\providecommand\cls[1]{\texttt{#1}}
+\providecommand\option[1]{\texttt{#1}}
+\providecommand\env[1]{\texttt{#1}}
+\providecommand\file[1]{\texttt{#1}}
+
 \begin{document}
 
 \maketitle
@@ -125,7 +131,7 @@ the early nineties that \LaTeXe{} (that was being developed to provide
 a \LaTeX{} version usable across the world) had to provide a solution
 to this issue.
 
-The \LaTeXe{} answer was the introduction of the \package{inputenc}
+The \LaTeXe{} answer was the introduction of the \pkg{inputenc}
 package~\cite{Mittelbach:Brno95} through which it is possible to
 provide support for multiple encodings. It also allows to correctly
 process a file written in one encoding on a computer using a different
@@ -135,10 +141,10 @@ midway.
 Since the first release of \LaTeXe{} in 1994, \LaTeX{} documents that
 used any characters outside \acro{ascii} in the source (i.e. any
 characters in the range of 128--255) were supposed to load
-\package{inputenc} and specify in which file encoding they were
+\pkg{inputenc} and specify in which file encoding they were
 written and stored.
 %
-If the \package{inputenc} package was not loaded then \LaTeX{} used a
+If the \pkg{inputenc} package was not loaded then \LaTeX{} used a
 ``raw'' encoding which essentially took each byte from the input file
 and typeset the glyph that happened to be in that position in the
 current font---something that sometimes produces the right result but
@@ -171,7 +177,7 @@ the same as the existing UTF-8 support from
 
 The \hologo{LuaTeX} and \hologo{XeTeX} engines always supported the
 UTF-8 encoding as their native (and only) input encoding, so with
-these engines \package{inputenc} was always a no-op.
+these engines \pkg{inputenc} was always a no-op.
 
 This means that with new documents one can assume UTF-8 input and it
 is no longer required to always specify
@@ -186,14 +192,14 @@ For most existing documents this change will be transparent:
 \item documents using only \acro{ascii} in the input file and
   accessing accented characters via commands;
 \item documents that specified the encoding of their file via an
-  option to the \package{inputenc} package and then used 8-bit
+  option to the \pkg{inputenc} package and then used 8-bit
   characters in that encoding;
 \item documents that already had been stored in UTF-8 (whether or not
-  specifying this via \package{inputenc}).
+  specifying this via \pkg{inputenc}).
 \end{itemize}
 Only documents that have been stored in a legacy encoding and used
 accented letters from the keyboard \emph{without} loading
-\package{inputenc} (relying on the similarities between the input used
+\pkg{inputenc} (relying on the similarities between the input used
 and the T1 font encoding) are affected.
 
 These documents will now generate an error that they contain invalid
@@ -215,12 +221,12 @@ Possible alternatives are reencoding the file to UTF-8 using a tool
 \verb=  \usepackage[=\meta{encoding}\verb=]{inputenc}=
 \end{flushleft}
 to the preamble specifying the \meta{encoding} that fits the file
-encoding.  In many cases this will be \texttt{latin1} or
-\texttt{cp1252}. For other encoding names and their meaning see the
-\package{inputenc} documentation.
+encoding.  In many cases this will be \option{latin1} or
+\option{cp1252}. For other encoding names and their meaning see the
+\pkg{inputenc} documentation.
 
 As usual, this change may also be reverted via the more general
-\package{latexrelease} package mechanism, by speciying a release date
+\pkg{latexrelease} package mechanism, by speciying a release date
 earlier than this release.
 
 
@@ -291,7 +297,7 @@ command being tested being defined if it was previously undefined may have to ad
 \verb|\let\|\meta{command}\verb|\relax|.
 
 
-\section{Changes to packages in the tools category}
+\section{Changes to packages in the \pkg{tools} category}
 
 \subsection{\LaTeX{} table columns with fixed widths}
 
@@ -317,14 +323,14 @@ off-chance that code that hooked into internals of \pkg{multicol}
 needs adjustment.
 
 
-\section{Changes to packages in the amsmath category}
+\section{Changes to packages in the \pkg{amsmath} category}
 
 With this release of \LaTeX{} a few minor issues with \pkg{amsmath}
 have been corrected.
 
 \subsection{Updated user's guide}
 
-Furthermore, \texttt{amsldoc.pdf}, the AMS user's
+Furthermore, \file{amsldoc.pdf}, the AMS user's
 guide for the \pkg{amsmath} package~\cite{amsldoc}, has been updated
 from version~2.0 to~2.1 to incorporate changes and corrections made
 between 2016 and 2018.
@@ -354,7 +360,7 @@ between 2016 and 2018.
   \url{https://www.latex-project.org/publications/}
 
 \bibitem{amsldoc} American Mathematical Society and The \LaTeX\ Project:
-  \emph{User's Guide for the \texttt{amsmath} package} (Version 2.1).
+  \emph{User's Guide for the \pkg{amsmath} package} (Version 2.1).
   April 2018.
   Available from
   \url{https://www.ctan.org}
-- 
cgit v1.2.3

