ASCII
{{pp-move-vandalism|small=yes}}{{otheruses}}
frame|The 95 graphic ASCII characters, numbered 32 to 126 (decimal)American Standard Code for Information Interchange (
ASCII), {{pronEng|ˈæski}}
(1) is a
character-encoding scheme based on the
English alphabet. ASCII codes represent
text in
computers,
communications equipment, and other devices that work with text. Most modern
character-encoding schemes—which support many more characters than did the original—have a historical basis in ASCII.Historically, ASCII developed from
telegraphic codes. Its first commercial use was as a seven-
bit teleprinter code promoted by Bell data services. Work on ASCII formally began October 6, 1960, with the first meeting of the ASA X3.2 subcommittee. The first edition of the standard was published in 1963,
(2)(3) a major revision in 1967,
(4) and the most recent update in 1986.
(5) 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.ASCII includes definitions for 128 characters: 33 are non-printing, mostly-obsolete
control characters that affect how text is processed;
(6) 94 are printable characters, and the
space is considered an invisible graphic.
(7) and ultimately the
American National Standards Institute.The X3.2 subcommittee designed ASCII based on 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 standard,
Fieldata and early
EBCDIC, more than 64 codes were required in ASCII.The committee debated the possibility of a
shift key function (like the
Baudot code), which would allow more than 64 codes to be represented by six
bits. In a shifted code, some character codes determine choices between options for the following character codes. This allows compact encoding, but is less reliable for data transmission; 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.
(8)The committee considered an eight-bit code, since eight bits would allow two four-bit patterns to efficiently encode two digits with
binary coded decimal. However this 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, this also allowed for a
parity bit for error checking if desired.
(9) Machines with
octets as the native data type that did not use parity checking typically set the eighth bit to
0.
(10)The code itself was structured so that most control codes were together, and all graphic codes were together. The first two columns (32 positions) were reserved for control characters.
(11) The
"space" character had to come before graphics to make
sorting algorithms easy, so it became position 32.
(12) The committee decided it was important to support
upper case 64-character alphabets, and chose to structure ASCII so it could easily be reduced to a usable 64-character set of graphic codes.
(13) Lower case letters were therefore not interleaved with upper case. To keep options open for lower case letters and other graphics, the special and numeric codes were placed before the letters, and the letter 'A' was placed in position 65 to match the draft of the corresponding British standard.
(14) The digits 0–9 were placed so they correspond to values in binary prefixed with 011, making conversion with
binary-coded decimal straightforward.Many of the non-alphanumeric characters were positioned to correspond to their shifted position on typewriters. Thus #, $ and % were placed to correspond to 3, 4, and 5 in the adjacent column. The parentheses could not correspond to 9 and 0, however, because the place corresponding to 0 was taken by the space character. Since many European typewriters placed the parentheses with 8 and 9, those corresponding positions were chosen for the parentheses. 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 64 next to the letter A.
(15)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.
(16)With the other special characters and control codes filled in, ASCII was published as ASA X3.4-1963, leaving 28 code positions without any assigned meaning, reserved for future standardization, and one unassigned control code.
(17) It now seems obvious that these positions should have been assigned to the lower case alphabet, but there was some debate at the time whether there should be more control characters instead.
(18) The indecision did not last long: in May 1963 the
CCITT Working Party on the New Telegraph Alphabet proposed to assign lower case characters to columns 6 and 7,
(19) and
International Organization for Standardization TC 97 SC 2 voted in October to incorporate the change into its draft standard.
(20) The X3.2.4 task group voted its approval for the change to ASCII at its May 1963 meeting.
(21) Locating the lowercase letters in columns 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
curly bracket and vertical line characters),
(22) renaming some control characters (SOM became start of header (SOH)) and moving or removing others (RU was removed).
(23) ASCII was subsequently updated as USASI X3.4-1967, then USASI X3.4-1968, ANSI X3.4-1977, and finally, ANSI X3.4-1986 (the first two are occasionally retronamed ANSI X3.4-1967, and ANSI X3.4-1968).The X3 committee also addressed how ASCII should be transmitted (least significant bit first), and how it should be recorded on perforated tape. They proposed a
9-track standard for magnetic tape, and attempted to deal with some forms of
punched card formats.ASCII itself first entered commercial use in 1963 as a seven-bit teleprinter code for
American Telephone & Telegraph's
TWX (Teletype Wide-area eXchange) network. TWX originally used the earlier five-bit
Baudot code, which was also used by the competing
Telex teleprinter system.
Bob Bemer introduced features such as the escape sequence.
(24)On March 11, 1968, U.S. President
Lyndon B. Johnson mandated that all computers purchased by the United States federal government support ASCII, stating:
I have also approved recommendations of the Secretary of Commerce regarding standards for recording the Standard Code for Information Interchange on magnetic tapes and paper tapes when they are used in computer operations.All computers and related equipment configurations brought into the Federal Government inventory on and after July 1, 1969, must have the capability to use the Standard Code for Information Interchange and the formats prescribed by the magnetic tape and paper tape standards when these media are used.(25)
Other international standards bodies have ratified character encodings such as
ISO/IEC 646 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 only suited the needs of the USA and a few other countries. For example, Canada had its own version that supported French characters. Other adapted encodings include
ISCII (India),
VISCII (Vietnam), and
YUSCII (Yugoslavia). Although these encodings are sometimes referred to as ASCII, true ASCII is strictly defined only by ANSI standard.ASCII was incorporated into the
Unicode character set as the first 128 symbols, so the ASCII characters have the same numeric codes in both sets. This allows
UTF-8 to be
backward compatible with ASCII, a significant advantage.Asteroid
3568 ASCII is named after the character encoding.
ASCII control characters
ASCII reserves the first 32 codes (numbers 0–31 decimal) for
control characters: codes originally intended not to carry 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". 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 left was sometimes intentional (where a character would be used slightly differently on a terminal link than on a data stream) and sometimes more accidental (such as what "delete" means).Probably the most influential single device on the interpretation of these characters was the
ASR-33 Teletype series, 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 up through the 1980s, lower cost and in some ways less fragile than magnetic tape. In particular, the Teletype 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. 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 faded out.The use of Control-S (XOFF, an abbreviation for "transmit off") as a handshaking signal warning a sender to stop transmission because of impending overflow, and Control-Q (XON, "transmit on") to resume sending, 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.Code 127 is officially named "delete" but the Teletype label was "rubout". Since the original standard gave no detailed interpretation for most control codes, interpretations of this code varied. The original Teletype meaning, and the intent of the standard, was to make it an ignored character, the same as NUL (all zeroes). This was specifically useful for
paper tape, because punching the all-ones bit pattern on top of an existing mark would obliterate it. Tapes designed to be "hand edited" could even be produced with spaces of extra NULs (blank tape) so that a block of characters could be "rubbed out" and then replacements put into the empty space.As video terminals began to replace printing ones, the value of the "rubout" character was lost. DEC systems, for example, interpreted "Delete" to mean "remove the character before the cursor," and this interpretation also became common in Unix systems. Most other systems used "Backspace" for that meaning and used "Delete" to mean "remove the character at the cursor". That latter interpretation is the most common today.Many more of the control codes have taken on meanings quite different from their original ones. The "escape" character (code 27), for example, was originally intended 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 drifted. 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") 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.The inherent ambiguity of many control characters, combined with their historical usage, created problems when transferring "plain text" files between systems. The clearest example of this is the
newline problem on various
operating systems. On printing terminals there is no question that you terminate a line of text with both "Carriage Return" and "Linefeed". The first returns the printing carriage to the beginning of the line and the second advances to the next line without moving the carriage. However, requiring two characters to mark the end of a line introduced unnecessary complexity and questions as to how to interpret each character when encountered alone. To simplify matters, plain text files on Unix and Amiga systems use line feeds alone to separate lines. Similarly, older Macintosh systems, among others, use only carriage returns in plain text files. Various
DEC operating systems used both characters to mark the end of a line, perhaps for compatibility with
teletypes, and this de facto standard was copied in the
CP/M operating system and then in
MS-DOS and eventually
Microsoft Windows. Transmission of text over the
Internet, for protocols as
E-mail and the
World Wide Web, uses both characters.The DEC operating systems, along with CP/M, tracked file length only in units of disk blocks and used Control-Z (SUB) to mark the end of the actual text in the file (also done for CP/M compatibility in some cases in MS-DOS, though MS-DOS has always recorded exact file-lengths). Text
strings ending with the
null character are known as
ASCIZ or
C strings.{| class="wikitable" style="text-align: center"
|
! Binary !! Oct !! Dec !! Hex !! Abbr !! PR(27) !! CS(28) !! CEC(29) !! Description
|
| 000 | style="background:#CFF;" | | 00 | | {{unicode>␀}} | Control-@ | > | | Null character |
|
| 001 | style="background:#CFF;" | | 01 | | {{unicode>␁}} | ^A | | align=left| Start of Header |
|
| 002 | style="background:#CFF;" | | 02 | | {{unicode>␂}} | ^B | | align=left| Start of Text |
|
| 003 | style="background:#CFF;" | | 03 | | {{unicode>␃}} | Control-C | > | | End of Text |
|
| 004 | style="background:#CFF;" | | 04 | | {{unicode>␄}} | Control-D | > | | End of Transmission |
|
| 005 | style="background:#CFF;" | | 05 | | {{unicode>␅}} | ^E | | align=left | Enquiry (computer communications)>Enquiry |
|
| 006 | style="background:#CFF;" | | 06 | | {{unicode>␆}} | ^F | | align=left | Acknowledge character>Acknowledgment |
|
| 007 | style="background:#CFF;" | | 07|BEL | {{unicode>␇}} | Control-G>^G| a | Bell |
|
| 010 | style="background:#CFF;" | | 08|BS | {{unicode>␈}} | Control-H>^H| b | Backspace | (30)(31)
|
| 011 | style="background:#CFF;" | | 09|HT | {{unicode>␉}} | Control-I>^I| t | Horizontal Tab |
|
| 012 | style="background:#CFF;" | | 0A|LF | {{unicode>␊}} | Control-J>^J| n | Line feed |
|
| 013 | style="background:#CFF;" | | 0B|VT | {{unicode>␋}} | |^K| v Vertical Tab |
|
| 014 | style="background:#CFF;" | | 0C|FF | {{unicode>␌}} | |^L| f Form feed |
|
| 015 | style="background:#CFF;" | | 0D|CR | {{unicode>␍}} | carriage return>^M| r | Carriage return | (32)
|
| 016 | style="background:#CFF;" | | 0E|SO | {{unicode>␎}} | |^N| Shift Out |
|
| 017 | style="background:#CFF;" | | 0F|SI | {{unicode>␏}} | |^O| Shift In |
|
| 020 | style="background:#CFF;" | | 10|DLE | {{unicode>␐}} | |^P| Data Link Escape |
|
| 021 | style="background:#CFF;" | | 11|DC1 | {{unicode>␑}} | |^Q| Device Control 1 (oft. XON) |
|
| 022 | style="background:#CFF;" | | 12|DC2 | {{unicode>␒}} | |^R| Device Control 2 |
|
| 023 | style="background:#CFF;" | | 13|DC3 | {{unicode>␓}} | |^S| Device Control 3 (oft. XOFF) |
|
| 024 | style="background:#CFF;" | | 14|DC4 | {{unicode>␔}} | |^T| Device Control 4 |
|
| 025 | style="background:#CFF;" | | 15|NAK | {{unicode>␕}} | |^U| Negative Acknowledgement |
|
| 026 | style="background:#CFF;" | | 16|SYN | {{unicode>␖}} | Control-V>^V| | Synchronous Idle |
|
| 027 | style="background:#CFF;" | | 17|ETB | {{unicode>␗}} | |^W| End of Trans. Block |
|
| 030 | style="background:#CFF;" | | 18|CAN | {{unicode>␘}} | Control-X>^X| | Cancel |
|
| 031 | style="background:#CFF;" | | 19|EM | {{unicode>␙}} | Control-Y>^Y| | End of Medium |
|
| 032 | style="background:#CFF;" | | 1A|SUB | {{unicode>␚}} | Control-Z>^Z| | Substitute |
|
| 033 | style="background:#CFF;" | | 1B|ESC | {{unicode>␛}} | |^[| e(33) Escape | (34)
|
| 034 | style="background:#CFF;" | | 1C|FS | {{unicode>␜}} | |^| File Separator |
|
| 035 | style="background:#CFF;" | | 1D|GS | {{unicode>␝}} | |^]| Group Separator |
|
| 036 | style="background:#CFF;" | | 1E|RS | {{unicode>␞}} | |^^| Record Separator |
|
| 037 | style="background:#CFF;" | | 1F|US | {{unicode>␟}} | |^_| Unit Separator |
|
|
|
| 177 | style="background:#CFF;" | | 7F|DEL | {{unicode>␡}} | |^?| Delete | (35)(36) Codes 33 to 126, known as the printable characters, represent letters, digits, punctuation marks, and a few miscellaneous symbols.Seven-bit ASCII provided seven "national" characters and, if the combined hardware and software permit, can use overstrikes to simulate some additional international characters: in such a scenario a backspace can precede a grave accent (which the American and British standards, but only those standards, also call "opening single quotation mark"), a backtick, or a breath mark (inverted vel).{| class="wikitable" style="text-align: center; float:left;"
|
!Binary !! Oct !! Dec !! Hex !! Glyph
|
| 040 | style="background:#CCFFFF;" | | 20 | Space (punctuation) | ␠}} |
|
| 041 | style="background:#CCFFFF;" | | 21 | ! |
|
| 042 | style="background:#CCFFFF;" | | 22 | " |
|
| 043 | style="background:#CCFFFF;" | | 23 | # |
|
| 044 | style="background:#CCFFFF;" | | 24 | $ |
|
| 045 | style="background:#CCFFFF;" | | 25 | % |
|
| 046 | style="background:#CCFFFF;" | | 26 | & |
|
| 047 | style="background:#CCFFFF;" | | 27 | ' |
|
| 050 | style="background:#CCFFFF;" | | 28 | ( |
|
| 051 | style="background:#CCFFFF;" | | 29 | ) |
|
| 052 | style="background:#CCFFFF;" | | 2A | * |
|
| 053 | style="background:#CCFFFF;" | | 2B | + |
|
| 054 | style="background:#CCFFFF;" | | 2C | , |
|
| 055 | style="background:#CCFFFF;" | | 2D | - |
|
| 056 | style="background:#CCFFFF;" | | 2E | . |
|
| 057 | style="background:#CCFFFF;" | | 2F | / |
|
| 060 | style="background:#CCFFFF;" | | 30 | 0 |
|
| 061 | style="background:#CCFFFF;" | | 31 | 1 |
|
| 062 | style="background:#CCFFFF;" | | 32 | 2 |
|
| 063 | style="background:#CCFFFF;" | | 33 | 3 |
|
| 064 | style="background:#CCFFFF;" | | 34 | 4 |
|
| 065 | style="background:#CCFFFF;" | | 35 | 5 |
|
| 066 | style="background:#CCFFFF;" | | 36 | 6 |
|
| 067 | style="background:#CCFFFF;" | | 37 | 7 |
|
| 070 | style="background:#CCFFFF;" | | 38 | 8 |
|
| 071 | style="background:#CCFFFF;" | | 39 | 9 |
|
| 072 | style="background:#CCFFFF;" | | 3A | (Colon (punctuation)|:) |
|
| 073 | style="background:#CCFFFF;" | | 3B | ; |
|
| 074 | style="background:#CCFFFF;" | | 3C | | <
|
| 075 | style="background:#CCFFFF;" | | 3D | = |
|
| 076 | style="background:#CCFFFF;" | | 3E | > |
|
| 077 | style="background:#CCFFFF;" | | 3F | ? |
{| class="wikitable" style="text-align:center; float:left;"|
valign="bottom"!Binary !! Oct !! Dec !! Hex !! Glyph
|
| 100 | style="background:#CCFFFF;" | | 40 | @ |
|
| 101 | style="background:#CCFFFF;" | | 41 | A |
|
| 102 | style="background:#CCFFFF;" | | 42 | B |
|
| 103 | style="background:#CCFFFF;" | | 43 | C |
|
| 104 | style="background:#CCFFFF;" | | 44 | D |
|
| 105 | style="background:#CCFFFF;" | | 45 | E |
|
| 106 | style="background:#CCFFFF;" | | 46 | F |
|
| 107 | style="background:#CCFFFF;" | | 47 | G |
|
| 110 | style="background:#CCFFFF;" | | 48 | H |
|
| 111 | style="background:#CCFFFF;" | | 49 | I |
|
| 112 | style="background:#CCFFFF;" | | 4A | J |
|
| 113 | style="background:#CCFFFF;" | | 4B | K |
|
| 114 | style="background:#CCFFFF;" | | 4C | L |
|
| 115 | style="background:#CCFFFF;" | | 4D | M |
|
| 116 | style="background:#CCFFFF;" | | 4E | N |
|
| 117 | style="background:#CCFFFF;" | | 4F | O |
|
| 120 | style="background:#CCFFFF;" | | 50 | P |
|
| 121 | style="background:#CCFFFF;" | | 51 | Q |
|
| 122 | style="background:#CCFFFF;" | | 52 | R |
|
| 123 | style="background:#CCFFFF;" | | 53 | S |
|
| 124 | style="background:#CCFFFF;" | | 54 | T |
|
| 125 | style="background:#CCFFFF;" | | 55 | U |
|
| 126 | style="background:#CCFFFF;" | | 56 | V |
|
| 127 | style="background:#CCFFFF;" | | 57 | W |
|
| 130 | style="background:#CCFFFF;" | | 58 | X |
|
| 131 | style="background:#CCFFFF;" | | 59 | Y |
|
| 132 | style="background:#CCFFFF;" | | 5A | Z |
|
| 133 | style="background:#CCFFFF;" | | 5B | [ |
|
| 134 | style="background:#CCFFFF;" | | 5C | |
|
| 135 | style="background:#CCFFFF;" | | 5D | ] |
|
| 136 | style="background:#CCFFFF;" | | 5E | ^ |
|
| 137 | style="background:#CCFFFF;" | | 5F | _ |
{| class="wikitable" style="text-align:center; float:left;"|
valign="bottom"!Binary !! Oct !! Dec !! Hex !! Glyph
|
| 140 | style="background:#CCFFFF;" | | 60 | ` |
|
| 141 | style="background:#CCFFFF;" | | 61 | a |
|
| 142 | style="background:#CCFFFF;" | | 62 | b |
|
| 143 | style="background:#CCFFFF;" | | 63 | c |
|
| 144 | style="background:#CCFFFF;" | | 64 | d |
|
| 145 | style="background:#CCFFFF;" | | 65 | e |
|
| 146 | style="background:#CCFFFF;" | | 66 | f |
|
| 147 | style="background:#CCFFFF;" | | 67 | g |
|
| 150 | style="background:#CCFFFF;" | | 68 | h |
|
| 151 | style="background:#CCFFFF;" | | 69 | i |
|
| 152 | style="background:#CCFFFF;" | | 6A | j |
|
| 153 | style="background:#CCFFFF;" | | 6B | k |
|
| 154 | style="background:#CCFFFF;" | | 6C | l |
|
| 155 | style="background:#CCFFFF;" | | 6D | m |
|
| 156 | style="background:#CCFFFF;" | | 6E | n |
|
| 157 | style="background:#CCFFFF;" | | 6F | o |
|
| 160 | style="background:#CCFFFF;" | | 70 | p |
|
| 161 | style="background:#CCFFFF;" | | 71 | q |
|
| 162 | style="background:#CCFFFF;" | | 72 | r |
|
| 163 | style="background:#CCFFFF;" | | 73 | s |
|
| 164 | style="background:#CCFFFF;" | | 74 | t |
|
| 165 | style="background:#CCFFFF;" | | 75 | u |
|
| 166 | style="background:#CCFFFF;" | | 76 | v |
|
| 167 | style="background:#CCFFFF;" | | 77 | w |
|
| 170 | style="background:#CCFFFF;" | | 78 | x |
|
| 171 | style="background:#CCFFFF;" | | 79 | y |
|
| 172 | style="background:#CCFFFF;" | | 7A | z |
|
| 173 | style="background:#CCFFFF;" | | 7B | { |
|
| 174 | style="background:#CCFFFF;" | | 7C | | |
|
| 175 | style="background:#CCFFFF;" | | 7D | } |
|
| 176 | style="background:#CCFFFF;" | | 7E | ~ |
{{clear}}Aliases
A June 1992 RFC(37) and the Internet Assigned Numbers Authority registry of character sets
- ANSI_X3.4-1968 (canonical name)
- iso-ir-6
- ANSI_X3.4-1986
- ISO_646.irv:1991
- ASCII (with ASCII-7 and ASCII-8 variants)
- ISO646-US
- US-ASCII (preferred MIME name(38))
- us
- IBM367
- cp367
- csASCII
Of these, the IANA encourages use of the name "US-ASCII" for Internet uses of ASCII. One often finds this in the optional "charset" parameter in the Content-Type header of some MIME messages, in the equivalent "meta" element of some HTML documents, and in the encoding declaration part of the prologue of some XML documents.Variants
As computer technology spread throughout the world, different standards bodies and corporations developed many variations of ASCII in order 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 cover all variants, including those that do not preserve ASCII's character-map in the 7-bit range.The PETSCII Code used by Commodore International for their 8-bit systems is probably unique among post-1970 codes in being based on ASCII-1963 instead of the far more common ASCII-1967, such as found on the ZX Spectrum computer. Atari and Galaksija computers also used ASCII variants.Incompatibility vs interoperability
From early in its development,(39) ASCII was intended to be just one of several national variants of an international character code standard, ultimately published as ISO/IEC 646 (1972), which 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 in 1967(40) caused ASCII's choices for the national use characters to appear to be de facto standards for the world, leading to confusion and incompatibility once other countries did begin to make their own assignments to these code points. ISO/IEC 646, like ASCII, was a 7-bit character set. It made no 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 these were rarely used, so it was often impossible to know what variant to work with and therefore which character a code represented, and text-processing systems could generally 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 had to get used to reading and writing
ä aÄiÜ='Ön'; ü
instead of
{ a[i]='n'; }
C trigraphs were created to solve this issue in ANSI C, although their late introduction and inconsistent implementation in compilers limited their use.Eventually, as 8-, 16-, and 32-bit computers began to replace 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, with the 128 additional characters providing room to avoid most of the ambiguity that had been necessary in 7-bit codes.For example, IBM developed 8-bit code pages, such as 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.Eight-bit standards such as ISO/IEC 8859 (derived from the DEC-MCS) and Mac OS Roman 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. This enabled representation of characters used in a broader range of languages. Because there were several competing 8-bit code standards, they continued to suffer from incompatibilities and limitations. Still, ISO-8859-1 (Latin 1), its variant Windows-1252 (often mislabeled as ISO-8859-1), and the original 7-bit ASCII remain the most common character encodings in use today.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).To permit backward compatibility, the 128 ASCII and 256 ISO-8859-1 (Latin 1) characters are assigned Unicode/UCS code points that are the same as their codes in the earlier standards. Therefore, ASCII can be considered a 7-bit encoding scheme for a very small subset of Unicode/UCS, and, conversely, the UTF-8 encoding forms are binary-compatible with ASCII for code points below 128, meaning every properly encoded ASCII file is also a valid UTF-8 file. The other encoding forms resemble ASCII in how they represent the first 128 characters of Unicode, but use 16 or 32 bits per character, so they require conversion for compatibility.Order
Collation of data is sometimes done in ASCII-code order rather than "standard" alphabetical order. The main deviations are:
- capitals come before lowercase letters, i.e. "Z" before "a"
- characters in extended character sets such as "é" come after "z"
The slang expression ASCIIbetical is sometimes used for this order.(41)In programming, alphanumeric sorting means to sort by numeric value, without regard for any character set. An alphanumerically sorted array of bytes will appear ASCIIbetically when viewed in an ASCII-compatible character set.A refined version of this order converts uppercase letters to lowercase before comparing ASCII values.References
-
[Audio pronunciation for ASCII. Merriam Webster. Accessed 2008-04-14.]
-
[Mary Brandel (July 6, 1999). 1963: The Debut of ASCII: CNN. Accessed 2008-04-14.]
-
[American Standard Code for Information Interchange, ASA X3.4-1963, American Standards Association, June 17, 1963]
-
[USA Standard Code for Information Interchange, USAS X3.4-1967, United States of America Standards Institute, July 7, 1967]
-
[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, American National Standards Institute, Inc., March 26, 1986]
-
[International Organization for Standardization (December 1, 1975). "The set of control characters for ISO 646". Internet Assigned Numbers Authority Registry. Alternate U.S. version: weblink. Accessed 2008-04-14.]
-
History
missing image!
- ASCII Code Chart-Quick ref card.jpg -
US ASCII 1968 Code Chart was structured with two columns of control characters, a column with special characters, a column with numbers, and four columns of letters
The American Standard Code for Information Interchange (ASCII) was developed under the auspices of a committee of the American Standards Association, called the X3 committee, by its X3.2 (later X3L2) subcommittee, and later by that subcommittee's X3.2.4 working group. The ASA became the United States of America Standards Institute or USASI[Mackenzie, p.211.]
-
[Decision 4. Mackenzie, p.215.]
-
[Decision 5. Mackenzie, p.217.]
-
[Sawyer A. Sawyer and Steven George Krantz (January 1, 1995). A Tex Primer for Scientists. CRC Press. ISBN 0-8493-7159-7. p.13.]
-
[Decision 8,9. Mackenzie, p.220.]
-
[Decision 10. Mackenzie, p.237.]
-
[Decision 14. Mackenzie, p.228.]
-
[Decision 18. Mackenzie, p.238.]
-
[Mackenzie, p.243.]
-
[Mackenzie, p.243-245.]
-
[Mackenzie, p.66, 245.]
-
[Mackenzie, p.435.]
-
[Brief Report: Meeting of CCITT Working Party on the New Telegraph Alphabet, May 13-15, 1963.]
-
[Report of ISO/TC/97/SC 2 - Meeting of October 29-31, 1963.]
-
[Report on Task Group X3.2.4, June 11, 1963, Pentagon Building, Washington, DC.]
-
[Report of Meeting No. 8, Task Group X3.2.4, December 17 and 18, 1963]
-
[Mackenzie, p.247-8.]
-
[Bob Bemer (n.d.). Bemer meets Europe. Trailing-edge.com. Accessed 2008-04-14. Employed at IBM at that time]
-
[Lyndon B. Johnson (March 11, 1968). Memorandum Approving the Adoption by the Federal Government of a Standard Code for Information Interchange. The American Presidency Project. Accessed 2008-04-14.]
-
[RFC 2822 (April 2001). "NO-WS-CTL".]
-
[Printable Representation, the Unicode characters from the area U+2400 to U+2421 reserved for representing control characters when it is necessary to print or display them rather than have them perform their intended function. Some browsers may not display these properly.]
-
[Control key Sequence/caret notation, the traditional key sequences for inputting control characters. The caret (^) that begins these sequences is not meant to signify the literal ^ character; rather, it represents the "Control" or "Ctrl" key that must be held down while pressing the second key in the sequence. Note that ^^ means Control-Caret (pressing the "Ctrl" and "^" keys), not Control-Control. The caret-key representation is also used by some software to represent control characters.]
-
[Character Escape Codes in C programming language and many other languages influenced by it, such as Java and Perl (though not all implementations necessarily support all escape codes).]
-
[The Backspace character can also be entered by pressing the "Backspace", "Bksp", or ← key on some systems.]
-
[The ambiguity surrounding Backspace comes from mismatches between the intent of the human or software transmitting the Backspace and the interpretation by the software receiving it. If the transmitter expects Backspace to erase the previous character and the receiver expects Delete to be used to erase the previous character, many receivers will echo the Backspace as "^H", just as they would echo any other uninterpreted control character. (A similar mismatch in the other direction may yield Delete displayed as "^?".)]
-
[The Carriage Return character can also be entered by pressing the "Return", "Ret", "Enter", or {{Unicode|↵}} key on most systems.]
-
[The 'e' escape sequence is not part of ISO C and many other language specifications. However, it is understood by several compilers.]
-
[The Escape character can also be entered by pressing the "Escape" or "Esc" key on some systems.]
-
[The Delete character can also be entered by pressing the "Delete" or "Del" key. It can also be entered by pressing the "Backspace", "Bksp", or ← key on some systems.]
-
{{reflist|group=t}}ASCII printable characters
Code 32, the "space" character, denotes the space between words, as produced by the space-bar of a keyboard. The "space" character is considered an invisible graphic rather than a control character.[Mackenzie, p.223.]
[RFC 1345 (June 1992).]
[Internet Assigned Numbers Authority (May 14, 2007). "Character Sets". Accessed 2008-04-14.]
["Specific Criteria," attachment to memo from R. W. Reach, "X3-2 Meeting -- September 14 and 15," September 18, 1961]
[R. Maréchal, ISO/TC 97 - Computers and Information Processing: Acceptance of Draft ISO Recommendation No. 1052, December 22, 1967]
[ASCIIbetical definition. PC Magazine. Accessed 2008-04-14.]
Further reading
- R.W. Bemer, "A Proposal for Character Code Compatibility," Communications of the ACM, Vol. 3. No. 2, February, 1960, pp. 71-72
- NEWS, History and impact of computer standards, G.S. Robinson & C. Cargill, Computer Vol. 29, no. 10, 79-85, October 1996,
- BOOK, American National Standard Code for Information Interchange, American National Standards Institute, et al, 1977, The Institute,
- BOOK, Coded Character Sets, History and Development, Charles E. Mackenzie, Addison-Wesley, 0201144603, 1980,
External links
{{character encoding}}آسكيঅ্যাস্কি(zh-min-nan:ASCII)ASCIIASCIIASCIIASCIIAmerican Standard Code for Information InterchangeASCIIASCIIASCIIAskioASCIIاسکی (استاندارد)American Standard Code for Information InterchangeASCIIASCII아스키 코드ASCIIASCIIASCIIASCIIASCIIASCIIASCIIASCIIASCIIASCIIASCII (tekenset)ASCIIASCIIASCIIASCIIASCIIASCIIASCIIASCIIASCIIASCIIASCIIASCIIASCIIASCIIแอสกีASCIIASCIIASCIIامریکی معیاری رمز براۓ اطلاعاتی تبادلہASCII
(...as imported from WP)
article has not been saved locally
