Follow-up Comment #3, bug #66054 (group groff): [comment #2 comment #2:] > 2. `.hcode \['a] \['a]` should have altered `\['a]`'s hyphenation code.
I might be misunderstanding the semantics of assigning a character's hcode to
itself. I understood it to mean "make this character eligible for hyphenation
(if it wasn't already)." The actual code assigned, as you've pointed out, is
(or can be) arbitrary.
So in the case above, \['a] already had an hcode. (Granted, it _shouldn't_
have, due to problem 1, but that's already been identified as a separate
problem.) Thus, ".hcode \['a] \['a]" is effectively a no-op.
Or my understanding is inadequate.
Maybe the root problem is that ".hcode a b" and ".hcode a a" use the same
syntax but do distinctly different things. It obscures to humans writing roff
code what they're really asking for.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66054>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
