Re: an observation and proposal about hyphenation codes

[Dave Kemper]

On Tue, Aug 6, 2024 at 9:48 AM G. Branden Robinson
<g.branden.robinson@gmail.com> wrote:
> I'm thinking this has more to do with line length handling than
> hyphenation; `-ww` before `-Wbreak` might have helped.

I'm half-certain it has to do with when latin1.tmac is loaded and when it isn't.

$ echo ".tm Hi, I'm latin1.tmac!" >> tmac/latin1.tmac
$ groff-latest -a < /dev/null
$ groff-latest -Tutf8 < /dev/null
Hi, I'm latin1.tmac!
$ groff-latest -Tascii < /dev/null
$

OK, now I'm certain.

> But as it happens I can't reproduce this misbehavior anyway.

You DID reproduce it.  Look at the first output line of each of your test cases:

> $ ./build/test-groff -Tutf8 -ww -Wbreak EXPERIMENTS/resume-special.groff
> troff:EXPERIMENTS/resume-special.groff:2: warning: setting computed line 
> length 0u to device horizontal motion quantum
> ré‐
> sumé

vs

> $ ./build/test-groff -Tps -a -ww -Wbreak EXPERIMENTS/resume-special.groff
> <beginning of page>
> r<'e>sum<'e>

This is the only line in your test file output before any .hcode
requests were run, so this shows the default hyphenation for the
system.