# data[].attributes.body
1. Utilizarea conceptelor fundamentale ale informaticii pentru reprezentarea și procesarea informației<br>2. Aplicarea algoritmilor pentru rezolvarea unor probleme din diferite domenii

# data[].attributes.body
La sfârșitul lecției, elevii vor fi capabili să identifice codul ASCII pentru cel puțin 10 caractere alfabetice și numerice într-un test practic de 5 minute.

# data[].attributes.body
Elevii vor demonstra capacitatea de a converti corect cel puțin 5 caractere din text în coduri ASCII și invers, folosind tabela de conversie, într-un exercițiu de grup de 10 minute.

# data[].attributes.body
La sfârșitul lecției, elevii vor explica în propriile cuvinte importanța codurilor ASCII în comunicarea digitală, redactând un răspuns de minimum 3 propoziții într-un bilet de ieșire.

# data[].attributes.headline
1. Provocarea inițială - Intrebarea esențială

# data[].attributes.subject
1. Provocarea inițială - Intrebarea esențială

# data[].attributes.body
Cum reușesc computerele să înțeleagă și să afișeze literele și cifrele pe care le vedem pe ecran? Discutați în perechi 3 minute despre această întrebare.

# data[].attributes.attachment_link.title
Computer Science for Everyone - 12 - What is ASCII?

# data[].attributes.headline
2. Atenția și motivația - Experimentul cu mesajul secret

# data[].attributes.subject
2. Atenția și motivația - Experimentul cu mesajul secret

# data[].attributes.body
Activitate: Decodificați mesajul: 72 101 108 108 111! Ce observați? Folosiți Padlet pentru a împărtăși teoriile voastre despre cum funcționează acest cod.

# data[].attributes.body
Astăzi vom învăța:
- Ce sunt codurile ASCII
- Cum se convertesc caracterele în coduri ASCII și invers
- De ce sunt importante în informatică
- Aplicații practice ale codurilor ASCII

# data[].attributes.headline
4. Instruire directă - Istoria și principiile ASCII

# data[].attributes.subject
4. Instruire directă - Istoria și principiile ASCII

# data[].attributes.body
ASCII (American Standard Code for Information Interchange) a fost dezvoltat în anii 1960. Folosește 7 biți pentru a reprezenta 128 de caractere diferite: litere mari și mici, cifre, simboluri și caractere de control. Fiecare caracter are un număr unic între 0-127.

# data[].attributes.headline
5. Demonstrație - Tabela ASCII în acțiune

# data[].attributes.subject
5. Demonstrație - Tabela ASCII în acțiune

# data[].attributes.body
Demonstrație practică: Vom vedea cum funcționează conversia. De exemplu: A=65, a=97, 0=48, spațiu=32. Observați diferența de 32 între literele mari și mici.

# data[].attributes.body
Activitate în perechi: Folosind tabela ASCII, convertiți următoarele:
- Numele vostru în coduri ASCII
- Codul 80 65 68 76 69 84 în text
Lucrați împreună și verificați-vă reciproc răspunsurile.

# data[].attributes.headline
7. Practică independentă - Exercițiul individual

# data[].attributes.subject
7. Practică independentă - Exercițiul individual

# data[].attributes.body
Exercițiu individual (10 minute):
1. Scrieți codul ASCII pentru cuvântul 'INFO'
2. Decodificați: 67 79 68
3. Calculați diferența dintre 'M' și 'm'
4. Găsiți toate cifrele ASCII (0-9)

# data[].attributes.headline
8. Diferențiere - Activități suplimentare

# data[].attributes.subject
8. Diferențiere - Activități suplimentare

# data[].attributes.body
Pentru remediere: Exerciții simple cu caractere de bază (A-Z, 0-9)<br>Pentru extindere: Creați un program simplu care convertește un text întreg în ASCII sau explorați ASCII extins (codurile 128-255)

