Unicode

qas: question: What was Unicode published as?
answers: text: The Unicode Standard

question: What was unicode developed in conjunction with?
answers: text: Universal Coded Character Set (UCS)

question: What is the most recent version of Unicode?
answers: text: Unicode 8.0

question: Who maintains the Unicode Standard? 
answers: text: Unicode Consortium

question: Unicode contains how many thousands of characters in its repertoire? 
answers: text: 120,000 characters

question: What is the Universal Coded Character set published as?

question: How many characters does Arabic have?

question: How many scripts does UCS cover?

question: What is the acronym for Unicode?

question: What is an example of a left-to-right script?
context: Unicode is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. Developed in conjunction with the Universal Coded Character Set (UCS) standard and published as The Unicode Standard, the latest version of Unicode contains a repertoire of more than 120,000 characters covering 129 modern and historic scripts, as well as multiple symbol sets. The standard consists of a set of code charts for visual reference, an encoding method and set of standard character encodings, a set of reference data files, and a number of related items, such as character properties, rules for normalization, decomposition, collation, rendering, and bidirectional display order (for the correct display of text containing both right-to-left scripts, such as Arabic and Hebrew, and left-to-right scripts). As of June 2015[update], the most recent version is Unicode 8.0. The standard is maintained by the Unicode Consortium.

qas: question: What are the most commonly used encodings of Unicode?
answers: text: UTF-8, UTF-16 and the now-obsolete UCS-2

question: What does UTF-8 use in terms of bytes? 
answers: text: UTF-8 uses one byte for any ASCII character

question: What type of code does UCS-2 use?
answers: text: 16-bit code unit

question: What does UTF-16 expand? 
answers: text: UCS-2

