From: Pablo Rodriguez via ntg-context <ntg-context@ntg.nl>
To: Denis Maier via ntg-context <ntg-context@ntg.nl>
Cc: Pablo Rodriguez <oinos@gmx.es>
Subject: Re: Hyphenation in multi-language projects
Date: Wed, 14 Sep 2022 19:40:53 +0200 [thread overview]
Message-ID: <62902e59-4e5b-7b7b-3ca7-54008803c6f6@gmx.es> (raw)
In-Reply-To: <5934b5da91c34085a68bdb3d0e9f896d@unibe.ch>
On 9/14/22 16:54, Denis Maier via ntg-context wrote:
>> [...]
>> Isn’t there a way to list exceptions that will work in *all*
>> languages?
>
> I thought that \hyphenation would work like that, or \startexceptions
> without a language code. Apparently that's not the case.
\hyphenation only works for the given language:
\hyphenation{macOS}
\starttext
\startTEXpage[offset=1em]
\currentlanguage:
\hyphenatedword{macOS}
\startlanguage[fr]
\currentlanguage:
\hyphenatedword{macOS}
\stoplanguage
\stopTEXpage
\stoptext
But I’d say that \registerhyphenationexception[macOS] was
language-independent for me some time ago. (Now it seems to work like
\hyphenation.)
In any case, \registerhyphenationexception seems to have issues with
ligatures:
\setuphyphenation[method=traditional]
\registerhyphenationexception[steff-en macOS]
\registerhyphenationexception[it][steff-en macOS]
\starttext
\startTEXpage[offset=1em]
\currentlanguage:
\hyphenatedword{steffen macOS}
\startlanguage[it]
\currentlanguage:
\hyphenatedword{steffen macOS}
\stoplanguage
\stopTEXpage
\stoptext
If there isn’t a command to add language-indepented hyphenation
exceptions or patterns, one for proper names (for people, products or
companies) would be really useful.
Just in case Hans or other wizard may take a look at this,
Pablo
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / https://www.ntg.nl/mailman/listinfo/ntg-context
webpage : https://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : https://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2022-09-14 17:40 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 15:11 Steffen Wolfrum via ntg-context
2022-09-12 15:45 ` Denis Maier via ntg-context
2022-09-14 6:35 ` Max Chernoff via ntg-context
2022-09-14 6:40 ` Steffen Wolfrum via ntg-context
2022-09-14 6:50 ` Max Chernoff via ntg-context
2022-09-14 7:19 ` Denis Maier via ntg-context
2022-09-14 14:44 ` Steffen Wolfrum via ntg-context
2022-09-14 14:54 ` Denis Maier via ntg-context
2022-09-14 17:38 ` Steffen Wolfrum via ntg-context
2022-09-14 17:40 ` Pablo Rodriguez via ntg-context [this message]
2022-10-24 13:08 ` Fwd: " Steffen Wolfrum via ntg-context
2022-10-24 15:09 ` Hans Hagen via ntg-context
2022-10-24 16:15 ` Pablo Rodriguez via ntg-context
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=62902e59-4e5b-7b7b-3ca7-54008803c6f6@gmx.es \
--to=ntg-context@ntg.nl \
--cc=oinos@gmx.es \
/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).