Newline · Lablypedia

History

In the mid-1800s, long before the advent of teleprinters and teletype machines, Morse code operators or telegraphists invented and used Morse code prosigns to encode white space text formatting in formal written text messages. In particular, the Morse prosign BT (mnemonic break text), represented by the concatenation of literal textual Morse codes "B" and "T" characters, sent without the normal inter-character spacing, is used in Morse code to encode and indicate a new line or new section in a formal text message.

Later, in the age of modern teleprinters, standardized character set control codes were developed to aid in white space text formatting. ASCII was developed simultaneously by the International Organization for Standardization (ISO) and the American Standards Association (ASA), the latter being the predecessor organization to American National Standards Institute (ANSI). During the period of 1963 to 1968, the ISO draft standards supported the use of either carriage return plus line feed (CR+LF) or LF alone as a newline, while the ASA drafts supported only CR+LF.

The sequence CR+LF was commonly used on many early computer systems that had adopted Teletype machines—typically a Teletype Model 33 ASR—as a console device, because this sequence was required to position those printers at the start of a new line. The separation of newline into two functions concealed the fact that the print head could not return from the far right to the beginning of the next line in time to print the next character. Any character printed after a CR would often print as a smudge in the middle of the page while the print head was still moving the carriage back to the first position. "The solution was to make the newline two characters: CR to move the carriage to column one, and LF to move the paper up." In fact, it was often necessary to send extra padding characters—extraneous CRs or NULs—which are ignored but give the print head time to move to the left margin. Many early video displays also required multiple character times to scroll the display.

On such systems, applications had to talk directly to the Teletype machine and follow its conventions since the concept of device drivers hiding such hardware details from the application was not yet well developed. Therefore, text was routinely composed to satisfy the needs of Teletype machines. Most minicomputer systems from DEC used this convention. CP/M also used it in order to print on the same terminals that minicomputers used. From there MS-DOS (1981) adopted CP/M's CR+LF in order to be compatible, and this convention was inherited by Microsoft's later Windows operating system.

The Multics operating system began development in 1964 and used LF alone as its newline. Multics used a device driver to translate this character to whatever sequence a printer needed (including extra padding characters), and the single byte was more convenient for programming. What seems like a more obvious choice – CR – was not used, as CR provided the useful function of overprinting one line with another to create boldface, underscore and strikethrough effects. Perhaps more importantly, the use of LF alone as a line terminator had already been incorporated into drafts of the eventual ISO/IEC 646 standard. Unix followed the Multics practice, and later Unix-like systems followed Unix. This created conflicts between Windows and Unix-like operating systems, whereby files composed on one operating system could not be properly formatted or interpreted by another operating system (for example a UNIX shell script written in a Windows text editor like Notepad).

3 more chapters are free with a Lably account.

Representation

Earlier history in Telegraphy and typewriters generally considered starting a new line a single action, and it would make sense to encode it as a single control character. However, the design of printing teletypes led to the idea of a newline being two actions, a carriage return CR and line feed LF. A CR by itself was useful to overprint the current line to make double-struck bold or underscores. A LF going straight down was mechanically simpler and could print some text faster if there was a working backspace. Requiring two characters to start a line did not waste any time as the mechanisms were slower than the time it took to send both of them (often extra "padding" characters had to be sent to be sure the carriage had reached the left before the next printing character). The CR was always sent first as it was the slow one.

If software did not want to process the characters before sending them to a teletype, this meant that each newline had to be stored as the CR+LF pair or CRLF, on paper tape or in text files. Often the "padding" characters had to be stored as well.

Making newline be a single character just like space is helpful for text processing and pattern matching, and made the files smaller. Some systems did require LF to go to the left edge and many terminals had a configuration option to allow this (though this broke too much software that relied on LF going straight down). Multics and thus Unix instead required processing, a LF sent to a terminal was replaced by the operating system with CRLF (or whatever the terminal needed including padding characters).

