On 6/12/2016 8:08 PM, Mark McGregor wrote:
A more minimal non-working example:
[
\documentclass{article}
\usepackage{fontspec}
\setmainfont{CMU Serif}
%\setmainfont{cmunrm.otf}
\begin{document}
А
\end{document}
]
If you comment the first \setmainfont line and uncomment the second one, the
file compiles. Rerunning /usr/bin/texlive-enable-fontconfig doesn't help.
I found an answer at the following:
http://tex.stackexchange.com/questions/296308/xelatex-setmainfontcmu-serif-produces-wrong-characters
Based on that, you can work around the problem by commenting out the
type1 fonts in /usr/share/fontconfig/conf.avail/09-texlive.conf, like this:
$ cat /usr/share/fontconfig/conf.avail/09-texlive.conf
<?xml version="1.0"?>
<!DOCTYPE fontconfig SYSTEM "fonts.dtd">
<fontconfig>
<dir>/usr/share/texmf-dist/fonts/opentype</dir>
<dir>/usr/share/texmf-dist/fonts/truetype</dir>
<!-- <dir>/usr/share/texmf-dist/fonts/type1</dir> -->
</fontconfig>
Then rerun the command '/usr/libexec/fc-cache-1 -sv' from
/etc/postinstall/zp_fontconfig_cache_1.sh.
What puzzles me is that the link above says that the problem is caused
by bugs in xdvipdfmx that have been fixed in TeX Live 2016. I'll look
into this and try to find out why it still seems to be broken.
Ken
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
