Mismatch between preview and print output for header numbering

s_h_a_n_e's Avatar


21 Apr, 2019 12:36 AM

// Please enter a detailed description of the issue // Description of the issue:

I customized a style to generate heading numbering such as 1, 1.1, 1.1.1, etc. It has been working fine for some time, though I haven't used it too recently. Today, though, I ran into an issue. In the preview, everything is numbered as expected, but when I export a paginated PDF, the second level numbering is off. I've attached documents to illustrate this. See below for description.

// Please enter a list of steps required to reproduce the issue // Steps to reproduce:

  1. Use attached .md file and attached style.
  2. Export file as paginated PDF.

// If applicable please attach a sample document that causes the issue for you.

I include a sample multimarkdown file that reproduces the issue, PDF output with the numbering issue, the CSS file for the modified style I use, and a screenshot of the preview to show how it looks before exporting. Note that I don't know CSS very well, and I modified the style file myself.

// Configuration (do not edit) Marked 2 972 (Direct)

macOS Version: 10.14.4

allowPageBreakInCode: YES
bookTxtIsLeanpub: NO
summaryMdIsGitBook: NO
codeIsPoetry: NO
codeCanWrap: YES
collapsibleHeadlines: NO
convertGithubCheckboxes: YES
convertYAMLToMMD: NO
defaultMathJaxConfig: TeX-AMS-MML_HTMLorMML
defaultPreviewStyle: 101
defaultProcessor: MultiMarkdown
enableMiniMap: NO
excludeBlockQuotesFromCounts: NO
excludeFootnotesFromCounts: NO
excludeVerbatimFromCounts: NO
excludeCaptionsFromCounts: NO
folderPreviewExtensionsArray: md, markdown, txt, mdown, html, opml
githubNewlines: YES
h1IsPageBreak: NO
h2IsPageBreak: NO
hrIsPageBreak: NO
includeMathJax: NO
includeKatex: NO
limitTextWidth: NO
minimalJavaScript: NO
permissionGranted: NO
printHeaderFirstPage: YES
printFooterFirstPage: YES
processHTMLFiles: YES
removeMetadataForPreview: NO
removeYAMLHeaders: NO
scrollToEdit: YES
shouldDetectCritic: YES
shouldHighlightMarkupErrors: NO
shouldLoadCritic: NO
syntaxHighlight: NO
syntaxHighlightOnlyLang: NO
useCustomMarkdownProcessor: NO
useCustomPreprocessor: NO
useFirstH1AsPrintTitle: YES

  1. Support Staff 1 Posted by Brett on 21 Apr, 2019 01:02 PM

    Brett's Avatar

    This is a known issue, and a mysterious one I haven't been able to solve yet. I apologize for the inconvenience, and am looking into it.

  2. 2 Posted by s_h_a_n_e on 21 Apr, 2019 07:03 PM

    s_h_a_n_e's Avatar

    Ah, I see. Sorry I missed that. Thanks for letting me know. I assume, then, that there is no workaround either?

  3. Support Staff 3 Posted by Brett on 21 Apr, 2019 08:07 PM

    Brett's Avatar

    Afraid not. I've spent quite some time trying to figure out why the CSS counters behave differently on the way to the print system where the PDF is generated. Thus far no luck solving it, but still working on it :).


  4. 4 Posted by rm on 21 Apr, 2019 09:36 PM

    rm's Avatar

    This comment was split into a new discussion: Fountain page breaks

    I'm writing in fountain.

    The print export pagebreaks never line up with the "---" pagebreaks in the preview.

    You need to improve the @mediaprint CSS for the pdf export, otherwise this app is useless for people who need to print

    pdf output never produces what you see on the screen, when processing as fountain.


Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Already uploaded files

  • Test_Example.md 604 Bytes
  • Test_Example.pdf 47.6 KB
  • Swiss_(numbered_headers).css 7.23 KB
  • Captura_de_Pantalla_2019-04-20_a_la(s)_7.16.05_p._m..png 890 KB

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac