Page Breaks

Lewis Levin's Avatar

Lewis Levin

07 Aug, 2016 08:41 PM

Please introduce a "standard" notation for indicating the location of page breaks.

I see on your site that you have a very elaborate justification for ignoring suggestions: not needed by many; too narrow; violates "philosophy".

Violates philosophy is either religious or ideological and is a great catch all that is equivalent to "developer dislikes feature or lacks personal use of requested feature."

You are thinking that a page break is not semantic meaning--it is formatting. Therefore, it has no place in markup. Allow me to contradict this interpretation: page breaks are as much meaning as a headline level. Have you ever read a book or research paper that contained no page breaks except those needed to allow long continuous flow? I doubt it. Such documents would be hard to read. A page break signals intention: one major topic has ended and new major topic has begun.

You could say that this should be part of a heading definition and a style sheet (with some awkwardness) can incorporate a page break as the formatting definition of the heading. So it can. This is useful for very long and highly structured documents. For less formal documents, it is a lot of unnecessary work. So, lets have page breaks.

In your stated rationale for multi markdown, you indicate that you wish to overcome some limitations in Gruber's original markdown, which was only for formatting text into html snippets to include in websites (principally blog posts). You sought to stick to the simplicity and philosophy of Gruber's markdown but extend it to *documents*. Documents have page breaks.

You see, I am trying to head off all of the excuses at the pass. I am sorry I sound a bit peeved but I have encountered lots of ideologically purist objections to obviously pragmatic features. You know that there are several non-standard ways to accomplish this. Several products (include Marked and Mou) have non-standard ways to encode a page break. Examples:

<p><!-- pagebreak --></p>
<hr> (really, really inappropriate way!)

So, the need is real. You have proposed the standard for multimarkdown and have provided the reference implementation. So, you can come up with standard markdown for page breaks, which we might call "required" for "force" page breaks because they are introduced as part of the semantics of a document and don't occur simply because the length of a rendered page has been exceeded.

This can be done in a way that makes sense in the raw text of the mmd document, which is consistent with the philosophy. Obviously, in the raw text no arbitrary amount of vertical whitespace can be introduced, nor should it be. That is **not** part of this request. The markup symbol itself should be obvious enough to most readers that a break is intended when reading the raw text of the mmd file.

It is really up to you to choose but some candidates might be:


In a dedicated multi markdown editor, the page break markup could be shown centered with a light gray background for the entire line. Plenty obvious. In a plain text editor (Sublime Text, etc) of course this is unlikely. Nothing is actually **required** as the markup *intention* is already clear.

Again, I apologize for the peevishness, but I can sort of tell that the suggestion doesn't fit with your *likely* views so I am handling the likely objections in advance.

  1. Support Staff 1 Posted by Fletcher on 08 Aug, 2016 11:48 PM

    Fletcher's Avatar

    No content.

Reply to this discussion

Internal reply

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

Attaching KB article:


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