ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Rik Kabel <context@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Strange problem with EBGaramond st ligature and 20150901 beta
Date: Thu, 3 Sep 2015 17:04:46 -0400	[thread overview]
Message-ID: <55E8B5EE.6030906@rik.users.panix.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1856 bytes --]

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.

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


-- 
Rik

[-- Attachment #1.2: Type: text/html, Size: 3297 bytes --]

[-- Attachment #2: Type: text/plain, Size: 485 bytes --]

___________________________________________________________________________________
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
___________________________________________________________________________________

             reply	other threads:[~2015-09-03 21:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-03 21:04 Rik Kabel [this message]
2015-09-04  9:19 ` 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=55E8B5EE.6030906@rik.users.panix.com \
    --to=context@rik.users.panix.com \
    --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).