â€å“iã¢â‚¬â„¢m Never Drinking Like That Againã¢â‚¬â

American character encoding standard

This commodity is near the character encoding. For other uses, come across ASCII (disambiguation).

ASCII

ASCII chart from a pre-1972 printer manual
MIME / IANA	united states-ascii
Allonym(es)	ISO-IR-006,[1] ANSI_X3.4-1968, ANSI_X3.4-1986, ISO_646.irv:1991, ISO646-The states, us, IBM367, cp367[ii]
Language(s)	English language
Nomenclature	ISO 646 series
Extensions	Unicode ISO/IEC 8859 (series) KOI-8 OEM (series) Windows-125x (serial) Others
Preceded by	ITA 2, FIELDATA
Succeeded by	ISO 8859, Unicode
v t eastward

ASCII ( Ass-kee),^{[three] : half dozen} abbreviated from American Standard Code for Data Interchange, is a character encoding standard for electronic advice. ASCII codes represent text in computers, telecommunications equipment, and other devices. Most modern graphic symbol-encoding schemes are based on ASCII, although they support many additional characters.

The Internet Assigned Numbers Authority (IANA) prefers the name US-ASCII for this character encoding.^[2]

ASCII is one of the IEEE milestones.

Overview [edit]

ASCII was developed from telegraph code. Its first commercial apply was equally a 7-bit teleprinter code promoted past Bell information services.^{[ when? ]} Work on the ASCII standard began in May 1961, with the offset meeting of the American Standards Clan'southward (ASA) (at present the American National Standards Institute or ANSI) X3.2 subcommittee. The starting time edition of the standard was published in 1963,^{[4] [5]} underwent a major revision during 1967,^{[half dozen] [7]} and experienced its near contempo update during 1986.^[8] Compared to earlier telegraph codes, the proposed Bell code and ASCII were both ordered for more convenient sorting (i.eastward., alphabetization) of lists and added features for devices other than teleprinters.^{[ citation needed ]}

The use of ASCII format for Network Interchange was described in 1969.^[ix] That document was formally elevated to an Internet Standard in 2015.^[x]

Originally based on the English alphabet, ASCII encodes 128 specified characters into 7-bit integers as shown by the ASCII chart above.^[11] Ninety-five of the encoded characters are printable: these include the digits 0 to 9, lowercase letters a to z, upper-case letter letters A to Z, and punctuation symbols. In addition, the original ASCII specification included 33 non-printing control codes which originated with Teletype machines; about of these are now obsolete,^[12] although a few are however 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.

History [edit]

ASCII (1963). Control pictures of equivalent controls are shown where they exist, or a greyness dot otherwise.

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 commission, by its X3.two (later X3L2) subcommittee, and later by that subcommittee'south X3.2.4 working group (now INCITS). The ASA subsequently became the United States of America Standards Constitute (USASI),^{[three] : 211} and ultimately became the American National Standards Plant (ANSI).

With the other special characters and control codes filled in, ASCII was published as ASA X3.4-1963,^{[v] [13]} leaving 28 code positions without any assigned meaning, reserved for future standardization, and one unassigned control code.^{[3] : 66, 245} At that place was some debate at the time whether in that location should exist more control characters rather than the lowercase alphabet.^{[three] : 435} The indecision did non final long: during May 1963 the CCITT Working Party on the New Telegraph Alphabet proposed to assign lowercase characters to sticks ^{[a] [14]} 6 and seven,^[15] and International Organization for Standardization TC 97 SC 2 voted during Oct to incorporate the change into its draft standard.^[16] The X3.2.4 task group voted its blessing for the modify to ASCII at its May 1963 coming together.^[17] Locating the lowercase letters in sticks ^{[a] [xiv]} 6 and 7 acquired the characters to differ in scrap blueprint from the upper instance past a single bit, which simplified instance-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),^[eighteen] renaming some control characters (SOM became starting time of header (SOH)) and moving or removing others (RU was removed).^{[3] : 247–248} ASCII was subsequently updated as USAS X3.4-1967,^{[half dozen] [xix]} then USAS X3.four-1968, ANSI X3.4-1977, and finally, ANSI X3.4-1986.^{[8] [twenty]}

Revisions of the ASCII standard:

• ASA X3.four-1963^{[three] [5] [xix] [20]}
• ASA X3.four-1965 (approved, only not published, notwithstanding used past IBM 2260 & 2265 Brandish Stations and IBM 2848 Brandish Control)^{[three] : 423, 425–428, 435–439 [21] [19] [20]}
• USAS X3.four-1967^{[three] [six] [xx]}
• USAS X3.4-1968^{[3] [xx]}
• ANSI X3.4-1977^[twenty]
• ANSI X3.4-1986^{[8] [20]}
• ANSI X3.4-1986 (R1992)
• ANSI X3.iv-1986 (R1997)
• ANSI INCITS 4-1986 (R2002)^[22]
• ANSI INCITS iv-1986 (R2007)^[23]
• (ANSI) INCITS four-1986[R2012]^[24]
• (ANSI) INCITS 4-1986[R2017]^[25]

In the X3.15 standard, the X3 committee too addressed how ASCII should exist transmitted (least meaning bit first),^{[3] : 249–253 [26]} and how it should be recorded on perforated record. They proposed a 9-track standard for magnetic tape, and attempted to deal with some punched card formats.

Pattern considerations [edit]

Bit width [edit]

The X3.ii subcommittee designed ASCII based on the earlier teleprinter encoding systems. Like other character encodings, ASCII specifies a correspondence between digital flake 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 grapheme-oriented information such as written language. Before ASCII was developed, the encodings in utilize included 26 alphabetic characters, ten numerical digits, and from xi 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,^{[27] [28]} FIELDATA (1956^{[ citation needed ]}), and early on EBCDIC (1963), more than than 64 codes were required for ASCII.

ITA2 was in plough based on the 5-scrap telegraph code that Émile Baudot invented in 1870 and patented in 1874.^[28]

