“ASCII”的意思、由来-开放百科全书

ASCII ({{IPAc-en|audio=En-us-ASCII.ogg|ˈ|æ|s|k|iː}} {{respell|ASS|kee}}),^[1]{{rp|6}} abbreviated from American Standard Code for Information Interchange, is a character encoding standard for electronic communication. ASCII codes represent text in computers, telecommunications equipment, and other devices. Most modern character-encoding schemes are based on ASCII, although they support many additional characters.

ASCII is the traditional name for the encoding system; the Internet Assigned Numbers Authority (IANA) prefers the updated name US-ASCII, which clarifies that this system was developed in the US and based on the typographical symbols predominantly in use there.^[2]

Overview

ASCII was developed from telegraph code. Its first commercial use was as a seven-bit teleprinter code promoted by Bell data services. Work on the ASCII standard began on October 6, 1960, with the first meeting of the American Standards Association's (ASA) (now the American National Standards Institute or ANSI) X3.2 subcommittee. The first edition of the standard was published in 1963,^[3]^[4] underwent a major revision during 1967,^[5]^[6] and experienced its most recent update during 1986.^[7] Compared to earlier telegraph codes, the proposed Bell code and ASCII were both ordered for more convenient sorting (i.e., alphabetization) of lists, and added features for devices other than teleprinters.

Originally based on the English alphabet, ASCII encodes 128 specified characters into seven-bit integers as shown by the ASCII chart above.^[8] Ninety-five of the encoded characters are printable: these include the digits 0 to 9, lowercase letters a to z, uppercase letters A to Z, and punctuation symbols. In addition, the original ASCII specification included 33 non-printing control codes which originated with Teletype machines; most of these are now obsolete,^[9] although a few are still commonly used, such as the carriage return, line feed and tab codes.

For example, lowercase i would be represented in the ASCII encoding by binary 1101001 = hexadecimal 69 (i is the ninth letter) = decimal 105.

{{anchor|1963|1965|1967|1968|1977|1986|1992|1997|2002|2007|2012}}History

The American Standard Code for Information Interchange (ASCII) was developed under the auspices of a committee of the American Standards Association (ASA), called the X3 committee, by its X3.2 (later X3L2) subcommittee, and later by that subcommittee's X3.2.4 working group (now INCITS). The ASA became the United States of America Standards Institute (USASI)^[1]{{rp|211}} and ultimately the American National Standards Institute (ANSI).

With the other special characters and control codes filled in, ASCII was published as ASA X3.4-1963,^[4]^[10] leaving 28 code positions without any assigned meaning, reserved for future standardization, and one unassigned control code.^[1]{{rp|66, 245}} There was some debate at the time whether there should be more control characters rather than the lowercase alphabet.^[1]{{rp|435}} The indecision did not last long: during May 1963 the CCITT Working Party on the New Telegraph Alphabet proposed to assign lowercase characters to sticks{{Efn|name="NB_Stick"|{{anchor|Stick}}The 128 characters of the 7-bit ASCII character set are divided into eight 16-character groups called sticks 0–7, associated with the three most-significant bits. Depending on the horizontal or vertical representation of the character map, sticks correspond with either table rows or columns.}} 6 and 7,^[11] and International Organization for Standardization TC 97 SC 2 voted during October to incorporate the change into its draft standard.^[12] The X3.2.4 task group voted its approval for the change to ASCII at its May 1963 meeting.^[13] Locating the lowercase letters in sticks{{Efn|name="NB_Stick"}} 6 and 7 caused the characters to differ in bit pattern from the upper case by a single bit, which simplified case-insensitive character matching and the construction of keyboards and printers.

The X3 committee made other changes, including other new characters (the brace and vertical bar characters),^[14] renaming some control characters (SOM became start of header (SOH)) and moving or removing others (RU was removed).^[1]{{rp|247–248}} ASCII was subsequently updated as USAS X3.4-1967,^[5]^[15] then USAS X3.4-1968, ANSI X3.4-1977, and finally, ANSI X3.4-1986.^[7]^[16]

In the X3.15 standard, the X3 committee also addressed how ASCII should be transmitted (least significant bit first),^[1]{{rp|249–253}}^[20] and how it should be recorded on perforated tape. They proposed a 9-track standard for magnetic tape, and attempted to deal with some punched card formats.

Design considerations

Bit width

The X3.2 subcommittee designed ASCII based on the earlier teleprinter encoding systems. Like other character encodings, ASCII specifies a correspondence between digital bit patterns and character symbols (i.e. graphemes and control characters). This allows digital devices to communicate with each other and to process, store, and communicate character-oriented information such as written language. Before ASCII was developed, the encodings in use included 26 alphabetic characters, 10 numerical digits, and from 11 to 25 special graphic symbols. To include all these, and control characters compatible with the Comité Consultatif International Téléphonique et Télégraphique (CCITT) International Telegraph Alphabet No. 2 (ITA2) standard of 1924,^[21]^[22] FIELDATA (1956{{citation needed|date=June 2016|reason=My sources state 1957 rather than 1956, but Wikipedia states 1956 in various places. This needs to be sorted out with better sources.}}), and early EBCDIC (1963), more than 64 codes were required for ASCII.

ITA2 were in turn based on the 5-bit telegraph code Émile Baudot invented in 1870 and patented in 1874.^[22]

The committee debated the possibility of a shift function (like in ITA2), which would allow more than 64 codes to be represented by a six-bit code. In a shifted code, some character codes determine choices between options for the following character codes. It allows compact encoding, but is less reliable for data transmission, as an error in transmitting the shift code typically makes a long part of the transmission unreadable. The standards committee decided against shifting, and so ASCII required at least a seven-bit code.^[1]{{rp|215, 236 § 4}}

