Follow-up Comment #12, bug #66054 (group groff): [comment #11 comment #11:] > [comment #9 comment #9:] > > Running with _groff_ 1.23 adds a different confounding factor. > > I'm not sure how your first output of the word got hyphenated under 1.23...
It wasn't. I rewound the source tree to right before the commit documented in
comment #1.
> > Specifically this:
> >
> > commit f66f771c22690f5f0e6dec3c9a53adb7243bb7fe
> > Author: G. Branden Robinson <g.branden.robin...@gmail.com>
> > Date: Thu Aug 1 18:16:19 2024 -0500
>
> ...but I am sure this commit from a year after 1.23's release can't be any
kind of factor in a 1.23 installation.
The point I was trying to make is that more than one thing (moving `hcode`
invocations from one macro file to another) has changed, and that one seemed
squarely on point.
> The point of using 1.23 rather than anything more recent was to show the
sequence:
> 0 The first output of the word, before the document does any .hcode
fiddling, has no break points.
> 0 After telling groff to treat é like e, the word gets broken.
> 0 After attempting to "undo" this mapping using .tr-like syntax, the word
still breaks as it did after the first .hcode, not as it did before it.
I don't know what I'm supposed to do about this. In _groff_ 1.23.0 you
couldn't unset a character's hyphenation code, as far as I know. You could
change it to some other nonzero value, but not ever put it back to zero.
$ iconv -f latin1 EXPERIMENTS/resume-dave-latin-1-gbr.groff
.ll 1n
r\['e]sum\['e]
.hcode é e \" sets up a mapping
r\['e]sum\['e]
.hcode é é \" undoes that mapping, maybe?
r\['e]sum\['e] \" ... what happens now?
.hcode é $ \" also undoes that mapping
r\['e]sum\['e] \" ... but only in Git HEAD
$ ~/groff-stable/bin/groff -W break -T utf8
EXPERIMENTS/resume-dave-latin-1-gbr.groff | cat -s
résumé
ré‐
sumé
ré‐
sumé
ré‐
sumé
$ ~/groff-HEAD/bin/groff -W break -T utf8
EXPERIMENTS/resume-dave-latin-1-gbr.groff | cat -s
ré‐
sumé
ré‐
sumé
ré‐
sumé
résumé
Oh, I see. I thought the 3rd résumé wouldn't hyphenate, but it did.
Huh.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66054>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