EBCDIC systems—mainly IBM mainframe systems, including z/OS (OS/390) and IBM i (OS/400)—use NL (New Line, 0x15) as the character combining the functions of line feed and carriage return. The equivalent Unicode character (0x85) is called NEL (Next Line). EBCDIC also has control characters called CR and LF, but the numerical value of LF (0x25) differs from the one used by ASCII (0x0A). Additionally, some EBCDIC variants also use NL but assign a different numeric code to the character. However, those operating systems use a record-based file system, which stores text files as one record per line. In most file formats, no line terminators are actually stored.
Operating systems for the CDC 6000 series defined a newline as two or more zero-valued six-bit characters at the end of a 60-bit word. Some configurations also defined a zero-valued character as a colon character, with the result that multiple colons could be interpreted as a newline depending on position.
RSX-11 and OpenVMS also use a record-based file system, which stores text files as one record per line. In most file formats, no line terminators are actually stored, but the Record Management Services facility can transparently add a terminator to each line when it is retrieved by an application. The records themselves can contain the same line terminator characters, which can either be considered a feature or a nuisance depending on the application. RMS not only stores records, but also stores metadata about the record separators in different bits for the file to complicate matters even more (since files can have fixed length records, records that are prefixed by a count or records that are terminated by a specific character). The bits are not generic, so while they can specify that CRLF or LF or even CR is the line terminator, they can not substitute some other code.
Fixed line length was used by some early mainframe operating systems. In such a system, an implicit end-of-line was assumed every 72 or 80 characters, for example. No newline character was stored. If a file was imported from the outside world, lines shorter than the line length had to be padded with spaces, while lines longer than the line length had to be truncated. This mimicked the use of punched cards, on which each line was stored on a separate card, usually with 80 columns on each card, often with sequence numbers in columns 73–80. Many of these systems added a carriage control character to the start of the next record; this could indicate whether the next record was a continuation of the line started by the previous record, or a new line, or should overprint the previous line (similar to a CR). Often this was a normal printing character such as # that thus could not be used as the first character in a line. Some early line printers interpreted these characters directly in the records sent to them.

Communication protocols

Many communications protocols have some sort of new line convention. In particular, protocols published by the Internet Engineering Task Force (IETF) typically use the ASCII CRLF sequence.

In some older protocols, the new line may be followed by a checksum or parity character.

Unicode

The Unicode standard defines a number of characters that conforming applications should recognize as line terminators:

While it may seem overly complicated compared to an approach such as converting all line terminators to a single character (e.g. LF), because Unicode is designed to preserve all information when converting a text file from any existing encoding to Unicode and back (round-trip integrity), Unicode needs to make the same distinctions between line breaks made by other encodings. For instance EBCDIC has NL, CR, and LF characters, so all three have to also exist in Unicode.

Most newline characters and sequences are in ASCII's C0 controls (i.e. have Unicode code points up to 0x1F). The three newline characters outside of this range—NEL, LS and PS—are often not recognized as newlines by software. For example:

JSON recognizes CR and LF as whitespace, but not any other newline characters. C0 controls cannot appear unescaped within strings, but any other line break characters can.
ECMAScript only recognizes CR, LF, LS and PS as line terminators. Historically, unescaped line terminators were not permitted in string literals, but this was changed in ES2019 to allow unescaped LS and PS in strings for compatibility with JSON.
YAML 1.1 recognized all three as line breaks; YAML 1.2 no longer recognizes them as line breaks in order to be compatible with JSON.
Windows Notepad, the default text editor of Microsoft Windows, does not treat any of NEL, LS, or PS as line breaks.
gedit, the default text editor of the GNOME desktop environment, treats LS and PS as line breaks, but not NEL.

Unicode includes some glyphs intended for presenting a user-visible character to the reader of the document, and are thus not recognized themselves as a newline:

U+23CE ⏎ RETURN SYMBOL
U+240A ␊ SYMBOL FOR LINE FEED
U+240D ␍ SYMBOL FOR CARRIAGE RETURN
U+2424 ␤ SYMBOL FOR NEWLINE

HTML

In HTML, line breaks are whitespace and are generally treated no different to spaces. Paragraphs are created using separate instances of the HTML element <p>, with the physical separation of paragraphs controlled by the rendering engine.

Line breaks can be explicitly created using the HTML element <br>. To facilitate screen readers being able to interpret pages, HTML documentation recommends against using this element for paragraphing. Instead, sources including MDN Web Docs suggest using this element for poems.

In programming languages

To facilitate creating portable programs, programming languages provide some abstractions to deal with the different types of newline sequences used in different environments.

The C language provides the escape sequences \n (newline) and \r (carriage return). However, these are not required to be equivalent to the ASCII LF and CR control characters. The C standard only guarantees two traits:

Each of these escape sequences maps to a unique implementation-defined number that can be stored in one char value.
When writing to a file, device node, or socket/fifo in text mode, \n is transparently translated to the native newline sequence used by the system, which may be longer than one character. When reading in text mode, the native newline sequence is translated back to \n. In binary mode, no translation is performed, and the internal representation produced by \n is output directly.

