From: Hans Hagen <j.hagen@xs4all.nl>
To: denis.maier@ub.unibe.ch, ntg-context@ntg.nl
Subject: Re: Another bug with ligature-blocking?
Date: Wed, 24 Mar 2021 22:21:28 +0100 [thread overview]
Message-ID: <600c4671-94ec-cd8b-7fe6-7142e884e93f@xs4all.nl> (raw)
In-Reply-To: <ac8993ba768a45fea70e08cc64533354@ub.unibe.ch>
On 3/24/2021 8:20 PM, denis.maier@ub.unibe.ch wrote:
>> -----Ursprüngliche Nachricht-----
>> Von: Hans Hagen <j.hagen@xs4all.nl>
>> Gesendet: Mittwoch, 24. März 2021 17:42
>> An: mailing list for ConTeXt users <ntg-context@ntg.nl>; Maier, Denis
>> Christian (UB) <denis.maier@ub.unibe.ch>
>> Betreff: Re: [NTG-context] Another bug with ligature-blocking?
>>
>> 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
>
> Sorry, Hans, I didn't mean to be offensive.
it has more to do with searching for solutions using the subjects of
mail ... in which case 'bug' is not a good one
>>
>> 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
>>
>
> I'm not sure I understand what is going on here. I thought \blockligatures simply means that instead of a ligature you'll have the regular glyphs in the output. Is that not correct?
sure but times doesn't have these ligatures (it has the shapes but not
the features)
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-03-24 21:21 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
2021-03-24 19:20 ` denis.maier
2021-03-24 21:21 ` 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=600c4671-94ec-cd8b-7fe6-7142e884e93f@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).