From: Bruce Horrocks via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Bruce Horrocks <ntg@scorecrow.com>
Subject: Re: Contractions in ligature suppression word list
Date: Mon, 6 Jun 2022 19:19:10 +0100 [thread overview]
Message-ID: <51A30A15-ECED-497E-821E-EB97319FCCC0@scorecrow.com> (raw)
In-Reply-To: <CAANrE7o3idfEcz0YnU7F0s-fELPyyAYEe0z8-4+wK_3VSQkR3Q@mail.gmail.com>
> On 6 Jun 2022, at 06:37, Thangalin via ntg-context <ntg-context@ntg.nl> wrote:
>
> Attached are tweaked endings for words like "wolf" to include contracted endings, but they are being ignored. This makes for a minor inconsistency:
>
> wolfing -- no ligature
> wolfish -- no ligature
> wolfin -- no ligature (incorrect spelling, though)
> wolfin' -- ligature
>
> Any ideas? I tried adding various -in suffixes without luck:
>
> suffixes = [[
> in,
> in',
> in’,
> ing
> ]],
>
> See https://wiki.contextgarden.net/Ligatures#Word_suppression for an example usage.
>
> Thank you!
> <lang-en.llg>
I'm probably missing something here but...
1) The file you attached doesn't include the word "wolfing", nor "wolfin". I assume they need to be added into the f|i section? Wolfish *is* present so I'm not sure why it's being ignored unless there is an error being generated as a result of point (2) below, causing the whole file to be ignored.
2) Your suffixes list has comma separators - all the other word lists use whitespace as a separator.
3) Lastly, dumb question but... have you checked that you edited the right file? In my ConTeXt install there are two "lang-en.llg" files - one under <root>/context-osx-64/tex/texmf-context/tex/context/patterns/lmtx and the other under .../patterns/mkxl
—
Bruce Horrocks
Hampshire, UK
___________________________________________________________________________________
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
___________________________________________________________________________________
next prev parent reply other threads:[~2022-06-06 18:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-06 5:37 Thangalin via ntg-context
2022-06-06 18:19 ` Bruce Horrocks via ntg-context [this message]
2022-06-06 21:56 ` Thangalin via ntg-context
2022-06-06 22:18 ` Denis Maier via ntg-context
2022-06-07 0:13 ` Thangalin via ntg-context
2022-06-07 7:10 ` Denis Maier via ntg-context
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=51A30A15-ECED-497E-821E-EB97319FCCC0@scorecrow.com \
--to=ntg-context@ntg.nl \
--cc=ntg@scorecrow.com \
/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).