From: Hans Hagen <j.hagen@xs4all.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
"Jan U. Hasecke" <juh+ntg-context@mailbox.org>
Subject: Re: endash emdash
Date: Wed, 23 Jun 2021 09:36:56 +0200 [thread overview]
Message-ID: <c2043d30-c686-3a67-cc95-97be70eddeac@xs4all.nl> (raw)
In-Reply-To: <5637cf0b-92b8-651e-1e85-9dea7d5108ba@mailbox.org>
On 6/23/2021 7:21 AM, Jan U. Hasecke wrote:
>
> Am 23.06.21 um 07:11 schrieb Jan U. Hasecke:
>> Dear all,
>>
>> I am completely lost with a ridicously small problem.
>
> This was a self motivation. ;-)
>
>> \starttext
>>
>> --
>>
>> ---
>>
>> –
>>
>> \stoptext
>>
>>
>> ConTeXt creates two endash rules and a very long dash in the middle,
>> as I expected.
>>
>> But in my project I always get the plain source chars.
>
> The culprit was
>
> \setbreakpoints[compound]
>
> Any idea why this command gives such an effect?
yes, so i'll fix it
Hans
-----------------------------------------------------------------
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
___________________________________________________________________________________
prev parent reply other threads:[~2021-06-23 7:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-23 5:11 Jan U. Hasecke
2021-06-23 5:21 ` Jan U. Hasecke
2021-06-23 7:36 ` Hans Hagen [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=c2043d30-c686-3a67-cc95-97be70eddeac@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=juh+ntg-context@mailbox.org \
--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).