(See also: all other Topics in this section plus Page Numbering)
Keystroke: Shift + Enter
It begins a new page unconditionally immediately at that point.
Anywhere you want to force a new page.
See next page for details.
[pg]
Details are as follows:
,see next page = details4
------------ page break ------------
,details >e z foll[s3- #a
[pg], which is inserted into a document when you push [pg], is the more potent of the two codes. It always causes a page break. Thus, it can be used to produce blank pages (containing only running headers, running footers, and page numbers, if appropriate) by inserting the code twice or more in a row.
But the [pg]code is sometimes a bit too potent in context. In particular, when [pg]appears at a spot in the document that would be the top of a new page anyhow, it will cause a blank page that you might not intend. This is particularly likely if you insert the code within a print document, with the intent of ensuring a fresh page (but not a blank page) in the braille. It may be that the braille would be breaking to a new page at that spot regardless, in which case, adding [pg] will cause an unexpected blank page when the document is translated from print to braille.
This is why the [top] code is often preferred. [top] tells DBT to insert a page break only if there is text (other than running headers, running footers, and page numbers) already on the page. So using [top] is the safe way to ensure that there will be a page break, without an unintended blank page.
By extension, [top][pg] is the best way to create a blank page, and [top][pg][pg] is the best way to create two blank pages in a row. Using [pg][pg] (without [top] first) to produce a blank page would usually leave one blank page, but sometimes leave two blank pages. Starting a sequence of [pg] codes with [top] makes the behavior more predictable.