# data[].attributes.body
Discutăm unde întâlnim ASCII în viața reală:
- Programare (tastatura, afișare text)
- Comunicații (email, mesaje)
- Stocarea datelor
- Protocoale de rețea

# data[].attributes.attachment_link.readable_text
MIME / IANA

us-ascii

Alias(es)

ISO-IR-006,[1] ANSI_X3.4-1968, ANSI_X3.4-1986, ISO_646.irv:1991, ISO646-US, us, IBM367, cp367[2]

Language(s)

English (made for; does not support all loanwords), Malay, Rotokas, Interlingua, Ido, and X-SAMPA

Classification
ISO/IEC 646 series

Extensions

Preceded by

ITA 2, FIELDATA

Succeeded by

ISO/IEC 8859, ISO/IEC 10646 ( Unicode)

ASCII ( ASS-kee), an acronym for American Standard Code for Information Interchange, is a character encoding standard for electronic communication. ASCII codes represent text in computers, telecommunications equipment, and other devices. Because of technical limitations of computer systems at the time it was invented, ASCII has just 128 code points, of which only 95 are printable characters, which severely limited its scope. Modern computer systems have evolved to use Unicode, which has millions of code points, but the first 128 of these are the same as the ASCII set.

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

ASCII is one of the IEEE milestones.

ASCII was developed in part from telegraph code. Its first commercial use was in the Teletype Model 33 and the Teletype Model 35 as a seven- bit teleprinter code promoted by Bell data services.[when? ] Work on the ASCII standard began in May 1961, 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, underwent a major revision during 1967, and experienced its most recent update during 1986. 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.

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

Originally based on the (modern) English alphabet, ASCII encodes 128 specified characters into seven-bit integers as shown by the ASCII chart in this article. 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 models; most of these are now obsolete, although a few are still commonly used, such as the carriage return, line feed, and tab codes.

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

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

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

With the other special characters and control codes filled in, ASCII was published as ASA X3.4-1963, leaving 28 code positions without any assigned meaning, reserved for future standardization, and one unassigned control code. There was some debate at the time whether there should be more control characters rather than the lowercase alphabet. 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 6 and 7, and International Organization for Standardization TC 97 SC 2 voted during October to incorporate the change into its draft standard. The X3.2.4 task group voted its approval for the change to ASCII at its May 1963 meeting. Locating the lowercase letters in sticks 6 and 7 caused the characters to differ in bit pattern from the upper case by a single bit, which simplified case-insensitive character matching and the construction of keyboards and printers.

The X3 committee made other changes, including other new characters (the brace and vertical bar characters), renaming some control characters (SOM became start of header (SOH)) and moving or removing others (RU was removed). ASCII was subsequently updated as USAS X3.4-1967, then USAS X3.4-1968, ANSI X3.4-1977, and finally, ANSI X3.4-1986.

Revisions of the ASCII standard:

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

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, FIELDATA (1956[citation needed ]), and early EBCDIC (1963), more than 64 codes were required for ASCII.

ITA2 was in turn based on Baudot code, the 5-bit telegraph code Émile Baudot invented in 1870 and patented in 1874.

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.: 215 §13.6, 236 §4

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.: 217 §c, 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.

Internal organization

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 (32 positions) were reserved for control characters.: 220, 236 8, 9)  The "space" character had to come before graphics to make sorting easier, so it became position 20; 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,: 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 41 to match the draft of the corresponding British standard. 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 (for example, 5 in encoded to 011 0101, where 5 is 0101 in binary).

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. Mechanical typewriters followed the de facto standard set by the Remington No. 2 (1878), the first typewriter with a shift key, and the shifted values of 23456789- were "#$%_&'() - early typewriters omitted 0 and 1, using O (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, positions 1-5, corresponding to the digits 1-5 in the adjacent stick. 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, differently from traditional mechanical typewriters.

Electric typewriters, notably the IBM Selectric (1961), used a somewhat different layout that has become de facto 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 :* ;+ -=.

Some then-common typewriter 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 40, right before the letter A.

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.

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