The committee considered an eight-bit code, since eight bits (octets) would allow two four-bit patterns to efficiently encode two digits with binary-coded decimal. However, it would require all data transmission to send eight bits when seven could suffice. The committee voted to use a seven-bit code to minimize costs associated with data transmission. Since perforated tape at the time could record eight bits in one position, it also allowed for a parity bit for error checking if desired.^[1]{{rp|217, 236 § 5}} Eight-bit machines (with octets as the native data type) that did not use parity checking typically set the eighth bit to 0.^[23] In some printers, the high bit was used to enable Italics printing.

Internal organization

The code itself was patterned so that most control codes were together and all graphic codes were together, for ease of identification. The first two so-called ASCII sticks{{Efn|name="NB_Stick"}} (32 positions) were reserved for control characters.^[1]{{rp|220, 236 § 8,9)}} The "space" character had to come before graphics to make sorting easier, so it became position 20_hex;^[1]{{rp|237 § 10}} for the same reason, many special signs commonly used as separators were placed before digits. The committee decided it was important to support uppercase 64-character alphabets, and chose to pattern ASCII so it could be reduced easily to a usable 64-character set of graphic codes,^[1]{{rp|228, 237 § 14}} as was done in the DEC SIXBIT code (1963). Lowercase letters were therefore not interleaved with uppercase. To keep options available for lowercase letters and other graphics, the special and numeric codes were arranged before the letters, and the letter A was placed in position 41_hex to match the draft of the corresponding British standard.^[1]{{rp|238 § 18}} The digits 0–9 are prefixed with 011, but the remaining 4 bits correspond to their respective values in binary, making conversion with binary-coded decimal straightforward.

Many of the non-alphanumeric characters were positioned to correspond to their shifted position on typewriters; an important subtlety is that these were based on mechanical typewriters, not electric typewriters.^[24] Mechanical typewriters followed the standard set by the Remington No. 2 (1878), the first typewriter with a shift key, and the shifted values of 23456789- were "#$%_&'(){{snd}} early typewriters omitted 0 and 1, using O (capital letter o) and l (lowercase letter L) instead, but 1! and 0) pairs became standard once 0 and 1 became common. Thus, in ASCII !"#$% were placed in the second stick,{{Efn|name="NB_Stick"}} positions 1–5, corresponding to the digits 1–5 in the adjacent stick.{{Efn|name="NB_Stick"}} The parentheses could not correspond to 9 and 0, however, because the place corresponding to 0 was taken by the space character. This was accommodated by removing _ (underscore) from 6 and shifting the remaining characters, which corresponded to many European typewriters that placed the parentheses with 8 and 9. This discrepancy from typewriters led to bit-paired keyboards, notably the Teletype Model 33, which used the left-shifted layout corresponding to ASCII, not to traditional mechanical typewriters. Electric typewriters, notably the IBM Selectric (1961), used a somewhat different layout that has become standard on computers{{snd}} following the IBM PC (1981), especially Model M (1984){{snd}} and thus shift values for symbols on modern keyboards do not correspond as closely to the ASCII table as earlier keyboards did. The /? pair also dates to the No. 2, and the ,< .> pairs were used on some keyboards (others, including the No. 2, did not shift , (comma) or . (full stop) so they could be used in uppercase without unshifting). However, ASCII split the ;: pair (dating to No. 2), and rearranged mathematical symbols (varied conventions, commonly -* =+) to * ;+ -=.