The committee debated the possibility of a shift office (like in ITA2), which would allow more than 64 codes to be represented by a 6-fleck lawmaking. In a shifted code, some grapheme codes determine choices between options for the post-obit grapheme codes. Information technology allows compact encoding, merely is less reliable for data transmission, as an error in transmitting the shift code typically makes a long office of the transmission unreadable. The standards committee decided against shifting, and and then ASCII required at least a seven-bit code.^{[three] : 215 §13.6, 236 §4}

The committee considered an viii-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 manual to transport eight bits when vii could suffice. The commission voted to use a seven-fleck lawmaking to minimize costs associated with data transmission. Since perforated record at the time could record viii bits in one position, information technology too allowed for a parity scrap for mistake checking if desired.^{[3] : 217 §c, 236 §v} Eight-flake machines (with octets as the native data type) that did non utilise parity checking typically ready the eighth bit to 0.^[29]

Internal arrangement [edit]

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-chosen ASCII sticks ^{[a] [xiv]} (32 positions) were reserved for control characters.^{[3] : 220, 236 8, 9)} The "infinite" character had to come up before graphics to make sorting easier, and so it became position 20_hex;^{[3] : 237 §10} for the aforementioned reason, many special signs commonly used equally 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 fix of graphic codes,^{[3] : 228, 237 §xiv} as was washed in the DEC SIXBIT code (1963). Lowercase letters were therefore not interleaved with capital letter. To continue options bachelor for lowercase messages and other graphics, the special and numeric codes were arranged before the letters, and the letter of the alphabet A was placed in position 41_hex to match the typhoon of the corresponding British standard.^{[3] : 238 §18} The digits 0–9 are prefixed with 011, but the remaining 4 bits correspond to their corresponding 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 of import subtlety is that these were based on mechanical typewriters, not electric typewriters.^[xxx] Mechanical typewriters followed the de facto standard set by the Remington No. 2 (1878), the first typewriter with a shift key, and the shifted values of 23456789- were "#$%_&'() – early typewriters omitted 0 and 1, using O (uppercase 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,^{[a] [14]} positions 1–5, corresponding to the digits 1–5 in the adjacent stick.^{[a] [xiv]} The parentheses could not correspond to nine and 0, however, because the place respective to 0 was taken by the space grapheme. 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 ix. This discrepancy from typewriters led to bit-paired keyboards, notably the Teletype Model 33, which used the left-shifted layout corresponding to ASCII, differently from traditional mechanical typewriters.

Electrical typewriters, notably the IBM Selectric (1961), used a somewhat different layout that has go de facto standard on computers – post-obit the IBM PC (1981), specially Model Thou (1984) – and thus shift values for symbols on modernistic keyboards do not stand for equally closely to the ASCII table equally 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 cease) so they could be used in uppercase without unshifting). However, ASCII split up the ;: pair (dating to No. 2), and rearranged mathematical symbols (varied conventions, commonly -* =+) to :* ;+ -=.

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

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

Character lodge [edit]

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

• All uppercase come before lowercase messages; for example, "Z" precedes "a"
• Digits and many punctuation marks come before letters

An intermediate order converts uppercase messages to lowercase before comparison ASCII values.

Character groups [edit]

Control characters [edit]

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

For instance, character 10 represents the "line feed" function (which causes a printer to advance its paper), and graphic symbol eight represents "backspace". RFC 2822 refers to control characters that do not include carriage return, line feed or white space as non-whitespace control characters.^[32] 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 certificate layout and formatting.

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

Probably the nearly influential single device affecting the interpretation of these characters was the Teletype Model 33 ASR, which was a printing terminal with an available paper tape reader/dial option. Paper tape was a very popular medium for long-term programme storage until the 1980s, less costly and in some ways less fragile than magnetic record. In particular, the Teletype Model 33 machine assignments for codes 17 (Control-Q, DC1, likewise known as XON), 19 (Control-S, DC3, also known as XOFF), and 127 (Delete) became de facto standards. The Model 33 was as well notable for taking the clarification of Command-G (lawmaking seven, BEL, significant audibly alert the operator) literally, as the unit independent an actual bong which information technology 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 graphic symbol instead of underscore), a noncompliant use of code 15 (Control-O, Shift In) interpreted as "delete previous character" was likewise adopted past many early timesharing systems only eventually became neglected.

When a Teletype 33 ASR equipped with the automatic newspaper record reader received a Command-Southward (XOFF, an abbreviation for transmit off), it caused the tape reader to finish; receiving Control-Q (XON, "transmit on") caused the tape reader to resume. This so-called flow control technique became adopted by several early computer operating systems equally a "handshaking" signal warning a sender to stop transmission because of impending buffer overflow; it persists to this twenty-four hours in many systems as a manual output control technique. On some systems, Control-S retains its meaning but Control-Q is replaced past a 2d Control-S to resume output.

The 33 ASR besides could exist configured to employ Control-R (DC2) and Control-T (DC4) to offset and stop the tape dial; on some units equipped with this function, the corresponding control character lettering on the keycap above the letter was TAPE and Tape respectively.^[33]

Delete vs Backspace [edit]

The Teletype could not move its typehead backwards, so information technology did not have a primal on its keyboard to transport a BS (backspace). Instead, there was a key marked RUB OUT that sent code 127 (DEL). The purpose of this key was to erase mistakes in a manually-input paper tape: the operator had to push a push button on the tape punch to back information technology up, then type the rubout, which punched all holes and replaced the mistake with a grapheme that was intended to be ignored.^[34] Teletypes were commonly used with the less-expensive computers from Digital Equipment Corporation; these systems had to use what keys were bachelor, and thus the DEL code was assigned to erase the previous grapheme.^{[35] [36]} Considering of this, Dec video terminals (by default) sent the DEL code for the key marked "Backspace" while the separate key marked "Delete" sent an escape sequence; many other competing terminals sent a BS code for the Backspace key.

The Unix terminal driver could only utilise one code to erase the previous character, this could be set to BS or DEL, just non both, resulting in recurring situations of ambiguity where users had to determine depending on what concluding they were using (shells that allow line editing, such every bit ksh, bash, and zsh, sympathize both). The assumption that no key sent a BS code allowed Command+H to exist used for other purposes, such as the "help" prefix command in GNU Emacs.^[37]

