At 2021-07-15T22:58:41+0200, Wim Stockman wrote: > Actually I don't think that is necessary. We could basically write a > macro that installs on the fly a system available font for groff. > Using the possibility to run an external script from within groff I m > sure it is possible to install the font on the fly. Running Peter > font-install script. Using the site-font directory so you don't need > root access. > Don't you think ?
I think you're raising an orthogonal concern. Accessing the file system like this would require the use of unsafe requests, which people would understandably shy away from. What I think we need is to absorb Peter's font installer into groff, give it a man page, make sure it works for a preponderance of expected scenarios, and so forth. I'd do it, but I haven't had the spoons. But none of this really has to do with making the _existing_ output drivers accurately document what they support as shipped, or whether we're adequately informing the users of the place of font description files in the groff system as a whole. I should probably mention that back at the end of May I already updated the introduction to the groff_font(5) page and its corresponding Texinfo manual node[1]. Do you think that this[2] is an improvement on groff 1.22.4's page? Regards, Branden [1] https://git.savannah.gnu.org/cgit/groff.git/commit/?id=7173468d984d13bc8d03c40905a9d47bc75338f8 https://git.savannah.gnu.org/cgit/groff.git/commit/?id=33112cce6690dae32d23d02052ad5c94c0329d7f [2] https://man7.org/linux/man-pages/man5/groff_font.5.html
signature.asc
Description: PGP signature
