The C0 and C1 control code or control character sets define control codes for use in text by computer systems that use ASCII and derivatives of ASCII. The codes represent additional information about the text, such as the position of a cursor, an instruction to start a new line, or a message that the text has been received.
C0 codes are the range 00HEX–1FHEX and the default C0 set was originally defined in ISO 646 (ASCII). C1 codes are the range 80HEX–9FHEX and the default C1 set was originally defined in ECMA-48 (harmonized later with ISO 6429). The ISO/IEC 2022 system of specifying control and graphic characters allows other C0 and C1 sets to be available for specialized applications, but they are rarely used.
C0 controls
ASCII defined 32 control characters, plus a necessary extra character for the DEL character, 7FHEX or 01111111BIN (needed to punch out all the holes on a paper tape and erase it).
This large number of codes was desirable at the time, as multi-byte controls would require implementation of a state machine in the terminal, which was very difficult with contemporary electronics and mechanical terminals.
Only a few codes have maintained their use: BEL, ESC, and the format effector[1] (FEn) characters BS, TAB, LF, VT, FF, and CR. Others are unused or have acquired different meanings such as NUL being the C string terminator. Some data transfer protocols such as ANPA-1312, Kermit, and XMODEM do make extensive use of SOH, STX, ETX, EOT, ACK, NAK and SYN for purposes approximating their original definitions; and some file formats use the "Information Separators" (ISn) such as the Unix info format[2] and Python's splitlines string method.[3]
The names of some codes were changed in ISO 6429:1992 (or ECMA-48:1991) to be neutral with respect to writing direction. The abbreviations used were not changed, as the standard had already specified that those would remain unchanged when the standard is translated to other languages. In this table both new and old names are shown for the renamed controls (the old name is the one matching the abbreviation).
Unicode provides Control Pictures that can replace C0 control characters to make them visible on screen. However caret notation is used more often.
Alters the meaning of a limited number of following bytes. Nowadays this is almost always used to introduce an ANSI escape sequence.
^\
28
1C
IS4, FS
␜
File Separator
Can be used as delimiters to mark fields of data structures. US is the lowest level, while RS, GS, and FS are of increasing level to divide groups made up of items of the level beneath it. SP (space) could be considered an even lower level.
^]
29
1D
IS3, GS
␝
Group Separator
^^
30
1E
IS2, RS
␞
Record Separator
^_
31
1F
IS1, US
␟
Unit Separator
While not technically part of the C0 control character range, the following two characters can be thought of as having some characteristics of control characters.
Should be ignored. Used to delete characters on punched tape by punching out all the holes.
^Teletype labelled the key WRU for 'who are you?'[7]
^The name BELL is assigned by Unicode to the unrelated emoji character 🔔 (U+1F514). While C0 and C1 control characters were not formally named by the Unicode standard itself at the time, this collided with existing use of BELL as the name of this control character in software following the previous versions of UTS#18 (the Unicode Regular Expressions standard),[8] e.g. in Perl.[9] Unicode now accepts ALERT and BEL (but not BELL) as formal aliases for the control character,[10] although the code chart still lists BELL as the ISO 6429 alias,[11] and the corresponding control picture code point is called SYMBOL FOR BELL. Perl subsequently switched to using BELL for the emoji in version 5.18.[12]
^ abISO/IEC 2022 (ECMA-35) refers to these as LS0 and LS1 in 8-bit environments, and as SI and SO in 7-bit environments.[13]
^The first, 1963 edition of ASCII classified DLE as a device control, rather than a transmission control, and gave it the abbreviation DC0 ("device control reserved for data link escape").[14]
^The '\e' escape sequence is not part of ISO C and many other language specifications. However, it is understood by several compilers, including GCC.
C1 controls
In 1973, ECMA-35 and ISO 2022[18] attempted to define a method so an 8-bit "extended ASCII" code could be converted to a corresponding 7-bit code, and vice versa.[19] In a 7-bit environment, the Shift Out (SO) would change the meaning of the 96 bytes 0x20 through 0x7F[a][21] (i.e. all but the C0 control codes), to be the characters that an 8-bit environment would print if it used the same code with the high bit set. This meant that the range 0x80 through 0x9F could not be printed in a 7-bit environment,[19] thus it was decided that no alternative character set could use them, and that these codes should be additional control codes, which become known as the C1 control codes. To allow a 7-bit environment to use these new controls, the sequences ESC @ through ESC _ were to be considered equivalent.[19] The later ISO 8859 standards abandoned support for 7-bit codes, but preserved this range of control characters.
The first C1 control code set to be registered for use with ISO 2022 was DIN 31626,[22] a specialised set for bibliographic use which was registered in 1979.[23]
The more common general-use ISO/IEC 6429 set was registered in 1983,[24] although the ECMA-48 specification upon which it was based had been first published in 1976[25] and JIS X 0211 (formerly JIS C 6323).[26] Symbolic names defined by RFC1345 and early drafts of ISO 10646, but not in ISO/IEC 6429 (PAD, HOP and SGC) are also used.[9][27]
Except for SS2 and SS3 in EUC-JP text, and NEL in text transcoded from EBCDIC, the 8-bit forms of these codes were almost never used. CSI, DCS and OSC are used to control text terminals and terminal emulators, but almost always by using their 7-bit escape code representations. Nowadays if these codes are encountered it is far more likely they are intended to be printing characters from that position of Windows-1252 or Mac OS Roman.
Except for NEL Unicode does not provide a "control picture" for any of these. There is also no well-known variation of Caret notation for them either.
Proposed as a "padding" or "high byte" for single-byte characters to make them two bytes long for easier interoperability with multiple byte characters. Extended Unix Code (EUC) occasionally uses this.[32]
Follows a graphic character where a line break is permitted. Roughly equivalent to a soft hyphen or zero-width space except it does not define what is printed at the line break.
Followed by a string of printable characters (0x20 through 0x7E) and format effectors (0x08 through 0x0D), terminated by ST (0x9C). Xterm defined a number of these.[36]
Q
145
91
PU1
Private Use 1
Reserved for private function agreed on between the sender and the recipient of the data.
To be followed by a single printable character (0x20 through 0x7E) or format effector (0x08 through 0x0D), and to print it as ASCII no matter what graphic or control sets were in use.
Used to introduce control sequences that take parameters. Used for ANSI escape sequences.
\
156
9C
ST
String Terminator
Terminates a string started by DCS, SOS, OSC, PM or APC.
]
157
9D
OSC
Operating System Command
Followed by a string of printable characters (0x20 through 0x7E) and format effectors (0x08 through 0x0D), terminated by ST (0x9C), intended for use to allow in-band signaling of protocol information, but rarely used for that purpose.
Some terminal emulators, including xterm, use OSC sequences for setting the window title and changing the colour palette. They may also support terminating an OSC sequence with BEL instead of ST.[38]Kermit used APC to transmit commands.[39]
^
158
9E
PM
Privacy Message
_
159
9F
APC
Application Program Command
^In early versions the range excluded SP and DEL[20]
^ abcdNot part of the first edition of ISO/IEC 6429.[24][29]: 4
^Deprecated in 1988 and withdrawn in 1992 from ISO/IEC 6429[31]: 87 (1986[33] and 1991[34] respectively for ECMA-48).
Other control code sets
The ISO/IEC 2022 (ECMA-35) extension mechanism allowed escape sequences to change the C0 and C1 sets. The standard C0 control character set shown above is chosen with the sequence ESC ! @ and the above C1 set chosen with the sequence ESC " C.[24]
Several official and unofficial alternatives have been defined, but this is pretty much obsolete. Most were forced to retain a good deal of compatibility with the ASCII controls for interoperability. The standard makes ESC,[40][41] SP and DEL[a] "fixed" coded characters, which are available in their ASCII locations in all encodings that conform to the standard.[43] It also specifies that if a C0 set included transmission control (TCn) codes, they must be encoded at their ASCII locations[40] and could not be put in a C1 set,[44] and any new transmission controls must be in a C1 set.[40]
Other C0 control code sets
ANPA-1312, a text markup language used for news transmission, replaces several C0 control characters.
IPTC 7901, the newer international version of the above, has its own variations.
T.61/T.51,[45] and others[46] replaced EM and GS with SS2 and SS3 so these functions could be used in a 7-bit environment.
Some sets replaced FS with SS2,[47] (same as ANPA-1312).
The now-withdrawn JIS C 6225, designated JIS X 0207 in later sources.[48] replaced FS with CEX or "Control Extension"[49] which introduces control sequences for vertical text behaviour, superscripts and subscripts[50] and for transmitting custom character graphics.[48]
Replacement C1 character sets
A specialized C1 control code set is registered for bibliographic use (including string collation), such as by MARC-8.[23][51][52]
Various specialised C1 control code sets are registered for use by Videotex formats.[22]
EBCDIC defines up to 29 additional control codes besides those present in ASCII. When translating EBCDIC to Unicode (or to ISO 8859), these codes are mapped to C1 control characters in a manner specified by IBM's Character Data Representation Architecture (CDRA).[53][54] Although the New Line (NL) does translate to the ISO/IEC 6429 NEL (although it is often swapped with LF, following UNIX line ending convention),[53] the remainder of the control codes do not correspond. For example, the EBCDIC control SPS and the ECMA-48 control PLU are both used to begin a superscript or end a subscript, but are not mapped to one another. Extended-ASCII-mapped EBCDIC can therefore be regarded as having its own C1 set, although it is not registered with the ISO-IR registry for ISO/IEC 2022.[22]
Unicode reserves the 65 code points described above for compatibility with the C0 and C1 control codes, giving them the general categoryCc (control). These are:
Unicode only specifies semantics for the C0 format controls HT, LF, VT, FF, and CR (note BS is missing); the C0 information separators FS, GS, RS, US (and SP); and the C1 control NEL.[55] The rest of the codes are transparent to Unicode and their meanings are left to higher-level protocols, with ISO/IEC 6429 suggested as a default.[55]
Unicode includes many additional format effector characters besides these, such as marks, embeds, isolates and pops for explicit bidirectional formatting, and the zero-width joiner and non-joiner for controlling ligature use. However these are given the general category Cf (format) rather than Cc.
See also
Control Pictures - Unicode graphical representation characters for the C0 control codes
^ abUmamaheswaran, V.S. (1999-11-08). "3.3 Step 2: Byte Conversion". UTF-EBCDIC. Unicode Consortium. Unicode Technical Report #16. The 64 control characters […], the ASCII DELETE character (U+007F)[…] are mapped respecting EBCDIC conventions, as defined in IBM Character Data Representation Architecture, CDRA, with one exception -- the pairing of EBCDIC Line Feed and New Line control characters are swapped from their CDRA default pairings to ISO/IEC 6429 Line Feed (U+000A) and Next Line (U+0085) control characters