Headings containing monospace formatting revert to non-monospace formatting when exported to PDF
We're migrating to Confluence (v5.3.1) for our technical documentation, with Scroll for PDF (v3.1.8) exports, and our product includes new shell (command-line) commands. We want to always show our shell commands using monospace fonts, including when they're mentioned in headings (like h1, h2, h3, etc).
Currently, any monospace formatting is lost in headings when we export to PDF. This happens regardless of whether the entire heading, or just a portion of it, is formatted with monospace. The formatting is, of course, also lost in the PDF's generated TOC. This makes reading our headings extremely difficult when the shell command itself is a commonly-used word.
Will we be forced to tweak the formatting of thousands of pages of docs, so that all shell commands are wrapped in quotes in addition to monospace fonts, simply so that the shell commands can be easily distinguished when included in headings?
(We're already extremely disappointed by monospace-related bugs like https://k15t.jira.com/browse/EXP-472 and https://k15t.jira.com/browse/EXP-429 )
-
Hi Robert,
I'll just copy the information from the suppor request to this forum post to make it available for other users as well.
[...] unfortunately it's not possible to preserve the monospaced text in headings, due to the current metamodel we're using to create the HTML (which will be converted to PDF).
[...]Best,
Nils
Please sign in to leave a comment.
Comments
1 comment