Talk:ASCII

From Wikipedia, the free encyclopedia

Former featured article ASCII is a former featured article. Please see the links under Article milestones below for its original nomination page (for older articles, check the nomination archive) and why it was removed.
This article is within the scope of the following WikiProjects:
Peer review This Engtech article has been selected for Version 0.5 and subsequent release versions of Wikipedia. It has been rated B-Class on the assessment scale (comments).

Contents

[edit] Featured article review of December 30, 2005

This review resulted in the passing of a new version of the article.

This was the promoted version and here's the diff. Looks like it's been more or less completely rewritten. Referencing looks inadequate for an article of this size, and the "see also" is too big. I support passing this review. Tuf-Kat 04:38, 2 December 2005 (UTC)

  • Many of the references were improperly put in the external links section. I fix some of it by moving them and I removed the link to Bob Bemer's website as it is either being blocked or no longer archived. I also collapsed the "see also" section into parallel lines. The article looks like featured quality. --maclean25 22:49, 17 December 2005 (UTC)

[edit] ASCII's "success"

ASCII is generally accounted the most successful software standard ever promulgated.

What does this really mean? If first computers were mostly build in 1960s in United States, this does not mean the code is the best. Right? The code is probably the best in the Western world. But this is far far away from the whole World in fact. Any other nice codes are appropriated. The code is today rather obsolete... :) Best regards. -- XJamRastafire 14:39 Sep 9, 2002 (UTC)

Well actually ASCII is only a successful for English, for other languages there has been a prolifertation of competing codes due to the 8-Bit limitation. Probably a good code to go for now is UTF-8. --HJH

Or, more to the point, Unicode, with UTF-8 as its character encoding. And 7-bit ASCII is a subset of Unicode, and also of UTF-8.

That was my line. I didn't say it was good, I said it was successful. I doubt there is a single serious text-handling application of any kind that doesn't recognize and process ASCII. I doubt there is any other software standard anywhere else, graphics, network, whatever, of which the equivalent statement is true. Ortolan88
Yes, I do believe that too. I was just asking, cause I am curious. There must be a certain key on which they have selected other non-alphabetical characters from the set of the Latin alphabet. Perhaps I exaggerated saying the code is obsolete today. Yes, it is perfect for a Latin based languages and specially for English. And in fact it is possible to (re)build such software standard elsewhere - but I guess this won't never happen. Thank you HJH and Ortolan88 for your answers. Long ago, when PC were not so common as these days, I visited one older friend who had made his own OS and his own ASCII-like code, but this is a history. -- XJamRastafire 11:46 Sep 10, 2002 (UTC)

ASCII is indeed a very successful standard. Today the plain ASCII files (with ASCII characters extended to 8 bits by adding one zero bit) are the only text encoding that will be interpreted correctly by all computers of the world. — Monedula 08:26, 11 September 2006 (UTC)

Strictly speaking, pure ASCII (that is the 7-bit standard) is not used much. Enhancements/extensions like ISO-8859-1 and UTF-8 are used, but not pure strict ASCII because it is not good enough outside the USA. The use of ASCII for programming languages (and the usage of []{}\| in them) have required the preservation of ASCII for the ASCII extensions since one want to preserve existing well-working software code. -- BIL (talk) 22:39, 12 January 2008 (UTC)

[edit] ASCII versions and variants

I might get around to this myself, but we need a mention, if not a better explanation of the differences / relationships between, the following:

  • ASA ASCII (1963)
  • ANSI X3.4-1968
  • ANSI X3.4-1977
  • ANSI X3.4-1986
  • ISO 646:1967, including an IRV and two 6-bit subsets
  • ISO 646:1972, including ISO 646-US, ISO 646-CA, ISO 646-CN, ISO 646-CU, ISO 646-DE, ISO 646-DK, ISO 646-ES, ISO 646-FR, ISO 646-HU, ISO 646-IT, ISO 646-JP, ISO 646-KR, ISO 646-NO, ISO 646-PT, ISO 646-SE, ISO 646-UK, ISO 646-YU, and ISO 646-IRV
  • ISO 646:1983
  • ISO/IEC 646:1991
  • ECMA-6 (1965, 1967, 1970, 1973, 1983, 1991 editions)
  • CCITT Recommendation V.3 (International Telegraph Alphabet No. 5) (1972?)
  • DIN 66003 (1974)
I've now made an entry for ISO 646 national variations. A bit rough, and far from complete - there is an external link at the end of the page where more specific info for a number of languages may be extracted. -- Egil 07:44 Mar 9, 2003 (UTC)

…as well as the IANA registry's names for ANSI X3.4-1968, and the fact that they are the names approved on the Internet, such as in the "charset" parameter of a MIME header or in the encoding declaration of an XML document or parsed general entity. I finally got around to adding this. — mjb 23:10, 18 Jul 2004 (UTC)

…oh, and the IANA names for the other variants.

More aliases (same as V.3?):

  • IRA5 (CCITT International Reference Alphabet No. 5)
  • IA5 (CCITT International Alphabet No. 5)

The standards listed in this talk section are IMHO more important info than the aliases for mime charsets listed under "Aliases" in the article. I suggest removing "Aliases" and to add to "Variants" a list of standard names like the above. (IF we allow standards with tiny differences to ASCII, then there should be a parentesis about the difference.) -- David A 195.84.167.2 (talk) —Preceding comment was added at 22:10, 19 December 2007 (UTC)