On Unix operating system platforms, where C originated, the native newline sequence is ASCII LF (0x0A), so \n was simply defined to be that value. With the internal and external representation being identical, the translation performed in text mode is a no-op, and Unix has no notion of text mode or binary mode. This has caused many programmers who developed their software on Unix systems simply to ignore the distinction completely, resulting in code that is not portable to different platforms.

The C standard library function fgets() is best avoided in binary mode because any file not written with the Unix newline convention will be misread. Also, in text mode, any file not written with the system's native newline sequence (such as a file created on a Unix system, then copied to a Windows system) will be misread as well.

Another common problem is the use of \n when communicating using an Internet protocol that mandates the use of ASCII CR+LF for ending lines. Writing \n to a text mode stream works correctly on Windows systems, but produces only LF on Unix, and something completely different on more exotic systems. Using \r\n in binary mode is slightly better.

Many languages, such as C++, Perl, and Haskell provide the same interpretation of \n as C. C++ has an alternative input/output (I/O) model where the manipulator std::endl can be used to output a newline (and flushes the stream buffer).

Java, PHP, and Python provide the \r\n sequence (for ASCII CR+LF). In contrast to C, these are guaranteed to represent the values U+000D and U+000A, respectively.

The Java Class Library input/output (I/O) methods do not transparently translate these into platform-dependent newline sequences on input or output. Instead, they provide functions for writing a full line that automatically add the native newline sequence, and functions for reading lines that accept any of CR, LF, or CR+LF as a line terminator (see BufferedReader.readLine()). The System.lineSeparator() method can be used to retrieve the underlying line separator. This is also automatically inserted when using the format specifier %n in System.out::printf.

Example:

<span id="mwAqM"></span><span class="n" id="mwAqQ">String</span><span class="w" id="mwAqU"> </span><span class="n" id="mwAqY">eol</span><span class="w" id="mwAqc"> </span><span class="o" id="mwAqg">=</span><span class="w" id="mwAqk"> </span><span class="n" id="mwAqo">System</span><span class="p" id="mwAqs">.</span><span class="na" id="mwAqw">lineSeparator</span><span class="p" id="mwAq0">();</span> <span class="n" id="mwAq4">String</span><span class="w" id="mwAq8"> </span><span class="n" id="mwArA">lineColor</span><span class="w" id="mwArE"> </span><span class="o" id="mwArI">=</span><span class="w" id="mwArM"> </span><span class="s" id="mwArQ">"Color: Red"</span><span class="w" id="mwArU"> </span><span class="o" id="mwArY">+</span><span class="w" id="mwArc"> </span><span class="n" id="mwArg">eol</span><span class="p" id="mwArk">;</span>

Python has a "universal newline support" feature enabled by default, which translates all three commonly found line ending conventions (\n, \r, \r\n) into Python's standard \n convention when opening a file for reading, when importing modules, and when executing a file. This feature can be controlled using the newline argument in the open() function when opening the file.

Some languages have created special variables, constants, and subroutines to facilitate newlines during program execution. In some languages such as PHP and Perl, double quotes are required to perform escape substitution for all escape sequences, including \n and \r. In PHP, to avoid portability problems, newline sequences should be issued using the PHP_EOL constant.

Example in C#:

<span id="mwAto"></span><span class="kt" id="mwAts">string</span><span class="w" id="mwAtw"> </span><span class="n" id="mwAt0">eol</span><span class="w" id="mwAt4"> </span><span class="o" id="mwAt8">=</span><span class="w" id="mwAuA"> </span><span class="n" id="mwAuE">Environment</span><span class="p" id="mwAuI">.</span><span class="n" id="mwAuM">NewLine</span><span class="p" id="mwAuQ">;</span> <span class="kt" id="mwAuU">string</span><span class="w" id="mwAuY"> </span><span class="n" id="mwAuc">lineColor</span><span class="w" id="mwAug"> </span><span class="o" id="mwAuk">=</span><span class="w" id="mwAuo"> </span><span class="s" id="mwAus">"Color: Red"</span><span class="w" id="mwAuw"> </span><span class="o" id="mwAu0">+</span><span class="w" id="mwAu4"> </span><span class="n" id="mwAu8">eol</span><span class="p" id="mwAvA">;</span> <span class="w" id="mwAvE"> </span> <span class="kt" id="mwAvI">string</span><span class="w" id="mwAvM"> </span><span class="n" id="mwAvQ">eol2</span><span class="w" id="mwAvU"> </span><span class="o" id="mwAvY">=</span><span class="w" id="mwAvc"> </span><span class="s" id="mwAvg">"\n"</span><span class="p" id="mwAvk">;</span> <span class="kt" id="mwAvo">string</span><span class="w" id="mwAvs"> </span><span class="n" id="mwAvw">lineColor2</span><span class="w" id="mwAv0"> </span><span class="o" id="mwAv4">=</span><span class="w" id="mwAv8"> </span><span class="s" id="mwAwA">"Color: Blue"</span><span class="w" id="mwAwE"> </span><span class="o" id="mwAwI">+</span><span class="w" id="mwAwM"> </span><span class="n" id="mwAwQ">eol2</span><span class="p" id="mwAwU">;</span>

