From: Rik Kabel <ConTeXt@rik.users.panix.com>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Soft-hyphen in Antykwa.
Date: Sun, 27 Jun 2021 16:16:47 -0400 [thread overview]
Message-ID: <d0dc0eab-e9a6-f40f-4e4c-367797c37a5e@rik.users.panix.com> (raw)
In-Reply-To: <b191e76d-f90a-7a42-9189-a9f3520ca55e@rik.users.panix.com>
On 6/27/2021 14:14, Rik Kabel wrote:
>
> On 6/27/2021 07:46, Hans Hagen wrote:
>> On 6/27/2021 12:38 AM, Rik Kabel wrote:
>>> All,
>>>
>>> In recent compilations of a document using Antykwa Torunska
>>> Condensed (in headings in the margin), I now have no hyphen at a
>>> word break, and see the following in the log:
>>>
>>> fonts > checking > char  (U+000AD) in font
>>> 'AntykwaTorunskaCond-Regular' with id 73: missing
>>>
>>> Is there a way to restore the hyphen that once appeared? (ConTeXt
>>> ver: 2021.06.25 22:49 LMTX).
>>
>> fixed in next upload
>>
> Thank you for the fix.
>
> For the record, I note that this is still a problem in MkIV.
>
And additionally, for the record, erasing the font cache and
regenerating got it back for MkIV (via --luatex).
--
Rik
___________________________________________________________________________________
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-06-27 20:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-26 22:38 Rik Kabel
2021-06-27 1:38 ` Rik Kabel
2021-06-27 11:46 ` Hans Hagen
2021-06-27 18:14 ` Rik Kabel
2021-06-27 20:16 ` Rik Kabel [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=d0dc0eab-e9a6-f40f-4e4c-367797c37a5e@rik.users.panix.com \
--to=context@rik.users.panix.com \
--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).