Some common characters were not included, notably ½¼¢, while ^`~ were included as diacritics for international use, and <> for mathematical use, together with the simple line characters \\| (in addition to common /). The @ symbol was not used in continental Europe and the committee expected it would be replaced by an accented À in the French variation, so the @ was placed in position 40_hex, right before the letter A.^[1]{{rp|243}}

The control codes felt essential for data transmission were the start of message (SOM), end of address (EOA), end of message (EOM), end of transmission (EOT), "who are you?" (WRU), "are you?" (RU), a reserved device control (DC0), synchronous idle (SYNC), and acknowledge (ACK). These were positioned to maximize the Hamming distance between their bit patterns.^[1]{{rp|243–245}}

{{anchor|Order}}Character order

ASCII-code order is also called ASCIIbetical order.^[25] Collation of data is sometimes done in this order rather than "standard" alphabetical order (collating sequence). The main deviations in ASCII order are:

An intermediate order converts uppercase letters to lowercase before comparing ASCII values.

Character groups

{{anchor|ASCII control characters}}Control characters

ASCII reserves the first 32 codes (numbers 0–31 decimal) for control characters: codes originally intended not to represent printable information, but rather to control devices (such as printers) that make use of ASCII, or to provide meta-information about data streams such as those stored on magnetic tape.

For example, character 10 represents the "line feed" function (which causes a printer to advance its paper), and character 8 represents "backspace". {{IETF RFC|2822}} refers to control characters that do not include carriage return, line feed or white space as non-whitespace control characters.^[26] Except for the control characters that prescribe elementary line-oriented formatting, ASCII does not define any mechanism for describing the structure or appearance of text within a document. Other schemes, such as markup languages, address page and document layout and formatting.

The original ASCII standard used only short descriptive phrases for each control character. The ambiguity this caused was sometimes intentional, for example where a character would be used slightly differently on a terminal link than on a data stream, and sometimes accidental, for example with the meaning of "delete".

Probably the most influential single device on the interpretation of these characters was the Teletype Model 33 ASR, which was a printing terminal with an available paper tape reader/punch option. Paper tape was a very popular medium for long-term program storage until the 1980s, less costly and in some ways less fragile than magnetic tape. In particular, the Teletype Model 33 machine assignments for codes 17 (Control-Q, DC1, also known as XON), 19 (Control-S, DC3, also known as XOFF), and 127 (Delete) became de facto standards. The Model 33 was also notable for taking the description of Control-G (code 7, BEL, meaning audibly alert the operator) literally, as the unit contained an actual bell which it rang when it received a BEL character. Because the keytop for the O key also showed a left-arrow symbol (from ASCII-1963, which had this character instead of underscore), a noncompliant use of code 15 (Control-O, Shift In) interpreted as "delete previous character" was also adopted by many early timesharing systems but eventually became neglected.

When a Teletype 33 ASR equipped with the automatic paper tape reader received a Control-S (XOFF, an abbreviation for transmit off), it caused the tape reader to stop; receiving Control-Q (XON, "transmit on") caused the tape reader to resume. This technique became adopted by several early computer operating systems as a "handshaking" signal warning a sender to stop transmission because of impending overflow; it persists to this day in many systems as a manual output control technique. On some systems Control-S retains its meaning but Control-Q is replaced by a second Control-S to resume output. The 33 ASR also could be configured to employ Control-R (DC2) and Control-T (DC4) to start and stop the tape punch; on some units equipped with this function, the corresponding control character lettering on the keycap above the letter was TAPE and ~~TAPE~~ respectively.^[27]

The Teletype could not move the head backwards, so it did not put a key on the keyboard to send a BS (backspace). Instead there was a key marked {{keypress|RUB OUT}} that sent code 127 (DEL). The purpose of this key was to erase mistakes in a hand-typed paper tape: the operator had to push a button on the tape punch to back it up, then type the rubout, which punched all holes and replaced the mistake with a character that was intended to be ignored.^[28] Teletypes were commonly used for the less-expensive computers from Digital Equipment Corporation, so these systems had to use the available key and thus the DEL code to erase the previous character.^[29]^[30] Because of this, DEC video terminals (by default) sent the DEL code for the key marked "Backspace" while the key marked "Delete" sent an escape sequence, while many other terminals sent BS for the Backspace key. The Unix terminal driver could only use one code to back up, this could be set to BS or DEL, but not both, resulting in a very long period of annoyance where you had to correct it depending on what terminal you were using (shells that allow line editing, such as ksh, bash, and zsh, understand both). The assumption that no key sent a BS caused Control+H to be used for other purposes, such as the "help" prefix command in GNU Emacs.^[31]

Many more of the control codes have been given meanings quite different from their original ones. The "escape" character (ESC, code 27), for example, was intended originally to allow sending other control characters as literals instead of invoking their meaning. This is the same meaning of "escape" encountered in URL encodings, C language strings, and other systems where certain characters have a reserved meaning. Over time this meaning has been co-opted and has eventually been changed. In modern use, an ESC sent to the terminal usually indicates the start of a command sequence usually in the form of a so-called "ANSI escape code" (or, more properly, a "Control Sequence Introducer") from ECMA-48 (1972) and its successors, beginning with ESC followed by a "[" (left-bracket) character. An ESC sent from the terminal is most often used as an out-of-band character used to terminate an operation, as in the TECO and vi text editors. In graphical user interface (GUI) and windowing systems, ESC generally causes an application to abort its current operation or to exit (terminate) altogether.

The inherent ambiguity of many control characters, combined with their historical usage, created problems when transferring "plain text" files between systems. The best example of this is the newline problem on various operating systems. Teletype machines required that a line of text be terminated with both "Carriage Return" (which moves the printhead to the beginning of the line) and "Line Feed" (which advances the paper one line without moving the printhead). The name "Carriage Return" comes from the fact that on a manual typewriter the carriage holding the paper moved while the position where the typebars struck the ribbon remained stationary. The entire carriage had to be pushed (returned) to the right in order to position the left margin of the paper for the next line.

DEC operating systems (OS/8, RT-11, RSX-11, RSTS, TOPS-10, etc.) used both characters to mark the end of a line so that the console device (originally Teletype machines) would work. By the time so-called "glass TTYs" (later called CRTs or terminals) came along, the convention was so well established that backward compatibility necessitated continuing the convention. When Gary Kildall created CP/M he was inspired by some command line interface conventions used in DEC's RT-11. Until the introduction of PC DOS in 1981, IBM had no hand in this because their 1970s operating systems used EBCDIC instead of ASCII and they were oriented toward punch-card input and line printer output on which the concept of carriage return was meaningless. IBM's PC DOS (also marketed as MS-DOS by Microsoft) inherited the convention by virtue of being loosely based on CP/M,^[32] and Windows inherited it from MS-DOS.

Unfortunately, requiring two characters to mark the end of a line introduces unnecessary complexity and questions as to how to interpret each character when encountered alone. To simplify matters plain text data streams, including files, on Multics^[33] used line feed (LF) alone as a line terminator. Unix and Unix-like systems, and Amiga systems, adopted this convention from Multics. The original Macintosh OS, Apple DOS, and ProDOS, on the other hand, used carriage return (CR) alone as a line terminator; however, since Apple replaced these operating systems with the Unix-based macOS operating system, they now use line feed (LF) as well. The Radio Shack TRS-80 also used a lone CR to terminate lines.

Computers attached to the ARPANET included machines running operating systems such as TOPS-10 and TENEX using CR-LF line endings, machines running operating systems such as Multics using LF line endings, and machines running operating systems such as OS/360 that represented lines as a character count followed by the characters of the line and that used EBCDIC rather than ASCII. The Telnet protocol defined an ASCII "Network Virtual Terminal" (NVT), so that connections between hosts with different line-ending conventions and character sets could be supported by transmitting a standard text format over the network. Telnet used ASCII along with CR-LF line endings, and software using other conventions would translate between the local conventions and the NVT.^[34] The File Transfer Protocol adopted the Telnet protocol, including use of the Network Virtual Terminal, for use when transmitting commands and transferring data in the default ASCII mode.^[35]^[36] This adds complexity to implementations of those protocols, and to other network protocols, such as those used for E-mail and the World Wide Web, on systems not using the NVT's CR-LF line-ending convention.^[37]^[38]

The PDP-6 monitor,^[29] and its PDP-10 successor TOPS-10,^[30] used Control-Z (SUB) as an end-of-file indication for input from a terminal. Some operating systems such as CP/M tracked file length only in units of disk blocks and used Control-Z to mark the end of the actual text in the file.^[39] For these reasons, EOF, or end-of-file, was used colloquially and conventionally as a three-letter acronym for Control-Z instead of SUBstitute. The end-of-text code (ETX), also known as Control-C, was inappropriate for a variety of reasons, while using Z as the control code to end a file is analogous to it ending the alphabet and serves as a very convenient mnemonic aid. A historically common and still prevalent convention uses the ETX code convention to interrupt and halt a program via an input data stream, usually from a keyboard.

In C library and Unix conventions, the null character is used to terminate text strings; such null-terminated strings can be known in abbreviation as ASCIZ or ASCIIZ, where here Z stands for "zero".

Other representations might be used by specialist equipment, for example ISO 2047 graphics or hexadecimal numbers.

{{anchor|ASCII-printable-characters}}Printable characters

Codes 20_hex to 7E_hex, known as the printable characters, represent letters, digits, punctuation marks, and a few miscellaneous symbols. There are 95 printable characters in total.{{efn|Printed out, the characters are: {{Pre2|scroll| !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\\]^_`abcdefghijklmnopqrstuvwxyz{|}~}}}}

