From: Hans Hagen <pragma@wxs.nl>
To: ntg-context@ntg.nl
Subject: Re: Strange problem with EBGaramond st ligature and 20150901 beta
Date: Fri, 4 Sep 2015 11:19:45 +0200 [thread overview]
Message-ID: <55E96231.6040607@wxs.nl> (raw)
In-Reply-To: <55E8B5EE.6030906@rik.users.panix.com>
On 9/3/2015 11:04 PM, Rik Kabel wrote:
> Please help with the strangest problem I have come across.
>
> The following document fails (does not complete, hangs) when the
> following conditions hold:
>
> * ConTeXt ver: 2015.09.01 11:10 MKIV beta fmt: 2015.9.3 int:
> english/english
> * \mainlanguage[en] or fr
> * Font EBGaramond otf from EBGaramond-0.016.zip
> https://bitbucket.org/georgd/eb-garamond/downloads
> * Font features clig and hlig
> * Font style \it or \sl
> * Text string (among others) astro istar istra ister istor istro istur
>
> The problem is the same with \usemodule[newotf] and without.
>
> The problem does not occur with:
>
> * ConTeXt ver: 2015.08.30 17:07 MKIV beta fmt: 2015.8.30 int:
> english/english.
> * \mainlanguage la or de.
> * \tf or \sc or \bd (there is no bold in the font).
>
> The issue appears to be related to the st ligature, but only in
> conjunction with some other letters.
more in conjunction with hyphenation
> Can somebody else reproduce the problem. For the record, this is running
> on Windows 10 Pro 64-bit.
>
> The problem document:
>
> \definefontfeature [ff:ebg][default][
> clig=yes,hlig=yes, %% 1 %%
> ]
> \definefontfamily [mainface][serif][ebgaramond]
> [features=ff:ebg]
> \setupbodyfont [mainface]
> % \mainlanguage[la] %% 2 %%
> \mainlanguage[fr] %% 3 %%
> \starttext
> \it %% 4 %%
> % \tf %% 5 %%
> astro %% 6 %%
> % aStro %% 7 %%
> % asTor %% 8 %%
> \stoptext
There is indeed a loop there. I uploaded a fixed version. Recently Kai
and I have upgraded the fonthandler with respect to ligature
(contextual) and kerning which is sort of messy given the different
approaches that font use for dealing with ligatures. This is normally no
issue but interferes badly with hyphenation.
The new font handler (m-newotf) is also updated and has a bit better
performance (and I have a local experimental variant that is again
somewhat faster (15%) but that depends on a few more pending luatex
helpers).
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | voip: 087 875 68 74 | www.pragma-ade.com
| www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
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://tex.aanhet.net
archive : http://foundry.supelec.fr/projects/contextrev/
wiki : http://contextgarden.net
___________________________________________________________________________________
prev parent reply other threads:[~2015-09-04 9:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 21:04 Rik Kabel
2015-09-04 9:19 ` Hans Hagen [this message]
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=55E96231.6040607@wxs.nl \
--to=pragma@wxs.nl \
--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).