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 18:20:00 -0000 [thread overview]
Message-ID: <b00a3dc0-2241-1ba9-6967-9d963f1e321b@cornell.edu> (raw)
In-Reply-To: <cd2b8df2-9aa7-9e68-25ae-7d8da5119efe@gmx.de>
On 6/13/2016 9:28 AM, Mark McGregor wrote:
> ---- Ken wrote:
>> Would this solution affect the compilation processes of lualatex
>> (which does compile the file in question) or pdflatex?
>
> No. lualatex and pdftex don't use fontconfig.
>
> By the way, I've filed a bug report about this problem:
>
> https://sourceforge.net/p/xetex/bugs/131/
> ----
>
> Ken, thank you!
> (You might probably have more experience with XeTeX than me. Is XeTeX
> dying? The last bugfix was in March, months ago, and apart from A.R.
> nobody seems to work on it anyway...)
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.
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 14:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1465820332.127780.ezmlm@cygwin.com>
2016-06-13 17:10 ` Mark McGregor
2016-06-13 18:20 ` 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
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=b00a3dc0-2241-1ba9-6967-9d963f1e321b@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).