I wonder if this is just my problem...:
after a very recent full update of texlive everything I tried to compile
failed with:
<snip>
(/usr/local/texlive/2016/texmf-dist/tex/latex/fontspec/fontspec-luatex.sty
*************************************************
* fontspec warning: "tu-clash"
*
* I have found the tuenc.def encoding definition file but the TU
encoding is
* not defined by the LaTeX2e kernel; attempting to correct but you really
* should update to the latest version of LaTeX2e.
*************************************************
(/usr/local/texlive/2016/texmf-dist/tex/latex/base/fontenc.sty
(/usr/local/texlive/2016/texmf-dist/tex/latex/base/tuenc.def
! Missing \endcsname inserted.
<to be read again>
\def
l.252 ... \UnicodeEncodingName {}{"007E}
?
<snip>
The two (newly introduced) lines in tuenc.def which offended my lualatex
(0.95, from texlive 2016) are:
\DeclareTextComposite{\^} \UnicodeEncodingName {}{"005E}
\DeclareTextComposite{\~} \UnicodeEncodingName {}{"007E}
After commenting these out the compilation worked fine. Please note,
that the "offending" lines caused no problem when compiling the MWE with
xelatex (but I am using lualatex).
Here's a M(N)WE:
\documentclass{article}
%\usepackage{luatex85} % un-comment when compiling with lualatex
\usepackage{fontspec}
%\setmainfont{Brill} % this would be a free and rather comprehensive
typeface
\begin{document}
Won't compile under lualatex with newest tuenc.def.
Compiles fine with xelatex.
\end{document}
Is there just something wrong with my system? And if so, what would be a
remedy (other than commenting the two lines out, which I did to be able
to continue working)?
(MacOS 10.8.5, texlive (mactex) 2016, last update 3 days ago.)
Best,
Rembrandt
--
人生䘮亂世無君欲誰仕
- 劉因