All uppercase come before lowercase letters; for example, "Z" precedes "a"

Digits and many punctuation marks come before letters

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

Character set

Early symbols assigned to the 32 control characters, space and delete characters. (ISO 2047, MIL-STD-188-100, 1972)

For example, character 0x0A 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. Except for the control characters that prescribe elementary line-oriented formatting, ASCII does not define any mechanism for describing the structure or appearance of text within a document. Other schemes, such as markup languages, address page and document layout and formatting.

The original ASCII standard used only short descriptive phrases for each control character. The ambiguity this 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 the standard is unclear about the meaning of "delete".

Probably the most influential single device affecting the interpretation of these characters was the Teletype Model 33 ASR, which was a printing terminal with an available paper tape reader/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.

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 so-called flow control technique became adopted by several early computer operating systems as a "handshaking" signal warning a sender to stop transmission because of impending buffer 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.

Delete vs backspace

The Teletype could not move its typehead backwards, so it did not have a key on its keyboard to send a BS (backspace). Instead, there was a key marked RUB OUT that sent code 127 (DEL). The purpose of this key was to erase mistakes in a manually-input paper tape: the operator had to push a 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. Teletypes were commonly used with the less-expensive computers from Digital Equipment Corporation (DEC); these systems had to use what keys were available, and thus the DEL character was assigned to erase the previous character. Because of this, DEC video terminals (by default) sent the DEL character for the key marked "Backspace" while the separate key marked "Delete" sent an escape sequence; many other competing terminals sent a BS character for the backspace key.

The early Unix tty drivers, unlike some modern implementations, allowed only one character to be set to erase the previous character in canonical input processing (where a very simple line editor is available); this could be set to BS or DEL, but not both, resulting in recurring situations of ambiguity where users had to decide depending on what terminal they were using ( shells that allow line editing, such as ksh, bash, and zsh, understand both). The assumption that no key sent a BS character allowed Ctrl+H to be used for other purposes, such as the "help" prefix command in GNU Emacs.

Many more of the control characters have been assigned meanings quite different from their original ones. The "escape" character (ESC, code 27), for example, was intended originally to allow sending of other control characters as literals instead of invoking their meaning, an "escape sequence". 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 interpretation has been co-opted and has eventually been changed.

In modern usage, an ESC sent to the terminal usually indicates the start of a command sequence, which can be used to address the cursor, scroll a region, set/query various terminal properties, and more. They are usually in the form of a so-called " ANSI escape code" (often starting with a " Control Sequence Introducer", "CSI", "ESC [") from ECMA-48 (1972) and its successors. Some escape sequences do not have introducers, like the VT100 full reset command "ESC c".

In contrast, an ESC read from the terminal is most often used as an out-of-band character used to terminate an operation or special mode, 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.

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 moves while the typebars that strike the ribbon remain stationary. The entire carriage had to be pushed (returned) to the right in order to position the paper for the next line.

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 "dumb terminals") came along, the convention was so well established that backward compatibility necessitated continuing to follow it. When Gary Kildall created CP/M, he was inspired by some of the command line interface conventions used in DEC's RT-11 operating system.

Until the introduction of PC DOS in 1981, IBM had no influence in this because their 1970s operating systems used EBCDIC encoding instead of ASCII, and they were oriented toward punch-card input and line printer output on which the concept of "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, and Windows in turn inherited it from MS-DOS.

Requiring two characters to mark the end of a line introduces unnecessary complexity and ambiguity as to how to interpret each character when encountered by itself. To simplify matters, plain text data streams, including files, on Multics used line feed (LF) alone as a line terminator. The tty driver would handle the LF to CRLF conversion on output so files can be directly printed to terminal, and NL (newline) is often used to refer to CRLF in UNIX documents. Unix and Unix-like systems, and Amiga systems, adopted this convention from Multics. On the other hand, the original Macintosh OS, Apple DOS, and ProDOS used carriage return (CR) alone as a line terminator; however, since Apple later replaced these obsolete operating systems with their Unix-based macOS (formerly named OS X) operating system, they now use line feed (LF) as well. The Radio Shack TRS-80 also used a lone CR to terminate lines.

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 which used EBCDIC rather than ASCII encoding. 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. 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. 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.

