From: Thangalin via ntg-context <ntg-context@ntg.nl>
To: Bruce Horrocks <ntg@scorecrow.com>
Cc: Thangalin <thangalin@gmail.com>,
mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Contractions in ligature suppression word list
Date: Mon, 6 Jun 2022 14:56:00 -0700 [thread overview]
Message-ID: <CAANrE7p_rDPR7P66Ez1FGJswbAjtowfsN6otp6jutfF5q9io+g@mail.gmail.com> (raw)
In-Reply-To: <51A30A15-ECED-497E-821E-EB97319FCCC0@scorecrow.com>
[-- Attachment #1.1: Type: text/plain, Size: 1115 bytes --]
Thanks for the response, Bruce.
1) The file you attached doesn't include the word "wolfing", nor "wolfin".
> I assume they need to be
The suffixes section accounts for this. Wolfing and wolfish both suppress
the ligature correctly.
I removed the comma separators, good catch. No difference, though.
Looks like I edited
/opt/context/tex/texmf-context/tex/context/patterns/mkxl/lang-en.llg
instead of the LMTX file. SMH.
I've now tried both files, lmtx and mkxl:
suffixes = [[
in
in'
in’
ing
]],
Wolfish works fine, the ligature is suppressed as expected. Wolfing,
wolfin, and wolfin' aren't suppressed. I'd have thought that defining the
word "wolf" with a suffix of "ing" (and variations thereof) would suppress
ligatures at the suffix boundary?
Maybe that's not the case. If so, then it means having to define all the
*f-ing words (heh) a few times for the different suffixes (in', in’, and
ing), which seems to defeat the purpose of separating suffixes?
Help is appreciated.
[-- Attachment #1.2: Type: text/html, Size: 2416 bytes --]
[-- Attachment #2: Type: text/plain, Size: 493 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://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-06-06 21:56 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
2022-06-06 21:56 ` Thangalin via ntg-context [this message]
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=CAANrE7p_rDPR7P66Ez1FGJswbAjtowfsN6otp6jutfF5q9io+g@mail.gmail.com \
--to=ntg-context@ntg.nl \
--cc=ntg@scorecrow.com \
--cc=thangalin@gmail.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).