4

The LaTeX kernel defines a slew of 'purify' equivalents for standard font commands, both switches (\bfseries) and argument-absorbers (\textbf{}).

Why?

  1. The switches would be removed anyway.
  2. The argument-absorbing macros created with \DeclareTextFontCommand{}{} would be removed and their arguments typeset in the currently active font.

The 'purify' declarations look to be equivalent to these default behaviours.

So the declarations appear to make no difference.

\documentclass{article} \renewcommand\sfdefault{lmss} \makeatletter \DeclareRobustCommand \sbcweight {\not@math@alphabet\sbcweight\relax\fontseries{sbc}\selectfont} \DeclareTextFontCommand\textsbc{\sbcweight} \makeatother \begin{document} \ExplSyntaxOn \sffamily \tl_set:Ne \l_tmpa_tl { \text_purify:n { \textbf{Aardvarks ~ Anonymous} } } \meaning \l_tmpa_tl \par \tl_set:Ne \l_tmpa_tl { \text_purify:n { \textsbc{ Puzzling ~ Pangolin ~ Palindromes } } } \meaning \l_tmpa_tl \par \ExplSyntaxOff \end{document} 

So what purpose do the declarations serve1?

1Obviously the real question is not whether the declarations are useful, but whether other declarations are necessary, which should be declared by somebody else i.e. font package maintainers, to pick an entirely hypothetical example purely at randoma.

aUsing 'random' in this sense.

0

1 Answer 1

4

Looking back, these are now-redundant definitions that were needed during the evolution of the code. They will be removed in an upcoming release.

1
  • sorry. that probably sounded rude. Commented Apr 3 at 7:41

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.