Skip to content

Printing and PDF ​

Print a page from the browser, to paper or to PDF. The sheet, the margins and the typography come from the page's own properties.

The six properties ​

PropertyValuesDefault
page-sizea4, a5, letter, legala4
page-orientationportrait, landscapeportrait
page-marginmillimetres, 0–60, all four edges20
page-fontserif, sans, monoserif
page-font-sizepoints, 6–3211
page-line-height1–31.5

Every reader is total: a page with no properties prints on A4, and a page whose properties are nonsense prints on A4 too. Out-of-range values clamp rather than fall back — a margin of 500 mm on A4 is a mistake, and a 60 mm margin is the closest thing to what was asked for.

page-margin accepts 20, "20" and "20mm", because a property called page-margin will be given a value with mm on the end of it.

There is no paginator ​

This is the decision worth knowing about, because it explains what you can and cannot expect.

Notesflow does not implement pagination. There are no page boxes in the editor. There is a description of a sheet of paper, and a stylesheet that tells the browser's own layout engine about it when it is asked to print.

The consequence is good: the editor never grows a second opinion about the document's shape. A paginating editor has to agree with the print output, and when the two disagree — and they do — you get a document that looks right on screen and breaks wrongly on paper.

The other consequence is honest: you do not see page breaks while editing. Use the browser's print preview, which is the thing that will actually be doing the breaking.

No page numbers, deliberately ​

There is no page-number property. Running heads and folios are @page margin boxes, which browsers support unevenly, and a page-number feature that works in one browser is a worse promise than none.

The browser's own print dialog puts a page number on the sheet, and it is the same dialog you are already in.

Blocks and the op log are canonical. Markdown is a projection. Git is a target.