ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
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 12:40:59 -0600	[thread overview]
Message-ID: <4b10524d-b1e2-ecee-0ec9-d52c0b6c1cd5@comcast.net> (raw)
In-Reply-To: <3b85179f-55f7-7124-caa0-14bd6549aaed@xs4all.nl>

On 30/06/21 12:25, Hans Hagen wrote:
> On 6/30/2021 7:35 PM, Alan Braslau wrote:
>> 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.
> We can't use \= unless we drop the \= being macros (anyone using that?)
> 
> We can also use \+ which currently is just "+" because it needs some 
> value (sometimes it gets a local meaning).
> 
> So here is something to ponder:
> 
> \pushoverloadmode \unprotect
> 
>      \permanent\protected\def\superexplicitdiscretionary
>        {\begingroup
>         \hyphenationmode\explicithyphenationmodecode\explicitdiscretionary
>         \endgroup}
> 
>      \aliased\let\lang_explicit_discretionary_nop\explicitdiscretionary
> 
>      \permanent\protected\def\lang_explicit_discretionary_yes-%
>        {\superexplicitdiscretionary}
> 
>      \permanent\protected\def\-%
> 
> {\doifelsenextcharcs-\lang_explicit_discretionary_yes\lang_explicit_discretionary_nop} 
> 
> 
>      \protect \popoverloadmode
> 
>      \nohyphens \hsize 1mm
> 
>      test\-test \par test\--test
> 
> \stoptext

\= macron accent (bar) should not be changed.

\-- is a good suggestion, like insisting, and should not get confused 
with -- (en dash).


-- 
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
___________________________________________________________________________________

  reply	other threads:[~2021-06-30 18:40 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
2021-06-30 18:25     ` Hans Hagen
2021-06-30 18:40       ` Alan Braslau [this message]
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=4b10524d-b1e2-ecee-0ec9-d52c0b6c1cd5@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).