Follow-up Comment #11, bug #66054 (group groff):

[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...

> 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 of using 1.23 rather than anything more recent was to show the
sequence:
1. The first output of the word, before the document does any .hcode fiddling,
has no break points.
2. After telling groff to treat é like e, the word gets broken.
3. 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.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?66054>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to