From: Hans Hagen <j.hagen@xs4all.nl>
To: Denis Maier <denismaier@mailbox.org>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: How do you deal with inappropriate ligatures?
Date: Wed, 14 Oct 2020 13:58:46 +0200 [thread overview]
Message-ID: <120593ab-e5ff-91c0-6a6f-600333be6b03@xs4all.nl> (raw)
In-Reply-To: <1cc24121-f666-b35f-6ab0-a32db48fe3c5@mailbox.org>
On 10/12/2020 11:09 PM, Denis Maier wrote:
> Am 12.10.2020 um 22:35 schrieb Hans Hagen:
>> On 10/12/2020 4:55 PM, Denis Maier wrote:
>>> Hi,
>>>
>>> with LuaLaTeX I used to use the selnolig package to disable
>>> inappropriate ligatures. With ConTeXt I have just inputted the list
>>> prepared by Hraban (based on a wordlist originating from selnolig),
>>> but then ran into a curious bug (?) with disappearing characters (see
>>> my posts from a couple of days ago). I'm now converting this list to
>>> the \blockligatures mechanism (instead of using \replaceword), which
>>> also has better kerning support due to Hans. When done, I'll of
>>> course share this on the Wiki if there's any need for this.
>>>
>>> Now I'm wondering how others deal with inappropriate ligatures. Do
>>> you just ignore them? Do there just so many.
>>>
>>> What do you think?
>> I played a bit with what we have and in a next upload you can do this:
>>
>> \startexceptions[de]
>> au{f-}{f}{ff}(f\zwnj f)asseyou block them on an ad-hoc basis, like
>>> whenever they occur? Do you use scripts to pre-process your files
>>> before typesetting? Do you just disable ligatures globally?
>>>
>>> I tend to think there must be an automatic way to deal with the most
>>> awkward cases. The problem is that
>> \stopexceptions
>>
>> \showglyphs
>>
>> \starttext
>>
>> auffasse
>>
>> then is like:
>>
>> au\discretionary{f-}{-f}{f\zwnj f}asse
>>
>> \stoptext
> Oh, that looks interesting. So that would essentially be implemented
> like hyphenation exceptions? Any drawbacks? Performance hit with large
> exception lists? Kerning?
in a next release a
\zwj block ligature, permit kern
\zwnj block ligature, also inhibit kern
for now, lmtx only
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:[~2020-10-14 11:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 14:55 Denis Maier
2020-10-12 20:35 ` Hans Hagen
2020-10-12 21:09 ` Denis Maier
2020-10-13 11:32 ` Hans Hagen
2020-10-14 11:58 ` 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=120593ab-e5ff-91c0-6a6f-600333be6b03@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=denismaier@mailbox.org \
--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).