Code 20_hex, the "space" character, denotes the space between words, as produced by the space bar of a keyboard. Since the space character is considered an invisible graphic (rather than a control character)^[1]{{rp|223}}^[40] it is listed in the table below instead of in the previous section.

Code 7F_hex corresponds to the non-printable "delete" (DEL) control character and is therefore omitted from this chart; it is covered in the previous section's chart. Earlier versions of ASCII used the up arrow instead of the caret (5E_hex) and the left arrow instead of the underscore (5F_hex).^[4]^[41]

Character set

Use

ASCII was first used commercially during 1963 as a seven-bit teleprinter code for American Telephone & Telegraph's TWX (TeletypeWriter eXchange) network. TWX originally used the earlier five-bit ITA2, which was also used by the competing Telex teleprinter system. Bob Bemer introduced features such as the escape sequence.^[3] His British colleague Hugh McGregor Ross helped to popularize this work{{snd}} according to Bemer, "so much so that the code that was to become ASCII was first called the Bemer–Ross Code in Europe".^[42] Because of his extensive work on ASCII, Bemer has been called "the father of ASCII".^[43]

On March 11, 1968, U.S. President Lyndon B. Johnson mandated that all computers purchased by the United States Federal Government support ASCII, stating:^[44]^[45]^[46]

ASCII was the most common character encoding on the World Wide Web until December 2007, when UTF-8 encoding surpassed it; UTF-8 is backward compatible with ASCII.^[47]^[48]^[49]

{{anchor|Variants}}Variants and derivations

As computer technology spread throughout the world, different standards bodies and corporations developed many variations of ASCII to facilitate the expression of non-English languages that used Roman-based alphabets. One could class some of these variations as "ASCII extensions", although some misuse that term to represent all variants, including those that do not preserve ASCII's character-map in the 7-bit range. Furthermore, the ASCII extensions have also been mislabelled as ASCII.

{{anchor|7-bit}}7-bit codes

From early in its development,^[50] ASCII was intended to be just one of several national variants of an international character code standard.

Other international standards bodies have ratified character encodings such as ISO 646 (1967) that are identical or nearly identical to ASCII, with extensions for characters outside the English alphabet and symbols used outside the United States, such as the symbol for the United Kingdom's pound sterling (£). Almost every country needed an adapted version of ASCII, since ASCII suited the needs of only the US and a few other countries. For example, Canada had its own version that supported French characters.

Many other countries developed variants of ASCII to include non-English letters (e.g. é, ñ, ß, Ł), currency symbols (e.g. £, ¥), etc. See also YUSCII (Yugoslavia).

It would share most characters in common, but assign other locally useful characters to several code points reserved for "national use". However, the four years that elapsed between the publication of ASCII-1963 and ISO's first acceptance of an international recommendation during 1967^[51] caused ASCII's choices for the national use characters to seem to be de facto standards for the world, causing confusion and incompatibility once other countries did begin to make their own assignments to these code points.

ISO/IEC 646, like ASCII, is a 7-bit character set. It does not make any additional codes available, so the same code points encoded different characters in different countries. Escape codes were defined to indicate which national variant applied to a piece of text, but they were rarely used, so it was often impossible to know what variant to work with and, therefore, which character a code represented, and in general, text-processing systems could cope with only one variant anyway.

Because the bracket and brace characters of ASCII were assigned to "national use" code points that were used for accented letters in other national variants of ISO/IEC 646, a German, French, or Swedish, etc. programmer using their national variant of ISO/IEC 646, rather than ASCII, had to write, and thus read, something such as

C trigraphs were created to solve this problem for ANSI C, although their late introduction and inconsistent implementation in compilers limited their use. Many programmers kept their computers on US-ASCII, so plain-text in Swedish, German etc. (for example, in e-mail or Usenet) contained "{, }" and similar variants in the middle of words, something those programmers got used to. For example, a Swedish programmer mailing another programmer asking if they should go for lunch, could get "N{ jag har sm|rg}sar" as the answer, which should be "Nä jag har smörgåsar" meaning "No I've got sandwiches".