Does someone have an official electronic copy of any of the X3.4 versions (not ECMA-6) that they can share, so we can get the whole IRV, C0, G0 stuff summarized? (It's not important enough to me to shell out my own money) — mjb 22:17 Nov 1, 2002 (UTC)

Dik T. Winter's info on character code standards describes ASCII-1963, ASCII-1965, USASCII-8, ASCII-1967, and the two 6-bit subsets of ISO 646:1967. — mjb 6 July 2005 09:57 (UTC)
ASCII was published as ASA X3.4-1963. This version did specify codes for lower case characters.

"did specify"? 210.170.202.147 (talk) 01:56, 24 March 2008 (UTC)

[edit] Overlap with Unicode

You say: ...the first 127 code points of each code are the same as ASCII, and the first 256 code points of Unicode are the same as ISO 8859-1. is this the truth? How does it match with UTF-8? An ASCII encoded file is a valid UTF-8 file, but an ISO 8859-1 encoded file is not. --Keichwa 20:25 Feb 24, 2003 (UTC)

UTF-8 is an encoding of Unicode, which is a character set. The first 256 code points of Unicode do match with the 256 code points of ISO 8859-1, however UTF-8's encoding of a series of those code points into a byte stream is different from ISO 8859-1's for the 128-255 range, using two bytes instead of one. --Brion 20:29 Feb 24, 2003 (UTC)

You sure? I thought that other characters like Japanese ones are expressed in three bytes but not two. I am just unsure. See http://www.cl.cam.ac.uk/~mgk25/unicode.html -- Taku 20:32 Feb 24, 2003 (UTC)

Yes, I'm quite sure. :) UTF-8 is an encoding, not a character set. The Unicode characters at code points 128-255 are, by definition, the same as the ISO 8859-1 characters at code points 128-255. UTF-8 encodes these characters in two bytes (and various other characters which are not in ISO 8859-1 in from 2 to 6 bytes). These two-byte values are, obviously, not bit-for-bit identical to one-byte ISO 8859-1 encodings of the same code points. See UTF-8 for a table showing how the bits are spread out. --Brion 20:37 Feb 24, 2003 (UTC)
Umm doesn't UTF-8 as currently defined stop at 4 bytes (iirc it was 6 in the version that supported the old limit of UCS)? Plugwash 01:26, 26 December 2005 (UTC)

[edit] Link formatting

Anyone knows how to hide the underscore characters appearing for links in the character chart ? Lets have just the blue colour and make the underscore vanish. Jay 14:18, 2 Oct 2003 (UTC)

I don't think you can do this for individual pages. You can turn off all underscores in your User preferences though. Angela 14:23, Oct 2, 2003 (UTC)

[edit] Grave accent vs single quotes

It is incorrect to imply that ASCII has an "accent" character. It has an apostrophe (in the 1983 version, which is aligned with ISO 646). It has a "grave accent" character in that same version. It does not have an "acute accent". Many Unix users do not much care for the (IMHO mistaken) changes made in the post-1978 versions of ASCII for ISO 646 alignment, particularly the deletion of the alternate interpretations "open single quote" and "close single quote" for ` and ', respectively, which were valid in the 1967 and 1978 versions, and are emphatically quotation marks and not accents or apostrophes in Unix programming, TeX, and the StandardEncoding vector in PostScript. 18.24.0.120 20:36, 6 Dec 2003 (UTC)

[edit] Hard-coded fonts for printable representations

The table for control characters has the "Printable representation" column.  There is a font prescription there, saying style="font-family:'lucida sans unicode','arial unicode ms'".  I understand the reason of this, but still it is incorrect.  Font prescriptions may be used only if there indeed is some reason to use this typeface, and not that one.  But here we only want a character to be displayed, and not to be displayed using a specific typeface.  So it is the browser's responsibility to find an appropriate font for this, not Wikipedia's. — Monedula 01:01, 5 Jun 2004 (UTC)

I understand your position, but your contention that it is entirely the browser's responsibility is not necessarily reflected in the HTML and CSS specifications. It's good practice, yes, but required, no. CSS in particular states "If there is a matching font face, but it doesn't contain a glyph for the current character, and if there is a next alternative 'font-family' in the font sets, then repeat step 2 with the next alternative 'font-family'. [...] If there is no font within the family selected in 2, then use a UA-dependent default 'font-family' and repeat step 2, using the best match that can be obtained within the default font.". A strict interpretation of this would prevent the browser from finding a match from all available fonts. Given that there are popular user agents that don't make an attempt to find a good font for characters not displayable in the current font, and given the nature of these particular glyphs (there's going to be very little distinction, visually or semantically, between how they render in any typeface), it seems that encouraging the renderer to use commonly deployed fonts that we know support those characters is a good and harmless practice. Ideally, the style info would only be forced upon those user agents that need it, but I doubt Wikipedia is going to implement browser-dependent stylesheets. - mjb 18:23, 12 Jun 2004 (UTC)

[edit] 7-bit or 8-bit

I'm having difficulty understanding a certain aspect of ASCII. It is stated that ASCII is "strictly a 7-bit code", and we mention that historically, 8-bit bytes have been used to transmit ASCII, but that the high bit was either unused or was used for parity. Fair enough. But then we go on to show a chart in which ASCII codes are expressed in binary as 8-bit codes. Indeed, today it is quite common to label data stored and transmitted as 8-bit bytes as "ASCII".

I believe that ASCII was defined only in terms of 7-bit codes, but perhaps became, at some point, one of the following:

  • an 8-bit code in which the purpose of the high bit is entirely undefined (thus, the burden is on the decoder to know that only the first 7 bits encode the character);
  • an 8-bit code in which the high bit is undefined and allowed for use for any purpose other than determining which character is encoded (thereby relieving the burden mentioned above); or
  • an 8-bit code in which the high bit is explicitly defined as being used for padding (which seems to reflect actual practice, but I don't know if it is formally defined this way anywhere)

I thought that perhaps RFC 1345 was what defined ASCII as 8-bit first, but a brief Google search turns up references to ANSI X3.4 that call it an 8-bit code, so I'd appreciate some clarification here. - mjb 23:11, 18 Jul 2004 (UTC)

My computer teacher said the ASCII is 7-bit and extended ASCII is 8-bit and the chart in use looks like an incomplete extended ASCII chart. firstly the numbers match as far as I can tell those of Extended ASCII also the 8-bits then again a full ASCII chart of printable characters lists 224 characters so its gotta be incomplete. the person probably looked it up and got extended instead of regular --Shimonnyman 13:42, 5 September 2005 (UTC)
Extended ASCII *DOES NOT* reffer to any one character set. It is a name used to reffer to character sets in general that keep the lower 128 code values for ASCII whilst using the upper 128 for some kind of extention. Plugwash 13:48, 5 November 2005 (UTC)
For what it's worth: the original Wordstar word-processing software used all 8 bits, but it had 7-bit encoding. It used a high-bit flag at the end of every word, sort of an error-checking routine. If you trim off all the high bits, you get straight 7-bit ASCII. --Cbdorsett 16:04, 7 January 2007 (UTC)

[edit] Pronunciation?

How is ASCII pronounced? The article gives 'aski' but then does that mean 'a ski' or 'ask e?'

The article previously stated that ASCII was pronounce as ass-key (and it is generally pronounced like that.) But I guess it offended someone :). --GatesPlusPlus 10:57, 28 Jan 2005 (UTC)
A new description using IPA notation is now up. However, it's a little vague because it doesn't mention anything about stress. KJ 02:48, 2005 Mar 28 (UTC)
An anonymous user changed the pronounciation back to ASS-key, with no discussion. This might be an attempt to be helpful, but it follows my removal of the word penis from the article, so I suspect vandalism. Sigh. I've reverted the article back to ASK-EE. Would AS-key be better?
Chris Chittleborough 09:00, 10 September 2005 (UTC)

"You say 'toe may toe'"... How about 'ass ee'(The c is silent). That's how I say it anyways. E-)

It's fixed now. Accent on the first syllable. --Cbdorsett 16:06, 7 January 2007 (UTC)
How about "AIH ski"? P=) ~Kaimbridge~14:40, 4 January 2008 (UTC)

[edit] Suggest 26 possible wiki links and 64 possible backlinks for ASCII.

An automated Wikipedia link suggester has some possible wiki link suggestions for the ASCII article:

  • Can link Western European: ...]] as used in modern [[English language|English]] and other Western European languages. It is most commonly used by [[computer]]s and ot...
  • Can link written language: ...ce between digital bit patterns and the symbols/glyphs of a written language, thus allowing [[digital]] devices to communicate with each... (link to section)
  • Can link eight-bit: ...At the time ASCII was introduced, many computers dealt with eight-bit groups ([[byte]]s or, more specifically, [[octet]]s) as the... (link to section)
  • Can link Bell System: ...7-bit teleprinter code promoted by Bell data services. The Bell System had been planning to use a 6-bit code derived from [[Fielda... (link to section)
  • Can link lower-case: ...t code derived from [[Fieldata]] that added punctuation and lower-case letter to the earlier 5-bit [[Baudot code|Baudot]] teleprin... (link to section)
  • Can link storage medium: ..."erase" a section of [[punched tape|paper tape]], a popular storage medium until the [[1980s|80s]], by punching all possible holes at ... (link to section)
  • Can link data transmission protocol: ...CII control codes are to mark data packets, or to control a data transmission protocol (e.g. ENQuiry [effectively, "any stations out there?"], ACK... (link to section)
  • Can link SUBstitute: ...rt Of Header, Start Of Text, End Of Text, etc). ESCape and SUBstitute permit a communications protocol to, for instance, mark bin... (link to section)
  • Can link magnetic tape: ...racters (Record Separator, etc.) were intended for use with magnetic tape systems.... (link to section)
  • Can link end-of-line: ...f the control codes to represent "meta-information" such as end-of-line, start/end of a data element, and so on. These assignments ... (link to section)
  • Can link data element: ...sent "meta-information" such as end-of-line, start/end of a data element, and so on. These assignments often conflict, so part of th... (link to section)
  • Can link fifth column: ...9249; |DEL or Backspace |Delete |} In the table above, the fifth column contains glyphs reserved for representing control codes in ... (link to section)
  • Can link data stream: ...ontains glyphs reserved for representing control codes in a data stream, ie, when they must be printed or displayed rather than (or... (link to section)
  • Can link sixth column: ...allation of additional fonts in order to display them. The sixth column shows the key combinations traditionally used to input cont... (link to section)
  • Can link text editor: ...n transit to a remote server. If the code was received in a text editor that did not know what do with it, the result was often "^H... (link to section)
  • Can link space bar: ...ing the space between words, which is produced by the large space bar of a keyboard. Codes 33 to 126 are called the printable cha... (link to section)
  • Can link case-insensitive: ...gistry of character sets], ongoing, recognize the following case-insensitive aliases for ASCII as being suitable for use on the Internet... (link to section)
  • Can link standards bodies: ...many variations of ASCII were developed by corporations and standards bodies in order to facilitate the expression of non-English langua... (link to section)
  • Can link out-of-band: ...e variant, anyway. Eventually, improved technology brought out-of-band means to represent the information formerly encoded in the ... (link to section)
  • Can link code page 437: ...xample, [[IBM]] developed eight-bit [[code page]]s, such as code page 437, which replaced the control characters with graphic symbols... (link to section)
  • Can link Universal Character Set: ...se today. [[Unicode]] and [[ISO 10646|ISO/IEC 10646]]: the Universal Character Set, have a much wider array of characters, and their various e... (link to section)
  • Can link non-negative integer: ... are defined in terms of relatively abstract "code points": non-negative integer numbers that can be mapped, using different encoding forms ... (link to section)
  • Can link backward compatibility: ...d schemes, to sequences of 1 or more 8-bit bytes. To permit backward compatibility, Unicode and the UCS assign the first 128 code points to th... (link to section)
  • Can link Tom Jennings: ...s/codes/index.html Annotated History of Character Codes] by Tom Jennings, World Power Systems... (link to section)
  • Can link World Power: ...html Annotated History of Character Codes] by Tom Jennings, World Power Systems... (link to section)

Additionally, there are some other articles which may be able to linked to this one (also known as "backlinks"):

  • In ALGOL, can backlink ASCII: ...cters for 'open-string-quote' and 'close-string-quote', but ASCII does not allow these to be shown here....
  • In Amiga, can backlink ASCII: ...uk Amiga Wiki] *[http://www.asciiscene.org Boondocks] Amiga ASCII community...
  • In Data General Nova, can backlink ASCII: ...r lda 2,n16 ; set up bit counter loop: lda 0,chr0 ; load ASCII '0'...
  • In Flip-flop, can backlink ASCII: ...resent the state of a sequencer, the value of a counter, an ASCII character in a computer's memory or any other piece of info...
  • In Internet troll, can backlink ASCII: ...resting things up get wasted on moderating down things like ASCII pictures of the [[goatse.cx|goatse]] man. This lowers the ...
  • In International Statistical Classification of Diseases and Related Health Problems, can backlink ASCII: ...0 codes) and Long List of ICD-9 Codes (1,500 codes) in PDF, ASCII text, and “doc” file for Palm-compatible hand-held computer...
  • In Leet, can backlink ASCII: ...ayer gaming, especially involving other characters from the ASCII set. Some multiplayer games allow for users to be kicked o...
  • In Prolog, can backlink ASCII: ...y quotes. They are often internally represented as lists of ASCII codes....
  • In Sega, can backlink ASCII: ...t did not include a Sega trademark. <!--I believe it was an ASCII S-E-G-A --> If an unlicensed company included this trademar...
  • In Text editor, can backlink ASCII: ...10141644.html?tag=lst-0-1] - Features: designed for editing ASCII text art. Supports ANSI color (ANSI X3.64)....
  • In Uniform Resource Locator, can backlink ASCII: ...ss addresses in any character set using a limited subset of ASCII characters (for instance, whitespace is never used in a URL...
  • In 0 (number), can backlink ASCII: ...ut letter-O is not, you're probably looking at an old-style ASCII graphic set descended from the default [[typewheel]] on the...
  • In Unit interval, can backlink ASCII: ...al is almost always written <var>I</var>, and the following ASCII picture suffices in almost any context:...
  • In Graphics file format, can backlink ASCII: ...[[X Window System]], supported by most [[web browser]]s. An ASCII format which uses no compression designed so that files are...
  • In Tangloids, can backlink ASCII: ...s; whoever can untangle the strings fastest is the winner. ASCII diagram:...
  • In Befunge, can backlink ASCII: ...e>"</code></td><td>Start string mode: push each character's ASCII value all the way up to the next <code>"</code></td></tr>...
  • In Rock Ridge, can backlink ASCII: ...fly: *longer file names (up to 255 characters) *almost any ASCII character can be used in file and folder names...
  • In RIFF, can backlink ASCII: ...e endianness as previously stated. * Header ** 4 bytes: The ASCII identifier "RIFF"....
  • In Exidy Sorcerer, can backlink ASCII character set: ...n. The lower half was fixed in ROM, and contained the usual ASCII character set. The upper half was defined in RAM. This area would be load...
  • In Radix-64, can backlink ASCII: ...n RFC 2440, to permit encrypted data to be sent as ordinary ASCII text through email, without the need to treat the data as a...
  • In Transcription (linguistics), can backlink ASCII: ...lude the [[International Phonetic Alphabet]] (IPA), and its ASCII equivalent, [[SAMPA]]. One can see numerous examples of tra...
  • In Nkf, can backlink ASCII: ...IS-kanji (DEFAULT B) o_ Output sequence to designate ASCII (DEFAULT B) ...
  • In Number of the Beast (numerology), can backlink ASCII code: ...sing the English alphabet multiplied by 6 and combining the ASCII code, all characters have a value with amazing results. (Note 77...
  • In Malbolge, can backlink ASCII code: ...ds]]. ==== Method 1 ==== Find the result below. Store the ASCII code of the character below it at '''''[c]'''''....
  • In Forsyth-Edwards Notation, can backlink ASCII character set: ...ular game position, all in one text line and using only the ASCII character set. A text file with only FEN data records should have the fil...
  • In Stereogram, can backlink ASCII: ...hp ASCII Stereogram Movie Generator] Online; generates free ASCII stereogram movies!...
  • In Rog-O-Matic, can backlink ASCII: ... all information in Rogue is communicated to the player via ASCII text, Rog-O-Matic automatically has access to the same info...
  • In Identifier naming convention, can backlink ASCII: ... one finds ''atoi'' as the name of a function that converts ASCII strings to integers. In Lisp, one would be more likely to ...
  • In SideKick, can backlink ASCII: ... editor (with WordStar-like command interface), calculator, ASCII chart, and address book/phone dialer....
  • In Uuencode, can backlink ASCII: ...3. Decimal 32 is added to each number and they are ouput as ASCII characters which will lie in the range 32 (space) to 32+63 ...
  • In Punycode, can backlink ASCII: ... a domain name which is not representable solely within the ASCII charcter set, and a reserved prefix 'xn--' is added to the ...
  • In GIS file formats, can backlink ASCII: ...or GIS data *[[NTF]] - UK Ordnance Survey *[[ASC]] - Simple ASCII text point cloud format...
  • In QIF, can backlink ASCII: ...he <b>^</b> (caret). All the data in the file is stored in ASCII strings, and the file could be edited in any text editor (s...
  • In Serialize, can backlink ASCII: ...gramming, for example, when an object is serialized with an ASCII encoding, its information value (data) can be represented b...
  • In Shift-JIS, can backlink ASCII: ...IS only guarantees that the first byte will be in the upper ASCII range; the value of the second byte can be either high or l...
  • In Extended Unix Coding, can backlink ASCII: ...e simply incremented by 128. This allows easy mixing 7-bit ASCII and 8-bit Japanese without the need for the escape characte...
  • In 4chan, can backlink ASCII: ...re the fourth death of 4chan where it was common to post an ASCII image of Osaka from [[Azumanga Daioh]] holding a phone to h...
  • In KOI8-R, can backlink ASCII: ...deciphered) in case-reversed transliteration on an ordinary ASCII terminal. For instance, "&#1056;&#1091;&#1089;&#1089;&#108...
  • In KOI8-U, can backlink ASCII: ...deciphered) in case-reversed transliteration on an ordinary ASCII terminal. For instance, "&#1056;&#1091;&#1089;&#1089;&#108...
  • In GCIDE, can backlink ASCII: ...cense]]. It describes itself as "a freely-available set of ASCII files containing the marked-up text of a substantial Englis...
  • In Obfuna, can backlink ASCII: ...x</td> <td>ASCII</td> <td>Converts x's numeric value to an ASCII character and returns the result</td> </tr>...
  • In Kipple programming language, can backlink ASCII: ... When a program tries to push a value onto stack ''@'', the ASCII values of each of the value's digits are pushed onto it ins...
  • In Tyrant (computer game), can backlink ASCII: ...able features: *Graphical tiles used instead of traditional ASCII characters...
  • In Numeric character reference, can backlink ASCII: ...ent authors to use special sequences of characters from the ASCII range (the first 127 code points of Unicode) to represent, ...
  • In L33t programming language, can backlink ASCII: ...ointer.</td></tr> <tr><td>1</td><td>WRT</td><td> Writes the ASCII values of the byte under the memory pointer to the current ...
  • In John C. Wells, can backlink ASCII: ...to]] dictionary. He is also the inventor of the [[X-SAMPA]] ASCII phonetic alphabet....
  • In Keyer, can backlink ASCII: ...tomated teletype system, the sender presses keys to send an ASCII data stream to a receiver, and computation alleviates the n...
  • In SAMPA chart for Nahuatl, can backlink ASCII: ...t language, and tend to use the limited number of available ASCII symbols to represent those phonemes....
  • In TMMLPTEALPAITAFNFAL, can backlink ASCII: ...ON IDENTIFIERS FOR TODAY: IDENTIFIER CHARACTERS MUST BE IN ASCII RANGE 32 .. 75 (' ' .. 'K')...
  • In BinHex, can backlink ASCII: ...s [[CompuServe]], which were not "8-bit clean" and required ASCII armoring to survive. CompuServe later addressed this proble...
  • In Romanization of Ukrainian, can backlink ASCII: ... Methods Phonetic Alphabet, for representing IPA using only ASCII characters. An international version of [[SAMPA]]...
  • In Formatted text, can backlink ASCII: ...rightly be identified with binary files or be distinct from ASCII text. This is because formatted text is not necessarily bin...
  • In COSMAC VIP, can backlink ASCII: ... could be added to connect to sensors, interface relays, an ASCII [[keyboard]], or a [[Computer printer|printer]]....
  • In Diskmag, can backlink ASCII: ...ing characteristic about a diskmag in contrast to a typical ASCII "zine" or "t-file" (or even "g-file") is that a diskmag usu...
  • In Remorse ASCII, can backlink ASCII: ...''Remorse ASCII''', or ''Remorse 1981'' is now the official ASCII sub-label of [[ACiD Productions]]....
  • In Terminal node controller, can backlink ASCII: ... a device is used by [[amateur radio]] operators to convert ASCII characters to modulated tones and vice-versa. It was origin...
  • In EIA-708, can backlink ASCII: ...ble> <tr><td>CL Group: C0 <td>0x00-0x1F <td>Subset of ASCII Control Codes...
  • In Impure ASCII, can backlink ASCII: ...he group. [[2004|As of 2004]], Impure continues to release ASCII [[artpack]]s and [[ASCII colly|collies]]. They also appear...
  • In Hex editor, can backlink ASCII: ...values grouped in two groups of 8 bytes and one group of 16 ASCII chars, nonprintable characters normally are represented by ...
  • In All caps, can backlink ASCII: ...[Apple II family|Apple II]] models), but as full support of ASCII became standard, it became solely identified with "shouting...
  • In AX.25 protocol, can backlink ASCII: ...in the nonrepeater mode of operation. Octet ASCII Bin.Data Hex Data...
  • In Ardy Lightfoot, can backlink ASCII: ...form game released on the SNES in 1995. It was developed by ASCII and published by Titus. Ardy Lightfoot is a rabbit like cre...

* In MBASIC programming language, can backlink ASCII: ...ed to disk in either a compressed binary format or as plain ASCII text. Every source line was identified with a number, which...

  • In Galaxy Trek, can backlink ASCII: ...ships from attacking Federation Headquarters. The game uses ASCII graphics and can be played using RGB, Mono, or Composite gr...

Notes: The article text has not been changed in any way; Some of these suggestions may be wrong, some may be right.
Feedback: I like it, I hate it, Please don't link to — LinkBot 11:26, 1 Dec 2004 (UTC)

[edit] ASCII order

The introductory section shows the list of characters in "ASCII order" - this seems a little circular. Characters in order of numerical value would not be a circular definition. --Wtshymanski 19:22, 19 Apr 2005 (UTC)

[edit] Request for references

Hi, I am working to encourage implementation of the goals of the Wikipedia:Verifiability policy. Part of that is to make sure articles cite their sources. This is particularly important for featured articles, since they are a prominent part of Wikipedia. The Fact and Reference Check Project has more information. Thank you, and please leave me a message when a few references have been added to the article. - Taxman 19:31, Apr 22, 2005 (UTC)

[edit] ASCII art

Shouldn't this article have at least one picture of ASCII art? 24.54.208.177 04:24, 24 Jun 2005 (UTC)

No, that's what ASCII art is for. Cburnett 06:27, Jun 24, 2005 (UTC)


June 2007 — Image:Ascii.jpg

How does a 128x128 pixel image count as ASCII art?! --Drlog 06:39, 22 June 2007 (UTC)

I don't think it does, so I've removed it. I've asked the guy who put it there to consider uploading a higher-resolution image and adding it to the ASCII art article. Cheers, CWC 11:32, 22 June 2007 (UTC)

[edit] Misuse of the term "ASCII"

The term "ASCII" is sometimes misused to refer to a superset, or almost superset, of ASCII such as ISO-8859-1. I even once talked to someone who apparently thought "ASCII" was a general term for the whole concept of organising character glyphs in an ordered set. — JIP | Talk 6 July 2005 07:45 (UTC)

[edit] The image on the article depicting the character set

Not to be an anti-imagist, but I'm questioning the usefulness of including the image depicting the character set. I'm interested in removing it. Would there be support (or opposition) among you for doing so? Thanks. Courtland 01:08, July 27, 2005 (UTC)

[edit] Redirects for control characters

We should probably have redirects for the following:

For the record: I've changed the redirect from Control-M into a disambiguation page because only this talk page and ASCII were using it. I don't see the need to bug every reader on carriage return with the information that there's another meaning of Control-M. --32X 23:40, 9 February 2007 (UTC)

[edit] The whole table, not just printible?

I see that the printible ascii characters are included 3 times (two tables in introduction and another table below). Could someone include the entire table up to 255? Tell me how you get the binary information and I'll do it, or maybe I'll just leave it blank and then someone can fill in the rest.

Thanks!--142.51.21.39 18:51, 11 October 2005 (UTC)

As explained in the article, ASCII is a 7-bit code, so regardless of whether you're using 7-bit or 8-bit bytes, each character will only ever manifest as a value under 128 decimal. Historically, ASCII-encoded data was typically transmitted in 8-bit bytes, with the 8th bit used for either (1) nothing, (2) encoding characters beyond the range of ASCII, or (3) parity (something else unrelated to the encoded text itself). For situation #2 there emerged a number of standards like ISO 8859 and C1 control codes, but these are not part of ASCII; they are supplements to it. It would be wrong for you to add them to the tables. It might be useful to have a separate table for the IANA-approved "us-ascii" character map, which explicitly defines ASCII as an 8-bit encoding with values 128-255 unassigned/disallowed, but I'm guessing this isn't what you had in mind. — mjb 20:17, 11 October 2005 (UTC)

[edit] Future of ASCII

I would like to see some discussion of whether we can depend on someone's being able to read or convert ASCII text saved today in 20 or 50 years from now? In other words, is it a good format to use for documents created for posterity? —Preceding unsigned comment added by 24.5.85.54 (talk • contribs) 19 October 2005

I assume ASCII documents will be readable in 50 years, since so many documents are using it, and because the future encoding Unicode is backwards compatible with ASCII. The fact that major programming languages like C are using ASCII creates a kind of guarrantee to make ASCII unchanged, at least printable characters. No one want to destroy tested and well working source code. Whether documents with ISO-8859-1 and other 8-bit encodings are readable then, is a good question. Programming languages use extended ASCII only for non-English strings and comments. -- BIL (talk) 21:58, 29 December 2007 (UTC)

[edit] Policy re External Links

There are lots of ASCII charts on the web, and people keep adding links to them. Since the article contains a perfectly good chart itself, I suggest that it should not link to yet-another-chart pages. I therefore removed links to

yep nuke it, its HIGHLY misleading to state that what appears to be one of the old IBM code pages is the most common extended ascii set today. Plugwash 13:50, 5 November 2005 (UTC)

I left http://www.jimprice.com/jim-asc.htm in, because it has some useful material explaining how to send a document "as ASCII". Chris Chittleborough 14:47, 7 November 2005 (UTC)

Note: The content related to ASCII http://www.paulschou.com/tools/xlate/ has been fixed, thank you for noticing my error. I have fixed it and provide this link as an educational tool. If you have any questions or requests I will be open to amend it if needed - Paul Schou


I've deleted a link to www.asciivalue.com. Despite its name, it allows non-ASCII input (codepoints > 127) and does not label its HTTP responses as ASCII.
I've left the link to http://www.paulschou.com/tools/xlate/ in, because it does lots of conversion and so could be useful. However, it also treats codepoints 128-255 as "ASCII". Should we delete this link?
Chris Chittleborough 11:55, 15 December 2005 (UTC)
I'd by inclined not to link to anything that propogates the myth that there exist ascii codes 128-255. Also most of the stuff on that site whilst usefull isn't really very much to do with the topic of this article. Plugwash 22:19, 25 December 2005 (UTC)
To be brutally honest i think MOST IF NOT ALL of the external links currently in this article deserve to go. we need one reasonally authoritive source for the code chart (unicode.org seems a good choice) in the references section and possiblly one converter tool for seeing the raw ascii values in the external links section. We are not a web directory we are an encyclopeidia and should be carrying references for our content and good links for people to read more on the subject but not a list of every trashy website thats perhipherally associated with a subject. Plugwash 22:19, 25 December 2005 (UTC)
Belated thanks to User:Plugwash for good work on this list. I've just deleted an ad for www.ascii.com from it and edited the text of two other links. Paul Schou has added an interesting comment, and his translation page now mentions that "Only codepoints < 128 are ASCII". I suggest we drop the link to www.asciivalue.com in favour of Mr. Schou's link. Chris Chittleborough 04:48, 1 February 2006 (UTC)
Link to www.asciivalue.com removed. Plugwash 12:54, 1 February 2006 (UTC)
Link reinstated by User:67.187.249.55 2 Feb 2006 and then removed again by Chris Chittleborough 17:20, 5 February 2006 (UTC)

[edit] Notes on External Links

User:Nathanaeljones added a link to [QuickKey], a Visual Basic application for inserting any Unicode character into a document or application. Presumably this user is the Nathanael Jones who wrote QuickKey. He has added links to QuickKey to a number of pages. He has also created a useful-but-needs-some-tidying-up article on Alt_codes and added links to it to a number of articles. Thanks, Nathanael! However, I have commented out the link in the ASCII page, on the assumption that not many people will QuickKey to enter ASCII characters :-) Chris Chittleborough 09:27, 8 February 2006 (UTC)

User:68.158.159.129 has added a link to http://www.asciilist.com/, which appears to be a work in progress and seems promising to me. —Chris Chittleborough 11:21, 6 April 2006 (UTC) (edited 22:45, 12 April 2006 (UTC))

I disagree. It is not authoritative, it exists just to drive traffic to the owner's Google ads, and contains no information that isn't already presented in the article. Charts like these are a dime a dozen. I'm deleting the link.—mjb 01:18, 13 April 2006 (UTC)
Mjb is right. (I use Firefox and the NoScript extension, so I didn't see the Google ads.) Good riddance. Cheers, Chris Chittleborough 10:00, 13 April 2006 (UTC)
User 74.229.83.147 (talk · contribs) inserted asciilist.com again with the HTML comment
Note: This was previously marked as spam and deleted; however, I found it as a very useful. The only other decent website that I have been able to find was www.asciitable.com, which is covered with watermarks and ugly ads. Please don't remove this as I think other people may find this helpful as well. -Will
User:Mjb has since reverted that edit. I suggest that if we do have a link to www.asciilist.com, it should be to the printer-friendly version, not the main page. Cheers, ChriWs Chittleborough 20:26, 14 April 2006 (UTC)
I already stated my reasons for removing it; no amount of "I thought it was still useful" makes up for the shortcomings I pointed out. Will is actually in a better position to make a case for improving the charts in the article on Wikipedia. However, I doubt he wants to do that. The IPs used by the person who added the asciilist.com link were 68.158.159.129 and 74.229.83.147, which are both fed by the same BellSouth router, 65.14.249.166, which is apparently in the state of Georgia. The asciilist.com domain is owned by Will Buckner (wcc@techmonkeys.org) of Cumming, Georgia. The person posting here (and on my talk page) as "Will" (and who is the only person who seems to find asciilist.com worthy of inclusion) just started using the Wikipedia userid wcc44 today. I rest my case. >:D—mjb 03:39, 15 April 2006 (UTC)
I need to make myself clearer. I agree with Mjb's words and actions. I strongly oppose linking to a chart which is accompanied by ads. The point I was trying to make is that any case for linking to a chart which has ads would apply just as much to a printer-friendly version of that web page; therefore we should never link to the "unfriendly" version. (If there is no ad-free version of the chart, then I oppose any link to that site.) Chris Chittleborough 07:07, 15 April 2006 (UTC)
The printer friendly version is, of course, add free (wouldn't be too printer friendly otherwise :). The PDFs are also add free. Only the front page contains ads at all.
I still think that the arguments in favor of this external link are actually a case for adding a concise chart to Wikipedia (which has a Printable Version link on every article). There could be separate charts for each version of ASCII, too (1963, 1967, etc.). That way the material will be peer-reviewed and better disseminated.—mjb 18:55, 16 April 2006 (UTC)
Just because it's a "printable" version doesn't make it good enough. It needs to all fit on one printable page, yet make good use of space so that the fonts arent too small / etc. The version on asciilist.com was designed to fit entirely on one page and be a good quick reference (pin it up in your cubicle, etc.). Even if this could be accomplished on Wikipedia itself, would it really be worth the effort? It is providing something separate from the article. The article's purpose is to educate about ASCII itself (right?), whereas asciilist's printable page is meant as a "reference card" to the ASCII code. --Wcc 01:47, 17 April 2006 (UTC)
What about just linking to the printable page / PDF without ads? My intention in building the site was to provide a resource; the ads are just to help pay the bills. What would you guys think of a link directly to http://www.asciilist.com/index.php?a=showPrintableBasic ? This page contains no ads, and is a useful resource. It does add value to the article. The reason for which I created the page is that I, as a programmer, have been unable to find a good printable ASCII chart anywhere that isn't covered in ads and watermarks on the printable page and distracting from the content. While the article itself may provide all of the needed information on ASCII, it doesn't provide a quick, printable programmer's ASCII reference. Please consider allowing the add-free printable page to be added as an external link (I won't add it without approval). (And, yes, I am the owner of this site... I never denied that. That does not change the fact that it adds value to this article). Wcc 17:49, 15 April 2006 (UTC)

I've just deleted "ASCII Character Code Chart at Electronic Science Lobby", because it's not about ASCII (no DEL; 255 chars). This site has low-quality content and lots of Google ads. The link was added by User:61.17.232.207. —Chris Chittleborough 22:45, 12 April 2006 (UTC)

[edit] References and External links

I've just added http://www.wps.com/projects/codes/ into the External links section before I noticed it was in References. Rather than remove it I think the duplication is useful for clarity as I rarely think of references as offsite links. Is there a Wikipedia policy about this sort of duplication? Especially as in this case where the other website carries a lot more information than here. 86.16.135.53 11:41, 27 August 2006 (UTC)

I suggest we
(1) simplify the "References" section to just
<div class="references-small"><references/></div>
(2) move "Unicode.org chart on the ASCII range" to External links,
(3) drop the "Tom Jennings (October 29, 2004)" link in favour of the one User:86.16.135.53 just inserted (enhancing the latter to wikilink to Tom Jennings), and
(4) drop the direct wikilink to Alt codes.
Cheers, CWC(talk) 12:33, 27 August 2006 (UTC) who also added the "References and External links" subheading

I've made these changes. We now have the following External Links (HTML comments shown in italics):

(The linkified dates are the result of a bot editing inside HTML comments.)

Cheers, CWC(talk) 20:28, 31 August 2006 (UTC)

[edit] Binary alphabet

I have proposed that Binary alphabet be merged into this article. Seems to be really about ASCII and not an alphabet. Srl 17:53, 25 November 2005 (UTC)

personally i'd say that article deseves and AFD i've never seen that term used and imo a redirection to here would mislead people is was a synonym of ASCII. Plugwash 22:06, 25 November 2005 (UTC)

"Binary alphabet" is used in the context of formal languages for referring to the fact that the alphabet is composed of two symbols. The article is however misleading, and in any case should not redirect here. Paolo Liberatore (Talk) 17:16, 30 November 2005 (UTC)

[edit] scandanavian

rfc 1459 states

Because of IRC's scandanavian origin, the characters {}| are considered to be the lower case equivalents of the characters []\

does this apply to scandanavian languages in general or not and if so is the fact this is easy to do in ascii a design feature or a coincidence? Plugwash 00:29, 26 December 2005 (UTC)

I'm not sure I understand the question. Danish and Norwegian have three additional letters (æøå and ÆØÅ) compared to English, and it was natural to steal the "next three" symbols from ASCII when making a national variant. These symbolas are not tradionallly common in Danish or Norwegian text. Swedish (and I believe Finnish) has different symbols for the letters denoting (ÄÖÅ and äöå) the same sounds as the Danish/Norwegian letters, but the sorting sequence is different (ÅÄÖ). They choose to use the same sequence as Danish/Norwegian for compatibility, rather than the "correct" sequence.
So it is a design feature of the Danish/Norwegian (and partly Swedish/Finnish) variants of ASCII that they are easily implementable from an ASCII base, but it is unlikley that the ASCII standard was designed with non-English variants in mind. --Per Abrahamsen 09:51, 2 January 2006 (UTC)

[edit] 1986

What change was made in 1986?

Ben Arnold 10:41, 2 March 2006 (UTC)

[edit] Information about specific codes

Any information on the intended (and historical / actual) use for the FS, GS, RS, US codes? (GhostInTheMachine 15:27, 29 March 2006 (UTC))

They were intended for transmitting tabular information, the sort of thing you'd store in database tables nowadays. For example,
<message>      = <clients-file> { FS <clients-file> } EOD
<clients-file> = <client-header> { GS <invoice> }
<invoice>      = <invoice-header> { RS <line-item> }
<line-item>    = <product-code> US <price> US <amount> [ US <comments> ]

IIRC, Bob Bemer has written that he never saw them used. However, I believe Niklaus Wirth did use FS as the end-of-file indicator in the Oberon operating system. Chris Chittleborough 08:30, 30 March 2006 (UTC)

The Pick system used the codes as delimiters in the database records. GhostInTheMachine 10:20, 29 April 2006 (UTC)

The comment about TECO using ESC to introduce commands was incorrect - ESC terminated textual arguments to commands (e.g. the text to be inserted or the name of a file) but the interpreter started out processing commands. I replaced it with a more correct comment and added a note about introducing terminal control sequences. I'd like to say something about using it in command-completion shells, but I don't use one so I'm not familiar with the semantics. Jordan Brown 05:37, 11 September 2006 (UTC)

The explanation for CR vs LF vs NL didn't agree with my understanding of the history - that UNIX and MacOS used single characters for simplicity - and so I "was bold" and fixed it, and added history further back tracing the use of CRLF in files to DEC OSes, which is where CP/M got it. Jordan Brown 05:37, 11 September 2006 (UTC)

In my opinion, the comment about nobody using ^N and ^O to switch character sets was incorrect, and so I removed it. Most if not all ANSI terminal implementations include this feature. One might wonder how often one *wants* to switch character sets, but it used to be quite common as I believe it was how you reached the line-drawing set on VT-100s. Granted, most of my use of this feature is to echo a ^O to recover from cat'ing a file that included a ^N. Jordan Brown 05:37, 11 September 2006 (UTC)

Thanks, Jordan Brown, for that good edit. You're right about ^N and ^O, they're part of ISO-2022. Cheers, CWC(talk) 15:53, 11 September 2006 (UTC)
You're welcome. Here's another, clarifying why hitting Backspace may yield ^H. I'm not entirely happy with the first few words of that note - I don't exactly consider it an "ambiguity" - but it's the words that were there in the previous rev and I can't immediately come up with anything better. I also wonder whether this note is getting a bit too long. Jordan Brown 05:02, 13 September 2006 (UTC)

[edit] U+2400 etc not rendered?

Unicode has a block of "control picture" characters: U+2400 = SYMBOL FOR NULL, U+2401 = SYMBOL FOR START OF HEADING, and so on. The article uses these. However, it turns out that Internet Explorer does not render these characters, even though Firefox does. (Heartfelt rant about software development models omitted for brevity.) My tests used IE V6.0.2900.2180.xpsp_sp2_gdr.050301-1519 on XP service pack 2, and Firefox V1.5.0.1 on the same OS.

I have just edited the article to say that the PR column in the table of control characters may not render properly on some browsers.

Could people with other browsers take a close look at this page and report whether it renders the control picture characters properly? For instance, U+2400 should show up as "NUL" in small letters, probably arranged horizontally (NUL or diagonally (NUL).

Cheers, CWC(talk) 12:39, 20 April 2006 (UTC)

IEs font selection sucks. I've put template:unicode in place, if they still don't show can you use character map to tell us which fonts you have that contain them? Plugwash 12:50, 20 April 2006 (UTC)
Good move. But the control picture characters still aren't rendering for me in IE. I suspect that Firefox is constructing the "glyphs" itself from downsized capital letters. (Because some unicode characters are combinations of simple characters — eg. roman numerals — they can be rendered even if not defined directly in fonts.) I would hope that Microsoft's unicode font facilities, whose name currently escapes my mind, does this sort of combining. But, if so, why doesn't IE use combining? Oh, that's right: IE6 sucks. CWC(talk) 14:09, 20 April 2006 (UTC)
I don't think this is so much a failure in IE font handling as it is a gap in Windows' Unicode coverage. IE seems to do OK on a wide range of random Unicode characters. I presume that there simply isn't any font (that Windows searches) that includes these particular Unicode code points. I assume that there's a way to augment the fonts that Windows uses, but I haven't yet found anything that describes that process. (Yes, something could artificially construct these characters, but that would imply significant special-case work. It'd be simpler to supply an appropriate font.) Jordan Brown 06:03, 13 September 2006 (UTC)
Hi, Jordan. My guess (based only on stuff I've seen Mozilla browsers do) is that their cross-platform font-handling code has a facility to synthesize missing glyphs from other characters. I'd argue that Microsoft's unicode font system, whose name still escapes my mind, should do the same thing. So, yes, it's a possible defect in that system, not in IE, that causes the problem ... but can we please keep slagging IE anyhow?
(Maybe IE7 will fix things? Let's hope it comes with a better font handling system or better fonts.) Cheers, CWC(talk) 12:45, 13 September 2006 (UTC)
AHA! Imagine my surprise when I happened to look at this page on a different computer, also with IE6, and these characters looked OK! Judiciously trimming down the page yielded the answer: one computer had Arial Unicode MS and the other didn't. It looks like this font comes with MS Office, and it probably didn't get removed when I uninstalled the trial version of MS Office from this computer. (It's also available for purchase; see the article above.) Other fonts that MediaWiki:Common.css's .Unicode style looks for are: Code2000, TITUS Cyberbit Basic, Doulos SIL, Chrysanthi Unicode, Bitstream Cyberbit, Bitstream CyberBase, Thryomanes, Gentium, GentiumAlt, Visual Geez Unicode, Lucida Grande, Microsoft Sans Serif, and Lucida Sans Unicode. Perhaps some of them have these glyphs and are more readily available; I haven't had a chance to investigate. Jordan Brown 21:48, 13 September 2006 (UTC)
Code2000 is $5 shareware and has these glyphs, though they don't look all that good. Jordan Brown 22:26, 13 September 2006 (UTC)

[edit] CP/M

Don't CP/M files end with Ctrl-Z (following DEC conventions), not Ctrl-C? AnonMoos 07:04, 31 May 2006 (UTC)

Err, I think you mean Ctrl-D, the default end-of-file input character, not Ctrl-C, the interrupt character. Like Ctrl-Z on a DEC OS, Ctrl-D was typed on a terminal to tell the keyboard driver to report end of file, but was not stored in files. Unix and most DEC OSes stored the length of a file in bytes, so there was no need for an in-band end-of-file indicator.
(In ASCII, Ctrl-D is "End-of-transmission character" and Ctrl-Z is "Substitute character". Apparently Dennis Ritchie and Ken Thompson followed the standard, but DEC went for the easy-to-remember character.)
There was one low-end DEC OS, RT-11, that stored the length of a file only as a number of blocks; RT-11 programs which read text files simply ignored any contiguous sequence of zero bytes at the end of the last block. CP/M was reputedly influenced by RT-11 (or at least that's what I heard from fellow RT-11 programmers when CP/M appeared) and stored file lengths as a number of 128-byte "sectors", so they might well have used Ctrl-Z as an in-band indicator for text files. Certainly, MS-DOS used Ctrl-Z as an in-file marker (see PNG#File_header for a clever trick based on this), and I believe this, like most of MS-DOS V1, came from CP/M.
But I've never used CP/M, so I'm unable to answer your main question. Cheers, CWC(talk) 13:55, 31 May 2006 (UTC), former RT-11 guru
It says Ctrl-C on the article page right now: ASCII#ASCII control characters ; however VAX/VMS (the one DEC operating system I've had experience with) didn't use Ctrl-D to mark end of text input from console, but rather Ctrl-Z -- and I have strong reason to suspect that CP/M did the same. AnonMoos 16:44, 31 May 2006 (UTC)
Sorry, I didn't explain myself well enough. Despite its meaning in ASCII, Ctrl-C is not used as end-of-file in either Unix or DEC OSes; instead it's the stop-what-you're-doing character in both (though Unix allows you to change which character does what). Ctrl-D as the default end-of-file character for Unix is "in the spirit of" ASCII. Ctrl-Z as EOF for all(?) the PDP-11 DEC OSes and VMS is totally unrelated to the ASCII meaning. (I always assumed they chose it because it's easy to remember that end-of-alphabet means end-of-file.) I think you're right that (1) CP/M used Ctrl-Z for end-of-file, and (2) they they got it from DEC (along with PIP).
The relevance of this is that most of the ASCII control characters are used in ways that have nothing to do with their ASCII definitions. Basically, they are hangovers from the teletype era. Computer people have kept inventing new meanings for "unused" control characters, which rarely had anything to do with the original meaning. Cheers, CWC(talk) 20:38, 31 May 2006 (UTC)

I'm 100% sure that DEC's OS/8 used ^Z in the file to represent the end of file, and 90-something % sure that the same was true for RT-11. I'm less sure about TOPS-10, TOPS-20, and RSTS/E, though I think they did, and haven't a clue about VMS and RSX-11. Jordan Brown 05:21, 11 September 2006 (UTC)

[edit] FIFA WorldCup 06 live in ASCII

for those interested: [1] (^_^)

[edit] UNIX control characters

Originally UNIX (6th and 7th editions) used # as erase and @ as line kill (with ^D as EOF, DEL/RUBOUT as Interrupt and ^\ as Quit) - see unix/tty.h on sheet 79 in chapter 5 of "Lions' Commentary on UNIX 6th Edition with Source Code" ISBN 1-57398-013-7. This was because of the use of hard copy teletype terminals (I assume). Later on when glass ttys became popular the erase character was changed to ^H. Still later @ became a regular character (allowing it to be used for email addresses). BSD UNIX changed things to match the characters used by DEC on its VAX VMS operating system - DEL was reassigned to be erase (instead of ^H) and ^C replaced it for interrupt. TheGiantHogweed 07:02, 9 July 2006 (UTC)

Many years ago, when I first used Unix, I was very startled to find #=erase. I seem to recall that the way to input "#" was to press "\" and "#". (In other words, backslash was the terminal-driver-escape character. In modern Unix terms, LNEXT defaulted to \ instead of ^V.) Does anyone know for sure?
DEC had a fairly standard set of Control-key actions, but they were hard-coded. Eg., ^U=erase, ^C=interrupt(like Unix SIGINT). On TOPS-10 and TOPS-20, ^T (T for Tell?) produced a status report (CPU time used, etc). VMS had ^T and added ^Y (= Unix SIGQUIT). BSD (4.3 onwards) has a STATUS key, defaulting to ^T, which generates a SIGINFO.
I guess all the developer teams borrowed each other's better ideas. Does anyone know for sure? Cheers, CWC(talk) 10:45, 9 July 2006 (UTC)
Yes, Unix terminal drivers use "\" to escape the next character typed, so "\#" is required to enter a single "#" if that is the currently set delete character for the user's terminal. For historical ancestry, a lot of DEC TOPS-10 stuff was borrowed by CP/M, which was in turn borrowed by Microsoft DOS, including ^Z for end-of-file. — Loadmaster 16:24, 5 December 2006 (UTC)

[edit] \n is not always ASCII LF in C

The article Newline states :

The C programming language provides the escape sequences '\n' (newline) and '\r' (carriage return). However, contrary to popular belief, these are in fact not required to be equivalent to the ASCII LF and CR control characters.

But reading the table on the ASCII page it gives the suggestion that \n is always mapped to ASCII LF according to some (C) standard which isn't true for all C compilers. Not sure if its worth mentioning though...

Ervee 10:29, 25 January 2007 (UTC)

[edit] The Table with notes

This article has a table with notes inside the table. The notes are currently implemented with {{ref}}/{{note}}, but they has been converted to cite.php a few times with an automatic tool. This conversion moves the notes away from the table. I think these notes should stay with the table. Gimmetrow 12:45, 9 February 2007 (UTC)

Thanks for your excellent work on this article, Gimmetrow.
I agree that the notes should stay with the table.
Perhaps we should (shudder) "subst:" the {{ref}} and {{note}} tags? That would stop the well-intentioned automated conversion, but it would make subsequent editing much harder. Just a thought.
Cheers, CWC(talk) 14:01, 9 February 2007 (UTC)

[edit] rest of values

Why does the page not show the values up to 255? What do those mean? Nate | Talk Esperanza! 19:56, 13 March 2007 (UTC)

Whatever they might mean, they are not ASCII character codes. ASCII is a 7-bit character code standard. There are no ASCII characters for codes other than 00 to 7F. — Loadmaster 20:44, 13 March 2007 (UTC)

[edit] Clearer identification of overstrike characters

I have three coments or suggestions, all related to this paragraph from the section on "ASCII printable characters":

"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)."

1. I had no idea what an "inverted vel" was, so I followed the link (http://en.wikipedia.org/wiki/Vel) - but it was not at all relevant. I think the link should be removed -- or better, replaced with a link that does explain what a "vel" or "inverted vel" is. I did some search engine queries but found no explanation.

2. In this same sentence, I also wish that the references to "grave accent", "backtick", and "inverted vel" clearly specified the ASCII character/symbol being referred to. The reader should not have to figure this out (and this particular reader, in fact, cannot figure it out, as I explain below).

For example, "grave accent" clearly refers to character 96, and the link to the Wikipedia article explicitly states this: "In the ASCII character set the grave accent is encoded as character 96, hex 60." So in this article, I would suggest something like "grave accent (character 96)" to clearly specify the ASCII character being referred to.

Next, what character does "backtick" refer to? If it is character 96, as I believe, then perhaps the sentence should be modified to show the equivalence, as in "a backspace can precede a backtick or grave accent (character 96)". There is no Wikipedia article on the backtick, but "backtick" redirects to the Grave accent article. That article uses the term "backtick" but never explicitly states that "backtick" is synonymous with (or a homoglyph for) "grave accent".

Finally, "inverted vel" ... to which ASCII character does this refer? You tell me! Could someone in possession of this knowledge add it to the article?

3. Finally, in the same sentence, the existing text says "a backspace can precede ...", followed by a list of exactly three characters. One way to read this sentence is that the list is exhaustive - only those three characters - which I hope was not intended. It would be better to say something like "a backspace can, for example, precede ...". I note that the text has omitted other characters commonly used in the same way (as overstrikes), such as the comma (character 44), used to simulate a c with cedilla (Ç or ç), and the forward slash / (character 47), used to simulate a Scandinavian slashed "o" character or a greek phi (ø), or the hyphen/minus symbol (character 45), used with zero (character 48) or with uppercase O (character 79) to simulate the greek letter theta (θ)...

I hope these comments meet with favorable consideration, and that someone will rewrite this paragraph. Or I'd be glad to do so, if someone can point me to definitive information on the "inverted vel".

Aeolopile 06:16, 20 April 2007 (UTC)

I suspect that the "inverted vel" refers to character 94 (^) KerryVeenstra 06:54, 20 April 2007 (UTC)
The original author's sentence (from 11:42, 24 June 2003) considers an inverted vel to be a breath mark: "ASCII provides some internationalization for French and Spanish (both spoken in the U.S.) by providing a backspace with the grave, accent (miscalled a "single quote"), tilde, and breath mark (inverted vel)." I seem to remember some early glass terminals that provided this backspace capability. From elsewhere, a vel is a spear (Murugan). KerryVeenstra 22:43, 20 April 2007 (UTC)
IIRC, an early version of ASCII had "↑" (up-arrow) instead of "^" as character 94. CWC 03:02, 21 April 2007 (UTC)

[edit] Pound symbol

In England the Currency symbol mapped to character 35, so that telex transmissions which included the currency symbol did not automatically covert to a confusing value when transmitted between the two countries. That is, the $ symbol mapped to # when transmitted from US to GB, the LSD symbol mapped to # when transmitted GB to US, $ never mapped to LSD.—Preceding unsigned comment added by 150.101.166.15 (talk) 01:25, 2 July 2007 (UTC)

That makes sense. Do you happen to have a Reliable Source we could cite for that? CWC 07:38, 2 July 2007 (UTC)
ftp://ftp.isi.edu/in-notes/rfc20.txt
3 These characters should not be used in international interchange without determining that there is agreement between sender and recipient. (See Appendix B4.)
4 In applications where there is no requirement for the symbol #, the symbol (Pounds Sterling) may be used in position 2/3.
and
http://wps.com/projects/codes/Revised-ASCII/page4.JPG
http://wps.com/projects/codes/ECMA-6.pdf
also, in more detail:
http://www.transbay.net/~enf/ascii/ascii.pdf —Preceding unsigned comment added by 150.101.166.15 (talk) 05:03, 21 November 2007 (UTC)

[edit] EOF character in MSDOS.

MSDOS included two methods of file handling, 'text' and 'binary'. 'Text' method used the EOF character. When reading a file, file position and size of file was ignored, characters streamed to the EOF character. This method was faster. The MSDOS internal Copy command used 'binary' method for copying files with .com and .exe extension, used 'text' method for other files unless the /b option was specified. This meant that other files (for example .zip) files could be accidently truncated if used with the internal Copy command. The MSDOS external command xcopy did not have this behaviour. This behaviour was standard for all versions of MSDOS including Windows 98 SE, and probably for the copy of command.com included with Windows 2000. Windows XP does not include a copy of command.com (the command shell that included the copy command), and the copy command provided by the cmd shell probably does not have this behaviour.—Preceding unsigned comment added by 150.101.166.15 (talk) 01:48, 2 July 2007 (UTC)

[edit] Character Names

Would be nice if the printable char table included the english names for each character. —Preceding unsigned comment added by 74.93.101.81 (talk) 21:13, 23 September 2007 (UTC)

The following discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Y Done - WP:COMMONNAME seems to apply here. Neıl ☎ 11:03, 4 January 2008 (UTC)

[edit] Requested move

American Standard Code for Information Interchange → ASCII — Much more popular as an acronym than spelled out. (60,000,000 vs 182,000 Googlehits.) Was at ASCII for years, including getting to be a featured article. —Callmederek (talk) 21:15, 29 December 2007 (UTC)

[edit] Survey

Feel free to state your position on the renaming proposal by beginning a new line in this section with *'''Support''' or *'''Oppose''', then sign your comment with ~~~~. Since polling is not a substitute for discussion, please explain your reasons, taking into account Wikipedia's naming conventions.

[edit] Discussion

Any additional comments:
The above discussion is preserved as an archive. Please do not modify it. Subsequent comments should be made on the appropriate discussion page, such as the current discussion page. No further edits should be made to this discussion.

[edit] My ASCII

My ascii produces all characters as printable except 000. Is the article wrong or is it just my computer? Thanks, George D. Watson (Dendodge).TalkHelp and assistance 15:25, 20 February 2008 (UTC)

[edit] ASCII acronym

The term ASCII is an acronym which appears to have two potential expansions, one is the American Standard Code for Information Interchange, the other is the American Standards Committee for Information Interchange. The available online literature is unable to produce an absolute and unambiguous corroboration that it is one or the other.

The former, whilst appearing to make sense, makes less sense when one considers that ASCII was developed by ASC: the American Standards Committee.

Is there a citation available to the original ASCII standard? If not, then it should be acknowledged that two alternatives are in common use.

Gregmal (talk) 00:00, 11 March 2008 (UTC)

I think the relative google hits should be indicative. Standard Code (-wiki) = 225,000 hits, Standards Committee (-wiki) = 726 hits. But if that isn't enough, see scans of ASA standard X3.4-1963 and 1964 article on X3.4-1963. Don't trust O'Reilly. Gimmetrow 03:55, 11 March 2008 (UTC)
I scanned an ASCII article from the July 1964 issue of Electronics World and put it on my web site. This was written when the first version of the American Standard Code for Information Interchange was news. Notice it is Upper Case only and has early control codes. Electronics World, July 1964 -- SWTPC6800 (talk) 04:32, 1 April 2008 (UTC)
Yes, ASA X3.4-1963 did not specify codes for lower case characters, though it had a lot of undefined codes. Gimmetrow 04:40, 1 April 2008 (UTC)

[edit] Article freshness

In my opinion the article has grown in size I believe it is its size that impedes its appeal. Sasepeev (talk) —Preceding comment was added at 21:35, 31 March 2008 (UTC)

[edit] The pound sign in ASCII

On the BBC computer, the pound sign was in the lower ASCII table, as well as the hash and the dollar. However, on today's PCs, the pound sign is no longer in the first 7 bits - it's now 8-bit ASCII. The symbol that replaced it is the backwards apostrophe (`). Can anyone tell me why the pound sign (£) was taken out of 7-bit ASCII on today's PCs, when it was there on the BBC computer from the 80s? Thanks!

