From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: xdvipdfmx:fatal: This font using the "seac" command for accented characters...
Date: Mon, 13 Jun 2016 07:53:00 -0000 [thread overview]
Message-ID: <7c5d902a-5498-39cf-9d19-fc66f464c447@cornell.edu> (raw)
In-Reply-To: <trinity-65448339-5e78-4d88-bd88-c56cded8d4d5-1465776480726@3capp-gmx-bs72>
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
next prev parent reply other threads:[~2016-06-13 2:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-13 0:30 Mark McGregor
2016-06-13 7:53 ` Ken Brown [this message]
[not found] <1466280246.97757.ezmlm@cygwin.com>
2016-06-19 18:14 ` xdvipdfmx:fatal: This font using the "seac" command for accented, characters Mark
[not found] <1465890352.69476.ezmlm@cygwin.com>
2016-06-18 11:41 ` xdvipdfmx:fatal: This font using the "seac" command for accented characters Mark McGregor
2016-06-18 20:04 ` Ken Brown
[not found] <1465820332.127780.ezmlm@cygwin.com>
2016-06-13 17:10 ` Mark McGregor
2016-06-13 18:20 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2016-06-13 9:43 Mark McGregor
2016-06-13 14:31 ` Ken Brown
2016-06-13 0:08 Mark McGregor
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7c5d902a-5498-39cf-9d19-fc66f464c447@cornell.edu \
--to=kbrown@cornell.edu \
--cc=cygwin@cygwin.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).