Issues with different newline formats

The different newline conventions cause text files that have been transferred between systems of different types to be displayed incorrectly.

Text in files created with programs which are common on Unix-like or classic Mac OS, appear as a single long line on most programs common to MS-DOS and Microsoft Windows because these do not display a single line feed or a single carriage return as a line break.

Conversely, when viewing a file originating from a Windows computer on a Unix-like system, the extra CR may be displayed as a second line break, as ^M, or as <cr> at the end of each line.

Furthermore, programs other than text editors may not accept a file, e.g. some configuration file, encoded using the foreign newline convention, as a valid file.

The problem can be hard to spot because some programs handle the foreign newlines properly while others do not. For example, a compiler may fail with obscure syntax errors even though the source file looks correct when displayed on the console or in an editor. Modern text editors generally recognize all flavours of CR+LF newlines and allow users to convert between the different standards. Web browsers are usually also capable of displaying text files and websites which use different types of newlines.

Even if a program supports different newline conventions, these features are often not sufficiently labeled, described, or documented. Typically a menu or combo-box enumerating different newline conventions will be displayed to users without an indication if the selection will reinterpret, temporarily convert, or permanently convert the newlines. Some programs will implicitly convert on open, copy, paste, or save—often inconsistently.

Most textual Internet protocols (including HTTP, SMTP, FTP, IRC, and many others) mandate the use of ASCII CR+LF (\r\n, 0x0D 0x0A) on the protocol level, but recommend that tolerant applications recognize lone LF (\n, 0x0A) as well. Despite the dictated standard, many applications erroneously use the C newline escape sequence \n (LF) instead of the correct combination of carriage return escape and newline escape sequences \r\n (CR+LF) (see section Newline in programming languages above). This accidental use of the wrong escape sequences leads to problems when trying to communicate with systems adhering to the stricter interpretation of the standards instead of the suggested tolerant interpretation. One such intolerant system is the qmail mail transfer agent that actively refuses to accept messages from systems that send bare LF instead of the required CR+LF.

The standard Internet Message Format for email states: "CR and LF MUST only occur together as CRLF; they MUST NOT appear independently in the body". Differences between SMTP implementations in how they treat bare LF and/or bare CR characters have led to SMTP spoofing attacks referred to as "SMTP smuggling".

The File Transfer Protocol can automatically convert newlines in files being transferred between systems with different newline representations when the transfer is done in "ASCII mode". However, transferring binary files in this mode usually has disastrous results: any occurrence of the newline byte sequence—which does not have line terminator semantics in this context, but is just part of a normal sequence of bytes—will be translated to whatever newline representation the other system uses, effectively corrupting the file. FTP clients often employ some heuristics (for example, inspection of filename extensions) to automatically select either binary or ASCII mode, but in the end it is up to users to make sure their files are transferred in the correct mode. If there is any doubt as to the correct mode, binary mode should be used, as then no files will be altered by FTP, though they may display incorrectly.

Conversion between newline formats

Text editors are often used for converting a text file between different newline formats; most modern editors can read and write files using at least the different ASCII CR/LF conventions.

For example, the editor Vim can make a file compatible with the Windows Notepad text editor. Within vim

<span id="mwA3A"></span> :<span class="k" id="mwA3E">set</span> <span class="nb" id="mwA3I">fileformat</span><span class="p" id="mwA3M">=</span>dos :<span class="k" id="mwA3Q">wq</span>

Editors can be unsuitable for converting larger files or bulk conversion of many files. For larger files (on Windows NT) the following command is often used:

