From: Arthur Rosendahl <arthur.reutenauer@normalesup.org>
To: Hans Hagen <j.hagen@xs4all.nl>
Cc: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: Ligature suppression word list
Date: Thu, 8 Apr 2021 21:37:22 +0200 [thread overview]
Message-ID: <20210408193722.f54v3xf34ifzvtb5@phare.normalesup.org> (raw)
In-Reply-To: <4151376e-18ad-101f-57ec-210bf39124af@xs4all.nl>
On Sat, Apr 03, 2021 at 06:02:10PM +0200, Hans Hagen wrote:
> german is just an example, dutch has some specific things, and i bet other
> languages have their demands so my aim is some general mechanism
I appreciate that, but if you want to have data of sufficiently good
quality to use this mechanism for individual languages, you need to
invest a *lot* of time for each one of them. German is one of the very
few languages I know of that has an active group of people working to
produce that data, the “Trennmuster people”, as Mojca calls them ;-)
Their word list supports many fine points of typography, even those that
few programs can use, for example weighted hyphenation. Ligature
prevention came in as a side project.
Dutch, by contrast, does not seem so well served: the OpenTaal group
is dormant and no longer offers the hyphenated word list that was once
available (that was already the case five years ago). The most relevant
page I find: https://www.opentaal.org/projecten/woordafbreking is from
2009. There have apparently been recent updates by a single person (who
incidentally sometimes contributes to the German hyphenation working
group), but they’re rather generic.
Best,
Arthur
___________________________________________________________________________________
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-04-08 19:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-03 15:06 denis.maier
2021-04-03 15:20 ` Arthur Rosendahl
2021-04-03 16:02 ` Hans Hagen
2021-04-08 19:37 ` Arthur Rosendahl [this message]
2021-04-08 20:51 ` Hans Hagen
2021-04-03 15:58 ` Hans Hagen
2021-04-06 14:59 ` denis.maier
2021-04-06 15:03 ` denis.maier
2021-04-03 16:03 ` Hans Hagen
2021-04-03 16:30 ` Thangalin
2021-04-03 16:43 ` Hans Hagen
2021-04-03 19:21 ` Thangalin
2021-04-03 16:42 ` Hans Hagen
[not found] <mailman.248.1617745098.1120.ntg-context@ntg.nl>
2021-04-07 18:19 ` rha17
2021-04-08 8:52 ` denis.maier
2021-04-12 15:52 ` denis.maier
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=20210408193722.f54v3xf34ifzvtb5@phare.normalesup.org \
--to=arthur.reutenauer@normalesup.org \
--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).