From: Rik <rik@panix.com>
To: ntg-context@ntg.nl
Subject: Re: Hyphens missing (again) with setupbackend[export
Date: Mon, 24 Jul 2017 07:54:26 -0400 [thread overview]
Message-ID: <7b84eb3e-ffa6-4e15-dfaa-e058dffb06cf@panix.com> (raw)
In-Reply-To: <2ae2786d-901f-7e42-fc2b-cf93b0ac5897@wxs.nl>
On 2017-07-24 05:51, Hans Hagen wrote:
> On 7/24/2017 3:51 AM, Rik Kabel wrote:
>> Aditya came across this in 2011 ([NTG-context] export kills hyphen
>> symbol
>> <https://www.mail-archive.com/ntg-context@ntg.nl/msg58460.html>)[1]
>> with the Fontin font. It wasn’t answered then. It is back if it ever
>> left.
>>
>> Here is an example:
>>
>> \definefontfamily
>> [TestFont]
>> [rm]
>> [Antykwa Torunska Cond]
>> \setupbodyfont
>> [TestFont]
>> \setupbackend
>> [export=maybe]% or yes, or no, or ...
>> \setuppapersize
>> [A7]
>> \starttext
>> \input ward
>> \stoptext
>>
>> If the \setupbackend statement is removed, or an invalid key is used,
>> all is well. It fails with a valid key and any value for that key.
>>
>> I am experiencing the problem of missing hyphens with this font even
>> without \setupbackend, but cannot yet construct a working example.
> wipe your font cache, add this to the top of your file
>
> \enabledirectives[otf.checksofthyphen]
Thank you. That resolves it.
Is this an issue for all fonts that are missing a soft hyphen glyph at
x00A0?
--
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
___________________________________________________________________________________
next prev parent reply other threads:[~2017-07-24 11:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-24 1:51 Rik Kabel
2017-07-24 9:51 ` Hans Hagen
2017-07-24 11:54 ` Rik [this message]
2017-07-24 13:24 ` Hans Hagen
2017-07-26 16:56 ` Henning Hraban Ramm
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=7b84eb3e-ffa6-4e15-dfaa-e058dffb06cf@panix.com \
--to=rik@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).