summaryrefslogtreecommitdiff
path: root/macros/latex-dev/base/fntguide.tex
diff options
context:
space:
mode:
Diffstat (limited to 'macros/latex-dev/base/fntguide.tex')
-rw-r--r--macros/latex-dev/base/fntguide.tex39
1 files changed, 33 insertions, 6 deletions
diff --git a/macros/latex-dev/base/fntguide.tex b/macros/latex-dev/base/fntguide.tex
index 62d3538304..65467339f1 100644
--- a/macros/latex-dev/base/fntguide.tex
+++ b/macros/latex-dev/base/fntguide.tex
@@ -42,12 +42,17 @@
\title{\LaTeXe{} font selection}
-\author{\copyright~Copyright 1995--2021, \LaTeX\ Project
+\author{\copyright~Copyright 1995--2022, \LaTeX\ Project
Team.\thanks{Thanks to Arash Esbati for documenting the
newer NFSS features of 2020}\\
- All rights reserved.}
+ All rights reserved.%
+ \footnote{This file may distributed and/or modified under the
+ conditions of the \LaTeX{} Project Public License, either version 1.3c
+ of this license or (at your option) any later version. See the source
+ \texttt{fntguide.tex} for full details.}%
+}
-\date{December 2021}
+\date{August 2022}
\begin{document}
@@ -1431,6 +1436,20 @@ Example:
\DeclareFontEncoding{OT1}{}{}
\end{verbatim}
+\NEWfeature{2021/06/01}
+Fonts in encoding \texttt{TS1} are usually not implementing the full encoding but only a subset.
+This subset should be declared with a |\DeclareEncodingSubset|
+declaration:
+
+\begin{decl}
+ |\DeclareEncodingSubset| \arg{encoding}
+ \arg{font family}
+ \arg{subset number}
+\end{decl}
+This should even be done if the font is implementing the full
+\texttt{TS1} encoding; see page~\pageref{page:declareencodingsubset} for
+further details.
+
Some author commands need to change their definition depending on which
encoding is currently in use. For example, in the |OT1| encoding, the
letter `\AE' is in slot |"1D|, whereas in the |T1| encoding it is in
@@ -2048,7 +2067,7 @@ glyphs from the math fonts instead of the current text font (this means
they always keep the same shape and do not nicely blend in with the text
font).
-\newpage
+%\newpage
The following tables show the macros available. The next commands are
`constructed' accents and are built via \TeX{} macros:
@@ -2234,7 +2253,8 @@ question arises: ``Which glyphs of the |TS1| encoding are implemented by
which font?''
\NEWfeature{2021/06/01}
-Fonts can be ordered in sub-encodings with the |\DeclareEncodingSubset|
+Fonts\label{page:declareencodingsubset}
+can be ordered in sub-encodings with the |\DeclareEncodingSubset|
macro:
\begin{decl}
|\DeclareEncodingSubset| \arg{encoding}
@@ -2577,7 +2597,14 @@ is the same as writing
If only some are needed then one can define them individually but in
many cases all four are wanted, hence the shortcut.
-
+Maintainers of font bundles that include \texttt{TS1} encoded font files
+should add an appropriate declaration into the corresponding
+\texttt{ts1}\textit{family}\texttt{.fd} file, because otherwise the
+default subencoding is assumed, which is probably disabling too many
+glyphs that are actually available in the font.\footnote{The \LaTeX{}
+ format contains declarations for many font families already, but this
+ is really the wrong place for the declarations. Thus for new fonts
+ they should be placed into the corresponding \texttt{.fd} file.}
\section{If you need to know more \ldots}