Page break
This article needs additional citations for verification. (May 2013) |
A page break is a marker in an electronic document that tells the document interpreter that the content which follows is part of a new page. A page break causes a form feed to be sent to the printer during spooling of the document to the printer. Thus it is one of the elements that contributes to pagination.
Form feed
Form feed is a page-breaking
'\f'
. Unicode also provides the character U+21A1 ↡ DOWNWARDS TWO HEADED ARROW as a printable symbol for a form feed (not as the form feed itself).[1]isspace()
.
Form feed is seldom used when programming with modern printers in modern operating environments like
PrintPageEventArgs.HasMorePages
propertySemantic use
The form feed character is sometimes used in plain text files of source code as a delimiter for a page break, or as marker for sections of code. Some editors, in particular emacs and vi, have built-in commands to page up/down on the form feed character. This convention is predominantly used in Lisp code, and is also seen in C and Python source code. GNU Coding Standards require such form feeds in C.[2]
In Usenet, the form feed character is used by several newsreaders as a "spoiler character", causing them to automatically hide the following text until prompted, as a way to prevent spoilers from being inadvertently revealed.[3] The precise behavior depends on the client displaying the article: for example, Gnus displays "Next page..." in boldface, and switches to a second screen to display text after the form feed; slrn displays all non-space characters following the form feed as asterisks; Dialog turns the font and background color red between form feeds; and XRN simply inserts blank lines to fill up the remainder of the article display area so the user must scroll down to reveal the spoiler. This use of the form feed character is not supported by all newsreaders, and is not standardized, although it has appeared in a draft of a Usenet Best Practices document by the IETF's USEFOR working group, as a feature that user agents should (but are not required to) support.[4]
See also
References
- ^ "Unicode" (PDF). Retrieved 2013-05-11.
- ^ "Formatting Your Source Code (C)". GNU Coding Standards.
- ^ Spoilers on newsreaders.com
- ^ IETF USEFOR USEAGE Draft