I've just checked, and the pound sign was CHR$96 or CHR$&60 on the BBC (96 decimal, 60 hex). The hash was in its usual place of 35 (decimal).

90.205.80.229 (talk) 21:33, 7 April 2008 (UTC)

The sign ‘£’ was actually never in true ASCII, merely in encoding based upon ASCII but adapted to other use. As more powerful systems have been produced, they have supported more sophisticated encodings, supporting larger character sets. In order to facilitate inter-system compatibility, efforts are made to converge on an encoding. It was naturally that true ASCII should form the core of most extensions. —SlamDiego←T 21:58, 7 April 2008 (UTC)
The term ASCII has been misused. It means American Standard Code etc, and has characters needed in the USA, no other. ASCII has been used as name for a lot of 7-bit and 8-bit encodings. --BIL (talk) 07:44, 8 April 2008 (UTC)
  1. I don't need to be told this.
  2. The article begins by expanding the abbreviation to “American Standard Code for Information Interchange”.
  3. Many characters used in America are not found in ASCII, and the ‘£’ is used in America, albeït not as often as were the characters in the ASCII encoding.
—SlamDiego←T 23:43, 8 April 2008 (UTC)

[edit] Removed text

IMO this edit removed some interesting material. If the article is too long, let's split it, not throw away good content. Andrewa (talk) 06:41, 3 June 2008 (UTC)

