From 381915949b365625028c71574bcfd9cf6e063635 Mon Sep 17 00:00:00 2001 From: joseph Date: Wed, 27 Jan 2016 07:13:36 +0000 Subject: [PATCH] Team as singular git-svn-id: http://www.latex-project.org/svnroot/latex2e-public@1044 8685b20e-f38a-4a74-812f-bec00e2e18bd --- trunk/doc/ltnews24.tex | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/trunk/doc/ltnews24.tex b/trunk/doc/ltnews24.tex index 1bec737..6adad3a 100644 --- a/trunk/doc/ltnews24.tex +++ b/trunk/doc/ltnews24.tex @@ -113,7 +113,7 @@ used by (plain) \hologo{XeTeX} and to pre-process the ``raw'' Unicode data into a ready-to-use form as \verb|unicode-letters.def|. However, the relationship between the Unicode Consortium files and \TeX{} data structures is non-trivial and still being explored. As such, it is preferable to directly parse the original -(\verb|.txt|) files at point of use. The team have therefore ``spun-out'' both +(\verb|.txt|) files at point of use. The team has therefore ``spun-out'' both the data and the loading to a new generic package, \package{unicode-data}. This package makes the original Unicode Consortium data files available in the \verb|texmf| tree (in \verb|tex/generic/unicode-data|) and provides generic @@ -215,7 +215,7 @@ remains usable and gives reliable results for users. For the Unicode \TeX{} engines \hologo{XeTeX} and \hologo{LuaTeX} there are important differences in behaviour from classical ($8$-bit) \TeX{} engines which mean that identical default behaviours are not appropriate. Over the -past 18 months the team have addressed the most pressing of these +past 18 months the team has addressed the most pressing of these considerations (as detailed above and in \LaTeX{} News~22 and 23), primarily by integrating existing patches into the kernel. There are, though, important areas which still need consideration, and which @@ -231,14 +231,14 @@ Unicode code points. This means that hyphenation will be incorrect with Unicode engines unless a Unicode font is loaded. This requires a concept of a Unicode font encoding, which is currently provided by the \package{fontspec} package in two versions, \texttt{EU1} and -\texttt{EU2}. The team are working to fully understand what is meant +\texttt{EU2}. The team is working to fully understand what is meant by a `Unicode font encoding', as unlike a classical \TeX{} encoding it is essentially impossible to know what glyphs will be provided (though each slot is always defined with the same meaning). There is also an overlap between this area and ideas of language and writing system, most obviously in mixed Latin/Cyrillic/East Asian documents. -As well as these font considerations, the team are also exploring +As well as these font considerations, the team is also exploring to what extent it is possible to allow existing ($8$-bit) documents to compile directly with Unicode engines without requiring changes in the sources. Whether this is truly possible remains an open -- 2.11.4.GIT