Escape [edit]

Many more of the control codes have been assigned meanings quite unlike from their original ones. The "escape" character (ESC, lawmaking 27), for example, was intended originally to permit sending of other control characters as literals instead of invoking their meaning, a so-called "escape sequence". This is the aforementioned meaning of "escape" encountered in URL encodings, C language strings, and other systems where sure characters have a reserved significant. Over time this estimation has been co-opted and has eventually been changed.

In modern usage, an ESC sent to the last usually indicates the start of a command sequence ordinarily in the grade of a so-called "ANSI escape lawmaking" (or, more properly, a "Control Sequence Introducer") from ECMA-48 (1972) and its successors, beginning with ESC followed by a "[" (left-bracket) grapheme. In contrast, an ESC sent from the terminal is most ofttimes used equally an out-of-band grapheme used to terminate an operation or special mode, as in the TECO and six text editors. In graphical user interface (GUI) and windowing systems, ESC generally causes an application to abort its electric current performance or to exit (cease) altogether.

End of Line [edit]

The inherent ambiguity of many control characters, combined with their historical usage, created problems when transferring "manifestly 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 Render" (which moves the printhead to the beginning of the line) and "Line Feed" (which advances the paper ane line without moving the printhead). The name "Carriage Return" comes from the fact that on a transmission typewriter the wagon holding the paper moves while the typebars that strike the ribbon remain stationary. The entire carriage had to be pushed (returned) to the left in order to position the paper for the next line.

DEC operating systems (OS/viii, RT-11, RSX-xi, RSTS, TOPS-10, etc.) used both characters to mark the end of a line and then that the console device (originally Teletype machines) would piece of work. By the time so-called "glass TTYs" (later on called CRTs or "impaired terminals") came along, the convention was and so well established that backward compatibility necessitated continuing to follow it. When Gary Kildall created CP/M, he was inspired by some of the command line interface conventions used in DEC's RT-xi operating system.

Until the introduction of PC DOS in 1981, IBM had no influence in this because their 1970s operating systems used EBCDIC encoding instead of ASCII, and they were oriented toward punch-card input and line printer output on which the concept of "wagon render" was meaningless. IBM's PC DOS (also marketed as MS-DOS past Microsoft) inherited the convention by virtue of being loosely based on CP/Chiliad,^[38] and Windows in turn inherited it from MS-DOS.

Unfortunately, requiring two characters to mark the stop of a line introduces unnecessary complexity and ambiguity as to how to interpret each character when encountered by itself. To simplify matters, evidently text information streams, including files, on Multics^[39] used line feed (LF) alone as a line terminator. Unix and Unix-similar systems, and Amiga systems, adopted this convention from Multics. On the other paw, the original Macintosh Bone, Apple DOS, and ProDOS used carriage render (CR) alone as a line terminator; however, since Apple tree has now replaced these obsolete operating systems with the Unix-based macOS operating system, they at present utilize line feed (LF) besides. The Radio Shack TRS-80 as well used a lone CR to terminate lines.

Computers fastened 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 which used EBCDIC rather than ASCII encoding. The Telnet protocol defined an ASCII "Network Virtual Terminal" (NVT), so that connections between hosts with unlike line-ending conventions and character sets could be supported past transmitting a standard text format over the network. Telnet used ASCII along with CR-LF line endings, and software using other conventions would interpret betwixt the local conventions and the NVT.^[40] 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.^{[41] [42]} This adds complication to implementations of those protocols, and to other network protocols, such every bit those used for Email and the Www, on systems not using the NVT's CR-LF line-catastrophe convention.^{[43] [44]}

End of File/Stream [edit]

The PDP-6 monitor,^[35] and its PDP-10 successor TOPS-10,^[36] used Control-Z (SUB) as an end-of-file indication for input from a terminal. Some operating systems such as CP/Thousand tracked file length only in units of disk blocks, and used Command-Z to mark the end of the actual text in the file.^[45] For these reasons, EOF, or stop-of-file, was used colloquially and conventionally equally a three-letter acronym for Command-Z instead of SUBstitute. The end-of-text lawmaking (ETX), also known every bit Control-C, was inappropriate for a variety of reasons, while using Z as the control lawmaking to end a file is analogous to its position at the finish of the alphabet, and serves as a very convenient mnemonic assist. A historically common and still prevalent convention uses the ETX code convention to interrupt and halt a programme via an input data stream, normally from a keyboard.

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

Control code chart [edit]

Binary	Oct	Dec	Hex	Abridgement			Unicode Command Pictures[b]	Caret notation[c]	C Escape Sequences[d]	Name (1967)
				1963	1965	1967