The "structural features" are still there in history, which describes how it came to be. Gimmetrow 07:23, 3 June 2008 (UTC)
Well, yes, of course they are, I linked to the history above, didn't I? I don't see any justification for the removal in the summaries. Would you like to give one? Andrewa (talk) 01:39, 4 June 2008 (UTC)
The text which was moved (not removed) had no link to the history section. Gimmetrow 01:44, 4 June 2008 (UTC)
Oops, so it was. Missed that somehow. Thanks! Andrewa (talk) 10:40, 4 June 2008 (UTC)

[edit] More removed text

Here's another edit removing what seems to be useful references. I think these are worth having in a separate subsection. The neologism "asciify" is not mentioned elsewhere in the article and I'm hesitant to put up a new article just for that. --A12n (talk) 15:09, 11 June 2008 (UTC)

It doesn't need an article, it's at best a dictionary definition, and since one of the "refs" is a wiki and the other is a blog about software called "asciify", is it even notable? Gimmetrow 20:47, 11 June 2008 (UTC)
The principle I think is that it is worthwhile to show how the key term of the article is used. So for instance the neologism "ASCIIbetical" is indicated elsewhere in the article. I don't think it's inappropriate at all to mention such usage (which has a place also in dictionaries we'd agree) in an encyclopedic article. Is this knowledge really so irrelevant to the subject that it is excluded from the article? And since we agree a separate article is not currently merited, effectively excluded from being explained anywhere in Wikipedia as a whole? I think not. "Asciify" is obviously a coinage, but is established enough to get 58,000 hits on Google (I cherry-picked a couple of refs; perhaps better ones can be found); "asciified" 1420 hits; and "asciification" 463. That ain't huge I admit, but it is significant, representing at least an emerging usage related to use of ASCII. In fact maybe the core issue here should be that conversion into ASCII is something people do for various purposes (namely certain text needs or preferences and ASCII art), and there's a word for that.--A12n (talk) 14:05, 12 June 2008 (UTC)