From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: Losing a character during line break at a hyphen
Date: Sun, 22 Aug 2021 11:27:30 +0200 [thread overview]
Message-ID: <b2127561-5d27-2175-64ab-5999b6a2e7ed@xs4all.nl> (raw)
In-Reply-To: <0F332468-ABB9-4340-BBB1-7A88A02FE37D@scorecrow.com>
On 8/22/2021 1:27 AM, Bruce Horrocks via ntg-context wrote:
>
>
>> On 22 Aug 2021, at 00:12, Bruce Horrocks via ntg-context <ntg-context@ntg.nl> wrote:
>>
>> Not sure whether this is a ligature problem or a hyphenation problem or both!
>
> Smaller MWE - it's not hyphenation:
>
> \starttext Diffe \stoptext
>
> gives "Dife".
if you're in a hurry you can patch font-ots.lmt, line 922
ligature = ligature.ligature
else
ligature = ligature.ligature
end
and remake the format
-----------------------------------------------------------------
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
___________________________________________________________________________________
next prev parent reply other threads:[~2021-08-22 9:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-21 23:12 Bruce Horrocks via ntg-context
2021-08-21 23:27 ` Bruce Horrocks via ntg-context
2021-08-22 3:59 ` Richard Mahoney via ntg-context
2021-08-22 9:27 ` Hans Hagen via ntg-context [this message]
2021-08-22 13:11 ` Bruce Horrocks 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=b2127561-5d27-2175-64ab-5999b6a2e7ed@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).