graves inside a second-level heading render incorrectly

[steveklabnik]

Put this in a file named test.md:

test
====

## this title `will render` strangely

This is the body text.

Then run this:

$ marked-man test.md > test.1
$ man ./test.1 

On my system, I get this:

note that strangely is missing the highlight.

.SH this title \fBwill render\fR strangely

this is the text output, but I'm kind bad at troff, so I think that \fR ends the formatting, but this is impossible to google, so hopefully you know :)

One solution is to just pitch anything in graves in a title: they're not being shown any differently anyway.

[steveklabnik]

Oh, this is affecting npm: npm/npm#8984 (comment)

[steveklabnik]

Ah ha!

\fx names a font x. So, here, \fB switches to bold, and \fR switches to 'roman'. \fP switches to 'previous`, and so I would recommend making this example render

.SH this title \fBwill render\fP strangely

which, on my machine, displays correctly, at least. Of course, .SH is already bold, it seems, so just not even showing anything differently might work. Another option:

.SH this title \fIwill render\fP strangely

This renders like this:

[steveklabnik]

Actually https://www.gnu.org/software/groff/manual/html_node/Font-Families.html

Note that \FP doesn’t work; it selects font family ‘P’ instead.

So the right thing is

If no argument is given, switch back to the previous font family.

But using just \f seems to render wrong on my machine.

[kapouer]

Thank you ! i've added a test case - and now i'm fixing the tests, comparing man output without formatting is too relaxed and doesn't test this issue.

[steveklabnik]

🎊 Thanks so much!