End of file/stream

The PDP-6 monitor, and its PDP-10 successor TOPS-10, 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. 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 character ( ETX), also known as control-C, was inappropriate for a variety of reasons, while using control-Z as the control character to end a file is analogous to the letter Z's position at the end of the alphabet, and serves as a very convenient mnemonic aid. A historically common and still prevalent convention uses the ETX character convention to interrupt and halt a program via an input data stream, usually from a keyboard.

The Unix terminal driver uses the end-of-transmission character ( EOT), also known as control-D, to indicate the end of a data stream.

In the C programming language, and in 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".

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

Codes 20 hex to 7E hex, known as the printable characters, represent letters, digits, punctuation marks, and a few miscellaneous symbols. There are 95 printable characters in total.

Code 20 hex, 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) it is listed in the table below instead of in the previous section.

Code 7F hex 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 (5E hex) and the left arrow instead of the underscore (5F hex).

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. 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". Because of his extensive work on ASCII, Bemer has been called "the father of ASCII".

On March 11, 1968, US President Lyndon B. Johnson mandated that all computers purchased by the United States Federal Government support ASCII, stating:

I have also approved recommendations of the Secretary of Commerce [ Luther H. Hodges] 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.

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.

Variants and derivations

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.

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

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 (£); e.g. with code page 1104. 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.

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

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

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.

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

instead of

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

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

In Europe, teletext character sets, which are variants of ASCII, are used for broadcast TV subtitles, defined by World System Teletext and broadcast using the DVB-TXT standard for embedding teletext into DVB transmissions. In the case that the subtitles were initially authored for teletext and converted, the derived subtitle formats are constrained to the same character sets.

For some countries, 8-bit extensions of ASCII were developed that included support for characters used in local languages; for example, ISCII for India and VISCII for Vietnam. Kaypro CP/M computers used the "upper" 128 characters for the Greek alphabet.[citation needed ]

Most ASCII extensions are based on ASCII-1967 (the current standard), but some extensions are instead based on the earlier ASCII-1963. For example, PETSCII, which was developed by Commodore International for their 8-bit systems, is based on ASCII-1963. Likewise, many Sharp MZ character sets are based on ASCII-1963.

IBM defined code page 437 for the IBM PC, replacing the control characters with graphic symbols such as smiley faces, and mapping additional graphic characters to the upper 128 positions. 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. Apple defined Mac OS Roman for the Macintosh and Adobe defined the PostScript Standard Encoding for PostScript; both sets contained "international" letters, typographic symbols and punctuation marks instead of graphics, more like modern character sets.

The ISO/IEC 8859 standard (derived from the DEC-MCS) provided a standard that most systems copied (or at least were based on, when not copied exactly). 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 on the World Wide Web until 2008, when UTF-8 overtook them.

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.

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, respectively).

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.

1. ^ The 128 characters of the 7-bit ASCII character set are divided into eight 16-character groups called sticks 0-7, associated with the three most-significant bits. Depending on the horizontal or vertical representation of the character map, sticks can correspond with either table rows or columns.

2. Caret notation is often used to represent control characters on a terminal. On most text terminals, holding down the key while typing the second character will type the control character. Sometimes the shift key is not needed, for instance ^ ^@ may be typable with just Ctrl+2 or Ctrl+Space.

3. Character escape sequences in C programming language and many other languages influenced by it, such as ^ Java and Perl (though not all implementations necessarily support all escape sequences).

4. Entering any Single-Byte character is supported by escaping its octal value. However, because of the role of NULL in ^ C-strings, this case see particular use.

