ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
	denis.maier@ub.unibe.ch
Subject: Re: Another bug with ligature-blocking?
Date: Wed, 24 Mar 2021 17:41:58 +0100	[thread overview]
Message-ID: <41fe5a10-1538-825e-7c8c-20599ba504ae@xs4all.nl> (raw)
In-Reply-To: <5fa86622f3034007a5b42548eed97b90@ub.unibe.ch>

On 3/24/2021 4:48 PM, denis.maier@ub.unibe.ch wrote:

> \definefontfamily[times][rm][Times New Roman]
don't assume beforehand that something that doesn't work as expected is 
a bug

the font just has no ligatures defined which you can remedy (in this 
cae) with because it does have the glyphs

\startluacode
     fonts.handlers.otf.addfeature {
         name = "moreligatures",
         type = "ligature",
         data = {
             ['ff'] = { "f", "f" },
             ['fi'] = { "f", "i" },
             ['fl'] = { "f", "l" },
         }
     }
\stopluacode


\blockligatures[begrif:fl:ich]
\definefontfeature[default][default][dlig=yes,liga=yes,moreligatures=yes]
\definefontfamily[times][rm][Times New Roman]
\definefontfamily[termes[rm][TeX Gyre Termes]

\definefontfeature[default:block][default][blockligatures=yes]

\starttext

{\switchtobodyfont[times] \definedfont[Serif*default]        begrifflich 
ff fi fl\blank
                           \definedfont[Serif*default:block] 
begrifflich ff fi fl\blank}
{\switchtobodyfont[termes]\definedfont[Serif*default]        begrifflich 
ff fi fl\blank
                           \definedfont[Serif*default:block] 
begrifflich ff fi fl\blank}

\stoptext



-----------------------------------------------------------------
                                           Hans Hagen | PRAGMA ADE
               Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
        tel: 038 477 53 69 | www.pragma-ade.nl | 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://context.aanhet.net
archive  : https://bitbucket.org/phg/context-mirror/commits/
wiki     : http://contextgarden.net
___________________________________________________________________________________

  reply	other threads:[~2021-03-24 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-24 15:48 denis.maier
2021-03-24 16:41 ` Hans Hagen [this message]
2021-03-24 19:20   ` denis.maier
2021-03-24 21:21     ` 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=41fe5a10-1538-825e-7c8c-20599ba504ae@xs4all.nl \
    --to=j.hagen@xs4all.nl \
    --cc=denis.maier@ub.unibe.ch \
    --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).