Skip to content

Commit

Permalink
WIP
Browse files Browse the repository at this point in the history
  • Loading branch information
FrankMittelbach committed Dec 15, 2024
1 parent cd048ac commit 94b601a
Showing 1 changed file with 15 additions and 14 deletions.
29 changes: 15 additions & 14 deletions base/ltfssaxes.dtx
Original file line number Diff line number Diff line change
Expand Up @@ -28,7 +28,7 @@
% \fi
% \iffalse
%%% From File: ltfssaxes.dtx
%% Copyright (C) 2019-2020 Frank Mittelbach
%% Copyright (C) 2019-2020 Frank Mittelbach (initial implementation)
%
%<*driver>
% \fi
Expand Down Expand Up @@ -59,8 +59,8 @@
% \maketitle
%
% This file contains the implementation for handling extra axes
% splitting the series and the values into sub-categories. selection
% commands. See other parts of the \LaTeX\ distribution, or \emph{The
% by splitting the series and the shape values into sub-categories.
% See other parts of the \LaTeX\ distribution, or \emph{The
% \LaTeX\ Companion} for higher level documentation of the
% \LaTeX\ Font Selection Scheme.
%
Expand Down Expand Up @@ -191,13 +191,14 @@
% automatically gets reduced to \texttt{b}, or \texttt{mc} (medium
% weight condensed) which becomes \texttt{c} as a result.
%
% There is one exception: we do have rules for a request to
% There is one exception: We do have rules for a request to
% \texttt{bx}, because the Computer Modern fonts (or related
% families like Latin modern) need \texttt{bx} as their
% \cs{seriesdefault} because they don't have a \texttt{b} series
% or only for a restricted set of font faces in bold. Many other
% font families have only \texttt{b} but no \texttt{bx}. We
% therefore have explicit rules that fall back from one to the other.
% families like Latin Modern) need \texttt{bx} as their bold series
% default (\cs{bfdefault})
% because they don't have a \texttt{b} series or only for a
% restricted set of font faces. Many other font families have only
% \texttt{b} but no \texttt{bx}. We therefore have explicit rules
% that fall back from one to the other.
% \end{itemize}
%
% \item
Expand Down Expand Up @@ -1068,11 +1069,11 @@
\DeclareFontSeriesChangeRule {sbc}{el} {elc} {}
\DeclareFontSeriesChangeRule {sbc}{l} {lc} {}
\DeclareFontSeriesChangeRule {sbc}{sl} {slc} {}
\DeclareFontSeriesChangeRule {sbc}{sb} {sbc} {bc}
\DeclareFontSeriesChangeRule {sbc}{sb} {sbc} {}
\DeclareFontSeriesChangeRule {sbc}{b} {bc} {}
\DeclareFontSeriesChangeRule {sbc}{eb} {ebc} {bc}
\DeclareFontSeriesChangeRule {sbc}{ub} {ubc} {bc}
\DeclareFontSeriesChangeRule {sbc}{uc} {sbuc} {}
\DeclareFontSeriesChangeRule {sbc}{uc} {sbuc} {sbc}
\DeclareFontSeriesChangeRule {sbc}{ec} {sbec} {}
\DeclareFontSeriesChangeRule {sbc}{c} {sbc} {}
\DeclareFontSeriesChangeRule {sbc}{sc} {sbsc} {}
Expand Down Expand Up @@ -4123,9 +4124,9 @@
\DeclareFontShapeChangeRule {ssc}{ulc} {n} {}
% \end{macrocode}
% We implement the same logic as for \texttt{sc}, see above. The
% \texttt{ssc} shape doesn't need to care for 30 years of history,
% but it would be surprising is \cs{sscshape}\cs{upshape} would
% work differently to \cs{scshape}\cs{upshape}.
% \texttt{ssc} shape doesn't have to care about 30 years of history,
% but it would be surprising if \cs{sscshape}\cs{upshape} did not
% work like \cs{scshape}\cs{upshape}.
% \begin{macrocode}
% \DeclareFontShapeChangeRule {ssc}{up} {ssc} {}
\DeclareFontShapeChangeRule {ssc}{up} {n} {}
Expand Down

0 comments on commit 94b601a

Please sign in to comment.