| 1 |
% \iffalse meta-comment |
| 2 |
% |
| 3 |
% Copyright (C) 1993-2025 |
| 4 |
% The LaTeX Project and any individual authors listed elsewhere |
| 5 |
% in this file. |
| 6 |
% |
| 7 |
% This file is part of the LaTeX base system. |
| 8 |
% ------------------------------------------- |
| 9 |
% |
| 10 |
% It may be distributed and/or modified under the |
| 11 |
% conditions of the LaTeX Project Public License, either version 1.3c |
| 12 |
% of this license or (at your option) any later version. |
| 13 |
% The latest version of this license is in |
| 14 |
% http://www.latex-project.org/lppl.txt |
| 15 |
% and version 1.3c or later is part of all distributions of LaTeX |
| 16 |
% version 2008 or later. |
| 17 |
% |
| 18 |
% This file has the LPPL maintenance status "maintained". |
| 19 |
% |
| 20 |
% The list of all files belonging to the LaTeX base distribution is |
| 21 |
% given in the file `manifest.txt'. See also `legal.txt' for additional |
| 22 |
% information. |
| 23 |
% |
| 24 |
% The list of derived (unpacked) files belonging to the distribution |
| 25 |
% and covered by LPPL is defined by the unpacking scripts (with |
| 26 |
% extension .ins) which are part of the distribution. |
| 27 |
% |
| 28 |
% \fi |
| 29 |
% Filename: ltnews07.tex |
| 30 |
|
| 31 |
% This is issue 7 of LaTeX News. |
| 32 |
|
| 33 |
\documentclass |
| 34 |
% [lw35fonts] |
| 35 |
{ltnews} |
| 36 |
|
| 37 |
% \usepackage[T1]{fontenc} |
| 38 |
|
| 39 |
\publicationmonth{June} |
| 40 |
\publicationyear{1997} |
| 41 |
\publicationissue{7} |
| 42 |
|
| 43 |
\providecommand\pkg[1]{\texttt{#1}} |
| 44 |
\providecommand\cls[1]{\texttt{#1}} |
| 45 |
\providecommand\option[1]{\texttt{#1}} |
| 46 |
\providecommand\env[1]{\texttt{#1}} |
| 47 |
\providecommand\file[1]{\texttt{#1}} |
| 48 |
|
| 49 |
\begin{document} |
| 50 |
|
| 51 |
\maketitle |
| 52 |
|
| 53 |
\section{T1 encoded Computer Modern fonts} |
| 54 |
As in the last release the base \LaTeX\ distribution contains |
| 55 |
three different sets of `fd' files for T1 encoded fonts. |
| 56 |
|
| 57 |
In this release the default installation uses \file{ec.ins} |
| 58 |
and so installs files suitable for the current `EC fonts' |
| 59 |
distribution. If you have still not updated to the EC fonts and |
| 60 |
are using the earlier test versions, known as DC then you should |
| 61 |
unpack \file{newdc.ins} (for DC release 1.2 or later) or |
| 62 |
\file{olddc.ins} (for the original releases of the DC fonts). |
| 63 |
This should be done after unpacking \file{unpack.ins} but |
| 64 |
before making the format by running ini\TeX{} on \file{latex.ltx}. |
| 65 |
There are further details in \file{install.txt}. |
| 66 |
|
| 67 |
|
| 68 |
\section{T1 encoded Concrete fonts} |
| 69 |
The Metafont sources for T1 encoded `Concrete' fonts have been |
| 70 |
removed from the \textsf{mfnss} distribution as they were based |
| 71 |
on the now obsolete DC fonts release 1.1. Similarly the |
| 72 |
\file{cmextra.ins} install file in the \textsf{base} distribution no |
| 73 |
longer generates fd files for the `Concrete' fonts. |
| 74 |
To use these fonts in either T1 or OT1 encoding it is |
| 75 |
recommended that you obtain Walter Schmidt's \pkg{ccfonts} package |
| 76 |
and fonts from CTAN \file{macros/latex/contrib/supported/ccfonts}. |
| 77 |
|
| 78 |
|
| 79 |
\section{Further input encodings} |
| 80 |
Two more \pkg{inputenc} packages have been added: for latin5, |
| 81 |
thanks to H. Turgut Uyar; and for latin3, thanks to J\"org Knappen. |
| 82 |
|
| 83 |
|
| 84 |
\section{Normalising spacing after punctuation} |
| 85 |
The command \verb|\normalsfcodes| was introduced at the last patch |
| 86 |
release. This is normally given the correct definition automatically |
| 87 |
and so need not be explicitly set. It is used to correct a problem, |
| 88 |
reported by Donald Arseneau, that punctuation in page headers has |
| 89 |
always (in all known \TeX\ formats) been potentially incorrect if the |
| 90 |
page break happens while a local setting of the space codes (for |
| 91 |
instance by the command \verb|\frenchspacing|) is in effect. A common |
| 92 |
example of this happening in \LaTeX\ is in the \env{verbatim} |
| 93 |
environment. |
| 94 |
|
| 95 |
|
| 96 |
\section{Accessing Bold Math Symbols} |
| 97 |
The \textsf{tools} distribution contains a new package, \pkg{bm}, |
| 98 |
which defines a command \verb|\bm| that allows individual bold symbols |
| 99 |
to be accessed within a math expression (in contrast to |
| 100 |
\verb|\boldmath| which makes whole math expressions default to bold |
| 101 |
fonts). It is more general than the existing \pkg{amsbsy} package; |
| 102 |
however, to ease the translation of documents between these two |
| 103 |
packages, \pkg{bm} makes \verb|\boldsymbol| an alias for |
| 104 |
\verb|\bm|. |
| 105 |
|
| 106 |
This package was previously made available from the `contrib' area of |
| 107 |
the CTAN archives, and as part of Y\&Y's \LaTeX\ support for the |
| 108 |
MathTime fonts. |
| 109 |
|
| 110 |
|
| 111 |
\section{Policy on standard classes} |
| 112 |
|
| 113 |
Many of the problem reports we receive concerning the standard classes |
| 114 |
are not concerned with bugs but are suggesting, more or less politely, |
| 115 |
that the design decisions embodied in them are `not optimal' and |
| 116 |
asking us to modify them. |
| 117 |
|
| 118 |
There are several reasons why we have decided not to make such changes |
| 119 |
to these files. |
| 120 |
\begin{itemize} |
| 121 |
\item |
| 122 |
However misguided, the current behaviour is clearly what was |
| 123 |
intended when these classes were designed. |
| 124 |
\item |
| 125 |
It is not good practice to change such aspects of `standard classes' |
| 126 |
because many people will be relying on them. |
| 127 |
\end{itemize} |
| 128 |
|
| 129 |
We have therefore decided not to even consider making such |
| 130 |
modifications, nor to spend time justifying that decision. This does |
| 131 |
not mean that we do not agree that there are many deficiencies in the |
| 132 |
design of these classes, but we have many tasks with higher priority |
| 133 |
than continually explaining why the standard classes for \LaTeX{} |
| 134 |
cannot be changed. |
| 135 |
|
| 136 |
We would, of course, welcome the production of better classes, or of |
| 137 |
packages that can be used to enhance these classes. |
| 138 |
|
| 139 |
|
| 140 |
\section{New addresses for TUG} |
| 141 |
For information about joining the \TeX{} Users Group, and about lots |
| 142 |
of other \LaTeX-related matters, please contact |
| 143 |
them at their new address: |
| 144 |
\begin{quote}\small |
| 145 |
\TeX{} Users Group, P.O. Box 1239,\\ |
| 146 |
Three Rivers, CA~93271-1239, USA\\ |
| 147 |
Fax:~+1~209~561~4584\\ |
| 148 |
E-mail: \texttt{[email protected]}\\ |
| 149 |
URL: \texttt{http://www.tug.org/} |
| 150 |
\end{quote} |
| 151 |
|
| 152 |
\end{document} |