[latex3-commits] [git/LaTeX3-latex3-latex2e] develop: Update latexrelease.dtx, ltfssaxes.dtx, and 3 more files... to remove typos found in #428, #429 (dfa1c53b)
Johannes Braams
texniek at braams.xs4all.nl
Sun Dec 6 15:09:32 CET 2020
Repository : https://github.com/latex3/latex2e
On branch : develop
Link : https://github.com/latex3/latex2e/commit/dfa1c53bb7162e09db1c538faf8cee93cd9bba02
>---------------------------------------------------------------
commit dfa1c53bb7162e09db1c538faf8cee93cd9bba02
Author: Johannes Braams <texniek at braams.xs4all.nl>
Date: Sun Dec 6 15:09:32 2020 +0100
Update latexrelease.dtx, ltfssaxes.dtx, and 3 more files... to remove typos found in #428, #429
>---------------------------------------------------------------
dfa1c53bb7162e09db1c538faf8cee93cd9bba02
base/latexrelease.dtx | 6 +++---
base/ltfssaxes.dtx | 16 ++++++++--------
base/lthooks.dtx | 14 +++++++-------
base/ltluatex.dtx | 20 ++++++++++----------
base/ltoutput.dtx | 18 +++++++++---------
5 files changed, 37 insertions(+), 37 deletions(-)
diff --git a/base/latexrelease.dtx b/base/latexrelease.dtx
index 5ee39a3a..812d8f9c 100644
--- a/base/latexrelease.dtx
+++ b/base/latexrelease.dtx
@@ -40,7 +40,7 @@
%<*!fixltx2e>
% \fi
% \ProvidesFile{latexrelease.dtx}
- [2018/05/08 v1.0k LaTeX release emulation and tests
+ [2020/12/06 v1.0k LaTeX release emulation and tests
(including releases up to \latexreleaseversion)]
% \iffalse
%</!fixltx2e>
@@ -345,7 +345,7 @@
%
% Now if you make a further change to |\widget| in the future you
% simply copy the current definition into the empty block and add a new
-% empty declaration with todays date and the current format date. This
+% empty declaration with today's date and the current format date. This
% way your main code stays readable and the old versions accumulate at
% the end of the package.\footnote{Of course there may be some cases
% in which the old code has to be in a specific place within the
@@ -396,7 +396,7 @@
% \end{macro}
%
% \changes{v1.0c}{2015/02/19}{Swap argument order}
-% \changes{v1.0k}{2018/05/08}{reset \cs{\requestedLaTeXdate} for current and latest options, gitub issue 43}
+% \changes{v1.0k}{2018/05/08}{reset \cs{\requestedLaTeXdate} for current and latest options, github issue 43}
% \begin{macrocode}
\DeclareOption*{%
\def\@IncludeInRelease#1[#2]{\@IncludeInRele at se{#1}}%
diff --git a/base/ltfssaxes.dtx b/base/ltfssaxes.dtx
index d8e4286b..e8d6e9c4 100644
--- a/base/ltfssaxes.dtx
+++ b/base/ltfssaxes.dtx
@@ -35,7 +35,7 @@
%
%
\ProvidesFile{ltfssaxes.dtx}
- [2020/08/21 v1.0g LaTeX Kernel (NFSS Axes handing)]
+ [2020/12/06 v1.0g LaTeX Kernel (NFSS Axes handing)]
% \iffalse
\documentclass{ltxdoc}
\begin{document}
@@ -168,13 +168,13 @@
% request (i.e., second argument).
%
% In particular this is also true for cases involving \texttt{m},
-% e.g., \texttt{bm} (bold medium width) which automatially gets
+% e.g., \texttt{bm} (bold medium width) which automatically gets
% reduced result in \texttt{b} or \texttt{mc} (medium weight
% condensed) which becomes \texttt{c} as a result.
%
% \item
%
-% Only a few entries have ``alterative'' values and perhaps most of
+% Only a few entries have ``alternative'' values and perhaps most of
% them should get dropped. Or maybe not \ldots{} needs some thought
% perhaps.
%
@@ -183,7 +183,7 @@
% to stay with \texttt{b} when a change to \texttt{c} is requested
% and \texttt{bc} doesn't exist, than to go to first change the
% shape to \texttt{n} and then find that \texttt{bc/n} doesn't
-% exist either and thus ending up wth \texttt{m/n}.
+% exist either and thus ending up with \texttt{m/n}.
%
% \item
%
@@ -707,7 +707,7 @@
%
% \begin{macro}{\fontseries}
% The \cs{fontseries} command takes one argument which is the requested new
-% font series. In the orginal implementation it simply saved the
+% font series. In the original implementation it simply saved the
% expanded value in \cs{f at series}. Now we do a bit more processing
% and look up the final value in the font series data base. This is
% done by \cs{merge at font@series}.
@@ -845,7 +845,7 @@
% \end{macrocode}
% We need to \cs{edef} the argument first in case it starts with a
% conditional. Then we check (and perhaps drop) an ``m'' from the
-% value andassign the result to \cs{f at series}.
+% value and assign the result to \cs{f at series}.
% \changes{v1.0d}{2020/02/27}{Drop ``m'' only in a specific set of values (gh/293)}
% \begin{macrocode}
\edef\f at series{#1}%
@@ -1080,7 +1080,7 @@
% \texttt{n}. This is the way \texttt{fontspec} implemented its
% version on this interface, so this rule means we are also
% compatible with the way \texttt{fontspec} behaved. Still it
-% remains an odditywhic I would rather liked to have avoided.
+% remains an oddity which I would rather liked to have avoided.
% \begin{macrocode}
%\DeclareFontShapeChangeRule {sc}{up} {sc} {}
\DeclareFontShapeChangeRule {sc}{up} {n} {}
@@ -1100,7 +1100,7 @@
% \texttt{ulc} in \cs{f at series} which most certainly doesn't
% exist. So when a font is later selected that would result in a
% substitution (so no harm done really). Alternatively, we could in
-% this case use \texttt{n} as aternative, which may be a bit
+% this case use \texttt{n} as alternative, which may be a bit
% faster, but such a setup would be so weird in the first place
% that this isn't worth the effort.
%
diff --git a/base/lthooks.dtx b/base/lthooks.dtx
index e4ff7dd2..fe687ffd 100644
--- a/base/lthooks.dtx
+++ b/base/lthooks.dtx
@@ -32,7 +32,7 @@
%
% \begin{macrocode}
\def\lthooksversion{v1.0e}
-\def\lthooksdate{2020/10/23}
+\def\lthooksdate{2020/12/06}
% \end{macrocode}
%
%<*driver>
@@ -519,7 +519,7 @@
% There can only be a single relation between two labels for a
% given hook,
% i.e., a later \cs{DeclareHookrule} overwrites any previous
-% delcaration.
+% declaration.
%
% The \meta{hook} and \meta{label} can be specified using the
% dot-syntax to denote the current package name.
@@ -715,7 +715,7 @@
% \meta{label-2}, in that order, as detailed in \cs{DeclareHookRule}.
% If the relation is \texttt{default} it means that that rule applies
% to \meta{label-1} and \meta{label-2} in \emph{all} hooks, (unless
-% overrided by a non-default relation).
+% overridden by a non-default relation).
%
% Finally, line~12 lists the labels in the hook after sorting;
% that is, in the order they will be executed when the hook is used.
@@ -1250,7 +1250,7 @@
%
% The few hooks that existed previously in \LaTeXe{} used internally
% commands such as \cs{@begindocumenthook} and packages sometimes
-% augemented them directly rather than working through
+% augmented them directly rather than working through
% \cs{AtBeginDocumement}. For that reason there is currently support
% for this, that is, if the system detects that such an internal
% legacy hook command contains code it adds it to the new hook
@@ -1516,7 +1516,7 @@
%
%
% It is in also possible to use the generic \hook{env/document/end}
-% hook which is execuded by \cs{end}, i.e., just in front of the
+% hook which is executed by \cs{end}, i.e., just in front of the
% first hook above. Note however that the other generic \cs{end}
% environment hook, i.e., \hook{env/document/after} will never get
% executed, because by that time \LaTeX{} has finished the document
@@ -2071,7 +2071,7 @@
% \end{macro}
%
% \begin{macro}[EXP]{\@@_make_name:n,\@@_make_name:w}
-% Provides a standard sanitisation of a hook's name.
+% Provides a standard sanitization of a hook's name.
% It uses \cs{cs:w} to build a control sequence out of the hook name,
% then uses \cs{cs_to_str:N} to get the string representation of that,
% without the escape character. \cs{cs:w}-based expansion is used
@@ -4059,7 +4059,7 @@
% just make them do nothing which may or may not work depending on
% the code usage.
% \changes{v1.0d}{2020/10/04}{Definition \cs{AddToHookNext} was supposed
-% to be for \cs{AddToHook} vize versa (gh/401)}
+% to be for \cs{AddToHook} vice versa (gh/401)}
% \begin{macrocode}
%</2ekernel|latexrelease>
%<latexrelease>\EndIncludeInRelease
diff --git a/base/ltluatex.dtx b/base/ltluatex.dtx
index 8573b3e6..1bcc8df1 100644
--- a/base/ltluatex.dtx
+++ b/base/ltluatex.dtx
@@ -28,7 +28,7 @@
\ProvidesFile{ltluatex.dtx}
%</driver>
%<*tex>
-[2020/09/25 v1.1s
+[2020/12/06 v1.1s
%</tex>
%<plain> LuaTeX support for plain TeX (core)
%<*tex>
@@ -129,7 +129,7 @@
% \DescribeMacro{\newluachunkname}
% |newluachunkname{|\meta{chunkname}|}|\\
% Allocates a number for Lua chunk register, indexed from~$1$.
-% Also enters the name of the regiser (without backslash) into the
+% Also enters the name of the register (without backslash) into the
% \verb|lua.name| table to be used in stack traces.
%
% \noindent
@@ -582,7 +582,7 @@
% \changes{v1.0a}{2015/09/24}{Macro added}
% Category code tables are allocated with a limit half of that used by Lua\TeX{}
% for everything else. At the end of allocation there needs to be an
-% initialisation step. Table~$0$ is already taken (it's the global one for
+% initialization step. Table~$0$ is already taken (it's the global one for
% current use) so the allocation starts at~$1$.
% \begin{macrocode}
\ifx\e at alloc@ccodetable at count\@undefined
@@ -779,8 +779,8 @@
% \subsection{Lua loader}
% \changes{v1.1r}{2020/08/10}{Load ltluatex Lua module during format building}
%
-% Lua code loaded in the format often has to to be loaded again at the
-% beginning of every job, so we define a helper whch allows us to avoid
+% Lua code loaded in the format often has to be loaded again at the
+% beginning of every job, so we define a helper which allows us to avoid
% duplicated code:
%
% \begin{macrocode}
@@ -1113,7 +1113,7 @@ luatexbase.registernumber = registernumber
%
% \begin{macro}{new_attribute}
% \changes{v1.0a}{2015/09/24}{Function added}
-% \changes{v1.1c}{2017/02/18}{Parameterise count used in tracking}
+% \changes{v1.1c}{2017/02/18}{Parameterize count used in tracking}
% As attributes are used for Lua manipulations its useful to be able
% to assign from this end.
% \begin{macrocode}
@@ -1148,7 +1148,7 @@ luatexbase.new_attribute = new_attribute
% \subsection{Custom whatsit allocation}
%
% \begin{macro}{new_whatsit}
-% \changes{v1.1c}{2017/02/18}{Parameterise count used in tracking}
+% \changes{v1.1c}{2017/02/18}{Parameterize count used in tracking}
% Much the same as for attribute allocation in Lua.
% \begin{macrocode}
local whatsit_count_name = whatsit_count_name or "e at alloc@whatsit at count"
@@ -1169,7 +1169,7 @@ luatexbase.new_whatsit = new_whatsit
% \subsection{Bytecode register allocation}
%
% \begin{macro}{new_bytecode}
-% \changes{v1.1c}{2017/02/18}{Parameterise count used in tracking}
+% \changes{v1.1c}{2017/02/18}{Parameterize count used in tracking}
% Much the same as for attribute allocation in Lua.
% The optional \meta{name} argument is used in the log if given.
% \begin{macrocode}
@@ -1192,7 +1192,7 @@ luatexbase.new_bytecode = new_bytecode
% \subsection{Lua chunk name allocation}
%
% \begin{macro}{new_chunkname}
-% \changes{v1.1c}{2017/02/18}{Parameterise count used in tracking}
+% \changes{v1.1c}{2017/02/18}{Parameterize count used in tracking}
% As for bytecode registers but also store the name in the
% |lua.name| table.
% \begin{macrocode}
@@ -1735,7 +1735,7 @@ luatexbase.add_to_callback = add_to_callback
%
% \begin{macro}{remove_from_callback}
% \changes{v1.0a}{2015/09/24}{Function added}
-% \changes{v1.0k}{2015/12/02}{adjust initialisation of cb local (PHG)}
+% \changes{v1.0k}{2015/12/02}{adjust initialization of cb local (PHG)}
% \changes{v1.0k}{2015/12/02}{Give more specific error messages (PHG)}
% \changes{v1.1m}{2020/03/07}{Do not call callback.register for user-defined callbacks}
% Remove a function from a callback. First check arguments.
diff --git a/base/ltoutput.dtx b/base/ltoutput.dtx
index 35d049b9..f8aef498 100644
--- a/base/ltoutput.dtx
+++ b/base/ltoutput.dtx
@@ -37,7 +37,7 @@
%<*driver>
% \fi
\ProvidesFile{ltoutput.dtx}
- [2020/08/21 v1.4f LaTeX Kernel (Output Routine)]
+ [2020/12/06 v1.4f LaTeX Kernel (Output Routine)]
% \iffalse
\documentclass{ltxdoc}
\GetFileInfo{ltoutput.dtx}
@@ -1676,7 +1676,7 @@
% \begin{macro}{\@makecol}
% \changes{v0.1c}{1993/11/23}{Command changed}
% \changes{v1.0b}{1993/11/29}{\cs{@makespecialcolbox} added}
-% We must rewrite this macro to alllow for variations in page-makeup
+% We must rewrite this macro to allow for variations in page-makeup
% required by changes in page-length.
%
% This uses a different macro if a special-length column is being
@@ -1860,7 +1860,7 @@
% force the shortest possible column with the possibility of an
% overfull box.
%
-% This should work for bothe flush- and ragged-bottom setting since
+% This should work for both flush- and ragged-bottom setting since
% it makes the contents no smaller than the size (|\@colht|) of the
% box into which they are put.
%
@@ -2074,7 +2074,7 @@
% \end{macrocode}
%
% The |\catcode`\ = 10| was removed as it was considered useless
-% (presumably because nothing gets tokenised during shipout).
+% (presumably because nothing gets tokenized during shipout).
%
% This was put in as some error produced active spaces in a mark, I
% think.
@@ -2156,7 +2156,7 @@
%
% The rest was always inside the box.
%
-% RmS 91/08/15: aded this line:
+% RmS 91/08/15: added this line:
% \begin{macrocode}
\reset at font
% \end{macrocode}
@@ -3864,7 +3864,7 @@
% be printed in as small a space as possible, ie it uses any
% shrinkability in the column. If the column was not explicitly broken
% (\eg with |\pagebreak|) this may result in an overfull box message but
-% execpt for this it will come out as expected (if you know what to
+% except for this it will come out as expected (if you know what to
% expect).
%
% The star form of this command is dedicated to Leslie Lamport, the
@@ -3973,7 +3973,7 @@
% It also enables the use of an extra specifier, {\tt !}, in the
% location optional argument of a float. If this is present then,
% just for this particular float, whenever it is processed by the float
-% mechanism the followinhg are ignored:
+% mechanism the following are ignored:
%
% \begin{itemize}
% \item all restrictions on the number of floats which can appear;
@@ -4556,7 +4556,7 @@
% Yet another is to move the column count register from the multicol
% package into the kernel. This has been done.
% \item Where should the reinserts be put to maximise the
-% probability that footmotes come out on the correct page?
+% probability that footnotes come out on the correct page?
% Or should we go for as much compatibility as possible (but see
% next item)?
% \item Should we continue to support (as much as possible)
@@ -4980,7 +4980,7 @@
%
% At the top of the page |\@fptop| is inserted;
% typically this supplies some stretchable whitespace.
-% At the bottom of the page |\@fpbot| ais inserted.
+% At the bottom of the page |\@fpbot| is inserted.
% Between adjacent floats |\@fpsep| is inserted.
%
% These parameters are used for all floating objects on a
More information about the latex3-commits
mailing list.