{{anchor|8-bit}}8-bit codes

Eventually, as 8-, 16- and 32-bit (and later 64-bit) computers began to replace 12-, 18- and 36-bit computers as the norm, it became common to use an 8-bit byte to store each character in memory, providing an opportunity for extended, 8-bit relatives of ASCII. In most cases these developed as true extensions of ASCII, leaving the original character-mapping intact, but adding additional character definitions after the first 128 (i.e., 7-bit) characters.

Encodings include ISCII (India), VISCII (Vietnam). Although these encodings are sometimes referred to as ASCII, true ASCII is defined strictly only by the ANSI standard.

Most early home computer systems developed their own 8-bit character sets containing line-drawing and game glyphs, and often filled in some or all of the control characters from 0 to 31 with more graphics. Kaypro CP/M computers used the "upper" 128 characters for the Greek alphabet.

The PETSCII code Commodore International used for their 8-bit systems is probably unique among post-1970 codes in being based on ASCII-1963, instead of the more common ASCII-1967, such as found on the ZX Spectrum computer. Atari 8-bit computers and Galaksija computers also used ASCII variants.

The IBM PC defined code page 437, which replaced the control characters with graphic symbols such as smiley faces, and mapped additional graphic characters to the upper 128 positions. Operating systems such as DOS supported these code pages, and manufacturers of IBM PCs supported them in hardware. Digital Equipment Corporation developed the Multinational Character Set (DEC-MCS) for use in the popular VT220 terminal as one of the first extensions designed more for international languages than for block graphics. The Macintosh defined Mac OS Roman and Postscript also defined a set, both of these contained both international letters and typographic punctuation marks instead of graphics, more like modern character sets.

The ISO/IEC 8859 standard (derived from the DEC-MCS) finally provided a standard that most systems copied (at least as accurately as they copied ASCII, but with many substitutions). A popular further extension designed by Microsoft, Windows-1252 (often mislabeled as ISO-8859-1), added the typographic punctuation marks needed for traditional text printing. ISO-8859-1, Windows-1252, and the original 7-bit ASCII were the most common character encodings until 2008 when UTF-8 became more common.^[48]

ISO/IEC 4873 introduced 32 additional control codes defined in the 80–9F hexadecimal range, as part of extending the 7-bit ASCII encoding to become an 8-bit system.^[52]

Unicode

Unicode and the ISO/IEC 10646 Universal Character Set (UCS) have a much wider array of characters and their various encoding forms have begun to supplant ISO/IEC 8859 and ASCII rapidly in many environments. While ASCII is limited to 128 characters, Unicode and the UCS support more characters by separating the concepts of unique identification (using natural numbers called code points) and encoding (to 8-, 16- or 32-bit binary formats, called UTF-8, UTF-16 and UTF-32).

ASCII was incorporated into the Unicode (1991) character set as the first 128 symbols, so the 7-bit ASCII characters have the same numeric codes in both sets. This allows UTF-8 to be backward compatible with 7-bit ASCII, as a UTF-8 file containing only ASCII characters is identical to an ASCII file containing the same sequence of characters. Even more importantly, forward compatibility is ensured as software that recognizes only 7-bit ASCII characters as special and does not alter bytes with the highest bit set (as is often done to support 8-bit ASCII extensions such as ISO-8859-1) will preserve UTF-8 data unchanged.^[53]

See also

Notes

References

