document_title: Visual Basic .NET

question_text: what is the latest version of visual basic .net

text: Visual Basic .NET

text: Syntax[edit]

text: This section needs expansion. You can help by adding to it. (April 2014)

text: VB.NET uses statements to specify actions. The most common statement is an expression statement, consisting of an expression to be evaluated, on a single line. As part of that evaluation, functions or subroutines may be called and variables may be assigned new values. To modify the normal sequential execution of statements, VB.NET provides several control-flow statements identified by reserved keywords. Structured programming is supported by several constructs including two conditional execution constructs (If … Then … Else … End If and Select Case ... Case ... End Select ) and three iterative execution (loop) constructs (Do … Loop, For … To, and For Each) . The For … To statement has separate initialisation and testing sections, both of which must be present. (See examples below.) The For Each statement steps through each value in a list.

text: In addition, in Visual Basic .NET:

text:
There is no unified way of defining blocks of statements. Instead, certain keywords, such as "If … Then" or "Sub" are interpreted as starters of sub-blocks of code and have matching termination keywords such as "End If" or "End Sub".
Statements are terminated either with a colon (":") or with the end of line. Multiple line statements in Visual Basic .NET are enabled with " _" at the end of each such line. The need for the underscore continuation character was largely removed in version 10 and later versions.[2]
The equals sign ("=") is used in both assigning values to variables and in comparison.
Round brackets (parentheses) are used with arrays, both to declare them and to get a value at a given index in one of them. Visual Basic .NET uses round brackets to define the parameters of subroutines or functions.
A single quotation mark ('), placed at the beginning of a line or after any number of space or tab characters at the beginning of a line, or after other code on a line, indicates that the (remainder of the) line is a comment.

text: Simple example[edit]

text: The following is a very simple VB.NET program, a version of the classic "Hello world" example created as a console application:

text: It prints "Hello, world!" on a command-line window. Each line serves a specific purpose, as follows:

text:
This is a module definition. Modules are a division of code, which can contain any kind of object, like constants or variables, functions or methods, or classes, but can't be instantiated as objects like classes and cannot inherit from other modules. Modules serve as containers of code that can be referenced from other parts of a program.[3]
It is common practice for a module and the code file, which contains it, to have the same name; however, this is not required, as a single code file may contain more than one module and/or class definition.

text: It defines a subroutine called "Main". "Main" is the entry point, where the program begins execution.[4]

text: This line performs the actual task of writing the output. Console is a system object, representing a command-line interface (also known as "console") and granting programmatic access to the operating system's standard streams. The program calls the Console method WriteLine, which causes the string passed to it to be displayed on the console.

text: Instead of Console.WriteLine, one could use MsgBox, which prints the message in a dialog box instead of a command-line window.[5]

text: Complex example[edit]

text: This piece of code outputs Floyd's Triangle to the console:

text: Comparison with the classic Visual Basic[edit]

text: Whether Visual Basic .NET should be considered as just another version of Visual Basic or a completely different language is a topic of debate. There are new additions to support new features, such as structured exception handling and short-circuited expressions. Also, two important data-type changes occurred with the move to VB.NET: compared to Visual Basic 6, the Integer data type has been doubled in length from 16 bits to 32 bits, and the Long data type has been doubled in length from 32 bits to 64 bits. This is true for all versions of VB.NET. A 16-bit integer in all versions of VB.NET is now known as a Short. Similarly, the Windows Forms editor is very similar in style and function to the Visual Basic form editor.

text: The things that have changed significantly are the semantics—from those of an object-based programming language running on a deterministic, reference-counted engine based on COM to a fully object-oriented language backed by the .NET Framework, which consists of a combination of the Common Language Runtime (a virtual machine using generational garbage collection and a just-in-time compilation engine) and a far larger class library. The increased breadth of the latter is also a problem that VB developers have to deal with when coming to the language, although this is somewhat addressed e My feature in Visual Studio 2005.

text: The changes have altered many underlying assumptions about the "right" thing to do with respect to performance and maintainability. Some functions and libraries no longer exist; others are available, but not as efficient as the "native" .NET alternatives. Even if they compile, most converted Visual Basic 6 applications will require some level of refactoring to take full advantage of the new language. Documentation is available to cover changes in the syntax, debugging applications, deployment and terminology.[6]

text: Comparative examples[edit]

text: The following simple examples compare VB and VB.NET syntax. They assume that the developer has created a form, placed a button on it and has associated the subroutines demonstrated in each example with the click event handler of the mentioned button. Each example creates a "Hello, World" message box after the button on the form is clicked.

text: Visual Basic 6:

text: VB.NET (MsgBox or MessageBox class can be used):

text:
Both Visual Basic 6 and Visual Basic .NET automatically generate the Sub and End Sub statements when the corresponding button is double-clicked in design view. Visual Basic .NET will also generate the necessary Class and End Class statements. The developer need only add the statement to display the "Hello, World" message box.
All procedure calls must be made with parentheses in VB.NET, whereas in Visual Basic 6 there were different conventions for functions (parentheses required) and subs (no parentheses allowed, unless called using the keyword Call).
The names Command1 and Button1 are not obligatory. However, these are default names for a command button in Visual Basic 6 and VB.NET respectively.
In VB.NET, the Handles keyword is used to make the sub Button1_Click a handler for the Click event of the object Button1. In Visual Basic 6, event handler subs must have a specific name consisting of the object's name ("Command1"), an underscore ("_"), and the event's name ("Click", hence "Command1_Click").
There is a function called MessageBox.Show in the Microsoft.VisualBasic namespace which can be used (instead of MsgBox) similarly to the corresponding function in Visual Basic 6. There is a controversy[7] about which function to use as a best practice (not only restricted to showing message boxes but also regarding other features of the Microsoft.VisualBasic namespace). Some programmers prefer to do things "the .NET way", since the Framework classes have more features and are less language-specific. Others argue that using language-specific features makes code more readable (for example, using int (C#) or Integer (VB.NET) instead of System.Int32).
In Visual Basic 2008, the inclusion of ByVal sender as Object, ByVal e as EventArgs has become optional.

text: The following example demonstrates a difference between Visual Basic 6 and VB.NET. Both examples close the active window.

text: Visual Basic 6:

text: VB.NET:

text: The 'cmd' prefix is replaced by the 'btn' prefix, conforming to the new convention previously mentioned.[which?]

text: Visual Basic 6 did not provide common operator shortcuts. The following are equivalent:

text: Visual Basic 6:

text: VB.NET:

text: Comparison with C#[edit]

text: C# and Visual Basic .NET are Microsoft's first languages made to program on the .NET Framework (later adding F# and more and others have also added languages). Though C# and VB.NET are syntactically different, that is where the differences mostly end. Microsoft developed both of these languages to be part of the same .NET Framework development platform. They are both developed, managed, and supported by the same language development team at Microsoft.[8] They compile to the same intermediate language (IL), which runs against the same .NET Framework runtime libraries.[9] Although there are some differences in the programming constructs, their differences are primarily syntactic and, assuming one avoids the Visual Basic "Compatibility" libraries provided by Microsoft to aid conversion from Visual Basic 6, almost every command in VB has an equivalent command in C# and vice versa. Lastly, both languages reference the same Base Classes of the .NET Framework to extend their functionality. As a result, with few exceptions, a program written in either language can be run through a simple syntax converter to translate to the other. There are many open source and commercially available products for this task.

text: Examples[edit]

text: Hello World![edit]

text: Windows Form Application[edit]

text: Console Application[edit]

text: Speaking[edit]

text: Windows Form Application[edit]

text: Console Application[edit]

text: Version history[edit]

text: Succeeding the classic Visual Basic version 6.0, the first version of Visual Basic .NET debuted in 2002. As of 2017[update], eight versions of Visual Basic .NET are released.

text: 2002 (VB 7.0)[edit]

text: The first version, Visual Basic .NET, relies on .NET Framework 1.0. The most important feature is managed code, which contrasts with the classic Visual Basic.

text: 2003 (VB 7.1)[edit]

text: Visual Basic .NET 2003 was released with .NET Framework 1.1. New features included support for the .NET Compact Framework and a better VB upgrade wizard. Improvements were also made to the performance and reliability of .NET IDE (particularly the background compiler) and runtime. In addition, Visual Basic .NET 2003 was available in the Visual Studio.NET Academic Edition, distributed to a certain number of scholars[weasel words] from each country without cost.

text: 2005 (VB 8.0)[edit]

text: After Visual Basic .NET 2003, Microsoft dropped ".NET" from the name of the product, calling the next version Visual Basic 2005.

text: For this release, Microsoft added many features intended to reinforce Visual Basic .NET's focus as a rapid application development platform and further differentiate it from C#., including:

text:
Edit and Continue feature[further explanation needed]
Design-time expression evaluation[further explanation needed]
A pseudo-namespace called "My", which provides:[10][11]

Easy access to certain areas of the .NET Framework that otherwise require significant code to access like using

text: rather than

text:
Dynamically generated classes (e.g. My.Forms)

Improved VB-to-VB.NET converter[12]
A "using" keyword, simplifying the use of objects that require the Dispose pattern to free resources
Just My Code feature, which hides (steps over) boilerplate code written by the Visual Studio .NET IDE and system library code during debugging
Data Source binding, easing database client/server development

text: To bridge the gaps between itself and other .NET languages, this version added:

text:
Generics[13]
Partial classes, a method of defining some parts of a class in one file and then adding more definitions later; particularly useful for integrating user code with auto-generated code
Operator overloading and nullable types[14]
Support for unsigned integer data types commonly used in other languages

text: Visual Basic 2005 introduced the IsNot operator that makes 'If X IsNot Y' equivalent to 'If Not X Is Y'. It gained notoriety[15] when it was found to be the subject of a Microsoft patent application.[16][17]

text: 2008 (VB 9.0)[edit]

text: Visual Basic 9.0 was released along with .NET Framework 3.5 on 19 November 2007.

text: For this release, Microsoft added many features, including:

text:
A true conditional operator, "If(condition as boolean, truepart, falsepart)", to replace the "IIf" function.
Anonymous types
Support for LINQ
Lambda expressions
XML Literals
Type Inference
Extension methods

text: 2010 (VB 10.0)[edit]

text: In April 2010, Microsoft released Visual Basic 2010. Microsoft had planned to use Dynamic Language Runtime (DLR) for that release[18] but shifted to a co-evolution strategy between Visual Basic and sister language C# to bring both languages into closer parity with one another. Visual Basic's innate ability to interact dynamically with CLR and COM objects has been enhanced to work with dynamic languages built on the DLR such as IronPython and IronRuby.[19] The Visual Basic compiler was improved to infer line continuation in a set of common contexts, in many cases removing the need for the "_" line continuation character. Also, existing support of inline Functions was complemented with support for inline Subs as well as multi-line versions of both Sub and Function lambdas.[20]

text: 2012 (VB 11.0)[edit]

text: Visual Basic 2012 was released along .NET Framework 4.5. Major features introduced in this version include:[further explanation needed]

text:
Asynchronous programming with "async" and "await" statements
Iterators
Call hierarchy
Caller information
"Global" keyword in "namespace" statements

text: 2015 (VB 14.0)[edit]

text: Visual Basic 2015 (code named VB "14.0") has been released with Visual Studio 2015. Language features include a new "?." operator to perform inline null checks, and a new string interpolation feature is included to format strings inline.[21]

text: 2017 (VB 15.0)[edit]

text: Visual Basic 2017 (code named VB "15.0") has been released with Visual Studio 2017. Extends support for new Visual Basic 15 language features, and introduces new refactorings that allow organizing source code with one action.[22]

text: Cross-platform and open-source development[edit]

text: The creation of open-source tools for VB.NET development has been slow compared to C#, although the Mono development platform provides an implementation of VB.NET-specific libraries and a VB.NET 8.0 compatible compiler written in VB.NET,[23] as well as standard framework libraries such as Windows Forms GUI library.

text: SharpDevelop and MonoDevelop are open-source alternative IDEs.


document_title: United States at the FIFA World Cup

question_text: when was the last time us didn't make the world cup

question_tokens: when was the last time us did n 't make the world cup

root

text: United States at the FIFA World Cup

text: Record at the FIFA World Cup[edit]

text:
Year
Host
Round
Position
GP
W
D*
L
GF
GA

1930

Semi-finals
3rd
3
2
0
1
7
6

1934

Round of 16
16th
1
0
0
1
1
7

1938

Withdrew

1950

Group stage
10th
3
1
0
2
4
8

1954

Did not qualify

1958

1962

1966

1970

1974

1978

1982

1986

1990

Group stage
23rd
3
0
0
3
2
8

1994

Round of 16
14th
4
1
1
2
3
4

1998

Group stage
32nd
3
0
0
3
1
5

2002

Quarter-finals
8th
5
2
1
2
7
7

2006

Group stage
25th
3
0
1
2
2
6

2010

Round of 16
12th
4
1
2
1
5
5

2014

Round of 16
15th
4
1
1
2
5
6

2018

Did not qualify

2022

To be determined

2026

Qualified as one of the Host Nations

Total
10/21
-
33
8
6
19
37
62

tag: table

text:
showUnited States' World Cup record

First Match

 United States 3–0 Belgium  (13 July 1930; Montevideo, Uruguay)

Biggest Win

 United States 3–0 Belgium  (13 July 1930; Montevideo, Uruguay) United States 3–0 Paraguay  (17 July 1930; Montevideo, Uruguay)

Biggest Defeat

 Italy 7–1 United States  (27 May 1934; Rome, Italy)

Best Result

Third place in 1930

Worst Result

Group Stage in 1934, 1950, 1990, 1998 and 2006

text: By Match[edit]

text:
World Cup

Round

Opponent

Score

Result

Venue

Scorers

1930
Group stage
 Belgium
3–0
W
Montevideo
B. McGhee, T. Florie, B. Patenaude

 Paraguay
3–0
W
Montevideo
B. Patenaude (3)

Semi-finals
 Argentina
1–6
L
Montevideo
J. Brown

1934
Round of 16
 Italy
1–7
L
Rome
A. Donelli

1950
Group stage
 Spain
1–3
L
Curitiba
G. Pariani

 England
1–0
W
Belo Horizonte
J. Gaetjens

 Chile
2–5
L
Recife
F. Wallace, J. Maca

1990
Group stage
 Czechoslovakia
1–5
L
Florence
P. Caligiuri

 Italy
0–1
L
Rome
&—

 Austria
1–2
L
Florence
B. Murray

1994
Group stage
  Switzerland
1–1
D
Pontiac
E. Wynalda

 Colombia
2–1
W
Pasadena
A. Escobar (o.g.), E. Stewart

 Romania
0–1
L
Pasadena
&—

Round of 16
 Brazil
0–1
L
Stanford
&—

1998
Group stage
 Germany
0–2
L
Paris
&—

 Iran
1–2
L
Lyon
B. McBride

 FR Yugoslavia
0–1
L
Nantes
&—

2002
Group stage
 Portugal
3–2
W
Suwon
J. O'Brien, J. Costa (o.g.), B. McBride

 South Korea
1–1
D
Daegu
C. Mathis

 Poland
1–3
L
Daejeon
L. Donovan

Round of 16
 Mexico
2–0
W
Jeonju
B. McBride, L. Donovan

Quarter-finals
 Germany
0–1
L
Ulsan
&—

2006
Group stage
 Czech Republic
0–3
L
Gelsenkirchen
&—

 Italy
1–1
D
Kaiserslautern
C. Zaccardo (o.g.)

 Ghana
1–2
L
Nuremberg
C. Dempsey

2010
Group stage
 England
1–1
D
Rustenburg
C. Dempsey

 Slovenia
2–2
D
Johannesburg
L. Donovan, M. Bradley

 Algeria
1–0
W
Pretoria
L. Donovan

Round of 16
 Ghana
1–2 (a.e.t.)
L
Rustenburg
L. Donovan

2014
Group stage
 Ghana
2–1
W
Natal
C. Dempsey, J. Brooks

 Portugal
2–2
D
Manaus
J. Jones, C. Dempsey

 Germany
0–1
L
Recife
&—

Round of 16
 Belgium
1–2 (a.e.t.)
L
Salvador
J. Green

text: Record by Opponent[edit]

text:
FIFA World Cup matches (by team)

Opponent

Wins

Draws

Losses

Total

Goals Scored

Goals Conceded

 Algeria
1
0
0
1
1
0

 Argentina
0
0
1
1
1
6

 Austria
0
0
1
1
1
2

 Belgium
1
0
1
2
4
2

 Brazil
0
0
1
1
0
1

 Chile
0
0
1
1
2
5

 Colombia
1
0
0
1
2
1

 Czech Republic
0
0
1
1
0
3

 Czechoslovakia
0
0
1
1
1
5

 England
1
1
0
2
2
1

 FR Yugoslavia
0
0
1
1
0
1

 Germany
0
0
3
3
0
4

 Ghana
1
0
2
3
4
5

 Iran
0
0
1
1
1
2

 Italy
0
1
2
3
2
9

 Mexico
1
0
0
1
2
0

 Paraguay
1
0
0
1
3
0

 Poland
0
0
1
1
1
3

 Portugal
1
1
0
2
5
4

 Romania
0
0
1
1
0
1

 Slovenia
0
1
0
1
2
2

 South Korea
0
1
0
1
1
1

 Spain
0
0
1
1
1
3

  Switzerland
0
1
0
1
1
1

text: Individual tournament results[edit]

text: Uruguay 1930 FIFA World Cup[edit]

text:
showvteUnited States squad – 1930 FIFA World Cup third place
MF Auld
FW Bookie
MF Brown
GK Douglas
FW Florie (c)
DF Gallagher
DF Gentle
MF Gonsalves
FW McGhee
DF Moorhouse
MF Oliver
FW Patenaude
MF Slone
DF Tracey
DF Vaughn
DF Wood
Coach: Millar

text: Group 4 final standings[edit]

text:
Team

Pld

W

D

L

GF

GA

GD

Pts

 United States

2
2
0
0
6
0
+6
4

 Paraguay

2
1
0
1
1
3
−2
2

 Belgium

2
0
0
2
0
4
−4
0

text: Games[edit]

text: All times local (UYT)

tag: p

text:
United States

3–0

 Belgium

Report

text:
United States

3–0

 Paraguay

Report

text:
Argentina

6–1

 United States

Report

text: Italy 1934 FIFA World Cup[edit]

text:
showvteUnited States squad – 1934 FIFA World Cup
MF Amrhein
DF Czerkiewicz
FW Dick
FW Donelli
MF Fiedler
MF Florie
MF Gallagher
MF Gonsalves
DF Harker
GK Hjulian
MF Lehman
MF Lynch
DF Martinelli
FW McLean
DF Moorhouse
FW Nilsen
MF Pietras
DF Rapp
FW Ryan
Coach: Gould

text: Game[edit]

text:
Italy

7–1

 United States

Report

text: Brazil 1950 FIFA World Cup[edit]

text:
showvteUnited States squad – 1950 FIFA World Cup
GK Borghi
GK Gard
DF Annis
DF Coombes
DF Keough
DF Maca
MF Bahr
MF Colombo
MF McIlvenny
FW Craddock
FW DiOrio
FW Gaetjens
FW Pariani
FW E. Souza
FW J. Souza
FW Wallace
FW Wolanin
Coach: Jeffrey

text: Group 2 final standings[edit]

text:
Team

Pld

W

D

L

GF

GA

Pts

 Spain

3
3
0
0
6
1
6

 England

3
1
0
2
2
2
2

 Chile

3
1
0
2
5
6
2

 United States

3
1
0
2
4
8
2

text: Games[edit]

text: All times local BRT (UTC-03)

text:
Spain

3–1

 United States

Report

text:
United States

1–0

 England

Report

text:
Chile

5–2

 United States

Report

text: Italy 1990 FIFA World Cup[edit]

text:
showvteUnited States squad  –  1990 FIFA World Cup
1 Meola
2 Trittschuh
3 Doyle
4 Banks
5 Windischmann (c)
6 Harkes
7 Ramos
8 Bliss
9 Sullivan
10 Vermes
11 Wynalda
12 Krumpe
13 Eichmann
14 Stollmeyer
15 Armstrong
16 Murray
17 Balboa
18 Keller
19 Henderson
20 Caligiuri
21 Covone
22 Vanole
Coach: Gansler

text: Group A final standings[edit]

text:
Team

Pld

W

D

L

GF

GA

GD

Pts

 Italy

3
3
0
0
4
0
+4
6

 Czechoslovakia

3
2
0
1
6
3
+3
4

 Austria

3
1
0
2
2
3
−1
2

 United States

3
0
0
3
2
8
−6
0

text: Games[edit]

text: All times local (CEST/UTC+2)

text:
United States

1–5

 Czechoslovakia

Report

text:
Italy

1–0

 United States

Report

text:
Austria

2–1

 United States

Report

text: United States 1994 FIFA World Cup[edit]

text:
showvteUnited States squad  –  1994 FIFA World Cup
1 Meola (c)
2 Lapper
3 Burns
4 Kooiman
5 Dooley
6 Harkes
7 Pérez
8 Stewart
9 Ramos
10 Wegerle
11 Wynalda
12 Sommer
13 Jones
14 Klopas
15 Moore
16 Sorber
17 Balboa
18 Friedel
19 Reyna
20 Caligiuri
21 Clavijo
22 Lalas
Coach: Milutinović

text: Group A final standings[edit]

text:
Pos

Team[ vte ]

Pld

W

D

L

GF

GA

GD

Pts

Qualification

1

 Romania

3

2

0

1

5

5

0

6

Advance to knockout stage

2

  Switzerland

3

1

1

1

5

4

+1

4

3

 United States (H)

3

1

1

1

3

3

0

4

4

 Colombia

3

1

0

2

4

5

−1

3

text: Ranking of third-placed teams[edit]

text:
Pos

Grp

Team[ vte ]

Pld

W

D

L

GF

GA

GD

Pts

Qualification

1

D

 Argentina

3

2

0

1

6

3

+3

6

Advance to knockout stage

2

F

 Belgium

3

2

0

1

2

1

+1

6

3

A

 United States

3

1

1

1

3

3

0

4

4

E

 Italy

3

1

1

1

2

2

0

4

5

B

 Russia

3

1

0

2

7

6

+1

3

6

C

 South Korea

3

0

2

1

4

5

−1

2

text: Games[edit]

text:
United States

1–1

  Switzerland

Report

text:
United States

2–1

 Colombia

Report

text:
United States

0–1

 Romania

Report

text:
Brazil

1–0

 United States

Report

text: France 1998 FIFA World Cup[edit]

text:
showvteUnited States squad  –  1998 FIFA World Cup
1 Friedel
2 Hejduk
3 Pope
4 Burns
5 Dooley (c)
6 Regis
7 Wegerle
8 Stewart
9 Moore
10 Ramos
11 Wynalda
12 Agoos
13 Jones
14 Preki
15 Deering
16 Sommer
17 Balboa
18 Keller
19 Maisonneuve
20 McBride
21 Reyna
22 Lalas
Coach: Sampson

text: Group F final standings[edit]

text:
Pos

Team[ vte ]

Pld

W

D

L

GF

GA

GD

Pts

Qualification

1

 Germany

3

2

1

0

6

2

+4

7

Advance to knockout stage

2

 FR Yugoslavia

3

2

1

0

4

2

+2

7

3

 Iran

3

1

0

2

2

4

−2

3

4

 United States

3

0

0

3

1

5

−4

0

text: Games[edit]

text: All times local (CEST/UTC+2)

text:
Germany

2–0

 United States

Report

text:
United States

1–2

 Iran

Report

text:
United States

0–1

 FR Yugoslavia

Report

text: South Korea-Japan 2002 FIFA World Cup[edit]

text:
showvteUnited States squad  –  2002 FIFA World Cup
1 Friedel
2 Hejduk
3 Berhalter
4 Mastroeni
5 O'Brien
6 Regis
7 Lewis
8 Stewart
9 Moore
10 Reyna (c)
11 Mathis
12 Agoos
13 Jones
14 Cherundolo
15 Wolff
16 Llamosa
17 Beasley
18 Keller
19 Meola
20 McBride
21 Donovan
22 Sanneh
23 Pope
Coach: Arena

text: Group D final standings[edit]

text:
Pos

Team[ vte ]

Pld

W

D

L

GF

GA

GD

Pts

Qualification

1

 South Korea (H)

3

2

1

0

4

1

+3

7

Advance to knockout stage

2

 United States

3

1

1

1

5

6

−1

4

3

 Portugal

3

1

0

2

6

4

+2

3

4

 Poland

3

1

0

2

3

7

−4

3

text: Games[edit]

text: All times local (UTC+9)

text:
United States

3–2

 Portugal

Report

text:
South Korea

1–1

 United States

Report

text:
Poland

3–1

 United States

Report

text:
Mexico

0–2

 United States

Report

text:
Germany

1–0

 United States

Report

text: Germany 2006 FIFA World Cup[edit]

text:
showvteUnited States squad  –  2006 FIFA World Cup
1 Howard
2 Albright
3 Bocanegra
4 Mastroeni
5 O'Brien
6 Cherundolo
7 Lewis
8 Dempsey
9 Johnson
10 Reyna (c)
11 Ching
12 Berhalter
13 Conrad
14 Olsen
15 Convey
16 Wolff
17 Beasley
18 Keller
19 Hahnemann
20 McBride
21 Donovan
22 Onyewu
23 Pope
Coach: Arena

text: Group E final standings[edit]

text:
Pos

Team[ vte ]

Pld

W

D

L

GF

GA

GD

Pts

Qualification

1

 Italy

3

2

1

0

5

1

+4

7

Advance to knockout stage

2

 Ghana

3

2

0

1

4

3

+1

6

3

 Czech Republic

3

1

0

2

3

4

−1

3

4

 United States

3

0

1

2

2

6

−4

1

text: Games[edit]

text: All times local (CEST/UTC+2)

text:
United States

0–3

 Czech Republic

Report

text:
Italy

1–1

 United States

Report

text:
Ghana

2–1

 United States

Report

text: South Africa 2010 FIFA World Cup[edit]

text:
showvteUnited States squad  –  2010 FIFA World Cup
1 Howard
2 Spector
3 Bocanegra (c)
4 M. Bradley
5 Onyewu
6 Cherundolo
7 Beasley
8 Dempsey
9 Gomez
10 Donovan
11 Holden
12 Bornstein
13 Clark
14 Buddle
15 DeMerit
16 Torres
17 Altidore
18 Guzan
19 Edu
20 Findley
21 Goodson
22 Feilhaber
23 Hahnemann
Coach: B. Bradley

text: Group C final standings[edit]

text:
Pos

Team[ vte ]

Pld

W

D

L

GF

GA

GD

Pts

Qualification

1

 United States

3

1

2

0

4

3

+1

5

Advance to knockout stage

2

 England

3

1

2

0

2

1

+1

5

3

 Slovenia

3

1

1

1

3

3

0

4

4

 Algeria

3

0

1

2

0

2

−2

1

text: Games[edit]

text: All times local (UTC+02)

text:
England

1–1

 United States

Report

text:
Slovenia

2–2

 United States

Report

text:
United States

1–0

 Algeria

Report

text:
United States

1–2 (a.e.t.)

 Ghana

Report

text: Brazil 2014 FIFA World Cup[edit]

text:
showvteUnited States squad  –  2014 FIFA World Cup
1 Howard
2 Yedlin
3 Gonzalez
4 Bradley
5 Besler
6 Brooks
7 Beasley
8 Dempsey (c)
9 Jóhannsson
10 Diskerud
11 Bedoya
12 Guzan
13 Jones
14 Davis
15 Beckerman
16 Green
17 Altidore
18 Wondolowski
19 Zusi
20 Cameron
21 Chandler
22 Rimando
23 Johnson
Coach: Klinsmann

text: Group G final standings[edit]

text:
Pos

Team[ vte ]

Pld

W

D

L

GF

GA

GD

Pts

Qualification

1

 Germany

3

2

1

0

7

2

+5

7

Advance to knockout stage

2

 United States

3

1

1

1

4

4

0

4

3

 Portugal

3

1

1

1

4

7

−3

4

4

 Ghana

3

0

1

2

4

6

−2

1

text: Games[edit]

text:
Ghana

1–2

 United States

Report

text:
United States

2–2

 Portugal

Report

text:
United States

0–1

 Germany

Report

text:
Belgium

2–1 (a.e.t.)

 United States

Report

text: Record players[edit]

text:
No.

Name

Matches

World Cups

1
Landon Donovan
12
2002, 2006 and 2010

2

Cobi Jones
11
1994, 1998 and 2002

Earnie Stewart
11
1994, 1998 and 2002

DaMarcus Beasley
11
2002, 2006, 2010 and 2014

5

Brian McBride
10
1998, 2002 and 2006

Claudio Reyna
10
1998, 2002 and 2006

Clint Dempsey
10
2006, 2010 and 2014

8

Tab Ramos
9
1990, 1994 and 1998

Eddie Pope
9
1998, 2002 and 2006

10

Marcelo Balboa
8
1990, 1994 and 1998

Eric Wynalda
8
1990, 1994 and 1998

Michael Bradley
8
2010 and 2014

Tim Howard
8
2010 and 2014

text: Top Goalscorers[edit]

text:
Player

Goals

1930

1934

1950

1990

1994

1998

2002

2006

2010

2014

Landon Donovan

5

2

3

Bert Patenaude

4

4

Clint Dempsey

4

1
1
2

Brian McBride

3

1
2

Michael Bradley

1

1

Jim Brown

1

1

Paul Caligiuri

1

1

Aldo Donelli

1

1

Tom Florie

1

1

Joe Gaetjens

1

1

Julian Green

1

1

Joe Maca

1

1

Clint Mathis

1

1

Bart McGhee

1

1

Bruce Murray

1

1

John O'Brien

1

1

Gino Pariani

1

1

Earnie Stewart

1

1

Frank Wallace

1

1

Eric Wynalda

1

1

John Brooks

1

1

Jermaine Jones

1

1

Own goals

3

1

1
1

Total

37

7
1
4
2
3
1
7
2
5
5

text: Jeff Agoos (scored for Portugal in 2002)

tag: ul


document_title: Tincture of iodine

question_text: what is the solvent in tincture of iodine

text: Tincture of iodine

text: USP formulas[edit]

text: USP Tincture of Iodine is defined in the U.S. National Formulary (NF) as containing in each 100 mL, 1.8 to 2.2 grams of elemental iodine, and 2.1 to 2.6 grams of sodium iodide. Alcohol is 50 mL and the balance is purified water. This "2% free iodine" solution provides about one mg of free iodine per drop.

text: USP Strong Iodine Tincture is defined in the NF as containing in each 100 mL, 6.8 to 7.5 gram of iodine, and 4.7 to 5.5 gram of potassium iodide. Purified water is 50 mL and the balance is alcohol. This 7% tincture solution is about 3.5 times more concentrated than USP 2% tincture.[citation needed]

text: As in the case of Lugol's iodine, the role of iodide in the solution is to increase the solubility of the elemental iodine, by turning it to the soluble triiodide anion I3−. However, since iodine has moderate solubility in ethanol, it is also assisted by this solvent directly. Lugol's iodine, by contrast, has no alcohol, and has twice the mass of potassium iodide as of elemental iodine. Alcohol content in the tincture of iodine can be determined by the methods of Alcock, Roscoe - Schorlemmer and Thurston - Thurston.[5]

text: Usage[edit]

text: As both USP solutions contain elemental iodine, which is moderately toxic when ingested in amounts larger than those required to disinfect water, tincture of iodine is sold labelled “for external use only,” and used primarily as a disinfectant.

text: Tincture of iodine is often found in emergency survival kits, used both to disinfect wounds and to sanitize surface water for drinking. When an alcohol solution is not desirable for this purpose, the alcohol-free Lugol's iodine, an aqueous solution of iodine in potassium iodide solution, or else povidone-iodine (brand names Wokadine, Betadine), a PVPI solution, can be used.

text: Small amounts may be added to suspect drinking water as a disinfectant (typically 5 mg free iodine per liter, or 5 drops of 2% tincture). Though this treatment is effective against bacteria and virus, it does not protect against protozoan parasites such as Cryptosporidium and Giardia.[6]

text: Iodine solution is used to sanitize the surface of fruit and vegetables for bacteria and virus. The common concentration for sanitization is 25 ppm idophor for 1 minute.[7] However, the effectiveness depends on whether the solution penetrates into rifts, and whether dirt is effectively removed at first. But, oocytes of protozoan parasites will not be killed, and it is also doubtful that bacterial spores are killed. Iodine solutions should not be considered able to sanitize or disinfect salad, fruit or vegetables that are contaminated by feces. Thus, it should not be considered safe to eat raw fruit, salads and vegetables which are sanitized with iodine, if they could be contaminated by feces.[8]

text: Iodine tincture is not a recommended  source of solely-nutritional iodine. Nutritional iodine is better supplied in the form of the less toxic iodide (see SSKI) or iodate salts, which the body can easily convert to thyroid hormone.

text: Nevertheless, the iodide in tincture of iodine used as a water disinfectant does supply more than adequate nutritional iodine, perhaps 30 or more times the recommended daily allowance per liter or quart. Application of tincture or Lugol's to the skin also results in absorption and bioavailability of some moderate fraction of the iodine.


document_title: ASCII

question_text: how many characters are specified in ascii scheme

text: ASCII

text: Overview[edit]

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

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

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

text: History[edit]

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

text: With the other special characters and control codes filled in, ASCII was published as ASA X3.4-1963,[4][10] leaving 28 code positions without any assigned meaning, reserved for future standardization, and one unassigned control code.[1]:66, 245 There was some debate at the time whether there should be more control characters rather than the lowercase alphabet.[1]:435 The indecision did not last long: during May 1963 the CCITT Working Party on the New Telegraph Alphabet proposed to assign lowercase characters to sticks[a][11] 6 and 7,[12] and International Organization for Standardization TC 97 SC 2 voted during October to incorporate the change into its draft standard.[13] The X3.2.4 task group voted its approval for the change to ASCII at its May 1963 meeting.[14] Locating the lowercase letters in sticks[a][11] 6 and 7 caused the characters to differ in bit pattern from the upper case by a single bit, which simplified case-insensitive character matching and the construction of keyboards and printers.

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

text: Revisions of the ASCII standard:

text:
ASA X3.4-1963[1][4][16][17]
ASA X3.4-1965 (approved, but not published, nevertheless used by IBM 2260 & 2265 Display Stations and IBM 2848 Display Control)[1]:423, 425–428, 435–439[18][16][17]
USAS X3.4-1967[1][5][17]
USAS X3.4-1968[1][17]
ANSI X3.4-1977[17]
ANSI X3.4-1986[7][17]
ANSI X3.4-1986 (R1992)
ANSI X3.4-1986 (R1997)
ANSI INCITS 4-1986 (R2002)[19]
ANSI INCITS 4-1986 (R2007)[20]
ANSI INCITS 4-1986 (R2012)

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

text: Design considerations[edit]

text: Bit width[edit]

text: The X3.2 subcommittee designed ASCII based on the earlier teleprinter encoding systems. Like other character encodings, ASCII specifies a correspondence between digital bit patterns and character symbols (i.e. graphemes and control characters). This allows digital devices to communicate with each other and to process, store, and communicate character-oriented information such as written language. Before ASCII was developed, the encodings in use included 26 alphabetic characters, 10 numerical digits, and from 11 to 25 special graphic symbols. To include all these, and control characters compatible with the Comité Consultatif International Téléphonique et Télégraphique (CCITT) International Telegraph Alphabet No. 2 (ITA2) standard of 1924,[22][23] FIELDATA (1956[citation needed]), and early EBCDIC (1963), more than 64 codes were required for ASCII.

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

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

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

text: Internal organization[edit]

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

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

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

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

text: Character order[edit]

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

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

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

text: Character groups[edit]

text: Control characters[edit]

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

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

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

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

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

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

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

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

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

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

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

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

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

text:
Binary
Oct
Dec
Hex
Abbreviation
[b]
[c]
[d]
Name ('67)

'63
'65
'67

000 0000
000
0
00

NULL
NUL
␀
^@
\0
Null

000 0001
001
1
01

SOM
SOH
␁
^A

Start of Heading

000 0010
002
2
02

EOA
STX
␂
^B

Start of Text

000 0011
003
3
03

EOM
ETX
␃
^C

End of Text

000 0100
004
4
04

EOT
␄
^D

End of Transmission

000 0101
005
5
05

WRU
ENQ
␅
^E

Enquiry

000 0110
006
6
06

RU
ACK
␆
^F

Acknowledgement

000 0111
007
7
07

BELL
BEL
␇
^G
\a
Bell

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
␌
^L
\f
Form Feed

000 1101
015
13
0D

CR
␍
^M
\r
Carriage Return[h]

000 1110
016
14
0E

SO
␎
^N

Shift Out

000 1111
017
15
0F

SI
␏
^O

Shift In

001 0000
020
16
10

DC0
DLE
␐
^P

Data Link Escape

001 0001
021
17
11

DC1
␑
^Q

Device Control 1 (often XON)

001 0010
022
18
12

DC2
␒
^R

Device Control 2

001 0011
023
19
13

DC3
␓
^S

Device Control 3 (often XOFF)

001 0100
024
20
14

DC4
␔
^T

Device Control 4

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
␗
^W

End of Transmission Block

001 1000
030
24
18

S0
CAN
␘
^X

Cancel

001 1001
031
25
19

S1
EM
␙
^Y

End 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
30
1E

S6
RS
␞
^^[k]

Record Separator

001 1111
037
31
1F

S7
US
␟
^_

Unit Separator

111 1111
177
127
7F

DEL
␡
^?

Delete[l][f]

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

text: Printable characters[edit]

text: Codes 20hex to 7Ehex, known as the printable characters, represent letters, digits, punctuation marks, and a few miscellaneous symbols. There are 95 printable characters in total.[m]

text: Code 20hex, the "space" character, denotes the space between words, as produced by the space bar of a keyboard. Since the space character is considered an invisible graphic (rather than a control character)[1]:223[41] it is listed in the table below instead of in the previous section.

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

text:
Binary
Oct
Dec
Hex
Glyph

’63
’65
’67

010 0000
040
32
20
 space

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 1000
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
2D
-

010 1110
056
46
2E
.

010 1111
057
47
2F
/

011 0000
060
48
30
0

011 0001
061
49
31
1

011 0010
062
50
32
2

011 0011
063
51
33
3

011 0100
064
52
34
4

011 0101
065
53
35
5

011 0110
066
54
36
6

011 0111
067
55
37
7

011 1000
070
56
38
8

011 1001
071
57
39
9

011 1010
072
58
3A
:

011 1011
073
59
3B
;

011 1100
074
60
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
K

100 1100
114
76
4C
L

100 1101
115
77
4D
M

100 1110
116
78
4E
N

100 1111
117
79
4F
O

101 0000
120
80
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
X

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
60

@
`

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 1000
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

n

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

s

111 0100
164
116
74

t

111 0101
165
117
75

u

111 0110
166
118
76

v

111 0111
167
119
77

w

111 1000
170
120
78

x

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
|
~

text: Character set[edit]

text: Letter   Number   Punctuation   Symbol   Other   undefined

text:
ASCII (1977/1986)

_0

_1

_2

_3

_4

_5

_6

_7

_8

_9

_A

_B

_C

_D

_E

_F

0_

NUL00000

SOH00011

STX00022

ETX00033

EOT00044

ENQ00055

ACK00066

BEL00077

BS00088

HT00099

LF000A10

VT000B11

FF000C12

CR000D13

SO000E14

SI000F15

1_

DLE001016

DC1001117

DC2001218

DC3001319

DC4001420

NAK001521

SYN001622

ETB001723

CAN001824

EM001925

SUB001A26

ESC001B27

FS001C28

GS001D29

RS001E30

US001F31

2_

SP002032

!002133

"002234

#002335

$002436

%002537

&002638

'002739

(002840

)002941

*002A42

+002B43

,002C44

-002D45

.002E46

/002F47

3_

0003048

1003149

2003250

3003351

4003452

5003553

6003654

7003755

8003856

9003957

:003A58

;003B59

<003C60

=003D61

>003E62

?003F63

4_

@004064

A004165

B004266

C004367

D004468

E004569

F004670

G004771

H004872

I004973

J004A74

K004B75

L004C76

M004D77

N004E78

O004F79

5_

P005080

Q005181

R005282

S005383

T005484

U005585

V005686

W005787

X005888

Y005989

Z005A90

[005B91

\005C92

]005D93

^005E94

_005F95

6_

`006096

a006197

b006298

c006399

d0064100

e0065101

f0066102

g0067103

h0068104

i0069105

j006A106

k006B107

l006C108

m006D109

n006E110

o006F111

7_

p0070112

q0071113

r0072114

s0073115

t0074116

u0075117

v0076118

w0077119

x0078120

y0079121

z007A122

{007B123

|007C124

}007D125

~007E126

DEL007F127

text: Use[edit]

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

text: On March 11, 1968, U.S. President Lyndon B. Johnson mandated that all computers purchased by the United States federal government support ASCII, stating:[45][46][47]

text:
I have also approved recommendations of the Secretary of Commerce regarding standards for recording the Standard Code for Information Interchange on magnetic tapes and paper tapes when they are used in computer operations.
All computers and related equipment configurations brought into the Federal Government inventory on and after July 1, 1969, must have the capability to use the Standard Code for Information Interchange and the formats prescribed by the magnetic tape and paper tape standards when these media are used.

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

text: Variants and derivations[edit]

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

text: 7-bit codes[edit]

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

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

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

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

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

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

text: instead of

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

text: 8-bit codes[edit]

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

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

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

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

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

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

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

text: Unicode[edit]

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

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