Page one.
`, then `Page two.
`. That is a horizontal rule, and nothing in the output asks for a new page. The [guide to horizontal rules](markdown-horizontal-rules.md) covers the syntax behind it. Pandoc's extension listing showed `+raw_html` and `-raw_attribute` under `commonmark`, and `+raw_html` with `+raw_attribute` under `markdown`. Both extensions come up again in the sections that follow. ## A break style on a typed div The next test file, `pb-div.md`, put an empty div with a style between the two paragraphs: ```markdown Page one. Page two. ``` The two readers kept the style. They laid out the tags in different ways. The `commonmark` reader (`pandoc -f commonmark -t html pb-div.md`) kept the div on one line and added a blank line after it: ```htmlPage one.
Page two.
``` The `markdown` reader (`pandoc -f markdown -t html pb-div.md`) split the opening and closing tags onto separate lines, and a blank line sat between the two: ```htmlPage one.
Page two.
``` In both runs, the `page-break-after: always` style reached the output exactly as typed. Pandoc's part ends at that attribute. What any program does with that HTML after pandoc writes it was outside this test. Blank-line rules around hand-typed tags are covered in the [explainer on HTML you type by hand](raw-html-in-markdown.md). A div that centers text gets its own runs in the [post on centering text](markdown-center-text.md). ## The newpage command A `\newpage` line sat by itself in `pb-newpage.md`. Pandoc's extension listing for the `markdown` reader includes `+raw_tex`; the listing for `commonmark` has no `raw_tex` entry. The file: ```markdown Page one. \newpage Page two. ``` Three runs gave three results: - `pandoc -f commonmark -t html pb-newpage.md` kept the line as text: `\newpage
`. - `pandoc -f markdown -t html pb-newpage.md` dropped it. Only `Page one.
` and `Page two.
` came back. - `pandoc -f markdown -t latex pb-newpage.md` kept `\newpage` between `Page one.` and `Page two.`, with empty lines around it. So the same line went three ways. The HTML from the `commonmark` reader shows the backslash and the word. The HTML from the `markdown` reader loses the line. The LaTeX from the `markdown` reader keeps it as typed. ## A raw block for HTML output The file `pb-rawattr.md` tagged a fenced block `{=html}`. Pandoc's extension listing had `raw_attribute` on for `markdown` and off for `commonmark`: ````markdown Page one. ```{=html} ``` Page two. ```` Four runs, one per reader and format: - `pandoc -f markdown -t html pb-rawattr.md` gave `` on its own line between the two paragraphs. - `pandoc -f commonmark+raw_attribute -t html pb-rawattr.md` gave that same div line, then a blank line, then `Page two.
`. - Without `raw_attribute`, `pandoc -f commonmark -t html pb-rawattr.md` turned the block into code: `<div style="break-after: page"></div>` element, and the div showed up as escaped text. With it on, the div passed through. The LaTeX run left out the HTML block.
## A raw block for LaTeX output
A follow-up test, `pb-x-rawlatex.md`, swapped the tag to `{=latex}` and put `\newpage` inside:
````markdown
Page one.
```{=latex}
\newpage
```
Page two.
````
Here's what came back:
- `pandoc -f markdown -t latex pb-x-rawlatex.md` gave `\newpage` on its own line between the paragraphs.
- `pandoc -f commonmark+raw_attribute -t latex pb-x-rawlatex.md` matched that output line for line.
- `pandoc -f markdown -t html pb-x-rawlatex.md` dropped the block, leaving `Page one.
` and `Page two.
`.
- Without `raw_attribute`, `pandoc -f commonmark -t latex pb-x-rawlatex.md` wrapped the line in `Shaded` and `Highlighting` blocks, with the line itself written as `\NormalTok{\textbackslash{}newpage}`.
Put next to the previous section, the pattern holds in both directions. With `raw_attribute` on, in these runs, a block tagged for one format reached that format's output and went missing from the other.
## Test a break on its own
When a break you typed doesn't show up in pandoc's output, test the lines around it by themselves.
1. Copy the break line and the paragraphs on each side into a new, empty file.
2. First, try the `commonmark` reader with no extensions added. `pandoc -f commonmark -t html pb-hr.md | grep -c '
'` gave `1` for the dashed file.
3. For a typed div, count the style: `pandoc -f commonmark -t html pb-div.md | grep -c 'page-break-after'` gave `1`.
4. For a tagged block, compare reader settings. `pandoc -f commonmark -t html pb-rawattr.md | grep -c '