000 0000	000	0	00	Cypher	NUL		␀	^@	\0	Null
000 0001	001	1	01	SOM	SOH		␁	^A		Showtime of Heading
000 0010	002	2	02	EOA	STX		␂	^B		Start of Text
000 0011	003	3	03	EOM	ETX		␃	^C		Finish of Text
000 0100	004	four	04	EOT			␄	^D		End of Transmission
000 0101	005	5	05	WRU	ENQ		␅	^E		Enquiry
000 0110	006	six	06	RU	ACK		␆	^F		Acknowledgement
000 0111	007	vii	07	BELL	BEL		␇	^1000	\a	Bong
000 1000	010	8	08	FE0	BS		␈	^H	\b	Backspace[e] [f]
000 1001	011	9	09	HT/SK	HT		␉	^I	\t	Horizontal Tab[g]
000 1010	012	10	0A	LF			␊	^J	\n	Line Feed
000 1011	013	11	0B	VTAB	VT		␋	^K	\v	Vertical Tab
000 1100	014	12	0C	FF			␌	^50	\f	Form Feed
000 1101	015	xiii	0D	CR			␍	^M	\r	Carriage Render[h]
000 1110	016	xiv	0E	Then			␎	^N		Shift Out
000 1111	017	15	0F	SI			␏	^O		Shift In
001 0000	020	xvi	10	DC0	DLE		␐	^P		Data Link Escape
001 0001	021	17	11	DC1			␑	^Q		Device Control i (often XON)
001 0010	022	18	12	DC2			␒	^R		Device Control 2
001 0011	023	xix	13	DC3			␓	^S		Device Command three (oftentimes XOFF)
001 0100	024	xx	14	DC4			␔	^T		Device Control iv
001 0101	025	21	15	ERR	NAK		␕	^U		Negative Acknowledgement
001 0110	026	22	16	SYNC	SYN		␖	^V		Synchronous Idle
001 0111	027	23	17	LEM	ETB		␗	^Westward		Terminate of Transmission Block
001 1000	030	24	18	S0	CAN		␘	^X		Abolish
001 1001	031	25	19	S1	EM		␙	^Y		Stop of Medium
001 1010	032	26	1A	S2	SS	SUB	␚	^Z		Substitute
001 1011	033	27	1B	S3	ESC		␛	^[	\e [i]	Escape[j]
001 1100	034	28	1C	S4	FS		␜	^\		File Separator
001 1101	035	29	1D	S5	GS		␝	^]		Group Separator
001 1110	036	xxx	1E	S6	RS		␞	^^ [g]		Record Separator
001 1111	037	31	1F	S7	US		␟	^_		Unit Separator
111 1111	177	127	7F	DEL			␡	^?		Delete[fifty] [f]

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

Printable characters [edit]

Codes xx_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.^[m]

Lawmaking 20_hex, the "infinite" character, denotes the space betwixt words, as produced by the infinite bar of a keyboard. Since the space character is considered an invisible graphic (rather than a control graphic symbol)^{[iii] : 223 [46]} information technology is listed in the table beneath instead of in the previous section.

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

Binary	Oct	Dec	Hex	Glyph
				1963	1965	1967
010 0000	040	32	20	infinite
010 0001	041	33	21	!
010 0010	042	34	22	"
010 0011	043	35	23	#
010 0100	044	36	24	$
010 0101	045	37	25	%
010 0110	046	38	26	&
010 0111	047	39	27	'
010 one thousand	050	40	28	(
010 1001	051	41	29	)
010 1010	052	42	2A	*
010 1011	053	43	2B	+
010 1100	054	44	2C	,
010 1101	055	45	2nd	-
010 1110	056	46	2E	.
010 1111	057	47	2F	/
011 0000	060	48	30	0
011 0001	061	49	31	i
011 0010	062	fifty	32	ii
011 0011	063	51	33	3
011 0100	064	52	34	four
011 0101	065	53	35	5
011 0110	066	54	36	6
011 0111	067	55	37	7
011 k	070	56	38	8
011 1001	071	57	39	9
011 1010	072	58	3A	:
011 1011	073	59	3B	;
011 1100	074	threescore	3C	<
011 1101	075	61	3D	=
011 1110	076	62	3E	>
011 1111	077	63	3F	?
100 0000	100	64	40	@	`	@
100 0001	101	65	41	A
100 0010	102	66	42	B
100 0011	103	67	43	C
100 0100	104	68	44	D
100 0101	105	69	45	E
100 0110	106	70	46	F
100 0111	107	71	47	G
100 1000	110	72	48	H
100 1001	111	73	49	I
100 1010	112	74	4A	J
100 1011	113	75	4B	One thousand
100 1100	114	76	4C	L
100 1101	115	77	4D	Thousand
100 1110	116	78	4E	N
100 1111	117	79	4F	O
101 0000	120	eighty	50	P
101 0001	121	81	51	Q
101 0010	122	82	52	R
101 0011	123	83	53	S
101 0100	124	84	54	T
101 0101	125	85	55	U
101 0110	126	86	56	V
101 0111	127	87	57	W
101 1000	130	88	58	10
101 1001	131	89	59	Y
101 1010	132	90	5A	Z
101 1011	133	91	5B	[
101 1100	134	92	5C	\	~	\
101 1101	135	93	5D	]
101 1110	136	94	5E	↑	^
101 1111	137	95	5F	←	_
110 0000	140	96	threescore		@	`
110 0001	141	97	61		a
110 0010	142	98	62		b
110 0011	143	99	63		c
110 0100	144	100	64		d
110 0101	145	101	65		e
110 0110	146	102	66		f
110 0111	147	103	67		g
110 thou	150	104	68		h
110 1001	151	105	69		i
110 1010	152	106	6A		j
110 1011	153	107	6B		k
110 1100	154	108	6C		l
110 1101	155	109	6D		m
110 1110	156	110	6E		north
110 1111	157	111	6F		o
111 0000	160	112	70		p
111 0001	161	113	71		q
111 0010	162	114	72		r
111 0011	163	115	73		south
111 0100	164	116	74		t
111 0101	165	117	75		u
111 0110	166	118	76		five
111 0111	167	119	77		due west
111 1000	170	120	78		10
111 1001	171	121	79		y
111 1010	172	122	7A		z
111 1011	173	123	7B		{
111 1100	174	124	7C	ACK	¬	|
111 1101	175	125	7D		}
111 1110	176	126	7E	ESC	|	~

Character set up [edit]

ASCII (1977/1986)

0

1

ii

3

iv

v

6

7

8

9

A

B

C

D

E

F

0x

NUL

SOH

STX

ETX

EOT

ENQ

ACK

BEL

BS

HT

LF

VT

FF

CR

Then

SI

1x

DLE

DC1

DC2

DC3

DC4

NAK

SYN

ETB

Tin can

EM

SUB

ESC

FS

GS

RS

US

2x

SP

!

"

#

$

%

&

'

(

)

*

+

,

-

.

/

3x

0

i

two

3

4

v

half-dozen

vii

8

9

:

;

<

=

>

?

4x

@

A

B

C

D

Eastward

F

Thousand

H

I

J

K

50

M

N

O

5x

P

Q

R

S

T

U

V

Westward

X

Y

Z

[

\

]

^

_

6x

