summaryrefslogtreecommitdiff
path: root/macros/latex-dev/base/ltnews30.tex
diff options
context:
space:
mode:
authorNorbert Preining <norbert@preining.info>2019-11-19 03:02:21 +0000
committerNorbert Preining <norbert@preining.info>2019-11-19 03:02:21 +0000
commit025f7bfee79d7817a876831bb19f34a2dfb1b2e2 (patch)
tree76efc8c89514583aae7ddb55b59bfb879500a09d /macros/latex-dev/base/ltnews30.tex
parent96f9362fc3e3bb70fa2411c62418c42d9acda4d7 (diff)
CTAN sync 201911190302
Diffstat (limited to 'macros/latex-dev/base/ltnews30.tex')
-rw-r--r--macros/latex-dev/base/ltnews30.tex101
1 files changed, 52 insertions, 49 deletions
diff --git a/macros/latex-dev/base/ltnews30.tex b/macros/latex-dev/base/ltnews30.tex
index 48d5959c6a..cfc1430fb8 100644
--- a/macros/latex-dev/base/ltnews30.tex
+++ b/macros/latex-dev/base/ltnews30.tex
@@ -48,15 +48,14 @@
\providecommand\pdfTeX{\hologo{pdfTeX}}
\providecommand\MiKTeX{\hologo{MiKTeX}}
\providecommand\CTAN{\textsc{ctan}}
-\providecommand\TL{\TeX{}Live}
-
+\providecommand\TL{\TeX\,Live}
\providecommand\githubissue[2][]{\ifhmode\unskip\fi
\quad\penalty500\strut\nobreak\hfill
\mbox{\small\slshape(%
\href{https://github.com/latex3/latex2e/issues/\getfirstgithubissue#2 \relax}%
{github issue#1 #2}%
)}%
- \par}
+ \par\smallskip}
% simple solution right now (just link to the first issue if there are more)
\def\getfirstgithubissue#1 #2\relax{#1}
@@ -156,7 +155,7 @@ For users of the \TL{} and \MiKTeX{} distributions it is therefore now
straightforward to test their documents and code against the upcoming
\LaTeX{} release with ease, simply by selecting a different program name
(when using the command line) or by selecting a menu entry (after
-setting it up, see below).
+setting it up; see below).
If you do this then the latest version of the \LaTeX{} development format
will be used to process your document, allowing you to test the
@@ -190,7 +189,7 @@ including the use of the \pkg{latexbug} package as described.
Our bug reporting process normally states that issues involving
third-party software are out of scope as we can’t correct external
-packages, see~\cite{30:Mittelbach:TB39-1}. However, in the particular
+packages; see~\cite{30:Mittelbach:TB39-1}. However, in the particular
case of the development format showing an incompatibility with a
third-party package, it is fine to open an issue with us (in addition,
please, to informing the maintainer of that package) so that we know
@@ -199,24 +198,24 @@ about the problem and can jointly work on resolving it.
\subsection{Details please \ldots}
More details and some background information about the concepts and
-the process is available in an upcoming TUGboat article: \enquote{The
+the process are available in an upcoming \textsl{TUGboat} article: \enquote{The
\LaTeX{} release workflow and the \LaTeX{} dev
formats}~\cite{devformat}.
\subsection{Setting up menu items}
While the command line call works out of the box if you have a recent
-\TL{} or \MiKTeX{} installation, the use within an integrated
+\TL{} or \MiKTeX{} installation, its use within an integrated
editing environment doesn’t at this point in time (maybe the
developers of these editors will include it in the future). However,
-it is normally fairly simple to enable it as most (or even all?) of
+it is normally fairly simple to enable it as most (or even all?)\ of
them provide simple ways to call your own setup. How this works in
detail depends very much on the environment you use, so we can’t give
much help here.
But as an example: to provide an additional menu entry for
-\texttt{XeLaTeX-dev} on a MacBook all that was necessary was to copy
-the file \texttt{XeLaTeX.engine} to XeLaTeX-dev.engine and change the
+\texttt{XeLaTeX-dev} on a MacBook all that is necessary is to copy
+the file \texttt{XeLaTeX.engine} to \texttt{XeLaTeX-dev.engine} and change the
call from \texttt{xelatex} to \texttt{xelatex-dev} inside.
@@ -226,7 +225,7 @@ call from \texttt{xelatex} to \texttt{xelatex-dev} inside.
Perhaps the most important improvement in this release is
even
-better support for UTF-8 characters when using \pdfTeX{}.\footnote{The
+better support for \acro{utf}-8 characters when using \pdfTeX{}.\footnote{The
Japanese engines e-p\TeX{} and e-up\TeX{} can't use these features
yet as they don't support the primitive \cs{ifincsname}. Work is
under way to resolve this in the engines.}
@@ -240,13 +239,13 @@ written to a file. In 8-bit engines, however, this was severely
restricted:
essentially you had to limit yourself to using
\acro{ascii} letters, digits and a few punctuation symbols. With the
-new release most of these restrictions have been removed and you now
+new release, most of these restrictions have been removed and you now
can write labels such as
\begin{verbatim}
\label{eq:größer}
\end{verbatim}
-or use accented characters, etc.\ as part of a \cs{typeout} message.
-The only requirement remaining is that only those UTF-8 characters
+or use accented characters, etc., as part of a \cs{typeout} message.
+The only requirement remaining is that only those \acro{utf}-8 characters
that are also available for typesetting can be used, i.e., only those
characters for
which adequate font support is loaded. Otherwise you will get an
@@ -268,9 +267,9 @@ sequence of bytes and this is not supported in command names.
\section{Improving file name handling in \pdfTeX{}}
A related change is that file names used as part of \cs{input},
-\cs{includegraphics}, etc.\ commands
+\cs{includegraphics}, etc., commands
can now contain any
-Unicode characters allowed by the File System in use,
+Unicode characters allowed by the file system in use,
including spaces.
In this case,
even characters that can't be typeset
@@ -316,20 +315,20 @@ In the early days of \LaTeX{} many commands were fragile, i.e., they
needed \cs{protect} in front of them when used in places such as
section headings and other \enquote{moving arguments}, etc.
In \LaTeXe{} many of these commands were made robust,
-but still a fairly huge number remained unnecessarily fragile.
+but still a fairly large number remained unnecessarily fragile.
In this release of \LaTeX{} we have now
made a lot more commands robust.
There is a very small collection of commands that must stay fragile
because their expansion (maybe partially) at just the right time is critical.
-Yet others are unlikely to ever be needed in an \enquote{moving argument}.
+Yet others are unlikely to ever be needed in a \enquote{moving argument}.
Doing this for \cs{begin} and \cs{end} was rather tricky as the
standard mechanism with \cs{DeclareRobustCommand} doesn't work here,
at least not for \cs{end} as that needs to expand during typesetting
-without generating a \cs{relax} (from the \cs{protect}. Such a token
-would start a new row in table environments, such as \texttt{tabular}
-etc. Furthermore some packages try to look into the definition of
+without generating a \cs{relax} (from the \cs{protect}). Such a token
+would start a new row in table environments, such as \texttt{tabular},
+etc. Furthermore, some packages try to look into the definition of
\cs{end} by expanding it several times. Thus expansion with
\cs{expandafter} had to produce exactly the same result as before. But
in the end we overcame that hurdle too, so now environments are
@@ -345,8 +344,8 @@ redefines a number of basic math constructs
that are now robust, so that
they become fragile again
once the package is loaded.
-This area will be addressed in a follow up release.
-
+This area will be addressed in a followup release.
+%
\githubissue{123}
@@ -378,11 +377,13 @@ This change was also applied in the \pkg{array} package.
The Unicode slots \texttt{27E8} and \texttt{27E9} have been mapped to
\cs{textlangle} and \cs{textrangle} which is the recommended mapping.
-In the past they raised a \LaTeX{} error.
-
+In the past they raised a
+\\
+\LaTeX{} error.
+%
\githubissue{110}
-When doing cut-and-paste from other documents or websites f-ligatures and others ligatures
+When doing cut-and-paste from other documents or websites, f-ligatures and others ligatures
might end up as
single Unicode characters in your file. In the past those got rejected by \LaTeX{}.
We
@@ -405,7 +406,7 @@ would work incorrectly, e.g., a construction such as
\begin{verbatim}
\InputIfFileExists{foo}{\input{bar}}{}
\end{verbatim}
-Would not load the files \texttt{foo.tex} and \texttt{bar.tex} but
+would not load the files \texttt{foo.tex} and \texttt{bar.tex} but
would load \texttt{bar.tex} twice. This has been corrected.
\githubissue{109}
@@ -414,7 +415,7 @@ would load \texttt{bar.tex} twice. This has been corrected.
\subsection{Improve interface for cross-references}
%%CCC should be 'provide' as they still exist. FMi - no they no longer do that
-The packages \pkg{fcnylab} and \pkg{varioref} provided
+The packages \pkg{fncylab} and \pkg{varioref} provided
a slightly
improved definition of \cs{refstepcounter} which allowed
the internal
@@ -428,14 +429,15 @@ formatting of the value in the reference.
These packages also provided
the command \cs{labelformat} to help in the specification of
such formatting in an easy way. For
-example, \verb=\labelformat{equation}{eq.~(#1}}= specifies that
+example, \verb=\labelformat{equation}{eq.~(#1)}= specifies that
references to equations
automatically come out as
-\enquote{eq.~(5)} or similar. As this means a \cs{ref} command can no
-longer be used at the start of a sentence, the packages also
+\enquote{eq.~(5)} or similar. As such a \cs{labelformat} declaration
+means a \cs{ref} command can no
+longer be successfully used at the start of a sentence, the packages also
provided \cs{Ref} for such scenarios.
-Both of these commands, cs{labelformat} and \cs{Ref},
+Both of these commands, \cs{labelformat} and \cs{Ref},
are now removed from the packages and instead made available in
the kernel so there is no
need to load additional packages.
@@ -448,19 +450,19 @@ need to load additional packages.
The kernel now says \enquote{Trying to load \ldots}
instead of \enquote{Try loading \ldots} in one of its informal
messages to match style of similar messages.
-
+%
\githubissue{107}
-\subsection{Avoid bad side-effects of cs{DeclareErrorFont}}
+\subsection{Avoid bad side-effects of \cs{DeclareErrorFont}}
-As a side effect of setting up the error font for NFSS, this
-declaration also changed the current font-size back to 10pt.
+As a side effect of setting up the error font for \acro{nfss}, this
+declaration also changed the current font size back to 10pt.
In most
circumstances that doesn't matter, because that declaration was meant
to be used only during the format generation and not during
a \LaTeX{} run.
-However, it has turned out to
+However, it has turned out to be
used by some developers in other places
(incorrectly in fact:
e.g., inside some \texttt{.fd} files) where
@@ -473,7 +475,7 @@ The command has now changed to not produce such side effects.
-\subsection{\pkg{nfssfont}: Generate a font table as the default action}
+\subsection{\pkg{nfssfont}: Make font table generation the default action}
With the small file \texttt{nfssfont.tex} it is possible to produce
font tables and other font tests
@@ -485,7 +487,7 @@ Now one can simply hit enter
instead of having to write \verb=\table\bye=.
-\subsection{\pkg{trace} package support in the kernel}
+\subsection{\pkg{trace}: Add package support in the kernel}
The \pkg{trace} package implements the commands \cs{traceon}
and \cs{traceoff} that work like
@@ -510,14 +512,14 @@ regardless of \pkg{trace} being loaded or not.
\subsection{\pkg{array}: Warn if primitive column specifiers are overwritten}
With \cs{newcolumntype} it is possible to define your own column
-specifiers for a \texttt{tabular} preamble, it is also possible to
+specifiers for a \texttt{tabular} preamble; it is also possible to
change existing ones. However, doing that for a primitive column
-specifier, such a \texttt{c}, is seldom a good idea, since then its
+specifier, such as \texttt{c}, is seldom a good idea, since then its
functionality becomes unavailable.
The package was therefore supposed
to warn the user in this case, but due to a missing \cs{expandafter}
in the code it never did---now it does.
-
+%
\githubissue{148}
@@ -542,7 +544,7 @@ What is most appropriate really depends on the circumstances, but this
now gives you the tools to make local or global adjustments.
-\subsection{\pkg{varioref}: better support for \pkg{cleveref}}
+\subsection{\pkg{varioref}: Better support for \pkg{cleveref}}
The \pkg{varioref} package has been internally updated to provide
better interfaces for packages such as \pkg{hyperref} and
@@ -564,12 +566,13 @@ Support was also added for the Arabic language through the option
-\subsection{\pkg{xr}: Support citations to bibliographies in external documents}
+\subsection[\pkg{xr}: Support citations to bibliographies in\\ external documents]
+{\pkg{xr}: Support citations to bibliographies in external documents}
The \pkg{xr} package can be used to cross-reference an external \LaTeX{}
document.
This means that even when a work is split over different documents (that
-need to be processed separately) \cs{ref} or \cs{pageref} can use labels from
+need to be processed separately), \cs{ref} or \cs{pageref} can use labels from
any document, creating links between them. This facility has now been extended
so that \cs{cite} commands and
their cousins can now also reference bibliographies in external
@@ -583,7 +586,7 @@ package.
\section{Changes to packages in the \pkg{amsmath} category}
-\subsection{\pkg{amsmath}: Introduce \texttt{overunderset} command}
+\subsection{\pkg{amsmath}: Introduce \cs{overunderset} command}
The \pkg{amsmath} package has always offered
the commands \cs{overset} and
@@ -601,7 +604,7 @@ There are a number of
documentation updates in files
on the documentation page of the project website~\cite{30:site-doc}.
-\subsection{Highlighting the standard NFSS codes for series}
+\subsection{Highlighting the standard \texorpdfstring{\acro{nfss}}{NFSS} codes for series}
The \emph{Font Selection Guide}~\cite{fntguide} has been
updated to strongly recommend that the standard codes should be used
@@ -615,7 +618,7 @@ comparable, e.g., that you get a \enquote{light} weight if you specify
etc. Over the years people came up with a number of other creative
short codes like \texttt{k}, \texttt{j}, \texttt{t} and others with
the result that changing a font family required different codes and
-thus prevented user from easily mixing and matching different
+thus prevented users from easily mixing and matching different
families.
Some work has been undertaken to get back to a coherent scheme and
all the font families supported through the program \texttt{autoinst}
@@ -628,7 +631,7 @@ For a long time the \LaTeX{} distribution available from \CTAN{} was
split into several parts to allow them to be uploaded or downloaded
separately. As this is these days more confusing than helpful we have
recombined the base part with the documentation part (as both are
-anyway always updated jointly. Thus the package \texttt{latex-doc}
+anyway always updated together). Thus the package \texttt{latex-doc}
is no longer separately available from \CTAN{} but contained in the
\texttt{latex-base} distribution.