[latex3-commits] [git/LaTeX3-latex3-latex2e] develop: edits by BB [ci skip] (6faa3c6c)
Frank Mittelbach
frank.mittelbach at latex-project.org
Tue Sep 17 00:14:52 CEST 2019
Repository : https://github.com/latex3/latex2e
On branch : develop
Link : https://github.com/latex3/latex2e/commit/6faa3c6c805a514babe4d6bd8c1d6973cea8b122
>---------------------------------------------------------------
commit 6faa3c6c805a514babe4d6bd8c1d6973cea8b122
Author: Frank Mittelbach <frank.mittelbach at latex-project.org>
Date: Tue Sep 17 00:14:52 2019 +0200
edits by BB [ci skip]
>---------------------------------------------------------------
6faa3c6c805a514babe4d6bd8c1d6973cea8b122
base/doc/ltnews30.tex | 54 +++++++++++++++++++++++++--------------------------
1 file changed, 27 insertions(+), 27 deletions(-)
diff --git a/base/doc/ltnews30.tex b/base/doc/ltnews30.tex
index 48d5959c..d97803a5 100644
--- a/base/doc/ltnews30.tex
+++ b/base/doc/ltnews30.tex
@@ -48,7 +48,7 @@
\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
@@ -156,7 +156,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 +190,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 +199,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.
@@ -240,12 +240,12 @@ 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.
+or use accented characters, etc., as part of a \cs{typeout} message.
The only requirement remaining is that only those UTF-8 characters
that are also available for typesetting can be used, i.e., only those
characters for
@@ -268,7 +268,7 @@ 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,
including spaces.
@@ -322,14 +322,14 @@ 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,7 +345,7 @@ 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}
@@ -379,10 +379,10 @@ 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.
-
+%
\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 +405,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 +414,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
@@ -435,7 +435,7 @@ automatically come out as
longer be 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 +448,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.
+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
@@ -569,7 +569,7 @@ Support was also added for the Arabic language through the option
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
@@ -615,7 +615,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}
More information about the latex3-commits
mailing list