`

a

b

c

d

e

f

1000

h

i

j

g

l

m

northward

o

7x

p

q

r

s

t

u

5

w

x

y

z

{

|

}

~

DEL

Changed or added in 1963 version  Inverse in both 1963 version and 1965 typhoon

Usage [edit]

ASCII was first used commercially during 1963 as a seven-scrap teleprinter code for American Telephone & Telegraph'due south TWX (TeletypeWriter exchange) network. TWX originally used the before five-fleck ITA2, which was too used past the competing Telex teleprinter system. Bob Bemer introduced features such as the escape sequence.^[four] His British colleague Hugh McGregor Ross helped to popularize this work – according to Bemer, "so much so that the code that was to become ASCII was start called the Bemer–Ross Code in Europe".^[48] Because of his all-encompassing work on ASCII, Bemer has been called "the father of ASCII".^[49]

On March 11, 1968, US President Lyndon B. Johnson mandated that all computers purchased by the United States Federal Government support ASCII, stating:^{[50] [51] [52]}

I have also approved recommendations of the Secretary of Commerce [Luther H. Hodges] regarding standards for recording the Standard Lawmaking for Data Interchange on magnetic tapes and paper tapes when they are used in reckoner operations. All computers and related equipment configurations brought into the Federal Government inventory on and later on July ane, 1969, must have the adequacy to use the Standard Code for Information Interchange and the formats prescribed by the magnetic tape and paper record standards when these media are used.

ASCII was the well-nigh common character encoding on the Www until December 2007, when UTF-8 encoding surpassed it; UTF-8 is backward compatible with ASCII.^{[53] [54] [55]}

Variants and derivations [edit]

Equally computer engineering spread throughout the earth, unlike standards bodies and corporations developed many variations of ASCII to facilitate the expression of not-English languages that used Roman-based alphabets. I could course some of these variations as "ASCII extensions", although some misuse that term to represent all variants, including those that do non preserve ASCII'south character-map in the 7-scrap range. Furthermore, the ASCII extensions accept also been mislabelled as ASCII.

7-bit codes [edit]

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

Other international standards bodies take 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 Great britain's pound sterling (£); e.m. with code folio 1104. Almost every country needed an adapted version of ASCII, since ASCII suited the needs of only the Usa and a few other countries. For instance, Canada had its ain version that supported French characters.

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

Information technology would share about characters in common, but assign other locally useful characters to several code points reserved for "national use". All the same, the four years that elapsed between the publication of ASCII-1963 and ISO's beginning credence of an international recommendation during 1967^[57] acquired ASCII's choices for the national use characters to seem to be de facto standards for the world, causing defoliation and incompatibility once other countries did begin to make their ain assignments to these code points.

ISO/IEC 646, like ASCII, is a seven-bit graphic symbol set. Information technology does not make whatever additional codes available, so the same code points encoded unlike characters in different countries. Escape codes were defined to indicate which national variant applied to a piece of text, but they were rarely used, then information technology was often incommunicable 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 anyhow.

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. developer using their national variant of ISO/IEC 646, rather than ASCII, had to write, and, thus, read, something such as

ä aÄiÜ = 'Ön'; ü

instead of

{ a[i] = '\n'; }

C trigraphs were created to solve this problem for ANSI C, although their late introduction and inconsistent implementation in compilers express their utilise. Many programmers kept their computers on Us-ASCII, and then evidently-text in Swedish, German etc. (for example, in email or Usenet) independent "{, }" and similar variants in the middle of words, something those programmers got used to. For case, a Swedish programmer mailing another programmer asking if they should go for luncheon, 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".

In Japan and Korea, still as of the 2020s,^[update] a variation of ASCII is used, in which the backslash (5C hex) is rendered as ¥ (a Yen sign, in Japan) or ₩ (a Won sign, in Korea). This ways that, for instance, the file path C:\Users\Smith is shown as C:¥Users¥Smith (in Japan) or C:₩Users₩Smith (in Korea).

viii-bit codes [edit]

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

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

Most early habitation computer systems developed their own eight-bit graphic symbol 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/Thou 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 beingness based on ASCII-1963, instead of the more than mutual ASCII-1967, such equally establish on the ZX Spectrum computer. Atari viii-bit computers and Galaksija computers also used ASCII variants.

The IBM PC divers code folio 437, which replaced the command 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 i of the offset extensions designed more than 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 messages and typographic punctuation marks instead of graphics, more than similar modernistic grapheme sets.

The ISO/IEC 8859 standard (derived from the DEC-MCS) finally provided a standard that most systems copied (at least every bit accurately as they copied ASCII, but with many substitutions). A pop further extension designed past 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-scrap ASCII were the almost common character encodings until 2008 when UTF-8 became more common.^[54]

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

Unicode [edit]

Unicode and the ISO/IEC 10646 Universal Character Set (UCS) have a much wider array of characters and their diverse encoding forms have begun to supersede ISO/IEC 8859 and ASCII rapidly in many environments. While ASCII is limited to 128 characters, Unicode and the UCS support more than 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-xvi, and UTF-32, respectively).

ASCII was incorporated into the Unicode (1991) grapheme set as the kickoff 128 symbols, and then the 7-bit ASCII characters have the aforementioned numeric codes in both sets. This allows UTF-8 to exist backward uniform with seven-bit ASCII, every bit a UTF-8 file containing only ASCII characters is identical to an ASCII file containing the same sequence of characters. Even more importantly, forwards compatibility is ensured as software that recognizes only vii-bit ASCII characters as special and does not alter bytes with the highest bit gear up (equally is often done to support 8-flake ASCII extensions such as ISO-8859-ane) will preserve UTF-8 data unchanged.^[59]

See likewise [edit]

• 3568 ASCII, an asteroid named after the character encoding
• Alt codes
• Ascii85
• ASCII fine art
• ASCII Ribbon Campaign
• Basic Latin (Unicode block) (ASCII as a subset of Unicode)
• Extended ASCII
• HTML decimal character rendering
• Jargon File, a glossary of computer programmer slang which includes a list of mutual slang names for ASCII characters
• Listing of reckoner character sets
• List of Unicode characters

Notes [edit]

1. ^ ^{a b c d e} The 128 characters of the 7-bit ASCII character set are divided into eight 16-character groups called sticks 0–7, associated with the 3 most-significant bits.^[fourteen] Depending on the horizontal or vertical representation of the character map, sticks correspond with either table rows or columns.
2. ^ The Unicode characters from the "Control Pictures" surface area U+2400 to U+2421 reserved for representing control characters when it is necessary to print or brandish them rather than have them perform their intended office. Some browsers may not brandish these properly.
3. ^ Caret notation is often used to correspond control characters on a terminal. On most text terminals, holding down the Ctrl key while typing the 2d character will type the control character. Sometimes the shift primal is not needed, for instance ^@ may be typable with just Ctrl and 2.
4. ^ Character escape sequences in C programming language and many other languages influenced past it, such as Coffee and Perl (though not all implementations necessarily support all escape sequences).
5. ^ The Backspace character can also be entered by pressing the ← Backspace primal on some systems.
6. ^ ^{a b} The ambivalence of Backspace is due to early terminals designed assuming the main utilise of the keyboard would be to manually dial paper tape while not connected to a computer. To delete the previous character, one had to back up the paper tape dial, which for mechanical and simplicity reasons was a button on the dial itself and not the keyboard, and so type the rubout graphic symbol. They therefore placed a key producing rubout at the location used on typewriters for backspace. When systems used these terminals and provided control-line editing, they had to use the "rubout" code to perform a backspace, and often did not interpret the backspace character (they might repeat "^H" for backspace). Other terminals not designed for paper tape made the key at this location produce Backspace, and systems designed for these used that character to back up. Since the delete code often produced a backspace issue, this also forced last manufacturers to make any Delete key produce something other than the Delete character.
7. ^ The Tab graphic symbol can also be entered by pressing the Tab ↹ key on most systems.
8. ^ The Carriage Return character can also be entered by pressing the ↵ Enter or Render primal on most systems.
9. ^ The \east escape sequence is not part of ISO C and many other language specifications. However, information technology is understood by several compilers, including GCC.
10. ^ The Escape graphic symbol can too be entered by pressing the Esc key on some systems.
11. ^ ^^ means Ctrl+^ (pressing the "Ctrl" and caret keys).
12. ^ The Delete grapheme can sometimes be entered by pressing the ← Backspace key on some systems.
13. ^ Printed out, the characters are:

     !"#$%&'()*+,-./0123456789:;<=>?@ABCDEFGHIJKLMNOPQRSTUVWXYZ[\]^_`abcdefghijklmnopqrstuvwxyz{|}~

