Skip to content

Commit

Permalink
added a sentence explaining why both font faces give the same results
Browse files Browse the repository at this point in the history
  • Loading branch information
FrankMittelbach committed Oct 30, 2022
1 parent ee1a23a commit a49b1f4
Showing 1 changed file with 14 additions and 12 deletions.
26 changes: 14 additions & 12 deletions base/doc/ltnews36.tex
Expand Up @@ -238,12 +238,8 @@ \subsection{Better language handling for case-changing commands}
\MakeUppercase[lang = tr]{Ragıp Hulûsi Özdem}
\end{verbatim}
yields
%\begin{quotation}
% \MakeUppercase[lang = tr]{Ragıp Hulûsi Özdem}.
%\end{quotation}
\IfFormatAtLeastTF{2023/11/01}%
{\MakeUppercase[lang = tr]{Ragıp Hulûsi Özdem}}%
{RAGIP HULÛS\.I ÖZDEM}.
\MakeUppercase[lang = tr]{Ragıp Hulûsi Özdem}.
% RAGIP HULÛS\.I ÖZDEM. %TUB

\section{Code improvements}

Expand All @@ -262,7 +258,12 @@ \subsection{Support for slanted small caps in the EC fonts}
will give the expected result: {\fontfamily{cmr}
\textsc{\textsl{slanted small caps}}; \textsc{\textit{italic small caps}};
\bfseries
\textsc{\textsl{bold slanted small caps}}; \textsc{\textit{bold italic small caps}}}
\textsc{\textsl{bold slanted small caps}}; \textsc{\textit{bold italic small caps}}}.

Given that the fonts do not have real italic small caps but only
slanted small caps, the latter is substituted for the former, which is
why above both work but you see no difference between the two (and in the log you get a
substitution warning for the \cs{textit}\cs{textsc} shape combination).
%
\githubissue{782}

Expand Down Expand Up @@ -388,7 +389,7 @@ \subsection{Rule-based ordering for \LuaTeX\ callback handlers}
Code which relied on this implicit order should now define the order
rules explicitly.

\enlargethispage{.5\baselineskip}


\section{Bug fixes}

Expand All @@ -415,8 +416,10 @@ \subsection{Prevent \TeX{} from losing a \cs{smash}}
\qquad
\frac{1}{\drawbaseline2} = \frac{1}{\smash{2^X}} \neq
\frac{100}{\smash{2^X}}
\pagebreak % not TUB
\]
The differences are subtle but noticeable. This is now corrected and the \cs{smash} is always
The differences are subtle but noticeable.
This is now corrected and the \cs{smash} is always
honored. Thus now you get this output:
\vspace{-1.2\baselineskip}
\[
Expand Down Expand Up @@ -455,7 +458,8 @@ \subsection{Reporting of unused global options when using key/value processing}
%\section{Changes to packages in the \pkg{amsmath} category}


\newpage
%\newpage TUB?

\section{Changes to packages in the \pkg{graphics} category}

\subsection{Fix a \cs{mathcolor} bug}
Expand All @@ -469,8 +473,6 @@ \subsection{Fix a \cs{mathcolor} bug}
\githubissue{901}


\enlargethispage{.5\baselineskip}


\section{Changes to packages in the \pkg{tools} category}

Expand Down

0 comments on commit a49b1f4

Please sign in to comment.