<span id="mwA3g"></span><span class="gp" id="mwA3k">D:\></span><span class="k" id="mwA3o">TYPE</span> unix_file <span class="p" id="mwA3s">|</span> FIND /V <span class="s2" id="mwA3w">""</span> <span class="p" id="mwA30">></span> dos_file

Special purpose programs to convert files between different newline conventions include unix2dos and dos2unix, mac2unix and unix2mac, mac2dos and dos2mac, and flip. The tr command is available on virtually every Unix-like system and can be used to perform arbitrary replacement operations on single characters. A DOS/Windows text file can be converted to Unix format by simply removing all ASCII CR characters with

$ tr -d '\r' <span typeof="mw:Entity" id="mwA5g"><</span> <i id="mwA5k">inputfile</i> <span typeof="mw:Entity" id="mwA5o">></span> <i id="mwA5s">outputfile</i>

or, if the text has only CR newlines, by converting all CR newlines to LF with

$ tr '\r' '\n' <span typeof="mw:Entity" id="mwA6Q"><</span> <i id="mwA6U">inputfile</i> <span typeof="mw:Entity" id="mwA6Y">></span> <i id="mwA6c">outputfile</i>

The same tasks are sometimes performed with awk, sed, or in Perl if the platform has a Perl interpreter:

<span id="mwA64"></span><span class="gp" id="mwA68">$ </span>awk<span class="w" id="mwA7A"> </span><span class="s1" id="mwA7E">'{sub("$","\r\n"); printf("%s",$0);}'</span><span class="w" id="mwA7I"> </span>inputfile<span class="w" id="mwA7M"> </span>><span class="w" id="mwA7Q"> </span>outputfile<span class="w" id="mwA7U"> </span><span class="c1" id="mwA7Y"># UNIX to DOS (adding CRs on Linux and BSD based OS that haven't GNU extensions)</span> <span class="gp" id="mwA7c">$ </span>awk<span class="w" id="mwA7g"> </span><span class="s1" id="mwA7k">'{gsub("\r",""); print;}'</span><span class="w" id="mwA7o"> </span>inputfile<span class="w" id="mwA7s"> </span>><span class="w" id="mwA7w"> </span>outputfile<span class="w" id="mwA70"> </span><span class="c1" id="mwA74"># DOS to UNIX (removing CRs on Linux and BSD based OS that haven't GNU extensions)</span> <span class="gp" id="mwA78">$ </span>sed<span class="w" id="mwA8A"> </span>-e<span class="w" id="mwA8E"> </span><span class="s1" id="mwA8I">'s/$/\r/'</span><span class="w" id="mwA8M"> </span>inputfile<span class="w" id="mwA8Q"> </span>><span class="w" id="mwA8U"> </span>outputfile<span class="w" id="mwA8Y"> </span><span class="c1" id="mwA8c"># UNIX to DOS (adding CRs on Linux based OS that use GNU extensions)</span> <span class="gp" id="mwA8g">$ </span>sed<span class="w" id="mwA8k"> </span>-e<span class="w" id="mwA8o"> </span><span class="s1" id="mwA8s">'s/\r$//'</span><span class="w" id="mwA8w"> </span>inputfile<span class="w" id="mwA80"> </span>><span class="w" id="mwA84"> </span>outputfile<span class="w" id="mwA88"> </span><span class="c1" id="mwA9A"># DOS to UNIX (removing CRs on Linux based OS that use GNU extensions)</span> <span class="gp" id="mwA9E">$ </span>perl<span class="w" id="mwA9I"> </span>-pe<span class="w" id="mwA9M"> </span><span class="s1" id="mwA9Q">'s/\r?\n|\r/\r\n/g'</span><span class="w" id="mwA9U"> </span>inputfile<span class="w" id="mwA9Y"> </span>><span class="w" id="mwA9c"> </span>outputfile<span class="w" id="mwA9g"> </span><span class="c1" id="mwA9k"># Convert to DOS</span> <span class="gp" id="mwA9o">$ </span>perl<span class="w" id="mwA9s"> </span>-pe<span class="w" id="mwA9w"> </span><span class="s1" id="mwA90">'s/\r?\n|\r/\n/g'</span><span class="w" id="mwA94"> </span>inputfile<span class="w" id="mwA98"> </span>><span class="w" id="mwA-A"> </span>outputfile<span class="w" id="mwA-E"> </span><span class="c1" id="mwA-I"># Convert to UNIX</span> <span class="gp" id="mwA-M">$ </span>perl<span class="w" id="mwA-Q"> </span>-pe<span class="w" id="mwA-U"> </span><span class="s1" id="mwA-Y">'s/\r?\n|\r/\r/g'</span><span class="w" id="mwA-c"> </span>inputfile<span class="w" id="mwA-g"> </span>><span class="w" id="mwA-k"> </span>outputfile<span class="w" id="mwA-o"> </span><span class="c1" id="mwA-s"># Convert to old Mac</span>