question: How are two 16-bit units used? 
answers: text: (4 × 8 bits

question: What are character encodings implemented by?

question: Which two encodings are now obsolete?

question: What did UCS-2 expand?

question: How many ASCII characters are used to make one UTF-8?

question: What system has a minimum of four bytes?
context: Unicode can be implemented by different character encodings. The most commonly used encodings are UTF-8, UTF-16 and the now-obsolete UCS-2. UTF-8 uses one byte for any ASCII character, all of which have the same code values in both UTF-8 and ASCII encoding, and up to four bytes for other characters. UCS-2 uses a 16-bit code unit (two 8-bit bytes) for each character but cannot encode every character in the current Unicode standard. UTF-16 extends UCS-2, using one 16-bit unit for the characters that were representable in UCS-2 and two 16-bit units (4 × 8 bits) to handle each of the additional characters.

qas: question: What is the aim of Unicode?
answers: text: transcending the limitations of traditional character encodings

question: Traditional character encodings don't allow what type of computer processing?
answers: text: multilingual computer processing

question: What is multilingual computer processing?
answers: text: (computer processing of arbitrary scripts mixed with each other

question: Bilingual computer processing uses what characters?
answers: text: usually using Latin characters

question: What is the major limitation of traditional character encodings?
answers: text: wide usage in various countries of the world but remain largely incompatible with each other

question: What was Unicode defined in?

question: What characters does multilingual processors use?

question: What type of encodings do not allow bilingual computer processing?

question: What is the limitation of unicode globally?

question: What are traditional character encodings attempting to surpass?
context: Unicode has the explicit aim of transcending the limitations of traditional character encodings, such as those defined by the ISO 8859 standard, which find wide usage in various countries of the world but remain largely incompatible with each other. Many traditional character encodings share a common problem in that they allow bilingual computer processing (usually using Latin characters and the local script), but not multilingual computer processing (computer processing of arbitrary scripts mixed with each other).

qas: question: What were the first 256 code points of Unicode made identical to? 
answers: text: ISO-8859-1

question: Why were the first 256 code points made identical to ISO-8859-1?
answers: text: to make it trivial to convert existing western text

question: What does the "fullwidth forms" section of code points encompass?
answers: text: a full Latin alphabet that is separate from the main Latin alphabet

question: What are the CJK languages referenced?
answers: text: Chinese, Japanese, and Korean

question: What did ISO-8859-1 copy?

question: Latin is what kind of language?

question: What are Latin characters called when they are half width?

question: Why do coders avoid duplicate characters?

question: The 256 initial points make it difficult to translate what kind of text?
context: The first 256 code points were made identical to the content of ISO-8859-1 so as to make it trivial to convert existing western text. Many essentially identical characters were encoded multiple times at different code points to preserve distinctions used by legacy encodings and therefore, allow conversion from those encodings to Unicode (and back) without losing any information. For example, the "fullwidth forms" section of code points encompasses a full Latin alphabet that is separate from the main Latin alphabet section because in Chinese, Japanese, and Korean (CJK) fonts, these Latin characters are rendered at the same width as CJK ideographs, rather than at half the width. For other examples, see Duplicate characters in Unicode.

qas: question: When was a surrogate character mechanism implemented in Unicode 2.0?
answers: text: 1996

question: Why was a surrogate character mechanism implemented?
answers: text: so that Unicode was no longer restricted to 16 bits

question: What are some characters not originally intended for Unicode? 
answers: text: rarely used Kanji or Chinese characters

question: Why are some foreign characters rarely used? 
answers: text: many of which are part of personal and place names

question: Why was the Unicode 2.0 codespace increased? 
answers: text: allowed for the encoding of many historic scripts

question: When was Unicode restricted to 16 bits?

question: What types of egyptian hieroglyphs are rarely used?

question: What are the extra Unicode characters called?

question: What types of characters were removed with Unicode 2.0?

question: What was removed in 1996?
context: In 1996, a surrogate character mechanism was implemented in Unicode 2.0, so that Unicode was no longer restricted to 16 bits. This increased the Unicode codespace to over a million code points, which allowed for the encoding of many historic scripts (e.g., Egyptian Hieroglyphs) and thousands of rarely used or obsolete characters that had not been anticipated as needing encoding. Among the characters not originally intended for Unicode are rarely used Kanji or Chinese characters, many of which are part of personal and place names, making them rarely used, but much more essential than envisioned in the original architecture of Unicode.

qas: question: What are the General Categories of Unicode?
answers: text: Letter, Mark, Number, Punctuation, Symbol, Separator and Other

question: What type of use is the General Category not helpful for?
answers: text: not useful for every use, since legacy encodings have used multiple characteristics per single code point

question: What is the General Category in Unicode?
answers: text: Other, Control

question: How many General Category properties does each code point have?
answers: text: a single General Category property

question: What exists within the main Unicode categories? 
answers: text: subdivisions

question: What subcategories are found in the category Other?

question: Which category can always be used?

question: Why is Symbol not useful for all instances?

question: What is the title of the Separator category in Unicode?

question: "Other, Symbol" represents what unicode category?
context: Each code point has a single General Category property. The major categories are: Letter, Mark, Number, Punctuation, Symbol, Separator and Other. Within these categories, there are subdivisions. The General Category is not useful for every use, since legacy encodings have used multiple characteristics per single code point. E.g., U+000A <control-000A> Line feed (LF) in ASCII is both a control and a formatting separator; in Unicode the General Category is "Other, Control". Often, other properties must be used to specify the characteristics and behaviour of a code point. The possible General Categories are:

qas: question: What are code points in the range U+D800-U+DBFF known as? 
answers: text: high-surrogate code points

question: What are code points in the range U+DC00-U+DFFF known as? 
answers: text: low-surrogate code points

question: what is another name for a high-surrogate code point? 
answers: text: leading surrogate

question: what is another name for a low-surrogate code point? 
answers: text: trailing surrogate

question: What is known as a character's scalar value? 
answers: text: the range of code points that are available for use as characters

question: What is a low-surrogate followed by a high-surrogate called?

question: What is another name for a surrogate pair?

question: How many points are represented inside of BMP?

question: Which kinds of code points are valid by themselves?

question: What is the individual number of code points called?
context: Code points in the range U+D800–U+DBFF (1,024 code points) are known as high-surrogate code points, and code points in the range U+DC00–U+DFFF (1,024 code points) are known as low-surrogate code points. A high-surrogate code point (also known as a leading surrogate) followed by a low-surrogate code point (also known as a trailing surrogate) together form a surrogate pair used in UTF-16 to represent 1,048,576 code points outside BMP. High and low surrogate code points are not valid by themselves. Thus the range of code points that are available for use as characters is U+0000–U+D7FF and U+E000–U+10FFFF (1,112,064 code points). The value of these code points (i.e., excluding surrogates) is sometimes referred to as the character's scalar value.

qas: question: What is an ogonek? 
answers: text: a dot above

question: How does Unicode encode characters?
answers: text: associating an abstract character with a particular code point

question: How are some abstract characters represented in Unicode?
answers: text: a sequence of two or more characters

question: What is another name for an acute accent?

question: What does Latin require?

question: What are format characters associated with?

question: What do sets of graphic characters directly correspond to?

question: What are all encoded as singular unicode characters?
context: The set of graphic and format characters defined by Unicode does not correspond directly to the repertoire of abstract characters that is representable under Unicode. Unicode encodes characters by associating an abstract character with a particular code point. However, not all abstract characters are encoded as a single Unicode character, and some abstract characters may be represented in Unicode by a sequence of two or more characters. For example, a Latin small letter "i" with an ogonek, a dot above, and an acute accent, which is required in Lithuanian, is represented by the character sequence U+012F, U+0307, U+0301. Unicode maintains a list of uniquely named character sequences for abstract characters that are not directly encoded in Unicode.

qas: question: What policy guaranteed that characters have a unique and immutable name?
answers: text: Name Stability policy

question: What happens when a name is defective or misleading?
answers: text: a formal alias may be defined

question: How long has this name immutability been guaranteed? 
answers: text: since Unicode version 2.0

question: What policy identified misleading characters?

question: When an error is found, what is used in place of a formal alias?

question: When was the formal alias yi created?

question: What is an example of a symbol that does not use a formal alias?

question: Which types of characters do not have unique names?
context: All graphic, format, and private use characters have a unique and immutable name by which they may be identified. This immutability has been guaranteed since Unicode version 2.0 by the Name Stability policy. In cases where the name is seriously defective and misleading, or has a serious typographical error, a formal alias may be defined, and applications are encouraged to use the formal alias in place of the official character name. For example, U+A015 ꀕ YI SYLLABLE WU has the formal alias yi syllable iteration mark, and U+FE18 ︘ PRESENTATION FORM FOR VERTICAL RIGHT WHITE LENTICULAR BRAKCET (sic) has the formal alias presentation form for vertical right white lenticular bracket.

qas: question: Who was Unicode developed in conjunction with?
answers: text: International Organization for Standardization

question: What does Unicode share a character repertoire with?
answers: text: the Universal Character Set

question: What includes topics like bitwise encoding, collation, and rendering?
answers: text: The Unicode Standard

question: What do the two standards differ in? 
answers: text: slightly different terminology

question: Who created the character repertoire for IOS/IEC 10646?

question: What is another name for Unicode?

question: What is developed alongside the UCS?

question: Unicode has more information regarding what?

question: What have different character repertoires?
context: Unicode is developed in conjunction with the International Organization for Standardization and shares the character repertoire with ISO/IEC 10646: the Universal Character Set. Unicode and ISO/IEC 10646 function equivalently as character encodings, but The Unicode Standard contains much more information for implementers, covering—in depth—topics such as bitwise encoding, collation and rendering. The Unicode Standard enumerates a multitude of character properties, including those needed for supporting bidirectional text. The two standards do use slightly different terminology.

qas: question: When was the Unicode Standard first published? 
answers: text: 1991

question: When was the latest version, Unicode 8.0, released?
answers: text: June 2015

question: What was the last major version of Unicode to be published in book form? 
answers: text: Unicode 5.0

question: What year was it announced that only the core specification for Unicode would be printed in physical form?
answers: text: 2012

question: What does the print on demand, core version not include? 
answers: text: any code charts or standard annexes

question: When was the Consortium founded?

question: What month did the Consortium first publish Unicode?

question: When was it announced that Unicode would no longer be available in book form?

question: How many pages was the original Unicode standard?

question: What extra sections are not included on the Unicode website?
context: The Consortium first published The Unicode Standard (ISBN 0-321-18578-1) in 1991 and continues to develop standards based on that original work. The latest version of the standard, Unicode 8.0, was released in June 2015 and is available from the consortium's website. The last of the major versions (versions x.0) to be published in book form was Unicode 5.0 (ISBN 0-321-48091-0), but since Unicode 6.0 the full text of the standard is no longer being published in book form. In 2012, however, it was announced that only the core specification for Unicode version 6.1 would be made available as a 692-page print-on-demand paperback. Unlike the previous major version printings of the Standard, the print-on-demand core specification does not include any code charts or standard annexes, but the entire standard, including the core specification, will still remain freely available on the Unicode website.

qas: question: Michael Everson, Rick McGowan, and Ken Whistler make up what group?
answers: text: Unicode Roadmap Committee

question: What does the Unicode Roadmap Commmittee do? 
answers: text: maintain the list of scripts that are candidates or potential candidates for encoding

question: What proposal has been made for the Mayan script? 
answers: text: no proposal has yet been made

question: Where does the Unicode Roadmap Committee post information on these scripts?
answers: text: Unicode Consortium Web site

question: Who are the potential candidates for encoding?

question: Who made the proposal for the Mayan script?

question: What needs to be agreed upon before a script for Jurchen is proposed?

question: Which scripts are user committees no longer proposing?

question: What committies have to approve proposals?
context: The Unicode Roadmap Committee (Michael Everson, Rick McGowan, and Ken Whistler) maintain the list of scripts that are candidates or potential candidates for encoding and their tentative code block assignments on the Unicode Roadmap page of the Unicode Consortium Web site. For some scripts on the Roadmap, such as Jurchen, Nü Shu, and Tangut, encoding proposals have been made and they are working their way through the approval process. For others scripts, such as Mayan and Rongorongo, no proposal has yet been made, and they await agreement on character repertoire and other details from the user communities involved.

qas: question: How many mapping methods does Unicode define?
answers: text: two

question: What are the two mapping methods that Unicode defines?
answers: text: Unicode Transformation Format (UTF) encodings, and the Universal Coded Character Set (UCS) encodings

question: What do numbers in the names of the encodings indicate? 
answers: text: the number of bits per code value (for UTF encodings) or the number of bytes per code value

question: What are the most commonly used encodings? 
answers: text: UTF-8 and UTF-16

question: What does UCS stand for?
answers: text: Universal Coded Character Set

question: How many mapping modes does USC have?

question: What maps an encoding?

question: What is the subset of UTF-8?

question: What is functionally equivalent to USC-2?

question: What do the sequences of values indicate?
context: Unicode defines two mapping methods: the Unicode Transformation Format (UTF) encodings, and the Universal Coded Character Set (UCS) encodings. An encoding maps (possibly a subset of) the range of Unicode code points to sequences of values in some fixed-size range, termed code values. The numbers in the names of the encodings indicate the number of bits per code value (for UTF encodings) or the number of bytes per code value (for UCS encodings). UTF-8 and UTF-16 are probably the most commonly used encodings. UCS-2 is an obsolete subset of UTF-16; UCS-4 and UTF-32 are functionally equivalent.

qas: question: What does BOM stand for? 
answers: text: Unicode Byte Order Mark

question: What specifies the BOM?
answers: text: UCS-2 and UTF-16

question: what is the code point of the BOM?
answers: text: U+FEFF

question: What is U+UFFE the result of? 
answers: text: byte-swapping U+FEFF

question: What is the code point for BOM?

question: What changes the important property in BOM?

question: U+FFFE is equated to what?

question: What are UCS-2 and UTF-16 specified by?

question: What is the abbreviation for UCS-2 and UTF-16?
context: The UCS-2 and UTF-16 encodings specify the Unicode Byte Order Mark (BOM) for use at the beginnings of text files, which may be used for byte ordering detection (or byte endianness detection). The BOM, code point U+FEFF has the important property of unambiguity on byte reorder, regardless of the Unicode encoding used; U+FFFE (the result of byte-swapping U+FEFF) does not equate to a legal character, and U+FEFF in other places, other than the beginning of text, conveys the zero-width non-break space (a character with no appearance and no effect other than preventing the formation of ligatures).

qas: question: What is the UTF-8 standard? 
answers: text: RFC 3629

question: Byte order marks are forbidden in protocols using what standard? 
answers: text: UTF-8

question: Why is it possible to distinguish UTF-8 from other protocols?
answers: text: the large restriction on possible patterns

question: BOM can not replace what kind of UTF-8 text?

question: What is used to distinguish local 8-bit code pages?

question: What is the name of the BOM standard?

question: What type of bytes are required in a high bit set?

question: What type of patterns are rarely resticted?
context: The same character converted to UTF-8 becomes the byte sequence EF BB BF. The Unicode Standard allows that the BOM "can serve as signature for UTF-8 encoded text where the character set is unmarked". Some software developers have adopted it for other encodings, including UTF-8, in an attempt to distinguish UTF-8 from local 8-bit code pages. However RFC 3629, the UTF-8 standard, recommends that byte order marks be forbidden in protocols using UTF-8, but discusses the cases where this may not be possible. In addition, the large restriction on possible patterns in UTF-8 (for instance there cannot be any lone bytes with the high bit set) means that it should be possible to distinguish UTF-8 from other character encodings without relying on the BOM.

qas: question: How is UTF-32 widely used? 
answers: text: internal representation of text in programs

question: What programming language uses UTF-32 as internal representation of characters? 
answers: text: Seed7

question: what version of python can be used with UTF-32? 
answers: text: 2.2

question: What does not vary across platforms?

question: What uses UCS-4 as an internal representation?

question: What is the last version of Python that can use UTF-32?

question: What does Python use to generate the standard wide character encoding?

question: What is used to represent transmitted text?
context: In UTF-32 and UCS-4, one 32-bit code value serves as a fairly direct representation of any character's code point (although the endianness, which varies across different platforms, affects how the code value manifests as an octet sequence). In the other encodings, each code point may be represented by a variable number of code values. UTF-32 is widely used as an internal representation of text in programs (as opposed to stored or transmitted text), since every Unix operating system that uses the gcc compilers to generate software uses it as the standard "wide character" encoding. Some programming languages, such as Seed7, use UTF-32 as internal representation for strings and characters. Recent versions of the Python programming language (beginning with 2.2) may also be configured to use UTF-32 as the representation for Unicode strings, effectively disseminating such encoding in high-level coded software.

qas: question: What combinations does unicode contain in normal use?
answers: text: most letter/diacritic combinations

question: How is the latin small letter e represented in Unicode?
answers: text: U+0065

question: How is the accent added to the small latin e? 
answers: text: U+0301

question: What precomposed character represents the small latin e with an accent? 
answers: text: U+00E9

question: What are inserted before a main character?

question: What cannot have multiple instances of diacritics?

question: What do applications have to implement?

question: What prevents redundancy in the ways you can make one character?

question: How is the capital letter e indicated in unicode?
context: Unicode includes a mechanism for modifying character shape that greatly extends the supported glyph repertoire. This covers the use of combining diacritical marks. They are inserted after the main character. Multiple combining diacritics may be stacked over the same character. Unicode also contains precomposed versions of most letter/diacritic combinations in normal use. These make conversion to and from legacy encodings simpler, and allow applications to use Unicode as an internal text format without having to implement combining characters. For example, é can be represented in Unicode as U+0065 (LATIN SMALL LETTER E) followed by U+0301 (COMBINING ACUTE ACCENT), but it can also be represented as the precomposed character U+00E9 (LATIN SMALL LETTER E WITH ACUTE). Thus, in many cases, users have multiple ways of encoding the same character. To deal with this, Unicode provides the mechanism of canonical equivalence.

qas: question: The CJK ideographs comprise simpler elements called what in English?
answers: text: radicals

question: Why have ideographs been unable to be simplified like Hangul?
answers: text: ideographs do not decompose as simply or as regularly

question: What would be the benefit of Unicode decomposing  ideographs?
answers: text: greatly reduced the number of required code points

question: What ideographs do not have codes for their precomposed form yet?

question: What are precomposed forms called in English?

question: What are called radicals in Hangul?

question: What did Unicode do to CJK ideographs?

question: What decomposes regularly in Wubi?
context: The CJK ideographs currently have codes only for their precomposed form. Still, most of those ideographs comprise simpler elements (often called radicals in English), so in principle, Unicode could have decomposed them, as it did with Hangul. This would have greatly reduced the number of required code points, while allowing the display of virtually every conceivable ideograph (which might do away with some of the problems caused by Han unification). A similar idea is used by some input methods, such as Cangjie and Wubi. However, attempts to do this for character encoding have stumbled over the fact that ideographs do not decompose as simply or as regularly as Hangul does.

qas: question: What does ACE stand for? 
answers: text: Arabic Calligraphic Engine

question: Who created ACE?
answers: text: DecoType

question: When was ACE created? 
answers: text: 1980s

question: Who created OpenType?
answers: text: Adobe and Microsoft

question: Who created Graphite? 
answers: text: SIL International

question: When was OpenType created?

question: What does AAT stand for?

question: Who partnered with SIL International?

question: Which two companies produced DecoType?

question: What are two examples of scripts without orthographic rules?
context: Many scripts, including Arabic and Devanagari, have special orthographic rules that require certain combinations of letterforms to be combined into special ligature forms. The rules governing ligature formation can be quite complex, requiring special script-shaping technologies such as ACE (Arabic Calligraphic Engine by DecoType in the 1980s and used to generate all the Arabic examples in the printed editions of the Unicode Standard), which became the proof of concept for OpenType (by Adobe and Microsoft), Graphite (by SIL International), or AAT (by Apple).

qas: question: where are instructions embedded to tell fonts how to output sequences? 
answers: text: in fonts

question: Can real stacking be accomplished? 
answers: text: Real stacking is impossible

question: what is a solution to the placement of combining marks? 
answers: text: assigning the marks a width of zero and placing the glyph itself to the left or right of the left sidebearing

question: What type of stacking is required?

question: Approximated stacking is not possible with what kinds of fonts?

question: What does the operating system tell what to do?

question: What numerical value is assigned to the glyph?

question: What is a mark adjust its position relative to?
context: Instructions are also embedded in fonts to tell the operating system how to properly output different character sequences. A simple solution to the placement of combining marks or diacritics is assigning the marks a width of zero and placing the glyph itself to the left or right of the left sidebearing (depending on the direction of the script they are intended to be used with). A mark handled this way will appear over whatever character precedes it, but will not adjust its position relative to the width or height of the base glyph; it may be visually awkward and it may overlap some glyphs. Real stacking is impossible, but can be approximated in limited cases (for example, Thai top-combining vowels and tone marks can just be at different heights to start with). Generally this approach is only effective in monospaced fonts, but may be used as a fallback rendering method when more complex methods fail.

qas: question: What subset of Unicode is used by Windows? 
answers: text: WGL-4 with 652 characters

question: What are MES-1, MES-2, AND MES-3A AND MES-3B part of? 
answers: text: Multilingual European Subsets

question: What subset includes every character in MES-1 and WGL-4? 
answers: text: MES-2

question: How long has Microsoft Windows supported WGL-4? 
answers: text: since Windows NT 4.0

question: MES-1 uses what scripts only? 
answers: text: Latin scripts only

question: What system uses MES-3A?

question: How many Latin characters are supported in WGL-4?

question: How many characters are in MES-3B?

question: MES-3A combines which two other sets?

question: What subset only uses the Greek script?
context: Several subsets of Unicode are standardized: Microsoft Windows since Windows NT 4.0 supports WGL-4 with 652 characters, which is considered to support all contemporary European languages using the Latin, Greek, or Cyrillic script. Other standardized subsets of Unicode include the Multilingual European Subsets: MES-1 (Latin scripts only, 335 characters), MES-2 (Latin, Greek and Cyrillic 1062 characters) and MES-3A & MES-3B (two larger subsets, not shown here). Note that MES-2 includes every character in MES-1 and WGL-4.

qas: question: What does rendering software display when it can't process a Unicode character? 
answers: text: open rectangle, or the Unicode "replacement character"

question: What is the code for the Unicode replacement character? 
answers: text: U+FFFD

question: What is the name of Apple's font? 
answers: text: Last Resort

question: What does SIL's Unicode Fallback font display when it can't display a character properly? 
answers: text: a box showing the hexadecimal scalar value of the character

question: What company uses the Unicode Fallback font? 
answers: text: SIL International

question: What is the Unicode for an open rectangle?

question: What company uses U+FFFD?

question: What is the glyph that Apple's Last Resort font displays?

question: What software by SIL cannot process unicode characters?
context: Rendering software which cannot process a Unicode character appropriately often displays it as an open rectangle, or the Unicode "replacement character" (U+FFFD, �), to indicate the position of the unrecognized character. Some systems have made attempts to provide more information about such characters. The Apple's Last Resort font will display a substitute glyph indicating the Unicode range of the character, and the SIL International's Unicode Fallback font will display a box showing the hexadecimal scalar value of the character.

qas: question: What is the dominant scheme for internal processing? 
answers: text: Unicode

question: What is Unicode available through Windows on? 
answers: text: Microsoft Layer

question: What was the two-byte precursor to UTF-16? 
answers: text: UCS-2

question: What is used almost exclusively for building new information processing systems? 
answers: text: Unicode

question: What are legacy encodings used exclusively for?

question: What was the precursor to the UCS-2?

question: What descended from Mac OS X?

question: What are Mac OS X and KDE called?

question: What is fixed-width one byte?
context: Unicode has become the dominant scheme for internal processing and storage of text. Although a great deal of text is still stored in legacy encodings, Unicode is used almost exclusively for building new information processing systems. Early adopters tended to use UCS-2 (the fixed-width two-byte precursor to UTF-16) and later moved to UTF-16 (the variable-width current standard), as this was the least disruptive way to add support for non-BMP characters. The best known such system is Windows NT (and its descendants, Windows 2000, Windows XP, Windows Vista and Windows 7), which uses UTF-16 as the sole internal character encoding. The Java and .NET bytecode environments, Mac OS X, and KDE also use it for internal representation. Unicode is available on Windows 95 through Microsoft Layer for Unicode, as well as on its descendants, Windows 98 and Windows ME.

qas: question: What is recommended for email transmission of Unicode? 
answers: text: the UTF-8 character set and the Base64 or the Quoted-printable transfer encoding

question: Where are the details of the two mechanisms for email transmission specified? 
answers: text: MIME standards

question: How many different mechanisms does MIME define for encoding Unicode in email? 
answers: text: two different mechanisms

question: How many ways can ASCII characters be encoded in an email?

question: What is another way to refer to the text body?

question: What specifications are visible to the user?

question: When is Base64 not recommended?
context: MIME defines two different mechanisms for encoding non-ASCII characters in email, depending on whether the characters are in email headers (such as the "Subject:"), or in the text body of the message; in both cases, the original character set is identified as well as a transfer encoding. For email transmission of Unicode the UTF-8 character set and the Base64 or the Quoted-printable transfer encoding are recommended, depending on whether much of the message consists of ASCII-characters. The details of the two different mechanisms are specified in the MIME standards and generally are hidden from users of email software.

qas: question: How many fonts support the majority of Unicode's character repertoire? 
answers: text: fewer than a dozen fonts

question: What are the fonts that support Unicode referred to as? 
answers: text: "pan-Unicode" fonts

question: Unicode-based fonts are normally focused on supporting what? 
answers: text: basic ASCII and particular scripts or sets of characters or symbols

question: What are most of the fonts on the market called?

question: Pan unicode fonts only support what?

question: What normally need more than one or two writing systems?

question: What is another name for computing environments?
context: Thousands of fonts exist on the market, but fewer than a dozen fonts—sometimes described as "pan-Unicode" fonts—attempt to support the majority of Unicode's character repertoire. Instead, Unicode-based fonts typically focus on supporting only basic ASCII and particular scripts or sets of characters or symbols. Several reasons justify this approach: applications and documents rarely need to render characters from more than one or two writing systems; fonts tend to demand resources in computing environments; and operating systems and applications show increasing intelligence in regard to obtaining glyph information from separate font files as needed, i.e., font substitution. Furthermore, designing a consistent set of rendering instructions for tens of thousands of glyphs constitutes a monumental task; such a venture passes the point of diminishing returns for most typefaces.

qas: question: What is the code for separating lines? 
answers: text: U+2028

question: What is the code for separating paragraphs? 
answers: text: U+2029

question: How is newline normalization accomplished in Mac OS X? 
answers: text: Cocoa text system

question: How does the newliine normallization format work? 
answers: text: every possible newline character is converted internally to a common newline

question: What widely adopted solution did Unicode provide?

question: What uses HTML recommendations?

question: Why does it matter which newline character is chosen?

question: What is the name of the Cocoa text system?

question: What are common newlines converted into?
context: In terms of the newline, Unicode introduced U+2028 LINE SEPARATOR and U+2029 PARAGRAPH SEPARATOR. This was an attempt to provide a Unicode solution to encoding paragraphs and lines semantically, potentially replacing all of the various platform solutions. In doing so, Unicode does provide a way around the historical platform dependent solutions. Nonetheless, few if any Unicode solutions have adopted these Unicode line and paragraph separators as the sole canonical line ending characters. However, a common approach to solving this issue is through newline normalization. This is achieved with the Cocoa text system in Mac OS X and also with W3C XML and HTML recommendations. In this approach every possible newline character is converted internally to a common newline (which one does not really matter since it is an internal operation just for rendering). In other words, the text system can correctly treat the character as a newline, regardless of the input's actual encoding.

qas: question: Why has Unicode been criticized for not separately encoding forms of kanji?
answers: text: complicates the processing of ancient Japanese and uncommon Japanese names

question: What is TRON? 
answers: text: alternative encodings that preserve the stylistic differences between Chinese, Japanese, and Korean characters

question: What perception does the unification of glyphs cause? 
answers: text: the languages themselves, not just the basic character representation, are being merged

question: What does Unicode encode instead of characters?

question: What are characters defined as?

question: What alternative has become popular in Japan?

question: What languages do not suffer from the unification of glyphs?

question: What are being merged alongside just the glyphs?
context: Unicode has been criticized for failing to separately encode older and alternative forms of kanji which, critics argue, complicates the processing of ancient Japanese and uncommon Japanese names. This is often due to the fact that Unicode encodes characters rather than glyphs (the visual representations of the basic character that often vary from one language to another). Unification of glyphs leads to the perception that the languages themselves, not just the basic character representation, are being merged.[clarification needed] There have been several attempts to create alternative encodings that preserve the stylistic differences between Chinese, Japanese, and Korean characters in opposition to Unicode's policy of Han unification. An example of one is TRON (although it is not widely adopted in Japan, there are some users who need to handle historical Japanese text and favor it).

qas: question: what tables of OpenType allow permit the selection of alternative glyph representations?
answers: text: Advanced Typographic

question: Where is information provided to designate which character form to select? 
answers: text: plain text

question: How does modern font technology address the issue of depicting a Han character in alternate glyph representations? 
answers: text: Unicode variation sequences

question: What has worsened the practical aspects of unification?

question: What prevents OpenType from having alternative glyphs?

question: What designates which alternate character to select?
context: Modern font technology provides a means to address the practical issue of needing to depict a unified Han character in terms of a collection of alternative glyph representations, in the form of Unicode variation sequences. For example, the Advanced Typographic tables of OpenType permit one of a number of alternative glyph representations to be selected when performing the character to glyph mapping process. In this case, information can be provided within plain text to designate which alternate character form to select.

qas: question: Unicode was designed for a round trip format conversion to and from what? 
answers: text: preexisting character encodings

question: How many encoding forms are there for Korean Hangul?
answers: text: three different encoding forms

question: Since what version can already existing characters no longer be added to the standard? 
answers: text: version 3.0

question: What is Unicode converted into?

question: How many encoding forms does Unicode have?

question: After what version did it become possible to add preexisting characters?

question: What type of characters can be added in versions post 3.0? 

question: What does adding characters help to preserve?
context: Unicode was designed to provide code-point-by-code-point round-trip format conversion to and from any preexisting character encodings, so that text files in older character sets can be naïvely converted to Unicode, and then back and get back the same file. That has meant that inconsistent legacy architectures, such as combining diacritics and precomposed characters, both exist in Unicode, giving more than one method of representing some text. This is most pronounced in the three different encoding forms for Korean Hangul. Since version 3.0, any precomposed characters that can be represented by a combining sequence of already existing characters can no longer be added to the standard in order to preserve interoperability between software using different versions of Unicode.

qas: question: What kind of mappings must be provided between characters in existing legacy character sets and those in Unicode?
answers: text: Injective mappings

question: A lack of consistency between what earlier Japanese encodings and unicode led to mismatches?
answers: text: Shift-JIS or EUC-JP

question: what is the fullwidth tilde character code in Microsoft Windows?
answers: text: U+FF5E

question: What helps to convert characters out of Unicode?

question: WAVE DASH is only found in what version of OS?

question: What is the Windows code for EUC-JP?

question: What are the names of the two forms of Unicode?

question: What does a lack of consistency prevent?
context: Injective mappings must be provided between characters in existing legacy character sets and characters in Unicode to facilitate conversion to Unicode and allow interoperability with legacy software. Lack of consistency in various mappings between earlier Japanese encodings such as Shift-JIS or EUC-JP and Unicode led to round-trip format conversion mismatches, particularly the mapping of the character JIS X 0208 '～' (1-33, WAVE DASH), heavily used in legacy database data, to either U+FF5E ～ FULLWIDTH TILDE (in Microsoft Windows) or U+301C 〜 WAVE DASH (other vendors).

qas: question: How many code points are tamil and Devanagari allocated? 
answers: text: 128

question: What is another word for ligatures? 
answers: text: conjuncts

question: What is the ISCII standard? 
answers: text: 128 code points

question: How many points is Arabic given?

question: Who argued Indic scripts should follow the practice of other writing systems?

question: Why are more ligatures in Unicode likely to happen?

question: Which organization successfully argued for the Tibetan script?

question: What is the visual order transformed into?
context: Indic scripts such as Tamil and Devanagari are each allocated only 128 code points, matching the ISCII standard. The correct rendering of Unicode Indic text requires transforming the stored logical order characters into visual order and the forming of ligatures (aka conjuncts) out of components. Some local scholars argued in favor of assignments of Unicode code points to these ligatures, going against the practice for other writing systems, though Unicode contains some Arabic and other ligatures for backward compatibility purposes only. Encoding of any new ligatures in Unicode will not happen, in part because the set of ligatures is font-dependent, and Unicode is an encoding independent of font variations. The same kind of issue arose for Tibetan script[citation needed] (the Chinese National Standard organization failed to achieve a similar change).

qas: question: What standard did Unicode inherit involving a Thai language? 
answers: text: Thai Industrial Standard 620

question: Why has Thai alphabet support been criticized? 
answers: text: its ordering of Thai characters

question: How are the Thai characters ordered incorrectly? 
answers: text: Thai characters. The vowels เ, แ, โ, ใ, ไ that are written to the left of the preceding consonant are in visual order instead of phonetic order

question: How are Thai characters written similarly to other Unicode scripts?

question: What standard did Unicode create for the Thai language?

question: Who criticized the order of Thai characters?

question: What kind of machine was the Thai Industrial Standard 620 not implemented on?

question: What are written to the right of the preceding consonant?
context: Thai alphabet support has been criticized for its ordering of Thai characters. The vowels เ, แ, โ, ใ, ไ that are written to the left of the preceding consonant are in visual order instead of phonetic order, unlike the Unicode representations of other Indic scripts. This complication is due to Unicode inheriting the Thai Industrial Standard 620, which worked in the same way, and was the way in which Thai had always been written on keyboards. This ordering problem complicates the Unicode collation process slightly, requiring table lookups to reorder Thai characters for collation. Even if Unicode had adopted encoding according to spoken order, it would still be problematic to collate words in dictionary order. E.g., the word แสดง  [sa dɛːŋ] "perform" starts with a consonant cluster "สด" (with an inherent vowel for the consonant "ส"), the vowel แ-, in spoken order would come after the ด, but in a dictionary, the word is collated as it is written, with the vowel following the ส.

qas: question: How are characters with diacritical marks represented? 
answers: text: either as a single precomposed character or as a decomposed sequence of a base letter plus one or more non-spacing marks

question: What encoding does Charis SIL use? 
answers: text: Graphite, OpenType, or AAT technologies

question: What is the issue with underdots and their placement? 
answers: text: often be placed incorrectly

question: Characters with what marks can be displayed as a single character or a decomposed sequence? 
answers: text: diacritical marks

question: How should the characters with the macron and acute be displayed? 
answers: text: identically

question: What is the maximum number of non-spacing marks?

question: What romanization mark is rarely visually incorrect?

question: What is the name of the rendering technology OpenType uses?

question: What are rendered identically in practice?

question: Macrons are used only in what form of Idic?
context: Characters with diacritical marks can generally be represented either as a single precomposed character or as a decomposed sequence of a base letter plus one or more non-spacing marks. For example, ḗ (precomposed e with macron and acute above) and ḗ (e followed by the combining macron above and combining acute above) should be rendered identically, both appearing as an e with a macron and acute accent, but in practice, their appearance may vary depending upon what rendering engine and fonts are being used to display the characters. Similarly, underdots, as needed in the romanization of Indic, will often be placed incorrectly[citation needed]. Unicode characters that map to precomposed glyphs can be used in many cases, thus avoiding the problem, but where no precomposed character has been encoded the problem can often be solved by using a specialist Unicode font such as Charis SIL that uses Graphite, OpenType, or AAT technologies for advanced rendering features.