From: Denis Maier <denismaier@mailbox.org>
To: mailing list for ConTeXt users <ntg-context@ntg.nl>,
Taco Hoekwater <taco@elvenkind.com>
Subject: Re: Hyphenation patterns
Date: Fri, 9 Oct 2020 09:01:41 +0200 [thread overview]
Message-ID: <3b87555b-8eea-00a1-34b2-795b5b1a661f@mailbox.org> (raw)
In-Reply-To: <61C3E342-5A9D-4279-9015-AB1A86522C4A@elvenkind.com>
Am 09.10.2020 um 08:57 schrieb Taco Hoekwater:
>
>> On 9 Oct 2020, at 08:52, Denis Maier <denismaier@mailbox.org> wrote:
>>
>> Am 08.10.2020 um 19:05 schrieb Henning Hraban Ramm:
>>> \starttext
>>>
>>> {EN: \en\hyphenatedcoloredword{applicable}}
>>>
>>> {DE: \de\hyphenatedcoloredword{applicable}}
>>>
>>> \stoptext
>>>
>> Wow, that's super helpful. The English pattern seems to be "ap-plic-a-ble"
>> According to Meriam-Webster it should just be "ap·pli·ca·ble".
>>
>> {EN: \en\hyphenatedcoloredword{obligate}} gives me "ob-lig-ate"
>> According to Meriam-Webster it should be "ob·li·gate".
>>
>> I've had a look at the files mentioned by Tomáš, but as these are not just wordlists I can not really tell what is happening.
>>
>> So, is that a bug?
> Not really. hyphenation patterns are a bit like applying JPEG compression to
> a dictionary. It makes the data size smaller by recognising patterns while
> ignoring outliers.
>
> Occasional errors are to be expected, which is why \hyphenation exists.
>
>
I see. I've noticed lang-us.lua has a list of exceptions in it:
["exceptions"]={
["characters"]="abcdefghijlmnoprstuyz",
["data"]="as-so-ciate as-so-ciates dec-li-na-tion oblig-a-tory
phil-an-thropic present presents project projects reci-procity
re-cog-ni-zance ref-or-ma-tion ret-ri-bu-tion ta-ble",
["length"]=168,
["n"]=14,
},
Would it be possible to add more exceptions to that list as they come
up? Or is that inappropriate?
Denis
___________________________________________________________________________________
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:[~2020-10-09 7:01 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-08 15:41 Denis Maier
2020-10-08 16:20 ` Tomas Hala
2020-10-08 17:05 ` Henning Hraban Ramm
2020-10-09 6:52 ` Denis Maier
2020-10-09 6:57 ` Taco Hoekwater
2020-10-09 7:01 ` Denis Maier [this message]
2020-10-09 12:48 ` Hans Hagen
2020-10-09 12:59 ` Denis Maier
2020-10-09 8:15 ` Henning Hraban Ramm
2020-10-09 8:59 ` Hans Hagen
2021-04-09 21:57 ` Arthur Rosendahl
2020-10-09 8:54 ` Hans Hagen
-- strict thread matches above, loose matches on Subject: below --
2010-05-23 23:22 hyphenation patterns Rogutės Sparnuotos
2010-05-23 21:38 ` Mojca Miklavec
[not found] ` <4BF9AE8A.6040405@gmail.com>
2010-05-24 0:16 ` Mojca Miklavec
2010-05-24 8:17 ` Hans Hagen
2010-05-24 18:52 ` rogutes
2010-05-24 14:50 ` luigi scarso
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=3b87555b-8eea-00a1-34b2-795b5b1a661f@mailbox.org \
--to=denismaier@mailbox.org \
--cc=ntg-context@ntg.nl \
--cc=taco@elvenkind.com \
/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).