From: Ken Brown <kbrown@cornell.edu>
To: cygwin@cygwin.com
Subject: Re: Please update fontspec
Date: Thu, 04 May 2017 13:05:00 -0000 [thread overview]
Message-ID: <572c90aa-512c-dffd-bc12-767b422a74e0@cornell.edu> (raw)
In-Reply-To: <482171493854219@web22m.yandex.ru>
On 5/3/2017 7:30 PM, Леон Майер wrote:
> Dear texlive maintainers, might I ask you to update fontspec to v2.6 or newer. Reason: a nasty bug, see https://tex.stackexchange.com/questions/367559/emph-in-theorem-with-unicode-math-and-amsthm
fontspec is part of the Cygwin texlive-collection-latexrecommended package.
Just rebuilding that package with an updated fontspec partially solves the
problem, in the sense that your test case compiles under xelatex and lualatex
and displays properly. But the compilation yields the following warning:
* fontspec warning: "tu-missing"
*
* The TU encoding seems to be missing; please update to the latest version of
* LaTeX2e.
In order to fix this properly without breaking other parts of TeX Live, I think
I should update all the texlive-collection-* packages to their latest upstream
releases in the now frozen TeX Live 2016.
I will do this, but it will take me a few days. In the meantime, I could make
the partial fix available to you if it would be of use.
Ken Brown
Cygwin's TeX Live maintainer
--
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:[~2017-05-04 13:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 23:30 Леон Майер
2017-05-04 13:05 ` Ken Brown [this message]
[not found] <1493929898.106197.ezmlm@cygwin.com>
2017-05-04 23:50 ` please " Leon Meier
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=572c90aa-512c-dffd-bc12-767b422a74e0@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).