uses non-portable 'C' font, causing warnings from groff

[sudipm-mukherjee]

Debian now uses groff v1.23.0 and latest groff has added warnings for non-portable fonts.

Steps to reproduce:

1. Use Debian Testing image or Ubunto Mantic
2. man fsvs.1 >/dev/null

It will show lots of warnings like:

troff:<standard input>:1259: warning: cannot select font 'C'
troff:<standard input>:1261: warning: cannot select font 'C'
troff:<standard input>:1265: warning: cannot select font 'C'

More details can be seen at https://savannah.gnu.org/bugs/index.php?64594

[phmarek]

Yeah, well, that's what doxygen gives me.

Should we extend src/tools/man-repair.pl to add the .if \n(.g .if n \{\ block? Or what do you suggest?

[albert-github]

Yeah, well, that's what doxygen gives me.

• What sources do you give to doxygen and what settings do you use?
• What would be the correct syntax?

[phmarek]

See https://github.com/phmarek/fsvs/blob/master/src/Makefile.in#L103, just run make docs.

No idea about the correct syntax -- the referenced bug report recommends

 .\" Automatically generated by Pandoc IN AN IMAGINED FUTURE
.\"
.\" Remap Courier family to bold styles on terminals for
.\" visibility inline.
.if \n(.g .if n \{\
. do ftr CR B
. do ftr CI BI
. do ftr CB B
. do ftr CBI BI
.\}

Perhaps it would be enough to add that in the man pages?

[albert-github]

I don't think remapping to bold is a good idea, as the bold font is already used for highlighting some words and would make the page not well readable. Furthermore \fC is used. Maybe even removing \fC completely is a better solution.

Probably best to create an issue in the doxygen issue tracker at https://github.com/doxygen/doxygen/issues

[albert-github]

I've just pushed a proposed patch, pull request https://github.com/doxygen/doxygen/pull/10497

[albert-github]

Code has been integrated in master on GitHub, though there is a report that on a Mac there is a problem with mandoc.