Follow-up Comment #5, bug #65102 (group groff): At 2025-05-03T12:40:03-0400, Ingo Schwarze wrote: > Follow-up Comment #4, bug #65102 (group groff): > > I don't think mandoc(1) will ever follow the new practice of setting > the .Dt and .TH arguments in italic. There is no benefit, the header > and footer line stand out just fine without any markup. Besides, i > consider italic as logically wrong for strings that have to be typed > verbatim - i know that Branden disagrees and thinks it is just fine to > use italic sometimes for keywords, sometimes for placeholders. We can > agree to disagree in that respect.
Yes, I see where you're coming from, and would not characterize your
preferences or mandoc(1)'s approach as "wrong".
> That will likely require patching the italic font out in the OpenBSD
> groff port as well, because otherwise, this would be a massive
> regression introducing universial failure into every test in the test
> suite.
Such a patch should be straightforward, but if you have any trouble with
it, please ping me and I'll help construct one.
> The OP's concern might be that an underlined underscore is hard to
> distinguished from an underscore that is not underlined - but that
> font-dependent (potential) issue is not specific to .Dd, so if that is
> what they meant, it's not such a big deal.
Yes--I can't speak for наб here, but I think you're right that such a
problem is not confined to rendering of `Dd`'s argument, and I'd add
that it's _device_-specific, too. Some output devices are capable of
true italics and they should probably be used when available.
> Getting rid of the anachronistic ALL CAPS convention for .Dt and .TH
> is fine. In particular, it's good for accessibility and precision.
And of course I still agree with this. :)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?65102>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
