From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: xdvipdfmx:fatal: This font using the "seac" command for accented characters...
Date: Sat, 18 Jun 2016 20:04:00 -0000 [thread overview]
Message-ID: <b82c3f79-4271-ba3f-6aa7-6f6cdbb974b2@cornell.edu> (raw)
In-Reply-To: <trinity-4f46c890-4f51-4e11-a248-0acf33eebf50-1466200480864@3capp-gmx-bs03>
On 6/17/2016 5:54 PM, Mark McGregor wrote:
> ----Ken wrote:
> No, I don't think XeTeX is dying. A look at its git repository shows lots of commits from Jonathan Kew and Arthur Reutenauer in the last few months.
> ----
>
> The last commit was over 1 month ago: a 1-line change from JK. I'm not overly optimistic that anything will happen to this bug report at all. But, anyway, thank you for having reported!
I had some private correspondence with Akira Kakuto about my bug report,
and he said it isn't a bug. The problem is simply that xetex has very
limited support for type1 fonts, and the solution is to remove them from
the fonts that fontconfig knows about, as you've done. So I'll probably
make this change the next time I update texlive.
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-18 11:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1465890352.69476.ezmlm@cygwin.com>
2016-06-18 11:41 ` Mark McGregor
2016-06-18 20:04 ` 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] <1465820332.127780.ezmlm@cygwin.com>
2016-06-13 17:10 ` xdvipdfmx:fatal: This font using the "seac" command for accented characters Mark McGregor
2016-06-13 18:20 ` Ken Brown
2016-06-13 9:43 Mark McGregor
2016-06-13 14:31 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2016-06-13 0:30 Mark McGregor
2016-06-13 7:53 ` 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=b82c3f79-4271-ba3f-6aa7-6f6cdbb974b2@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).