[latex3-commits] [git/LaTeX3-latex3-latex2e] nfssaxes: nfssaxes doc typos (958e6fef)
Will Robertson
wspr81 at gmail.com
Fri Oct 25 13:36:25 CEST 2019
Repository : https://github.com/latex3/latex2e
On branch : nfssaxes
Link : https://github.com/latex3/latex2e/commit/958e6fefdd638a6dcf8a3bb24e76e59067666a6c
>---------------------------------------------------------------
commit 958e6fefdd638a6dcf8a3bb24e76e59067666a6c
Author: Will Robertson <wspr81 at gmail.com>
Date: Fri Oct 25 22:06:25 2019 +1030
nfssaxes doc typos
>---------------------------------------------------------------
958e6fefdd638a6dcf8a3bb24e76e59067666a6c
base/nfssaxes.tex | 57 ++++++++++++++++++++++++++++---------------------------
1 file changed, 29 insertions(+), 28 deletions(-)
diff --git a/base/nfssaxes.tex b/base/nfssaxes.tex
index e9d37f0e..c1356ee4 100644
--- a/base/nfssaxes.tex
+++ b/base/nfssaxes.tex
@@ -13,10 +13,10 @@
% \item[\texttt{\#1}] current \cs{f at series}
% \item[\texttt{\#2}] requested new series
% \item[\texttt{\#3}] result (if that exist for the given font family
-% \item[\texttt{\#4}] alternative result (if \textt{\#3} does not exist)
+% \item[\texttt{\#4}] alternative result (if \texttt{\#3} does not exist)
% \end{itemize}
% If an \texttt{.fd} file has its own substitution rules then
-% \texttt{\#3} exist and thus \textt{\#4} is not applied.
+% \texttt{\#3} exist and thus \texttt{\#4} is not applied.
%
% If there is no matching database entry or if neither the result
% nor the alternate result exist in the font family the requested
@@ -46,7 +46,7 @@
% \item
%
% We make \texttt{m} to reset both weight and width (as this is
-% how it always worked). To reset just the width \textt{?m} is
+% how it always worked). To reset just the width \texttt{?m} is
% provided and to reset just the weight \texttt{m?}.
%
% \item
@@ -83,7 +83,7 @@
% \item
%
% Also: while I did set up all nine standard weight values from
-% \texttt{ul} to \textt{ub} I only bothered to provide entries for
+% \texttt{ul} to \texttt{ub} I only bothered to provide entries for
% \texttt{ec}, \texttt{sc}, \texttt{c} and \texttt{x}, because other levels of
% compression/expansion are not in any real fonts that I know.
%
@@ -686,8 +686,8 @@
%\begin{verbatim}
\DeclareFontSeriesChangeRule {m}{sc}{msc}{mc}
%\end{verbatim}
-% instead of of using \texttt{sc} and \textt{c} as needed in the
-% \textt{.fd} file.
+% instead of of using \texttt{sc} and \texttt{c} as needed in the
+% \texttt{.fd} file.
% \begin{macrocode}
\def\set at target@series#1{%
% \end{macrocode}
@@ -706,6 +706,7 @@
}
% \end{macrocode}
% \end{macro}
+% \end{macro}
% \section{Changing the shape}
@@ -733,11 +734,11 @@
% second time it changes then \texttt{sc} back to normal. Maybe
% that's not a bad way to handle it, so I've done that below too.
% The alternative would be to provide something like \cs{noscshape}
-% as the \pkg{slantsc} package does.
+% as the \textsf{slantsc} package does.
%
% That sort of approach doesn't seem possible with the series as
% \cs{bfseries} produces \texttt{bx} (normally) and \cs{mdseries}
-% reverts that back to \texttt{{m} (ie no bold and normal width)
+% reverts that back to \texttt{m} (ie no bold and normal width)
% and I think that needs to be preserved.
%
% \begin{macro}{\ulcshape}
@@ -812,7 +813,7 @@
\DeclareFontShapeChangeRule {it}{sl} {sl} {it}
%\DeclareFontShapeChangeRule {it}{sw} {sw} {}
% \end{macrocode}
-% If neither \textt{scit} nor \texttt{scsl} exist then \texttt{sc}
+% If neither \texttt{scit} nor \texttt{scsl} exist then \texttt{sc}
% will be used as a fallback albeit with a log entry, so except for
% the latter there will be no change for CM or Latin Modern fonts.
% \begin{macrocode}
@@ -934,7 +935,7 @@
% \end{macro}
-% This code implements one aspect of what the package \pkg{fontaxes}
+% This code implements one aspect of what the package \textsf{fontaxes}
% provide. So its redefinitions for the vairous shape commands,
% such as \cs{itshape} should no longer happen.
%
@@ -969,7 +970,7 @@
}
% \end{macrocode}
%
-% The \pkg{fontaxes} package also implements two further shapes,
+% The \textsf{fontaxes} package also implements two further shapes,
% namely \cs{swshape} and \cs{sscshape}. They could now easily be
% integrated by specifying a few further table entries such as
% \begin{macrocode}
@@ -982,7 +983,7 @@
% currently only a few fonts
% that support swash letters). For ``spaced small capitals'' there a
% none among the free fonts. Nevertheless, perhaps that should also be integrated
-% in the kernel so that the existing \pkg{fontaxes} support continues to
+% in the kernel so that the existing \textsf{fontaxes} support continues to
% work in full.
%
%
@@ -1023,8 +1024,8 @@
% but instead of providing a fixed one \LaTeX{} now offers a
% general mechanism that allows to define arbitrary sequences.
%
-% \DeclareMacro\emfontdeclare
-% \DeclareMacro\emforce
+% \DescribeMacro\emfontdeclare
+% \DescribeMacro\emforce
%
% \emph{decide name! maybe \cs{DeclareEmSequence} ???}
%
@@ -1040,7 +1041,7 @@
% In such a case one has to use \cs{emforce} to which directs the
% mechanism to use the level even if the font attributes haven't changed.
%
-% \DecsribeMacro\emreset
+% \DescribeMacro\emreset
% If the nesting is so deep, that the specified levels are
% exhausted then \cs{emreset} is used as a final set of
% declarations (which by default returns
@@ -1052,7 +1053,7 @@
%
% \begin{macro}{\emfontdeclare}
%
-% \cs{emfontdeclare| expects a clist of declaration. Spaces in the
+% \cs{emfontdeclare} expects a clist of declaration. Spaces in the
% argument are dropped to avoid surious spaces in the output. The
% declarations are additive. At the very end the shape is reset
% using |\emreset| and |\emforce| so that this case is never
@@ -1077,7 +1078,7 @@
% \begin{macro}{\emrest}
% Reset the font to upright (this needs to undo \texttt{sc} and
-% \textt{it} separately as \cs{upshape} no longer resets both in
+% \texttt{it} separately as \cs{upshape} no longer resets both in
% one go).
% \begin{macrocode}
\DeclareRobustCommand\emreset{%
@@ -1184,7 +1185,7 @@
% \section{Custom series settings for main document families}
%
-% One problem with the \NFSS{} approach of handling the series axis
+% One problem with the NFSS approach of handling the series axis
% turned out to be that (especially with respect to ``boldness'')
% different font families implemented different strategies. For
% example, with Computer Modern fonts you normally only have
@@ -1196,7 +1197,7 @@
% with such fonts).
%
% The solution back then was to provide substitution rules in the
-% font \textt{.fd} such that if a \texttt{bx} series got requested
+% font \texttt{.fd} such that if a \texttt{bx} series got requested
% the \texttt{b} series got used. While this works in that
% particular case, it isn't a very
% general solution. For example, if you happen to have a font family that
@@ -1223,7 +1224,7 @@
% \item[document family interface:] Can either be \texttt{rm},
% \texttt{sf} or \texttt{tt}. This is optional and if not given the
% overall default.
-% \item[document series interface:] Can be \textt{md} or
+% \item[document series interface:] Can be \texttt{md} or
% \texttt{bf}.
% \item[series value:] This is the value that is going to be used
% with the combination is requested.
@@ -1238,11 +1239,11 @@
% redefining \cs{bfdefault} or \cs{mddefault}.
%
% If some family specify defaults aren't given, e.g. if there are
-% no declarations for, say, \textttt{tt} then the format defaults
+% no declarations for, say, \texttt{tt} then the format defaults
% of \cs{mddefault} and \cs{bfdefault} are assumed. If those are
% later changed this is \emph{not} reflected!\footnote{I see no
% easy way to achieve this without compromising compatibility with
-% existing packages that currently use \pkg{mweights} and directly
+% existing packages that currently use \textsf{mweights} and directly
% define (some) of the \cs{mdseries at ..} commands but not others.}
%
%
@@ -1335,7 +1336,7 @@
%
% The default for the medium series is \texttt{m} and this will be
% interpreted as resetting both weight and width. To reset only one
-% of them the virtual value \textt{?m} and \textt{m?} are available.
+% of them the virtual value \texttt{?m} and \texttt{m?} are available.
% \begin{macrocode}
\edef\mdseries at rm{\mddefault}
\edef\mdseries at sf{\mddefault}
@@ -1383,7 +1384,7 @@
\DeclareRobustCommand\bfseries{%
\not at math@alphabet\bfseries\mathbf
% \end{macrocode}
-% In the original \NFSS{} definition it then called \cs{fontseries}
+% In the original NFSS definition it then called \cs{fontseries}
% with the value \cs{bfdefault}. In the new scheme we have more
% alternatives and therefore check if the current family
% (\cs{f at family}) is the current \cs{rmdef at ult}, \cs{sfdef at ult} or
@@ -1435,7 +1436,7 @@
% change the current series before changing the family
% \end{macrocode}
% If families are changed then we have to do a bit more work.
-% In the original \NFSS implementation
+% In the original NFSS implementation
% a family change kept encoding, series shape and size unchanged
% but now we can't any
% longer simply reuse the current series value. Instead we may have
@@ -1478,7 +1479,7 @@
% If neither test was true we leave the series alone. This way a
% special manual setting such as \verb=\fontseries{lc}= is not
% undone if the family changes (of course there may not be any
-% support for it in the new family but then the \NFSS{}
+% support for it in the new family but then the NFSS
% substitution kicks in and sorts it out).
% \begin{macrocode}
\fi\fi\fi\fi
@@ -1506,7 +1507,7 @@
% If \cs{target at series@value} is still empty there is nothing more
% to do other than selecting the new family. However, if not then
% we should update the font series now as well. But there is one
-% further subtle issue. We may not have loaded an \textt{.fd} file
+% further subtle issue. We may not have loaded an \texttt{.fd} file
% for our target font family yet. In the past that was done in
% \cs{selectfont} if necessary but since we are now doing all the
% comparisons in \cs{fontseries} we need to make sure that the font
@@ -1652,7 +1653,7 @@
% As the kernel code now implements the same functionality as
-% \pkg{mweights}, albeit internally coded slightly differently,
+% \textsf{mweights}, albeit internally coded slightly differently,
% that package shouldn't be loaded any more. We therefore pretend
% that it already got loaded. Thus, a font package that tries to
% load it and then sets \cs{mdseries at ..}, etc.\ will continue to
More information about the latex3-commits
mailing list