Follow-up Comment #14, bug #63635 (group groff): Thanks for the explanation, Branden. To provide a TL;DR of your answer to my question, `hydefault` is expected to be used in localization and macro files rather than in manpages themselves.
To summarize the difference between `hydefault` and my proposal for neatroff,
with the input
+verbose+
.hy 2
.nh
.hy
-verbose-
the former will set hyphenation mode to whatever was set by the last
`hydefault` call (in a macro package or similar), whereas the latter will set
hyphenation mode to 2.
My understanding is that the proposals would result in the same effect
(localization files can configure which hyphenation mode argumentless `hy`
sets), the only significant difference being that with my proposal calling
regular `hy` with an argument changes the default mode. It is unclear to me
whether this is an advantage or a disadvantage.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63635>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
