From: Ulrike Fischer <news3@nililand.de>
To: ntg-context@ntg.nl
Subject: Re: em-dash ligature is converted to en-dash in the generic fontloader
Date: Mon, 25 Feb 2019 15:55:16 +0100 [thread overview]
Message-ID: <pcr47lscpkbc.dlg@nililand.de> (raw)
In-Reply-To: <0f1fd819-0955-57f8-5f08-8cd6c702bb36@xs4all.nl>
Am Sat, 23 Feb 2019 17:11:12 +0100 schrieb Hans Hagen:
> because <disc -> followed by -- is pretty obscure ... a replace could be
> seen as --- and when hyphenated as - -- and such ... it's about time
> that texies start using the proper unicode symbols instead of these
> funny ligatures
well the problem with the proper unicode symbols is that at first
they are not so easy to input (that could be handled by the editor)
and that they are not so visible. - - — look quite the same in my
editor, even more if the screen is not so large and when my eyes
tire. If -- wouldn't work I would resort to a command like \ndash
instead only to get a better visual clue what's in the document.
But regardless from the input method. How can one enable a line
break after an em-dash when \automichyphenmode is 1? The only way I
found is to explicitly insert a penalty:
\starttext
\hsize=2pt
dash---\penalty1 dash
dash—\penalty1 dash
\stoptext
--
Ulrike Fischer
http://www.troubleshooting-tex.de/
___________________________________________________________________________________
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:[~2019-02-25 14:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-23 12:50 Ulrike Fischer
2019-02-23 14:55 ` Hans Hagen
2019-02-23 15:30 ` Ulrike Fischer
2019-02-23 16:11 ` Hans Hagen
2019-02-25 14:55 ` Ulrike Fischer [this message]
2019-02-25 20:45 ` Henri Menke
2019-02-26 1:14 ` Rik Kabel
2019-02-25 20:46 ` Henri Menke
2019-02-28 11:38 Marcel Krüger
2019-03-01 10:17 ` Hans Hagen
2019-03-01 11:29 ` Marcel Krüger
2019-03-01 12:09 ` Hans Hagen
2019-03-01 12:15 ` Ulrike Fischer
2019-03-01 13:49 ` Hans Hagen
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=pcr47lscpkbc.dlg@nililand.de \
--to=news3@nililand.de \
--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).