From: "Mark McGregor" <mark.mcgregor@gmx.de>
To: cygwin@cygwin.com
Subject: Re: xdvipdfmx:fatal: This font using the "seac" command for accented characters...
Date: Sat, 18 Jun 2016 11:41:00 -0000 [thread overview]
Message-ID: <trinity-4f46c890-4f51-4e11-a248-0acf33eebf50-1466200480864@3capp-gmx-bs03> (raw)
In-Reply-To: <1465890352.69476.ezmlm@cygwin.com>
----Ken wrote:
> 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.
----
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!
Mark.
--
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 parent reply other threads:[~2016-06-17 21:54 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 [this message]
2016-06-18 20:04 ` Ken Brown
[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=trinity-4f46c890-4f51-4e11-a248-0acf33eebf50-1466200480864@3capp-gmx-bs03 \
--to=mark.mcgregor@gmx.de \
--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).