Follow-up Comment #7, bug #66054 (group groff):
[comment #4 comment #4:]
> I won't say this critique is invalid, but it's not something I
> have a hankering to overturn for _groff_ 1.24.
Yeah, I'm not even sure how it would be overturned in a way that maintains
compatibility, so this was more a g
Follow-up Comment #8, bug #66054 (group groff):
[comment #5 comment #5:]
> I would further note that `hcode`'s behavior seems pretty
> analogous to that of `tr` and `ftr`.
>
> .tr a b \" sets up a mapping
> .tr a a \" undoes that mapping
> .ftr TR PR \" sets up a mapping
> .ftr TR TR \" undoes t
Follow-up Comment #9, bug #66054 (group groff):
[comment #8 comment #8:]
> [comment #5 comment #5:]
> > I would further note that `hcode`'s behavior seems pretty
> > analogous to that of `tr` and `ftr`.
> >
> > .tr a b \" sets up a mapping
> > .tr a a \" undoes that mapping
> > .ftr TR PR \" se
Follow-up Comment #10, bug #66054 (group groff):
[comment #7 comment #7:]
> [comment #4 comment #4:]
> > I think the semantics can be defended if one understands what an
> > "equivalence class" is. Doesn't *everyone* take a university
> > course in discrete mathematics? ;-)
>
> Perhaps the info
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
> Autho
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
Follow-up Comment #13, bug #66054 (group groff):
[comment #10 comment #10:]
> [comment #7 comment #7:]
> > make more explicit what ".hcode a a" means in practical terms.
>
> I kind of think it does...?
[...]
> Assigning the
> code of an ordinary character code to itself effectively creates a
> un
Follow-up Comment #14, bug #66054 (group groff):
[comment #12 comment #12:]
> Oh, I see. I thought the 3rd résumé wouldn't hyphenate, but it did.
Right, sorry if that was unclear. I was trying to point out .hcode's lack of
parallelism with .tr when it came to pairing a character with itself. I
