Follow-up Comment #1, bug #68708 (group groff): I consider it useful that arguments of .No are _not_ hyphenated.
To understand why, consider how the No macro is typically used.
While in man(7), macros are typically used stand-alone, in mdoc(7) code, it is
very common to form groups of macros, marking individual parts of larger
expressions or chunks of text with their respective semantic roles. That is
where the .No macro is normally used, it is almost never used stand-alone in
practice.
Specifically, the .No and .Ns macros are typically used when, in the middle of
a larger expression or chunk of text where most words or parts are marked up
with a semantic function, one word or a few words occur that should
specifically *not* be marked up - but that does *not* mean that in the middle
of such a larger expression (often an in-line syntax display) you suddenly
want individual words hyphenated, not even when they happen to be normal
English words.
I searched through section 1 of the OpenBSD manual pages for typical examples.
They are so few and far between that i only found a single one, which is in
ksh(1):
The following parameters are set and/or used by the shell:
.Bl -tag -width "EXECSHELL"
.It Ev _ No (underscore)
When an external command is executed by the shell, this parameter is set ...
You certainly wouldn't want the "(under-
score)" in the item head hyphenated.
The vast majority of .No macros do not contain a word long enough to be
hyphenated, anyway. Consequently, for well above 99% of .No macros, the
question is moot in the first place.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68708>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
