[latex3-commits] [latex2e-public] r1320 - wording adjustments and less ragged raggedright so it fits on one page, and looks less ragged...

[noreply at latex-project.org]

Author: carlisle
Date: 2017-01-04 01:16:34 +0100 (Wed, 04 Jan 2017)
New Revision: 1320

Modified:
   trunk/doc/ltnews26.tex
Log:
wording adjustments and less ragged raggedright so it fits on one page, and looks less ragged...

Modified: trunk/doc/ltnews26.tex
===================================================================
--- trunk/doc/ltnews26.tex	2017-01-01 20:12:21 UTC (rev 1319)
+++ trunk/doc/ltnews26.tex	2017-01-04 00:16:34 UTC (rev 1320)
@@ -44,7 +44,9 @@
 \begin{document}
 
 \maketitle
+\tableofcontents
 
+\rightskip=0pt plus 3em
 \section{\eTeX{}}
 
 In \LaTeX{} News~16 (December 2003) the team announced
@@ -76,7 +78,7 @@
 
 \section{Default Encodings in \hologo{XeLaTeX} and \hologo{LuaLaTeX}}
 The default encoding in \LaTeX\ has always been the original
-127-character encoding ``OT1''.  For Unicode based \TeX\ engines, this
+127-character encoding OT1.  For Unicode based \TeX\ engines, this
 is not really suitable, and is especially problematic with
 \hologo{XeLaTeX} as in the major distributions this is built with
 Unicode base hyphenation patterns in the format.  In practice this has
@@ -84,7 +86,7 @@
 \textsf{fontspec} package in order to switch to a
 Unicode encoded font..
 
-In this release we are adding ``TU'' as a new supported
+In this release we are adding TU as a new supported
 encoding in addition to the previously supported encodings such as OT1
 and T1. This denotes a Unicode based font encoding. It is essentially
 the same as the TU encoding that has been on trial with the
@@ -98,23 +100,27 @@
 of OpenType fonts.
 
 The \textsf{fontspec} package is being adjusted in a companion release
-to recognise the new encoding defaullt arrangements.
+to recognise the new encoding default arrangements.
 
 Note that in practice no font supports the full Unicode range, and so
-TU encoded fonts, unlike fonts specified for T1, may be expected to
-be incomplete in various ways. In the current release the format has 
-made some basic assumptions for (for example) default handling of
-accent commands. The \textsf{fontspec} package has more control over
-finer details of the font loading and control over OpenType
-features. More facilities may be added as needed. Initially they will
-be added in \textsf{fontspec} with some aspects possibly being moved
-to the base format at a later date.
+TU encoded fonts, unlike fonts specified for T1, may be expected to be
+incomplete in various ways. In the current release the file
+\texttt{tuenc.def} that implements the TU encoding-specific commands
+has made some basic assumptions for (for example) default handling of
+accent commands, and the set of command names is derived from the
+command names used for the UTF-8 support in the inputenc package,
+restricted roughly to the character ranges classically provided by
+the T1 and TS1 encodings, but is part of a longer term plan seen over
+recent releases to increase support for Unicode based \TeX\ engines into
+the core \LaTeX\ support.
 
+
+
 If for any reason you need to process a document with the previous
 default OT1 encoding, you may switch encoding in the usual ways, for
 example
 \begin{verbatim}
-\usepackage[T1]{fontenc}
+\usepackage[OT1]{fontenc}
 \end{verbatim}
 or you may roll back all the changes for this release by starting the
 document with