From: Alan Braslau <braslau.list@comcast.net>
To: Hans Hagen <j.hagen@xs4all.nl>, Steffen Wolfrum <context@st.estfiles.de>
Cc: mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: hyphenate nothyphenated
Date: Wed, 30 Jun 2021 11:35:05 -0600 [thread overview]
Message-ID: <5c02a12f-e7bd-ce0c-46e9-ec37c8f3ebc3@comcast.net> (raw)
In-Reply-To: <3eb85388-555c-a25b-3f5e-76a001408c4d@xs4all.nl>
On 29/06/21 05:52, Hans Hagen wrote:
> well, you ask for nothyphenated; we could define
>
> \permanent\protected\def\-%
> {\begingroup
> \hyphenationmode\explicithyphenationmodecode\explicitdiscretionary
> \endgroup}
>
> i will ponder this
I believe that \- defines an *optional* hyphenation point.
Specifying nothyphenated should not hyphenate, even at optional points.
The author can otherwise use hyphenated and arrange to help the words
get hyphenated at certain points.
Perhaps a new "optional" hyphenation point macro can be added that would
have super-powers to override the align parameter. There would be no
surprises using such a feature.
--
Alan
___________________________________________________________________________________
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-06-30 17:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-29 10:06 Steffen Wolfrum
2021-06-29 11:52 ` Hans Hagen
2021-06-30 17:35 ` Alan Braslau [this message]
2021-06-30 18:25 ` Hans Hagen
2021-06-30 18:40 ` Alan Braslau
2021-06-30 18:50 ` Wolfgang Schuster
2021-06-30 22:12 ` Hans Hagen
2021-07-01 15:54 ` Alan Braslau
2021-07-01 15:57 ` Steffen Wolfrum
2021-07-01 16:05 ` Alan Braslau
2021-07-01 16:58 ` 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=5c02a12f-e7bd-ce0c-46e9-ec37c8f3ebc3@comcast.net \
--to=braslau.list@comcast.net \
--cc=context@st.estfiles.de \
--cc=j.hagen@xs4all.nl \
--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).