ntg-context - mailing list for ConTeXt users
 help / color / mirror / Atom feed
From: Arthur Reutenauer <arthur.reutenauer@normalesup.org>
To: Mailing list for ConTeXt users <ntg-context@ntg.nl>
Subject: Re: wrong hyphenation in ancient Greek?
Date: Mon, 15 Oct 2018 10:44:32 +0200	[thread overview]
Message-ID: <20181015084432.GA3839177@phare.normalesup.org> (raw)
In-Reply-To: <bda6d4cf-a2ca-4ea4-7a94-0d271d4b02ad@uni-bonn.de>

On Sat, Oct 13, 2018 at 11:05:01AM +0200, Thomas A. Schmitz wrote:
> You're right, this shouldn't happen. I tried in vain to find the culprit in
> lang-agr.lua and to see more with
> 
> \enabletrackers[hyphenator.visualize,hyphenator.steps,languages.patterns]
> 
>     failed. Arthur is the guru here, so maybe he has a suggestion?

  Ah, I was going for a title that inspired more awe, like “Emperor of
Hyphenation”, but guru will do for the time being :-)

  The reason you can’t find any obvious culprit is because you need to
look at the patterns that are missing: taking πράγματσς as an example,
the matching patterns are

	.π4 ά1 α1 ο1 4ς.

that allow a break after any vowel and prohibit breaks after the first
letter and before the last letter in the word (which is relevant because
\lefthyphenmin and \righthyphenmin are both set to 1).  Since these are
the only patterns that apply, the possible hyphenation points are thus

	πρά-γμα-τος

  Digging deeper in the pattern file, you’ll see that it takes quite
many two-consonant clusters into account, starting at line 267 of the
master file in the repository, with a comment “other divisable consonant
combinations” (https://github.com/hyphenation/tex-hyphen/blob/82e5651/hyph-utf8/tex/generic/hyph-utf8/patterns/tex/hyph-grc.tex#L267):

  2β1γ 2β1ζ 2β1θ 2β1κ ... 2γ1θ 2γ1κ 2γ1ξ 2γ1π ...

  You can see that γμ is not there (nor, of course, γν, which was
expected).  If it was, the pattern 2γ1μ would force the break πράγ-μα,
hence its absence leads me to believe that the breaks before γμ are
intentional.  I suggest you contact Dimitrios Filippou, the main author
of the patterns, to ask if it was somehow an oversight or if he was
following a different rule (email address at the top of the file linked
to, in a slightly obfuscated form).

	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
___________________________________________________________________________________

  parent reply	other threads:[~2018-10-15  8:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-13  8:05 Pablo Rodriguez
2018-10-13  9:05 ` Thomas A. Schmitz
2018-10-13  9:49   ` Pablo Rodriguez
2018-10-13 12:32     ` Pablo Rodriguez
2018-10-15  8:48     ` Arthur Reutenauer
2018-10-15  8:44   ` Arthur Reutenauer [this message]
2018-10-15 13:04     ` Henning Hraban Ramm
2018-10-15 14:52     ` Pablo Rodriguez
2018-10-30 14:42 ` Arthur Reutenauer

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=20181015084432.GA3839177@phare.normalesup.org \
    --to=arthur.reutenauer@normalesup.org \
    --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).