1. ^¹²³⁴⁵⁶⁷⁸⁹¹⁰¹¹¹²¹³¹⁴¹⁵¹⁶¹⁷¹⁸{{cite book |url=https://textfiles.meulie.net/bitsaved/Books/Mackenzie_CodedCharSets.pdf |title=Coded Character Sets, History and Development |work=The Systems Programming Series |author-last=Mackenzie |author-first=Charles E. |date=1980 |edition=1 |publisher=Addison-Wesley Publishing Company, Inc. |isbn=978-0-201-14460-4 |lccn=77-90165 |pages=6, 66, 211, 215, 217, 220, 223, 228, 236–238, 243–245, 247–253, 423, 425–428, 435–439 |archive-url=https://web.archive.org/web/20160526172151/https://textfiles.meulie.net/bitsaved/Books/Mackenzie_CodedCharSets.pdf |archive-date=May 26, 2016 |dead-url=no |access-date=2018-09-28}}
2. ^Internet Assigned Numbers Authority (IANA) (May 14, 2007). "Character Sets". Accessed 2008-04-14.
3. ^¹{{cite news |author-first=Mary |author-last=Brandel |date=July 6, 1999 |url=http://edition.cnn.com/TECH/computing/9907/06/1963.idg/ |title=1963: The Debut of ASCII |publisher=CNN |access-date=2008-04-14}}
4. ^¹²³{{cite web |title=American Standard Code for Information Interchange, ASA X3.4-1963 |publisher=American Standards Association (ASA) |date=1963-06-17 |url=http://worldpowersystems.com/ARCHIVE/codes/X3.4-1963/index.html |access-date=2018-09-28 |dead-url=no |archive-url=https://web.archive.org/web/20180928201050/http://worldpowersystems.com/ARCHIVE/codes/X3.4-1963/index.html |archive-date=September 28, 2018}}
5. ^¹²{{cite journal |title=USA Standard Code for Information Interchange, USAS X3.4-1967 |publisher=United States of America Standards Institute (USASI) |date=July 7, 1967}}
6. ^{{cite web |title=An annotated history of some character codes or ASCII: American Standard Code for Information Infiltration |author-first=Thomas Daniel |author-last=Jennings |author-link=Thomas Daniel Jennings |website=World Power Systems (WPS) |date=2016-04-20 |orig-year=1999 |url=http://worldpowersystems.com/ARCHIVE/codes/#ASCII-1967 |access-date=2018-09-28 |dead-url=no |archive-url=https://web.archive.org/web/20180928201025/http://worldpowersystems.com/ARCHIVE/codes/#ASCII-1967 |archive-date=September 28, 2018}}
7. ^¹²{{cite journal |title=American National Standard for Information Systems — Coded Character Sets — 7-Bit American National Standard Code for Information Interchange (7-Bit ASCII), ANSI X3.4-1986 |publisher=American National Standards Institute (ANSI) |date=March 26, 1986}}
8. ^{{citation |title=Internet Security Glossary, Version 2 |date=August 2007 |author-first=R. |author-last=Shirley |rfc=4949 |url=https://tools.ietf.org/html/rfc4949 |access-date=2016-06-13 |dead-url=no |archive-url=https://web.archive.org/web/20160613203815/https://tools.ietf.org/html/rfc4949 |archive-date=2016-06-13}}
9. ^{{cite book |author-last=Maini |author-first=Anil Kumar |title=Digital Electronics: Principles, Devices and Applications |url=https://books.google.com/?id=NQSpNAEACAAJ&pg=PA28 |date=2007 |publisher=John Wiley and Sons |isbn=978-0-470-03214-5 |page=28 |quote=In addition, it defines codes for 33 nonprinting, mostly obsolete control characters that affect how the text is processed.}}
10. ^{{cite journal |title=Binary Computer Codes and ASCII |author-first=Ed |author-last=Bukstein |journal=Electronics World |date=July 1964 |volume=72 |number=1 |pages=28–29 |url=http://www.swtpc.com/mholley/ElectronicsWorld/Jul1964/EW_Jul1964.htm |access-date=2016-05-22}}
11. ^Brief Report: Meeting of CCITT Working Party on the New Telegraph Alphabet, May 13–15, 1963.
12. ^Report of ISO/TC/97/SC 2 – Meeting of October 29–31, 1963.
13. ^Report on Task Group X3.2.4, June 11, 1963, Pentagon Building, Washington, DC.
14. ^Report of Meeting No. 8, Task Group X3.2.4, December 17 and 18, 1963
15. ^¹²{{cite web |title=US and International standards: ASCII |url=http://homepages.cwi.nl/~dik/english/codes/stand.html#ascii |author-first=Dik T. |author=Winter |date=2010 |orig-year=2003 |dead-url=yes |archive-url=https://web.archive.org/web/20100116001012/http://homepages.cwi.nl/~dik/english/codes/stand.html#ascii |archive-date=2010-01-16}}
16. ^¹²³⁴⁵⁶{{cite web |title=7-bit character sets: Revisions of ASCII |author-first=Tuomas |author-last=Salste |publisher=Aivosto Oy |date=January 2016 |id={{URN|nbn|fi-fe201201011004}} |url=http://www.aivosto.com/vbtips/charsets-7bit.html#body |access-date=2016-06-13 |dead-url=no |archive-url=https://web.archive.org/web/20160613145224/http://www.aivosto.com/vbtips/charsets-7bit.html#body |archive-date=2016-06-13}}
17. ^{{cite journal |title=Information |author-first= |author-last= |date=September 1966 |volume=215 |number=3 |type=special edition |journal=Scientific American |url=https://www.jstor.org/stable/e24931041 |jstor=e24931041 |pages=}}
18. ^{{cite book |title=Unicode Explained – Internationalize Documents, Programs, and Web Sites |author-first=Jukka K. |author-last=Korpela |edition=2nd release of 1st |date=2014-03-14 |orig-year=2006-06-07 |publisher=O'Reilly Media, Inc. |isbn=978-0-596-10121-3 |page=118}}
19. ^{{citation |title=ANSI INCITS 4-1986 (R2007): American National Standard for Information Systems – Coded Character Sets – 7-Bit American National Standard Code for Information Interchange (7-Bit ASCII) |date=2007 |orig-year=1986 |id= |url=http://sliderule.mraiow.com/w/images/7/73/ASCII.pdf |access-date=2016-06-12 |dead-url=no |archive-url=https://web.archive.org/web/20140207170900/http://sliderule.mraiow.com/w/images/7/73/ASCII.pdf |archive-date=2014-02-07}}
20. ^{{citation |title=Bit Sequencing of the American National Standard Code for Information Interchange in Serial-by-Bit Data Transmission |id=X3.15-1966 |date=1966 |publisher=American National Standards Institute (ANSI)}}
21. ^{{cite web |title=BruXy: Radio Teletype communication |date=2005-10-10 |access-date=2016-05-09 |url=http://bruxy.regnet.cz/web/hamradio/EN/radio-teletype-communication/ |quote=The transmitted code use International Telegraph Alphabet No. 2 (ITA-2) which was introduced by CCITT in 1924.}}
22. ^¹{{cite web |author-last=Smith |author-first=Gil |title=Teletype Communication Codes |publisher=Baudot.net |date=2001 |url=http://www.baudot.net/docs/smith--teletype-codes.pdf |access-date=2008-07-11}}
23. ^{{cite book |author-first1=Stanley A. |author-last1=Sawyer |author-first2=Steven George |author-last2=Krantz |title=A TeX Primer for Scientists |url=https://books.google.com/books?id=bXLDwmIJNkUC&pg=PA13 |date=1995 |publisher=CRC Press, LLC |isbn=978-0-8493-7159-2 |page=13|bibcode=1995tps..book.....S }}
24. ^{{cite web |title=Computer Keyboards |url=http://www.quadibloc.com/comp/kybint.htm |author-first=John J. G. |author-last=Savard |access-date=2014-08-24}}
25. ^{{cite journal |url=https://www.pcmag.com/encyclopedia_term/0,2542,t=ASCIIbetical&i=38025,00.asp |title=ASCIIbetical definition |journal=PC Magazine |access-date=2008-04-14}}
26. ^{{citation |title=Internet Message Format |author-first=P. |author-last=Resnick |date=April 2001 |rfc=2822 |url=https://tools.ietf.org/html/rfc2822 |access-date=2016-06-13 |dead-url=no |archive-url=https://web.archive.org/web/20160613203505/https://tools.ietf.org/html/rfc2822 |archive-date=2016-06-13}} (NB. NO-WS-CTL.)
27. ^{{cite web |title=Understanding ASCII Codes |author-last1=McConnell |author-first1=Robert |author-last2=Haynes |author-first2=James |author-last3=Warren |author-first3=Richard |url=http://www.nadcomm.com/ascii_code.htm |access-date=2014-05-11}}
28. ^{{cite mailing list |url=http://lists.gnu.org/archive/html/help-gnu-emacs/2014-05/msg00448.html |title=Re: editor and word processor history (was: Re: RTF for emacs) |author=Barry Margolin |mailing-list=help-gnu-emacs |date=May 29, 2014}}
29. ^¹{{cite web |url=http://bitsavers.trailing-edge.com/pdf/dec/pdp6/DEC-6-0-EX-SYS-UM-IP-PRE00_Multiprogramming_System_Manual_1965.pdf |title=PDP-6 Multiprogramming System Manual |page=43 |publisher=Digital Equipment Corporation (DEC) |date=1965}}
30. ^¹{{cite web |url=http://bitsavers.org/pdf/dec/pdp10/1970_PDP-10_Ref/1970PDP10Ref_Part3.pdf |title=PDP-10 Reference Handbook, Book 3, Communicating with the Monitor |at=p. 5-5 |publisher=Digital Equipment Corporation (DEC) |date=1969}}
31. ^{{cite web|url=https://www.gnu.org/software/emacs/manual/html_node/emacs/Help.html|title=Help - GNU Emacs Manual}}
32. ^{{cite web|url=http://dosmandrivel.blogspot.com/2007/08/is-dos-rip-off-of-cpm.html|title=Is DOS a Rip-Off of CP/M?|author=Tim Paterson|date=August 8, 2007|website=DosMan Drivel}}
33. ^{{cite conference |url=http://www.multicians.org/jhs-jfo-terminals.pdf |title=Technical and human engineering problems in connecting terminals to a time-sharing system |author-last1=Ossanna |author-first1=J. F. |author-link1=Joe Ossanna |author-last2=Saltzer |author-first2=J. H. |author-link2=Jerry Saltzer |date=November 17–19, 1970 |publisher=AFIPS Press |booktitle=Proceedings of the November 17–19, 1970, Fall Joint Computer Conference (FJCC) |pages=355–362 |location=p. 357 |quote=Using a "new-line" function (combined carriage-return and line-feed) is simpler for both man and machine than requiring both functions for starting a new line; the American National Standard X3.4-1968 permits the line-feed code to carry the new-line meaning.}}
34. ^{{citation |title=TELNET Protocol |rfc=158 |pages=4–5 |author-first=T. |author-last=O'Sullivan |date=1971-05-19 |publisher=Internet Engineering Task Force (IETF) |url=https://tools.ietf.org/html/rfc158 |access-date=2013-01-28 |dead-url=no |archive-url=https://web.archive.org/web/20160613202223/https://tools.ietf.org/html/rfc158 |archive-date=2016-06-13}}
35. ^{{citation |title=File Transfer Protocol |rfc=542 |author-first=Nancy J. |author-last=Neigus |date=1973-08-12 |publisher=Internet Engineering Task Force (IETF) |url=https://tools.ietf.org/html/rfc542 |access-date=2013-01-28 |dead-url=no |archive-url=https://web.archive.org/web/20160613202314/https://tools.ietf.org/html/rfc542 |archive-date=2016-06-13}}
36. ^{{citation |title=File Transfer Protocol |rfc=765 |author-first=Jon |author-last=Postel |author-link=Jon Postel |date=June 1980 |publisher=Internet Engineering Task Force (IETF) |url=https://tools.ietf.org/html/rfc765 |access-date=2013-01-28 |dead-url=no |archive-url=https://web.archive.org/web/20160613202356/https://tools.ietf.org/html/rfc765 |archive-date=2016-06-13}}
37. ^{{cite web|url=https://www.mercurial-scm.org/wiki/EOLTranslationPlan |title=EOL translation plan for Mercurial |publisher=Mercurial |access-date=2017-06-24}}
38. ^{{cite web |title=Bare LFs in SMTP |url=http://cr.yp.to/docs/smtplf.html |author-first=Daniel J. |author-last=Bernstein |author-link=Daniel J. Bernstein |access-date=2013-01-28}}
39. ^{{cite book |url=http://www.bitsavers.org/pdf/digitalResearch/cpm/1.4/CPM_1.4_Interface_Guide_1978.pdf |title=CP/M 1.4 Interface Guide |date=1978 |page=10 |publisher=Digital Research}}
40. ^{{citation |title=ASCII format for Network Interchange |author-first=Vinton Gray |author-last=Cerf |author-link=Vinton Gray Cerf |publisher=Network Working Group |date=1969-10-16 |rfc=20 |url=https://tools.ietf.org/html/rfc20 |access-date=2016-06-13 |dead-url=no |archive-url=https://web.archive.org/web/20160613203624/https://tools.ietf.org/html/rfc20 |archive-date=2016-06-13}} (NB. Almost identical wording to USAS X3.4-1968 except for the intro.)
41. ^{{cite web|title=First-Hand: Chad is Our Most Important Product: An Engineer's Memory of Teletype Corporation |author-first=Jim |publisher=Engineering and Technology History Wiki (ETHW) |date=2015-01-13 |author-last=Haynes |url=http://ethw.org/First-Hand:Chad_is_Our_Most_Important_Product:_An_Engineer's_Memory_of_Teletype_Corporation |access-date=2016-10-31 |dead-url=no |archive-url=https://web.archive.org/web/20161031223347/http://ethw.org/First-Hand%3AChad_is_Our_Most_Important_Product%3A_An_Engineer%27s_Memory_of_Teletype_Corporation |archive-date=October 31, 2016 |quote=There was the change from 1961 ASCII to 1968 ASCII. Some computer languages used characters in 1961 ASCII such as up arrow and left arrow. These characters disappeared from 1968 ASCII. We worked with Fred Mocking, who by now was in Sales at Teletype, on a type cylinder that would compromise the changing characters so that the meanings of 1961 ASCII were not totally lost. The underscore character was made rather wedge-shaped so it could also serve as a left arrow.}}
42. ^{{cite web |author-link=Robert William Bemer |author-last=Bemer |author-first=Robert William |url=http://www.trailing-edge.com/~bobbemer/EUROPE.HTM |title=Bemer meets Europe (Computer Standards) – Computer History Vignettes |publisher=Trailing-edge.com |access-date=2008-04-14 |dead-url=yes |archive-url=https://web.archive.org/web/20131017062722/http://www.trailing-edge.com/~bobbemer/EUROPE.HTM |archive-date=2013-10-17}} (NB. Bemer was employed at IBM at that time.)
43. ^{{cite web |url=http://www.thocp.net/biographies/bemer_bob.htm |title=Robert William Bemer: Biography |date=2013-03-09 |dead-url=no |archive-url=https://web.archive.org/web/20160616081929/http://www.thocp.net/biographies/bemer_bob.htm |archive-date=2016-06-16}}
44. ^{{cite web |title=Memorandum Approving the Adoption by the Federal Government of a Standard Code for Information Interchange |author-last=Johnson |author-first=Lyndon Baines |author-link=Lyndon Baines Johnson |publisher=The American Presidency Project |date=1968-03-11 |url=http://www.presidency.ucsb.edu/ws/index.php?pid=28724 |access-date=2008-04-14}}
45. ^{{cite newsgroup|url=https://groups.google.com/d/msg/alt.folklore.computers/gbg5YVFaT48/wlVFfJ2j4hYJ|title=Re: Early history of ASCII?|author=Richard S. Shuford|date=December 20, 1996|newsgroup=alt.folklore.computers|message-id=Pine.SUN.3.91.961220100220.13180C-100000@duncan.cs.utk.edu}}
46. ^{{cite book |publisher=McGraw-Hill Inc. |title=Compilation of Data Communications Standards |editor-first1=Harold C. |editor-last1=Folts |editor-first2=Harry |editor-last2=Karp |date=1982-02-01 |edition=2nd revised |isbn=978-0-07-021457-6 }}
47. ^{{cite web |title=UTF-8 Growth on the Web |author-last=Dubost |author-first=Karl |date=2008-05-06 |work=W3C Blog |publisher=World Wide Web Consortium |url=http://www.w3.org/QA/2008/05/utf8-web-growth.html |access-date=2010-08-15 |dead-url=no |archive-url=https://web.archive.org/web/20160616084132/https://www.w3.org/blog/2008/05/utf8-web-growth/ |archive-date=2016-06-16}}
48. ^¹{{cite web |title=Moving to Unicode 5.1 |author-last=Davis |author-first=Mark |author-link=Mark Davis (Unicode) |date=2008-05-05 |work=Official Google Blog |url=http://googleblog.blogspot.com/2008/05/moving-to-unicode-51.html |access-date=2010-08-15 |dead-url=no |archive-url=https://web.archive.org/web/20160616084637/https://googleblog.blogspot.de/2008/05/moving-to-unicode-51.html |archive-date=2016-06-16}}
49. ^{{cite web |title=Unicode nearing 50% of the web |author-last=Davis |author-first=Mark |author-link=Mark Davis (Unicode) |date=2010-01-28 |work=Official Google Blog |url=http://googleblog.blogspot.com/2010/01/unicode-nearing-50-of-web.html |access-date=2010-08-15 |dead-url=no |archive-url=https://web.archive.org/web/20160616085323/https://googleblog.blogspot.de/2010/01/unicode-nearing-50-of-web.html |archive-date=2016-06-16}}
50. ^"Specific Criteria", attachment to memo from R. W. Reach, "X3-2 Meeting – September 14 and 15", September 18, 1961
51. ^{{citation |author-last=Maréchal |author-first=R. |title=ISO/TC 97 – Computers and Information Processing: Acceptance of Draft ISO Recommendation No. 1052 |date=1967-12-22}}
52. ^{{cite book |author=The Unicode Consortium |editor-first=Julie D. |editor-last=Allen |title=The Unicode standard, Version 5.0 |date=2006-10-27 |publisher=Addison-Wesley Professional |location=Upper Saddle River, New Jersey, US |isbn=978-0-321-48091-0 |chapter-url=http://unicode.org/book/ch13.pdf |access-date=2015-03-13 |chapter=Chapter 13: Special Areas and Format Characters |page=314}}
53. ^{{cite web |title=utf-8(7) – Linux manual page |publisher=Man7.org |date=2014-02-26 |url=http://man7.org/linux/man-pages/man7/utf-8.7.html |access-date=2014-04-21}}