Follow-up Comment #17, bug #67544 (group groff): [comment #16 comment #16:] > There is usually no necessity to define a font family in a document, > as only the font styles (R, I, B, C, etc.) are commonly used.
That's a weirdly sweeping statement to cover the thousands of different
document types roff typesetters can handle, all with vastly different needs.
> Man pages (documents) can be rendered by using a command option like
> "-f U-T", and that only makes sense with "troff", not "nroff".
...and won't work for PostScript output, which lacks a U-T family in the
default installation.
> Why can (may) you not add your needed kerning data just to
> your own Times fonts ?
I can, and do, do plenty of things in my own font files. The purpose of a
savannah ticket is to improve groff for everyone who uses it.
> The same man page is rendered so many times again and again
> (worldwide !), that the energy (resource) is better used for
> more valuable things.
The vast majority of man pages are rendered with nroff, where, as you point
out, none of this discussion applies.
A single AI query uses more energy than any groff user could ever hope to. So
if you're going to fight a battle over energy usage, focus on where it'll make
the most difference, and take the issue up with your favorite LLM purveyor.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67544>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
