From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: +ssty leads to wrong parentheses with stix2math fonts.
Date: Wed, 12 Jul 2017 11:41:37 +0200 [thread overview]
Message-ID: <1sgblygcpyfbv$.dlg@nililand.de> (raw)
In-Reply-To: <6d3e451d-cd4f-9a26-fe45-e549d103962f@wxs.nl>
Am Wed, 12 Jul 2017 11:33:22 +0200 schrieb Hans Hagen:
>> (But I don't know if it is really a bug in the font as xelatex with
>> harfbuzz has no problems.)
> I don't know what harfbuzz does but the font definitely does some ssty
> mapping to rather simple glyphs with no extensible parts so basically
> it's a font bug. If xetex catches it, find but it's still a bug. Anyway,
> the previous mail with the patch checks for al three 'missing' fields so
> this is basically the same issue. If not, let me know.
I will check the code in the evening (and also try out if I can
inject it in luaotfload).
But on the whole I tried to avoid to work around bugs too much - in
the end one pay with too complicated code. If it is a font bug then
one should try to resolve the issue there.
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2017-07-12 9:41 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-12 8:00 Ulrike Fischer
2017-07-12 9:01 ` Ulrike Fischer
2017-07-12 9:33 ` Hans Hagen
2017-07-12 9:41 ` Ulrike Fischer [this message]
2017-07-14 17:18 ` Ulrike Fischer
2017-07-14 17:35 ` Hans Hagen
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='1sgblygcpyfbv$.dlg@nililand.de' \
--to=news3@nililand.de \
--cc=ntg-context@ntg.nl \
/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 NNTP newsgroup(s).