From: Hans Hagen via ntg-context <ntg-context@ntg.nl>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>
Cc: Hans Hagen <j.hagen@xs4all.nl>
Subject: Re: manual hyphenation LMTX
Date: Tue, 28 Sep 2021 11:49:33 +0200 [thread overview]
Message-ID: <6988d088-76d6-5369-9277-f9ed482f4f65@xs4all.nl> (raw)
In-Reply-To: <05b36126-b70d-13a8-affb-7feb2f998e20@gmail.com>
On 9/28/2021 2:57 AM, jbf via ntg-context wrote:
> I may have seen a response to this at some stage in the list, but I
> cannot find it.
>
> \- works for manual hyphenation in Mkiv but not (for me at least) in LMTX.
>
> My general setting is \setupalign [hz,
> nothyphenated,stretched,verytolerant] because I am typesetting a book
> for visually-impaired readers using Atkinson Hyperlegible, especially
> developed by the Braille Foundation. In general, hyphenation is not
> recommended for the visually-impaired, but just occasionally it becomes
> necessary.
>
> Is there a reason for LMTX is not accepting \- or is there another way
> to achieve it in LMTX?
just a side effect of more control (in the engine) and therefore also in
lmtx
we can do something like this:
\unprotect
\def\v!explicit{explicit}
\permanent\protected\def\doexplicithyphens{\hyphenationmode\bitwiseflip\hyphenationmode
\explicithyphenationcode}
\permanent\protected\def\noexplicithyphens{\hyphenationmode\bitwiseflip\hyphenationmode-\explicithyphenationcode}
\defcsname\??aligncommand\v!explicit\endcsname{\toksapp\t_spac_align_collected{\nohyphens\doexplicithyphens}}
\protect
\starttext
{ \setupalign [hz,nothyphenated,stretched,verytolerant]
\dorecurse{100}{test\-}test \par }
{ \setupalign [hz,explicit,stretched,verytolerant]
\dorecurse{100}{test\-}test \par }
\stoptext
if we can agree on the keyword ...
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-09-28 9:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-28 0:57 jbf via ntg-context
2021-09-28 9:49 ` Hans Hagen via ntg-context [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=6988d088-76d6-5369-9277-f9ed482f4f65@xs4all.nl \
--to=ntg-context@ntg.nl \
--cc=j.hagen@xs4all.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).