[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #61919] wrong(?) hyphenation (word division) of "material" (for "FO
From: |
G. Branden Robinson |
Subject: |
[bug #61919] wrong(?) hyphenation (word division) of "material" (for "FOR-RELEASE")) |
Date: |
Wed, 26 Jan 2022 02:53:33 -0500 (EST) |
Update of bug #61919 (project groff):
Category: General => Core
Item Group: Documentation => Incorrect behaviour
Status: None => Duplicate
Open/Closed: Open => Closed
Summary: Wrong(?) hyphenation (word division) of "material"
(for "FOR-RELEASE")) => wrong(?) hyphenation (word division) of "material"
(for "FOR-RELEASE"))
_______________________________________________________
Follow-up Comment #2:
Thanks, Dave. I thought this stuff sounded familiar.
Not only is the subject of this ticket subsumed by existing bug #57594, but
the exact issue, down to the very word, that Bjarni raises was addressed in a
commit message and ChangeLog entry.
commit b2284ab01d2d87507f3bcbd7de2a081efb6528a6
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date: Sun Jul 11 00:50:27 2021 +1000
Update English hyphenation patterns.
* NEWS: Add item.
* tmac/hyphen.en: Update file using `hyph-en-us.tex` patterns file from
the TeX hyph-utf8 project.
* tmac/hyphenex.en: Remove explicit hyphenations for words that no
longer require them when using the new patterns. Add one item scraped
from an erratum comment in hyphen.en ("dem-o-crat").
The new patterns likely _will_ change the automatic hyphenation break
points of your English documents. Here is a sample of affected words
found within groff's own documentary corpus.
OLD NEW
=== ===
ar‐range‐ment arrange‐ment
col‐umns columns
con‐struc‐ted con‐structed
cus‐tom‐ized cus‐tomized
def‐i‐ni‐tions de‐f‐i‐n‐i‐tions
der‐i‐va‐tions de‐riva‐tions
hy‐phen‐a‐tion hy‐phen‐ation
ma‐te‐rial ma‐te‐r‐ial
Mi‐cro‐soft Mi‐crosoft
pipe‐lines pipelines
post‐pro‐ces‐sors post‐proces‐sors
pro‐cessed processed
pro‐cesses processes
spa‐ces spaces
Wer‐ner Werner
Partially addresses <https://savannah.gnu.org/bugs/?57594>.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?61919>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/