References [edit]

1. ^ ANSI (1975-12-01). ISO-IR-6: ASCII Graphic graphic symbol gear up (PDF). ITSCJ/IPSJ.
2. ^ ^{a b} "Character Sets". Internet Assigned Numbers Authority (IANA). 2007-05-14. Retrieved 2019-08-25 .
3. ^ ^{a b c d east f m h i j k l m n o p q r due south} Mackenzie, Charles E. (1980). Coded Character Sets, History and Development (PDF). The Systems Programming Series (one ed.). Addison-Wesley Publishing Company, Inc. pp. vi, 66, 211, 215, 217, 220, 223, 228, 236–238, 243–245, 247–253, 423, 425–428, 435–439. ISBN978-0-201-14460-4. LCCN 77-90165. Archived (PDF) from the original on May 26, 2016. Retrieved August 25, 2019.
4. ^ ^{a b} Brandel, Mary (1999-07-06). "1963: The Debut of ASCII". CNN. Archived from the original on 2013-06-17. Retrieved 2008-04-xiv .
5. ^ ^{a b c d} "American Standard Code for Information Interchange, ASA X3.4-1963". American Standards Association (ASA). 1963-06-17. Retrieved 2020-06-06 .
6. ^ ^{a b c} "USA Standard Code for Data Interchange, USAS X3.4-1967". United states of America Standards Institute (USASI). 1967-07-07.
7. ^ Jennings, Thomas Daniel (2016-04-20) [1999]. "An annotated history of some grapheme codes or ASCII: American Standard Code for Data Infiltration". Sensitive Research (SR-Nine) . Retrieved 2020-03-08 .
8. ^ ^{a b c} "American National Standard for Information Systems — Coded Character Sets — vii-Bit American National Standard Code for Information Interchange (7-Bit ASCII), ANSI X3.4-1986". American National Standards Institute (ANSI). 1986-03-26.
9. ^ Vint Cerf (1969-10-16). ASCII format for Network Interchange. IETF. doi:x.17487/RFC0020. RFC 20.
10. ^ Barry Leiba (2015-01-12). "Correct classification of RFC 20 (ASCII format) to Internet Standard". IETF.
11. ^ Shirley, R. (Baronial 2007), Cyberspace Security Glossary, Version 2, RFC4949, archived from the original on 2016-06-13, retrieved 2016-06-13
12. ^ Maini, Anil Kumar (2007). Digital Electronics: Principles, Devices and Applications. John Wiley and Sons. p. 28. ISBN978-0-470-03214-five. In improver, it defines codes for 33 nonprinting, mostly obsolete command characters that touch on how the text is processed.
13. ^ Bukstein, Ed (July 1964). "Binary Computer Codes and ASCII". Electronics World. 72 (1): 28–29. Archived from the original on 2016-03-03. Retrieved 2016-05-22 .
14. ^ ^{a b c d east f} Bemer, Robert William (1980). "Chapter i: Inside ASCII" (PDF). Full general Purpose Software. Best of Interface Age. Vol. 2. Portland, OR, Usa: dilithium Press. pp. i–50. ISBN978-0-918398-37-six. LCCN 79-67462. Archived from the original on 2016-08-27. Retrieved 2016-08-27 , from:
    • Bemer, Robert William (May 1978). "Inside ASCII – Part I". Interface Historic period. 3 (v): 96–102.
    • Bemer, Robert William (June 1978). "Inside ASCII – Part II". Interface Historic period. three (half dozen): 64–74.
    • Bemer, Robert William (July 1978). "Inside ASCII – Part Iii". Interface Age. 3 (7): lxxx–87.