The file command can identify the type of line endings:

<span id="mwA_E"></span><span class="gp" id="mwA_I"> $ </span>file<span class="w" id="mwA_M"> </span>myfile.txt <span class="go" id="mwA_Q"> myfile.txt: ASCII English text, with CRLF line terminators</span>

The Unix egrep (extended grep) command can be used to print filenames of Unix or DOS files (assuming Unix and DOS-style files only, no classic Mac OS-style files):

<span id="mwA_k"></span><span class="gp" id="mwA_o">$ </span>egrep<span class="w" id="mwA_s"> </span>-L<span class="w" id="mwA_w"> </span><span class="s1" id="mwA_0">'\r\n'</span><span class="w" id="mwA_4"> </span>myfile.txt<span class="w" id="mwA_8"> </span><span class="c1" id="mwBAA"># show UNIX style file (LF terminated)</span> <span class="gp" id="mwBAE">$ </span>egrep<span class="w" id="mwBAI"> </span>-l<span class="w" id="mwBAM"> </span><span class="s1" id="mwBAQ">'\r\n'</span><span class="w" id="mwBAU"> </span>myfile.txt<span class="w" id="mwBAY"> </span><span class="c1" id="mwBAc"># show DOS style file (CRLF terminated)</span>

Other tools permit the user to visualise the EOL characters:

<span id="mwBAs"></span><span class="gp" id="mwBAw">$ </span>od<span class="w" id="mwBA0"> </span>-a<span class="w" id="mwBA4"> </span>myfile.txt <span class="gp" id="mwBA8">$ </span>cat<span class="w" id="mwBBA"> </span>-e<span class="w" id="mwBBE"> </span>myfile.txt <span class="gp" id="mwBBI">$ </span>cat<span class="w" id="mwBBM"> </span>-v<span class="w" id="mwBBQ"> </span>myfile.txt <span class="gp" id="mwBBU">$ </span>hexdump<span class="w" id="mwBBY"> </span>-c<span class="w" id="mwBBc"> </span>myfile.txt

Interpretation

Two ways to view newlines, both of which are self-consistent, are that newlines either separate lines or that they terminate lines. If a newline is considered a separator, there will be no newline after the last line of a file. Some programs have problems processing the last line of a file if it is not terminated by a newline. On the other hand, programs that expect newline to be used as a separator will interpret a final newline as starting a new (empty) line. Conversely, if a newline is considered a terminator, all text lines including the last are expected to be terminated by a newline. If the final character sequence in a text file is not a newline, the final line of the file may be considered to be an improper or incomplete text line, or the file may be considered to be improperly truncated. The POSIX standard takes the latter position, considering newlines to be line terminators.

In text intended primarily to be read by humans using software which implements the word wrap feature, a newline character typically only needs to be stored if a line break is required independent of whether the next word would fit on the same line, such as between paragraphs and in vertical lists. Therefore, in the logic of word processing and most text editors, newline is used as a paragraph break and is known as a "hard return", in contrast to "soft returns" which are dynamically created to implement word wrapping and are changeable with each display instance. In many applications a separate control character called "manual line break" exists for forcing line breaks inside a single paragraph. The glyph for the control character for a hard return is usually a pilcrow (¶), and for the manual line break is usually a carriage return arrow (↵).

Reverse and partial line feeds

RI (U+008D REVERSE LINE FEED, ISO/IEC 6429 8D, decimal 141) is used to move the printing position back one line (by reverse feeding the paper, or by moving a display cursor up one line) so that other characters may be printed over existing text. This may be done to make them bolder, or to add underlines, strike-throughs or other characters such as diacritics. The reverse line feed was called a line starve – a pun on line feed – in the Hacker's Dictionary.

Similarly, PLD (U+008B PARTIAL LINE FORWARD, decimal 139) and PLU (U+008C PARTIAL LINE BACKWARD, decimal 140) can be used to advance or reverse the text printing position by some fraction of the vertical line spacing (typically, half). These can be used in combination for subscripts (by advancing and then reversing) and superscripts (by reversing and then advancing), and may also be useful for printing diacritics.