Stanford Extended ASCII (SEASCII) is a derivation of the 7-bit ASCII character set developed at the Stanford Artificial Intelligence Laboratory (SAIL/SU-AI) in the early 1970s. Not all symbols match ASCII.
Carnegie Mellon University, the Massachusetts Institute of Technology, and the University of Southern California also had their own modified versions of ASCII.
Character set
Each character is given with a potential Unicode equivalent.
SEASCII345| 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | A | B | C | D | E | F | |
| 0x | · | ↓ | α | β | ∧/^ | ¬ | ε | π | λ | γ | δ | ∫ | ± | ⊕ | ∞ | ∂/∇ |
| 1x | ⊂ | ⊃ | ∩ | ∪ | ∀ | ∃ | ⊗ | ↔ | _ | → | ~ | ≠ | ≤ | ≥ | ≡/≍ | ∨ |
| 2x | SP | ! | " | # | $ | % | & | ' | ( | ) | * | + | , | - | . | / |
| 3x | 0 | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | : | ; | < | = | > | ? |
| 4x | @ | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O |
| 5x | P | Q | R | S | T | U | V | W | X | Y | Z | [ | \ | ] | ↑ | ← |
| 6x | ` | a | b | c | d | e | f | g | h | i | j | k | l | m | n | o |
| 7x | p | q | r | s | t | u | v | w | x | y | z | { | | | ◊ | } | ^ |
See also
- Stanford Artificial Intelligence Laboratory (SAIL/SU-AI)
- Stanford Artificial Intelligence Language (SAIL)
- Stanford/ITS character set
Further reading
- "double bucky". Free On-line Dictionary of Computing (FOLDOC). 1994-12-07. Archived from the original on 2017-03-07. Retrieved 2017-03-07.
- Knuth, Donald Ervin (1979). TEX and METAFONT — New Directions in Typesetting. Bedford, MA, USA: Digital Press. p. 169. ISBN 0-932376-02-9. (NB. Shows a table of SEASCII differing in a few code points from that described in RFC 698.)
External links
References
Beebe, Nelson H. F. (2005). "Proceedings of the Practical TEX 2005 Conference: The design of TEX and METAFONT: A retrospective" (PDF). TUGboat. 26 (1). Salt Lake City, Utah, USA: University of Utah, Department of Mathematics: 39-40. Retrieved 2017-03-07. The underscore operator in SAIL source-code assignments printed as a left arrow in the Stanford variant of ASCII, but PDP-10 sites elsewhere just saw it as a plain underscore. However, its use as the assignment operator meant that it could not be used as an extended letter to make compound names more readable, as is now common in many other programming languages. The left arrow in the Stanford variant of ASCII was not the only unusual character. (NB. Shows a table of Stanford extended ASCII following that described in RFC 698.) https://www.tug.org/tugboat/tb26-1/beebe.pdf ↩
Beebe, Nelson H. F. (2005). "Proceedings of the Practical TEX 2005 Conference: The design of TEX and METAFONT: A retrospective" (PDF). TUGboat. 26 (1). Salt Lake City, Utah, USA: University of Utah, Department of Mathematics: 39-40. Retrieved 2017-03-07. The underscore operator in SAIL source-code assignments printed as a left arrow in the Stanford variant of ASCII, but PDP-10 sites elsewhere just saw it as a plain underscore. However, its use as the assignment operator meant that it could not be used as an extended letter to make compound names more readable, as is now common in many other programming languages. The left arrow in the Stanford variant of ASCII was not the only unusual character. (NB. Shows a table of Stanford extended ASCII following that described in RFC 698.) https://www.tug.org/tugboat/tb26-1/beebe.pdf ↩
Mock, T. (1975-07-23). "RFC 698: Telnet extended ASCII option". doi:10.17487/RFC0698. RFC 698. NIC #32964. Archived from the original on 2017-03-07. Retrieved 2017-03-07. {{cite journal}}: Cite journal requires |journal= (help) [1] (NB. Replaced by RFC 5198.) https://www.heise.de/netze/rfc/rfcs/rfc698.shtml ↩
Cowan, John Woldemar (1999-09-08). "Stanford Extended ASCII to Unicode". 0.1. Unicode, Inc. /wiki/John_Woldemar_Cowan ↩
Beebe, Nelson H. F. (2005). "Proceedings of the Practical TEX 2005 Conference: The design of TEX and METAFONT: A retrospective" (PDF). TUGboat. 26 (1). Salt Lake City, Utah, USA: University of Utah, Department of Mathematics: 39-40. Retrieved 2017-03-07. The underscore operator in SAIL source-code assignments printed as a left arrow in the Stanford variant of ASCII, but PDP-10 sites elsewhere just saw it as a plain underscore. However, its use as the assignment operator meant that it could not be used as an extended letter to make compound names more readable, as is now common in many other programming languages. The left arrow in the Stanford variant of ASCII was not the only unusual character. (NB. Shows a table of Stanford extended ASCII following that described in RFC 698.) https://www.tug.org/tugboat/tb26-1/beebe.pdf ↩