Follow-up Comment #3, bug #68261 (group groff): I certainly don't have solutions to everything (or anything) you ask, sorry, but I can report from personal experience that it is correct that the warning is "unwelcome information". I venture to say that in most cases, the existing rendering was adequate, and spending time "fixing" it is not something maintainers want to do. I know I didn't.
So, maybe there could be some way to turn off that warning (or a more general
warning control, of course) within the man page itself? I recognize the desire
to give the warning by default, but having looked at the result and deemed it
ok, it sure would nice to be able to stop it. Doing it external to the man
page via options/envvars/etc. does not suffice, as we already discussed. It's
really a function of the man page content, not the build environment.
On other fronts, I don't see that it's necessary to invent support for
monospace with all possible font axes. Just plain regular monospace is all
anyone has ever wanted.
Also, .CS/.CE (if that's what you're saying, not sure) seems fine to me. I
would have used it if it had been available.
People want to use inline monospaced typewriter; your arguments that they
"shouldn't" do not eliminate that desire. Giving them a clear way to do so
seems desirable to me.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?68261>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