15. ^ Brief Report: Meeting of CCITT Working Political party on the New Telegraph Alphabet, May thirteen–15, 1963.
16. ^ Report of ISO/TC/97/SC 2 – Meeting of October 29–31, 1963.
17. ^ Report on Task Group X3.2.iv, June 11, 1963, Pentagon Building, Washington, DC.
18. ^ Report of Meeting No. viii, Job Group X3.two.four, December 17 and 18, 1963
19. ^ ^{a b c} Wintertime, Dik T. (2010) [2003]. "US and International standards: ASCII". Archived from the original on 2010-01-sixteen.
20. ^ ^{a b c d due east f m} Salste, Tuomas (Jan 2016). "7-chip grapheme sets: Revisions of ASCII". Aivosto Oy. urn:nbn:fi-fe201201011004. Archived from the original on 2016-06-13. Retrieved 2016-06-13 .
21. ^ "Information". Scientific American (special edition). 215 (3). September 1966. JSTOR e24931041.
22. ^ Korpela, Jukka Yard. (2014-03-14) [2006-06-07]. Unicode Explained – Internationalize Documents, Programs, and Spider web Sites (2nd release of 1st ed.). O'Reilly Media, Inc. p. 118. ISBN978-0-596-10121-3.
23. ^ ANSI INCITS 4-1986 (R2007): American National Standard for Information Systems – Coded Character Sets – seven-Bit American National Standard Code for Information Interchange (vii-Bit ASCII), 2007 [1986]
24. ^ "INCITS 4-1986[R2012]: Data Systems - Coded Character Sets - seven-Bit American National Standard Lawmaking for Information Interchange (vii-Bit ASCII)". 2012-06-xv. Archived from the original on 2020-02-28. Retrieved 2020-02-28 .
25. ^ "INCITS 4-1986[R2017]: Information Systems - Coded Character Sets - 7-Bit American National Standard Code for Data Interchange (7-Bit ASCII)". 2017-11-02 [2017-06-09]. Archived from the original on 2020-02-28. Retrieved 2020-02-28 .
26. ^ Flake Sequencing of the American National Standard Code for Information Interchange in Series-by-Scrap Data Transmission, American National Standards Institute (ANSI), 1966, X3.xv-1966
27. ^ "BruXy: Radio Teletype advice". 2005-x-10. Archived from the original on 2016-04-12. Retrieved 2016-05-09 . The transmitted code use International Telegraph Alphabet No. 2 (ITA-2) which was introduced by CCITT in 1924.
28. ^ ^{a b} Smith, Gil (2001). "Teletype Communication Codes" (PDF). Baudot.internet. Archived (PDF) from the original on 2008-08-20. Retrieved 2008-07-11 .
29. ^ Sawyer, Stanley A.; Krantz, Steven George (1995). A TeX Primer for Scientists. CRC Press. p. thirteen. Bibcode:1995tps..book.....S. ISBN978-0-8493-7159-two. Archived from the original on 2016-12-22. Retrieved 2016-x-29 .
30. ^ Savard, John J. G. "Computer Keyboards". Archived from the original on 2014-09-24. Retrieved 2014-08-24 .
31. ^ "ASCIIbetical definition". PC Magazine. Archived from the original on 2013-03-09. Retrieved 2008-04-14 .
32. ^ Resnick, P. (April 2001), Internet Message Format, RFC2822, archived from the original on 2016-06-13, retrieved 2016-06-13 (NB. NO-WS-CTL.)
33. ^ McConnell, Robert; Haynes, James; Warren, Richard. "Understanding ASCII Codes". Archived from the original on 2014-02-27. Retrieved 2014-05-11 .
34. ^ Barry Margolin (2014-05-29). "Re: editor and word processor history (was: Re: RTF for emacs)". help-gnu-emacs (Mailing list). Archived from the original on 2014-07-fourteen. Retrieved 2014-07-xi .
35. ^ ^{a b} "PDP-vi Multiprogramming System Manual" (PDF). Digital Equipment Corporation (DEC). 1965. p. 43. Archived (PDF) from the original on 2014-07-14. Retrieved 2014-07-10 .
36. ^ ^{a b} "PDP-ten Reference Handbook, Book 3, Communicating with the Monitor" (PDF). Digital Equipment Corporation (DEC). 1969. p. five-v. Archived (PDF) from the original on 2011-xi-15. Retrieved 2014-07-10 .
37. ^ "Assist - GNU Emacs Manual". Archived from the original on 2018-07-11. Retrieved 2018-07-eleven .
38. ^ Tim Paterson (2007-08-08). "Is DOS a Rip-Off of CP/M?". DosMan Drivel. Archived from the original on 2018-04-20. Retrieved 2018-04-19 .
39. ^ Ossanna, J. F.; Saltzer, J. H. (November 17–19, 1970). "Technical and human engineering problems in connecting terminals to a time-sharing system" (PDF). Proceedings of the Nov 17–19, 1970, Autumn Joint Figurer Briefing (FJCC). p. 357: AFIPS Printing. pp. 355–362. Archived (PDF) from the original on 2012-08-19. Retrieved 2013-01-29 . Using a "new-line" function (combined carriage-return and line-feed) is simpler for both man and automobile 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. {{cite conference}}: CS1 maint: location (link)
40. ^ O'Sullivan, T. (1971-05-xix), TELNET Protocol, Internet Engineering Chore Force (IETF), pp. four–5, RFC158, archived from the original on 2016-06-13, retrieved 2013-01-28
41. ^ Neigus, Nancy J. (1973-08-12), File Transfer Protocol, Net Engineering science Task Forcefulness (IETF), RFC542, archived from the original on 2016-06-13, retrieved 2013-01-28
42. ^ Postel, Jon (June 1980), File Transfer Protocol, Internet Technology Job Force (IETF), RFC765, archived from the original on 2016-06-xiii, retrieved 2013-01-28
43. ^ "EOL translation programme for Mercurial". Mercurial. Archived from the original on 2016-06-16. Retrieved 2017-06-24 .
44. ^ Bernstein, Daniel J. "Blank LFs in SMTP". Archived from the original on 2011-x-29. Retrieved 2013-01-28 .
45. ^ CP/M 1.4 Interface Guide (PDF). Digital Research. 1978. p. x. Archived (PDF) from the original on 2019-05-29. Retrieved 2017-10-07 .
46. ^ Cerf, Vinton Grayness (1969-10-16), ASCII format for Network Interchange, Network Working Group, RFCxx, archived from the original on 2016-06-13, retrieved 2016-06-13 (NB. Almost identical wording to USAS X3.4-1968 except for the intro.)
47. ^ Haynes, Jim (2015-01-thirteen). "First-Hand: Chad is Our Nearly Important Product: An Engineer's Retentivity of Teletype Corporation". Engineering and Technology History Wiki (ETHW). Archived from the original on 2016-10-31. Retrieved 2016-10-31 . There was the change from 1961 ASCII to 1968 ASCII. Some reckoner languages used characters in 1961 ASCII such every bit up arrow and left pointer. These characters disappeared from 1968 ASCII. We worked with Fred Mocking, who past now was in Sales at Teletype, on a blazon cylinder that would compromise the changing characters and then that the meanings of 1961 ASCII were non totally lost. The underscore character was fabricated rather wedge-shaped so it could also serve as a left arrow.
48. ^ Bemer, Robert William. "Bemer meets Europe (Computer Standards) – Computer History Vignettes". Trailing-border.com. Archived from the original on 2013-10-17. Retrieved 2008-04-14 . (NB. Bemer was employed at IBM at that fourth dimension.)
49. ^ "Robert William Bemer: Biography". 2013-03-09. Archived from the original on 2016-06-16.
50. ^ Johnson, Lyndon Baines (1968-03-xi). "Memorandum Approving the Adoption by the Federal Government of a Standard Code for Information Interchange". The American Presidency Project. Archived from the original on 2007-09-14. Retrieved 2008-04-fourteen .
51. ^ Richard Southward. Shuford (1996-12-20). "Re: Early history of ASCII?". Newsgroup: alt.folklore.computers. Usenet: Pine.Lord's day.3.91.961220100220.13180C-100000@duncan.cs.utk.edu.
52. ^ Folts, Harold C.; Karp, Harry, eds. (1982-02-01). Compilation of Data Communications Standards (2nd revised ed.). McGraw-Loma Inc. ISBN978-0-07-021457-6.
53. ^ Dubost, Karl (2008-05-06). "UTF-viii Growth on the Web". W3C Blog. World wide web Consortium. Archived from the original on 2016-06-sixteen. Retrieved 2010-08-fifteen .
54. ^ ^{a b} Davis, Mark (2008-05-05). "Moving to Unicode five.1". Official Google Blog. Archived from the original on 2016-06-sixteen. Retrieved 2010-08-15 .
55. ^ Davis, Mark (2010-01-28). "Unicode nearing 50% of the spider web". Official Google Web log. Archived from the original on 2016-06-16. Retrieved 2010-08-fifteen .
56. ^ "Specific Criteria", attachment to memo from R. West. Accomplish, "X3-two Coming together – September 14 and 15", September eighteen, 1961
57. ^ Maréchal, R. (1967-12-22), ISO/TC 97 – Computers and Information Processing: Acceptance of Draft ISO Recommendation No. 1052
58. ^ The Unicode Consortium (2006-10-27). "Chapter thirteen: Special Areas and Format Characters" (PDF). In Allen, Julie D. (ed.). The Unicode standard, Version 5.0. Upper Saddle River, New Bailiwick of jersey, US: Addison-Wesley Professional. p. 314. ISBN978-0-321-48091-0 . Retrieved 2015-03-13 .
59. ^ "utf-8(7) – Linux transmission page". Man7.org. 2014-02-26. Archived from the original on 2014-04-22. Retrieved 2014-04-21 .