5. The ambiguity of Backspace is due to early terminals designed assuming the main use of the keyboard would be to manually punch paper tape while not connected to a computer. To delete the previous character, one had to back up the paper tape punch, which for mechanical and simplicity reasons was a button on the punch itself and not the keyboard, then type the rubout character. They therefore placed a key producing rubout at the location used on typewriters for backspace. When systems used these terminals and provided command-line editing, they had to use the "rubout" code to perform a backspace, and often did not interpret the backspace character (they might echo "^H" for backspace). Other terminals not designed for paper tape made the key at this location produce Backspace, and systems designed for these used that character to back up. Since the delete code often produced a backspace effect, this also forced terminal manufacturers to make any Delete key produce something other than the Delete character.

6. The ^ Carriage Return character can also be entered by pressing the ↵ Enter or Return key on most systems.

7. The \e ^ escape sequence is not part of ISO C and many other language specifications. However, it is understood by several compilers, including GCC.

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

1. "Character Sets". Internet Assigned Numbers Authority (IANA). 2007-05-14.

2. ^ Mackenzie, Charles E. (1980). Coded Character Sets, History and Development (PDF). The Systems Programming Series (1 ed.). Addison-Wesley Publishing Company, Inc. pp. 6, 66, 211, 215, 217, 220, 223, 228, 236-238, 243-245, 247-253, 423, 425-428, 435-439. ISBN 978-0-201-14460-4. LCCN 77-90165. Archived (PDF) from the original on May 26, 2016.

3. ^ "Milestone-Proposal:ASCII MIlestone - IEEE NJ Coast Section". IEEE Milestones Wiki. 2016-03-29.

4. ^ "American Standard Code for Information Interchange, ASA X3.4-1963". Sensitive Research. American Standards Association. 1963-06-17.

5. ^ USA Standard Code for Information Interchange, USAS X3.4-1967 (Technical report). United States of America Standards Institute. 1967-07-07.

6. ^ Jennings, Thomas Daniel (2016-04-20) [1999]. "An annotated history of some character codes or ASCII: American Standard Code for Information Infiltration". Sensitive Research (SR-IX).

7. ^ American National Standard for Information Systems - Coded Character Sets - 7-Bit American National Standard Code for Information Interchange (7-Bit ASCII), ANSI X3.4-1986 (Technical report). American National Standards Institute (ANSI). 1986-03-26.

8. Cerf, Vint (1969-10-16). ASCII format for Network Interchange. Network Working Group. doi:10.17487/RFC0020. RFC 20. (NB. Almost identical wording to USAS X3.4-1968 except for the intro.)

9. ^ Barry Leiba (2015-01-12). "Correct classification of RFC 20 (ASCII format) to Internet Standard". IETF.

10. ^ Maini, Anil Kumar (2007). Digital Electronics: Principles, Devices and Applications. John Wiley and Sons. p. 28. ISBN 978-0-470-03214-5. In addition, it defines codes for 33 nonprinting, mostly obsolete control characters that affect how the text is processed.

11. ^ Bukstein, Ed (July 1964). "Binary Computer Codes and ASCII". Electronics World. 72 (1): 28-29. Archived from the original on 2016-03-03.

12. ^ Bemer, Robert William (1980). "Chapter 1: Inside ASCII" (PDF). General Purpose Software. Best of Interface Age. Vol. 2. Portland, OR, US: dilithium Press. pp. 1-50. ISBN 978-0-918398-37-6. LCCN 79-67462. Archived from the original on 2016-08-27, from:

13. ^ Winter, Dik T. (2010) [2003]. "US and International standards: ASCII". Archived from the original on 2010-01-16.

14. USA Standard Code for Information Interchange, USAS X3.4-1968 (Technical report). United States of America Standards Institute. 1968-10-10.

15. ^ Salste, Tuomas (January 2016). "7-bit character sets: Revisions of ASCII". Aivosto Oy. urn:nbn:fi-fe201201011004. Archived from the original on 2016-06-13.

