On Sunday, 7 December 2025 00:16:54 GMT G. Branden Robinson wrote: > At 2025-12-06T16:55:52+0000, Deri wrote: > > The reason you see a dashed line with the T and H fonts is because > > these two families are part of the base-14 fonts which do not need to > > be embedded in the pdf. It is then the duty of the pdf viewer to > > supply its own version of those fonts. Most viewers provide some way > > of interrogating which actual fonts are used in the document. > > And even if the view on one's machine doesn't, there exists the > "pdffonts" command-line tool.
"pdffonts" will only tell you the font is not embedded, so not much help, it does not tell you which font will be used by the pdf viewer in its place. > > If you add "-P-e" to your command the actual fonts groff uses will be > > embedded in the document, and you will see a solid line. > > > > As you are using a bleeding edge groff you can use:- > > > > export GROPDF_OPTIONS=-e > > > > (NB No -P) Which will ensure fonts are always embedded - this is now > > considered best practice. > > Since it's not considered best practice, I've submitted a patch making > gropdf always embed, de-documenting `-e` and making it silently ignored. > > https://savannah.gnu.org/bugs/?66342 It is the PDF/A standard which mandates font embedding and gropdf only supports PDF 1.4 and 1.7, for this reason I am not changing gropdf to embed all fonts. Users who want this behaviour should add the above export command to their shell start-up script which gets run when you login. > Regards, > Branden Cheers Deri