Further reading [edit]

• Bemer, Robert William (1960). "A Proposal for Character Lawmaking Compatibility". Communications of the ACM. iii (two): 71–72. doi:10.1145/366959.366961. S2CID 9591147.
• Bemer, Robert William (2003-05-23). "The Babel of Codes Prior to ASCII: The 1960 Survey of Coded Grapheme Sets: The Reasons for ASCII". Archived from the original on 2013-10-17. Retrieved 2016-05-09 , from:
  • Bemer, Robert William (December 1960). "Survey of coded graphic symbol representation". Communications of the ACM. 3 (12): 639–641. doi:ten.1145/367487.367493. S2CID 21403172.
  • Smith, H. J.; Williams, F. A. (Dec 1960). "Survey of punched carte codes". Communications of the ACM. 3 (12): 642. doi:10.1145/367487.367491.
• "American National Standard Code for Data Interchange | ANSI X3.64-1977" (PDF). National Institute for Standards. 1977. (facsimile, non car readable)
• Robinson, G. Southward.; Cargill, C. (1996). "History and affect of computer standards". Computer. 29 (10): 79–85. doi:x.1109/2.539725.
• Mullendore, Ralph Elvin (1964) [1963]. Ptak, John F. (ed.). "On the Early on Development of ASCII – The History of ASCII". JF Ptak Science Books (published March 2012). Archived from the original on 2016-05-26. Retrieved 2016-05-26 .

External links [edit]

Wikimedia Eatables has media related to ASCII.

• "C0 Controls and Bones Latin – Range: 0000–007F" (PDF). The Unicode Standard 8.0. Unicode, Inc. 2015 [1991]. Archived (PDF) from the original on 2016-05-26. Retrieved 2016-05-26 .
• Fischer, Eric. "The Evolution of Character Codes, 1874–1968". CiteSeerX10.1.one.96.678. [1]

bondcommothe1982.blogspot.com

Source: https://en.wikipedia.org/wiki/ASCII

Share this post