16. ^ Korpela, Jukka K. (2014-03-14) [2006-06-07]. Unicode Explained - Internationalize Documents, Programs, and Web Sites (2nd release of 1st ed.). O'Reilly Media, Inc. p. 118. ISBN 978-0-596-10121-3.

17. ^ ANSI INCITS 4-1986 (R2007): American National Standard for Information Systems - Coded Character Sets - 7-Bit American National Standard Code for Information Interchange (7-Bit ASCII), 2007 [1986]

18. ^ Bit Sequencing of the American National Standard Code for Information Interchange in Serial-by-Bit Data Transmission, American National Standards Institute (ANSI), 1966, X3.15-1966

19. ^ "BruXy: Radio Teletype communication". 2005-10-10. Archived from the original on 2016-04-12. The transmitted code use International Telegraph Alphabet No. 2 (ITA-2) which was introduced by CCITT in 1924.

20. Smith, Gil (2001). "Teletype Communication Codes" (PDF). Baudot.net. Archived (PDF) from the original on 2008-08-20.

21. ^ Sawyer, Stanley A.; Krantz, Steven George (1995). A TeX Primer for Scientists. CRC Press. p. 13. Bibcode:1995tps..book.....S. ISBN 978-0-8493-7159-2. Archived from the original on 2016-12-22.

22. ^ Barry Margolin (2014-05-29). "Re: editor and word processor history (was: Re: RTF for emacs)". help-gnu-emacs (Mailing list). Archived from the original on 2014-07-14.

23. "PDP-6 Multiprogramming System Manual" (PDF). Digital Equipment Corporation (DEC). 1965. p. 43. Archived (PDF) from the original on 2014-07-14.

24. "PDP-10 Reference Handbook, Book 3, Communicating with the Monitor" (PDF). Digital Equipment Corporation (DEC). 1969. p. 5-5. Archived (PDF) from the original on 2011-11-15.

25. ^ Ossanna, J. F.; Saltzer, J. H. (November 17-19, 1970). "Technical and human engineering problems in connecting terminals to a time-sharing system" (PDF). Proceedings of the November 17-19, 1970, Fall Joint Computer Conference (FJCC). AFIPS Press. pp. 355-362. Archived (PDF) from the original on 2012-08-19. Using a "new-line" function (combined carriage-return and line-feed) is simpler for both man and machine than requiring both functions for starting a new line; the American National Standard X3.4-1968 permits the line-feed code to carry the new-line meaning.

26. ^ Haynes, Jim (2015-01-13). "First-Hand: Chad is Our Most Important Product: An Engineer's Memory of Teletype Corporation". Engineering and Technology History Wiki (ETHW). There was the change from 1961 ASCII to 1968 ASCII. Some computer languages used characters in 1961 ASCII such as up arrow and left arrow. These characters disappeared from 1968 ASCII. We worked with Fred Mocking, who by now was in Sales at Teletype, on a type cylinder that would compromise the changing characters so that the meanings of 1961 ASCII were not totally lost. The underscore character was made rather wedge-shaped so it could also serve as a left arrow.

27. ^ Richard S. Shuford (1996-12-20). "Re: Early history of ASCII?". Newsgroup: alt.folklore.computers. Usenet: Pine.SUN.3.91.961220100220.13180C-100000@duncan.cs.utk.edu.

28. ^ Folts, Harold C.; Karp, Harry, eds. (1982-02-01). Compilation of Data Communications Standards (2nd revised ed.). McGraw-Hill Inc. ISBN 978-0-07-021457-6.

29. ^ Dubost, Karl (2008-05-06). "UTF-8 Growth on the Web". W3C Blog. World Wide Web Consortium. Archived from the original on 2016-06-16.

30. Davis, Mark (2008-05-05). "Moving to Unicode 5.1". Official Google Blog. Archived from the original on 2016-06-16.

31. ^ Davis, Mark (2010-01-28). "Unicode nearing 50% of the web". Official Google Blog. Archived from the original on 2016-06-16.

