Page break

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 ASCII control character. It forces the printer to eject the current page and to continue printing at the top of another. Often, it will also cause a carriage return. The form feed character code is defined as 12 (0xC in hexadecimal), and may be represented as control+L or ^L. In a related use, control+L can be used to clear the screen in Unix shells such as bash. In the C programming language (and other languages derived from C), the form feed character is represented as '\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] The form feed character is considered whitespace by the C character classification function isspace().

Form feed is seldom used when programming with modern printers in modern operating environments like Windows, Unix, Linux or macOS. Instead, form feeds are generated by having the printing program call a form feed API function. For example, when printing using the .NET Framework, the PrintPageEventArgs.HasMorePages property is used to indicate a form feed is desired.

Semantic 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] Editors like Vim and Emacs understand such sections and have shortcuts for moving among them.

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]

gollark: The UK has living costs too!
gollark: Iceland's neat. I don't live there. It's just quite a nice country.
gollark: There are less bad ones.
gollark: > whatsapp
gollark: ???

See also

References
  1. "Unicode" (PDF). Retrieved 2013-05-11.
  2. "Formatting Your Source Code (C)". GNU Coding Standards.
  3. Spoilers on newsreaders.com
  4. IETF USEFOR USEAGE Draft
This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.