summaryrefslogtreecommitdiff
path: root/macros/latex/base/latexrelease.dtx
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2020-02-03 03:02:01 +0000
committerNorbert Preining <norbert@preining.info>2020-02-03 03:02:01 +0000
commit34897eebd22c3de968b64f09bb4a371d96cb0b89 (patch)
tree19a50e54fca63f1f6482d6cb4c2fdee676fd97b1 /macros/latex/base/latexrelease.dtx
parente05dc0bb38b16bfb9ba35591285e40af0adaadc4 (diff)
CTAN sync 202002030302
Diffstat (limited to 'macros/latex/base/latexrelease.dtx')
-rw-r--r--macros/latex/base/latexrelease.dtx26
1 files changed, 13 insertions, 13 deletions
diff --git a/macros/latex/base/latexrelease.dtx b/macros/latex/base/latexrelease.dtx
index cfb1bff8aa..5ee39a3a2d 100644
--- a/macros/latex/base/latexrelease.dtx
+++ b/macros/latex/base/latexrelease.dtx
@@ -1,6 +1,6 @@
% \iffalse meta-comment
%
-% Copyright (C) 1993-2019
+% Copyright (C) 1993-2020
% The LaTeX3 Project and any individual authors listed elsewhere
% in this file.
%
@@ -30,7 +30,7 @@
% \iffalse
%
%<*dtx>
- \def\latexreleaseversion{<date only known in .sty file>}
+ \def\latexreleaseversion{<date only known in .sty file>}
\ProvidesFile{latexrelease.dtx}
%</dtx>
%<driver>\ProvidesFile{latexrelease.drv}
@@ -83,7 +83,7 @@
% explicitly opt-in to bug fixes and improvements, and the vast
% majority of documents did not benefit.
%
-% As described in \LaTeX\ News 22, a new policy is being implemented
+% As described in \LaTeX\ News 22, a new policy is being implemented
% in which improvements will now be added to the format by default,
% and this \Lpack{latexrelease} package may be used to ensure
% stability where needed, either by making a new format use an older
@@ -108,7 +108,7 @@
% the commands defined here to adjust their definitions to the
% specified date as described below.
%
-% Note that the \Lpack{latexrelease} package is intended for use
+% Note that the \Lpack{latexrelease} package is intended for use
% at the start of a \emph{document}. Package and class code should not
% include this package as loading a package should not normally globally
% reset the effective version of \LaTeX\ that is in force, so affecting all
@@ -126,8 +126,8 @@
% \item \emph{yyyy/mm/dd} or \emph{yyyy-nn-dd}
% The package accepts any possible \LaTeX\ format date as argument,
% although dates in the future for which the current release of this
-% package has no information will generate a warning. Dates
-% earlier than 2015 will work but will roll back to some point in 2015
+% package has no information will generate a warning. Dates
+% earlier than 2015 will work but will roll back to some point in 2015
% when the method was introduced.
% |\IncludeInRelease| command is defined.
% The |\requestedLaTeXdate| is set to the normalized date argument
@@ -176,7 +176,7 @@
% \item[\marg{code-date}] This date is associated with the \marg{code}
% argument and will be compared to the requested date in the option to
% the \Lpack{latexrelease}.
-%
+%
% \item[\oarg{format-date}] This optional argument can be used to
% specify a format date with the code in addition to the mandatory
% \marg{code-date} argument. This can be useful for package developers
@@ -268,11 +268,11 @@
%\end{verbatim}
%
% To use the latest version, however it would have disadvantage that
-% until the next release of \LaTeX, by default, if the document does
+% until the next release of \LaTeX, by default, if the document does
% not use \Lpack{latexrelease} to specify a date, the new improved
% code will not be selected as the effective date will be 2015/01/01
% and so the first code block will be skipped.
-%
+%
% For this reason |\IncludeInRelease| has an optional argument that
% specifies an alternative date to use if a date option has not been
% specified to \Lpack{latexrelease}.
@@ -297,7 +297,7 @@
% skipped.
%
% If on the other hand the document requests an explicit release date
-% using \Lpack{latexrelease} then this date will be used to decide what
+% using \Lpack{latexrelease} then this date will be used to decide what
% code block to include.
%
% \subsection{Using \cs{IncludeInRelease} in Packages}
@@ -317,7 +317,7 @@
%
% To avoid this issue you can use the following coding
% strategy: place the current |\widget| definition in the main code
-% where it correctly belongs.
+% where it correctly belongs.
% \begin{verbatim}
% ...
% \def\widget {even newer improved March version}
@@ -366,7 +366,7 @@
% \section{fixltx2e}
%
% As noted above, prior to the 2015 \LaTeX\ release updates to the
-% \LaTeX\ kernel were not made in the format source files but were
+% \LaTeX\ kernel were not made in the format source files but were
% made available in the \Lpack{fixltx2e} package. That package is no
% longer needed but we generate a small package from this source
% that just makes a warning message but otherwise does nothing.
@@ -487,7 +487,7 @@ of this package available from CTAN}
%
% The code for each change will be inserted at this point, extracted
% from the kernel source files.
-%
+%
% \begin{macrocode}
%</latexrelease>
% \end{macrocode}