32. ^ Maréchal, R. (1967-12-22), ISO/TC 97 - Computers and Information Processing: Acceptance of Draft ISO Recommendation No. 1052

33. ^ "DVB-TXT (Teletext) Specification for conveying ITU-R System B Teletext in DVB bitstreams".

34. ^ Technical Reference (PDF). Personal Computer Hardware Reference Library (First ed.). IBM. August 1981. Appendix C. Of Characters Keystrokes and Color.

35. ^ The Unicode Consortium (2006-10-27). "Chapter 13: Special Areas and Format Characters" (PDF). In Allen, Julie D. (ed.). The Unicode standard, Version 5.0. Upper Saddle River, New Jersey, US: Addison-Wesley Professional. p. 314. ISBN 978-0-321-48091-0. Archived (PDF) from the original on 2022-10-09.

# data[].attributes.attachment_link.description
MIME / IANA us-ascii Alias(es) ISO-IR-006,[1] ANSI_X3.4-1968, ANSI_X3.4-1986, ISO_646.irv:1991, ISO646-US, us, IBM367, cp367[2] Language(s) English (made for; does not support all loanwords), Malay, Rotokas, Interlingua, Ido, and X-SAMPA Classification ISO/IEC 646 series Extensions Preceded by ITA 2, FIELDATA Succeeded by ISO/IEC 8859, ISO/IEC 10646 ( Unicode) ASCII ( ASS-kee ), an acronym for American Standard Code for Information Interchange, is a character encoding standard for electronic communication.

# data[].attributes.headline
Evaluare formativă - Observarea activității

# data[].attributes.subject
Evaluare formativă - Observarea activității

# data[].attributes.body
Pe parcursul lecției, voi observa:
- Participarea la discuții
- Corectitudinea conversiilor în activitățile de grup
- Calitatea întrebărilor puse de elevi
- Colaborarea în echipe

# data[].attributes.headline
Evaluare formativă - Verificarea înțelegerii

# data[].attributes.subject
Evaluare formativă - Verificarea înțelegerii

# data[].attributes.body
La mijlocul lecției: Quiz rapid cu 3 întrebări
1. Ce înseamnă ASCII?
2. Câte caractere poate reprezenta ASCII standard?
3. Dați un exemplu de conversie caracter-cod

# data[].attributes.body
Test de 10 minute la sfârșitul lecției:
- 5 conversii caracter → ASCII
- 5 conversii ASCII → caracter
- O întrebare despre aplicațiile practice
- Rezolvarea unui mesaj codat simplu

# data[].attributes.body
Discuție de grup (5 minute): Fiecare echipă va prezenta:
- Un aspect nou învățat despre ASCII
- O aplicație practică identificată
- O întrebare care a rămas nerezolvată

# data[].attributes.body
Fiecare elev completează pe o foaie:
1. Cea mai importantă informație învățată astăzi despre ASCII
2. Un exemplu de conversie ASCII pe care îl știu acum
3. Cum vă va ajuta această cunoștință în viitor?
4. O întrebare pe care încă o aveți

# data[].attributes.body
În lecția următoare vom explora:
- ASCII extins și Unicode
- Reprezentarea în alte sisteme de numerație
- Cum gestionează computerele caracterele speciale și emoji-urile

# data[].attributes.body
1. Creați un mesaj secret pentru un coleg folosind coduri ASCII (minimum 20 de caractere)
2. Decodificați mesajul primit de la un coleg
3. Completați tabelul cu codurile ASCII pentru toate literele alfabetului românesc

# data[].attributes.body
Opțional - pentru notă suplimentară:<br>Creați o poveste scurtă (100 cuvinte) despre 'Aventura unui caracter în lumea ASCII' - explicați într-un mod creativ cum ajunge o literă să devină cod și invers.

# data[].attributes.body
Găsiți online și studiați:
- Diferențele dintre ASCII și Unicode
- Cum se reprezintă caracterele românești (ă, â, î, ș, ț) în ASCII extins
- Exemple de ASCII art și înțelegerea modului de creare