Question: How many sub-national entities have surpassed 100 million people in total?

Answer: six

Sichuan was China's most populous province before Chongqing became a directly-controlled municipality; it is currently the fourth most populous, after Guangdong, Shandong and Henan. As of 1832, Sichuan was the most populous of the 18 provinces in China, with an estimated population at that time of 21 million. It was the third most populous sub-national entity in the world, after Uttar Pradesh, India and the Russian Soviet Federative Socialist Republic until 1991, when the Soviet Union was dissolved. <hl> It is also one of the only six to ever reach 100 million people (Uttar Pradesh, Russian RSFSR, Maharashtra, Sichuan, Bihar and Punjab). <hl> It is currently 10th.

Sichuan was China's most populous province before Chongqing became a directly-controlled municipality; it is currently the fourth most populous, after Guangdong, Shandong and Henan. As of 1832, Sichuan was the most populous of the 18 provinces in China, with an estimated population at that time of 21 million. It was the third most populous sub-national entity in the world, after Uttar Pradesh, India and the Russian Soviet Federative Socialist Republic until 1991, when the Soviet Union was dissolved. It is also one of the only <hl> six <hl> to ever reach 100 million people (Uttar Pradesh, Russian RSFSR, Maharashtra, Sichuan, Bihar and Punjab). It is currently 10th.


Question: In what year was the Soviet Union disbanded?

Sichuan was China's most populous province before Chongqing became a directly-controlled municipality; it is currently the fourth most populous, after Guangdong, Shandong and Henan. As of 1832, Sichuan was the most populous of the 18 provinces in China, with an estimated population at that time of 21 million. It was the third most populous sub-national entity in the world, after Uttar Pradesh, India and the Russian Soviet Federative Socialist Republic until 1991, when the Soviet Union was dissolved. It is also one of the only six to ever reach 100 million people (Uttar Pradesh, Russian RSFSR, Maharashtra, Sichuan, Bihar and Punjab). It is currently 10th.

Answer: 1991

Sichuan was China's most populous province before Chongqing became a directly-controlled municipality; it is currently the fourth most populous, after Guangdong, Shandong and Henan. As of 1832, Sichuan was the most populous of the 18 provinces in China, with an estimated population at that time of 21 million. <hl> It was the third most populous sub-national entity in the world, after Uttar Pradesh, India and the Russian Soviet Federative Socialist Republic until 1991 , when the Soviet Union was dissolved. <hl> It is also one of the only six to ever reach 100 million people (Uttar Pradesh, Russian RSFSR, Maharashtra, Sichuan, Bihar and Punjab). It is currently 10th.

Sichuan was China's most populous province before Chongqing became a directly-controlled municipality; it is currently the fourth most populous, after Guangdong, Shandong and Henan. As of 1832, Sichuan was the most populous of the 18 provinces in China, with an estimated population at that time of 21 million. It was the third most populous sub-national entity in the world, after Uttar Pradesh, India and the Russian Soviet Federative Socialist Republic until <hl> 1991 <hl>, when the Soviet Union was dissolved. It is also one of the only six to ever reach 100 million people (Uttar Pradesh, Russian RSFSR, Maharashtra, Sichuan, Bihar and Punjab). It is currently 10th.

It was the third most populous sub-national entity in the world, after Uttar Pradesh, India and the Russian Soviet Federative Socialist Republic until <hl> 1991 <hl> , when the Soviet Union was dissolved.


Question: What are the largest minorities of western Sichuan?

Garzê Tibetan Autonomous Prefecture and Ngawa Tibetan and Qiang Autonomous Prefecture in western Sichuan are populated by Tibetans and Qiang people. Tibetans speak the Khams and Amdo Tibetan, which are Tibetic languages, as well as various Qiangic languages. The Qiang speak Qiangic languages and often Tibetic languages as well. The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the Nuosu language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in 1974. The Southwest University for Nationalities has one of China's most prominent Tibetology departments, and the Southwest Minorities Publishing House prints literature in minority languages. In the minority inhabited regions of Sichuan, there is bi-lingual signage and public school instruction in non-Mandarin minority languages.

Answer: Tibetans and Qiang

<hl> Garzê Tibetan Autonomous Prefecture and Ngawa Tibetan and Qiang Autonomous Prefecture in western Sichuan are populated by Tibetans and Qiang people. <hl> Tibetans speak the Khams and Amdo Tibetan, which are Tibetic languages, as well as various Qiangic languages. The Qiang speak Qiangic languages and often Tibetic languages as well. The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the Nuosu language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in 1974. The Southwest University for Nationalities has one of China's most prominent Tibetology departments, and the Southwest Minorities Publishing House prints literature in minority languages. In the minority inhabited regions of Sichuan, there is bi-lingual signage and public school instruction in non-Mandarin minority languages.

Garzê Tibetan Autonomous Prefecture and Ngawa Tibetan and Qiang Autonomous Prefecture in western Sichuan are populated by <hl> Tibetans and Qiang <hl> people. Tibetans speak the Khams and Amdo Tibetan, which are Tibetic languages, as well as various Qiangic languages. The Qiang speak Qiangic languages and often Tibetic languages as well. The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the Nuosu language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in 1974. The Southwest University for Nationalities has one of China's most prominent Tibetology departments, and the Southwest Minorities Publishing House prints literature in minority languages. In the minority inhabited regions of Sichuan, there is bi-lingual signage and public school instruction in non-Mandarin minority languages.


Question: What languages do Tibetans in Sichuan speak?

Answer: Khams and Amdo Tibetan

Garzê Tibetan Autonomous Prefecture and Ngawa Tibetan and Qiang Autonomous Prefecture in western Sichuan are populated by Tibetans and Qiang people. <hl> Tibetans speak the Khams and Amdo Tibetan , which are Tibetic languages, as well as various Qiangic languages. <hl> The Qiang speak Qiangic languages and often Tibetic languages as well. The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the Nuosu language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in 1974. The Southwest University for Nationalities has one of China's most prominent Tibetology departments, and the Southwest Minorities Publishing House prints literature in minority languages. In the minority inhabited regions of Sichuan, there is bi-lingual signage and public school instruction in non-Mandarin minority languages.

Garzê Tibetan Autonomous Prefecture and Ngawa Tibetan and Qiang Autonomous Prefecture in western Sichuan are populated by Tibetans and Qiang people. Tibetans speak the <hl> Khams and Amdo Tibetan <hl>, which are Tibetic languages, as well as various Qiangic languages. The Qiang speak Qiangic languages and often Tibetic languages as well. The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the Nuosu language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in 1974. The Southwest University for Nationalities has one of China's most prominent Tibetology departments, and the Southwest Minorities Publishing House prints literature in minority languages. In the minority inhabited regions of Sichuan, there is bi-lingual signage and public school instruction in non-Mandarin minority languages.

Tibetans speak the <hl> Khams and Amdo Tibetan <hl> , which are Tibetic languages, as well as various Qiangic languages.


Question: What language do the Yi people speak?

Answer: Nuosu

Garzê Tibetan Autonomous Prefecture and Ngawa Tibetan and Qiang Autonomous Prefecture in western Sichuan are populated by Tibetans and Qiang people. Tibetans speak the Khams and Amdo Tibetan, which are Tibetic languages, as well as various Qiangic languages. The Qiang speak Qiangic languages and often Tibetic languages as well. <hl> The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the Nuosu language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in 1974. <hl> The Southwest University for Nationalities has one of China's most prominent Tibetology departments, and the Southwest Minorities Publishing House prints literature in minority languages. In the minority inhabited regions of Sichuan, there is bi-lingual signage and public school instruction in non-Mandarin minority languages.

Garzê Tibetan Autonomous Prefecture and Ngawa Tibetan and Qiang Autonomous Prefecture in western Sichuan are populated by Tibetans and Qiang people. Tibetans speak the Khams and Amdo Tibetan, which are Tibetic languages, as well as various Qiangic languages. The Qiang speak Qiangic languages and often Tibetic languages as well. The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the <hl> Nuosu <hl> language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in 1974. The Southwest University for Nationalities has one of China's most prominent Tibetology departments, and the Southwest Minorities Publishing House prints literature in minority languages. In the minority inhabited regions of Sichuan, there is bi-lingual signage and public school instruction in non-Mandarin minority languages.


Question: In what year was the language of the Yi people standardized?

Answer: 1974

Garzê Tibetan Autonomous Prefecture and Ngawa Tibetan and Qiang Autonomous Prefecture in western Sichuan are populated by Tibetans and Qiang people. Tibetans speak the Khams and Amdo Tibetan, which are Tibetic languages, as well as various Qiangic languages. The Qiang speak Qiangic languages and often Tibetic languages as well. <hl> The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the Nuosu language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in 1974 . <hl> The Southwest University for Nationalities has one of China's most prominent Tibetology departments, and the Southwest Minorities Publishing House prints literature in minority languages. In the minority inhabited regions of Sichuan, there is bi-lingual signage and public school instruction in non-Mandarin minority languages.

Garzê Tibetan Autonomous Prefecture and Ngawa Tibetan and Qiang Autonomous Prefecture in western Sichuan are populated by Tibetans and Qiang people. Tibetans speak the Khams and Amdo Tibetan, which are Tibetic languages, as well as various Qiangic languages. The Qiang speak Qiangic languages and often Tibetic languages as well. The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the Nuosu language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in <hl> 1974 <hl>. The Southwest University for Nationalities has one of China's most prominent Tibetology departments, and the Southwest Minorities Publishing House prints literature in minority languages. In the minority inhabited regions of Sichuan, there is bi-lingual signage and public school instruction in non-Mandarin minority languages.

The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the Nuosu language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in <hl> 1974 <hl> .


Question: Which University houses one of China's most prominent Tibetology departments?

Answer: Southwest University for Nationalities

Garzê Tibetan Autonomous Prefecture and Ngawa Tibetan and Qiang Autonomous Prefecture in western Sichuan are populated by Tibetans and Qiang people. Tibetans speak the Khams and Amdo Tibetan, which are Tibetic languages, as well as various Qiangic languages. The Qiang speak Qiangic languages and often Tibetic languages as well. The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the Nuosu language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in 1974. <hl> The Southwest University for Nationalities has one of China's most prominent Tibetology departments, and the Southwest Minorities Publishing House prints literature in minority languages. <hl> In the minority inhabited regions of Sichuan, there is bi-lingual signage and public school instruction in non-Mandarin minority languages.

Garzê Tibetan Autonomous Prefecture and Ngawa Tibetan and Qiang Autonomous Prefecture in western Sichuan are populated by Tibetans and Qiang people. Tibetans speak the Khams and Amdo Tibetan, which are Tibetic languages, as well as various Qiangic languages. The Qiang speak Qiangic languages and often Tibetic languages as well. The Yi people of Liangshan Yi Autonomous Prefecture in southern Sichuan speak the Nuosu language, which is one of the Lolo-Burmese languages; Yi is written using the Yi script, a syllabary standardized in 1974. The <hl> Southwest University for Nationalities <hl> has one of China's most prominent Tibetology departments, and the Southwest Minorities Publishing House prints literature in minority languages. In the minority inhabited regions of Sichuan, there is bi-lingual signage and public school instruction in non-Mandarin minority languages.


Question: What was Unicode published as?

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.

Answer: The Unicode Standard

Unicode is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. <hl> 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. <hl> 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.

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 <hl> The Unicode Standard <hl>, 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.

Developed in conjunction with the Universal Coded Character Set (UCS) standard and published as <hl> The Unicode Standard <hl> , 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.


Question: What was unicode developed in conjunction with?

Answer: Universal Coded Character Set (UCS)

Unicode is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. <hl> 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. <hl> 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.

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 <hl> Universal Coded Character Set (UCS) <hl> 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.


Question: What is the most recent version of Unicode?

Answer: Unicode 8.0

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). <hl> As of June 2015[update], the most recent version is Unicode 8.0 . <hl> The standard is maintained by the Unicode Consortium.

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 <hl> Unicode 8.0 <hl>. The standard is maintained by the Unicode Consortium.

As of June 2015[update], the most recent version is <hl> Unicode 8.0 <hl> .


Question: Who maintains the Unicode Standard?

Answer: Unicode Consortium

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. <hl> The standard is maintained by the Unicode Consortium . <hl>

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 <hl> Unicode Consortium <hl>.

The standard is maintained by the <hl> Unicode Consortium <hl> .


Question: Unicode contains how many thousands of characters in its repertoire?

Answer: 120,000 characters

Unicode is a computing industry standard for the consistent encoding, representation, and handling of text expressed in most of the world's writing systems. <hl> 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. <hl> 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.

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 <hl> 120,000 characters <hl> 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.


Question: What are the most commonly used encodings of Unicode?

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.

Answer: UTF-8, UTF-16 and the now-obsolete UCS-2

Unicode can be implemented by different character encodings. <hl> The most commonly used encodings are UTF-8, UTF-16 and the now-obsolete UCS-2 . <hl> 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.

Unicode can be implemented by different character encodings. The most commonly used encodings are <hl> UTF-8, UTF-16 and the now-obsolete UCS-2 <hl>. 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.

The most commonly used encodings are <hl> UTF-8, UTF-16 and the now-obsolete UCS-2 <hl> .


Question: What does UTF-8 use in terms of bytes?

Answer: UTF-8 uses one byte for any ASCII character

Unicode can be implemented by different character encodings. The most commonly used encodings are UTF-8, UTF-16 and the now-obsolete UCS-2. <hl> 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. <hl> 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.

Unicode can be implemented by different character encodings. The most commonly used encodings are UTF-8, UTF-16 and the now-obsolete UCS-2. <hl> UTF-8 uses one byte for any ASCII character <hl>, 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.

<hl> UTF-8 uses one byte for any ASCII character <hl> , all of which have the same code values in both UTF-8 and ASCII encoding, and up to four bytes for other characters.


Question: What does UTF-16 expand?

Answer: UCS-2

Unicode can be implemented by different character encodings. <hl> The most commonly used encodings are UTF-8, UTF-16 and the now-obsolete UCS-2 . <hl> 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.

Unicode can be implemented by different character encodings. The most commonly used encodings are UTF-8, UTF-16 and the now-obsolete <hl> UCS-2 <hl>. 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.

The most commonly used encodings are UTF-8, UTF-16 and the now-obsolete <hl> UCS-2 <hl> .


Question: What type of code does UCS-2 use?

Answer: 16-bit code unit

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

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 <hl> 16-bit code unit <hl> (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.


Question: How are two 16-bit units used?

Answer: (4 × 8 bits

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

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 <hl> (4 × 8 bits <hl>) to handle each of the additional characters.

UTF-16 extends UCS-2, using one 16-bit unit for the characters that were representable in UCS-2 and two 16-bit units <hl> (4 × 8 bits <hl> ) to handle each of the additional characters.


Question: What is the aim of Unicode?

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

Answer: transcending the limitations of traditional character encodings

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

Unicode has the explicit aim of <hl> transcending the limitations of traditional character encodings <hl>, 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).

Unicode has the explicit aim of <hl> transcending the limitations of traditional character encodings <hl> , 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.


Question: Traditional character encodings don't allow what type of computer processing?

Answer: multilingual computer processing

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

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 <hl> multilingual computer processing <hl> (computer processing of arbitrary scripts mixed with each other).


Question: What is multilingual computer processing?

Answer: (computer processing of arbitrary scripts mixed with each other

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

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 <hl> (computer processing of arbitrary scripts mixed with each other <hl>).

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 <hl> (computer processing of arbitrary scripts mixed with each other <hl> )


Question: Bilingual computer processing uses what characters?

Answer: usually using Latin characters

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

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 (<hl> usually using Latin characters <hl> and the local script), but not multilingual computer processing (computer processing of arbitrary scripts mixed with each other).

Many traditional character encodings share a common problem in that they allow bilingual computer processing ( <hl> usually using Latin characters <hl> and the local script), but not multilingual computer processing (computer processing of arbitrary scripts mixed with each other).


Question: What is the major limitation of traditional character encodings?

Answer: wide usage in various countries of the world but remain largely incompatible with each other

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

Unicode has the explicit aim of transcending the limitations of traditional character encodings, such as those defined by the ISO 8859 standard, which find <hl> wide usage in various countries of the world but remain largely incompatible with each other <hl>. 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).

Unicode has the explicit aim of transcending the limitations of traditional character encodings, such as those defined by the ISO 8859 standard, which find <hl> wide usage in various countries of the world but remain largely incompatible with each other <hl> .


Question: What were the first 256 code points of Unicode made identical to?

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.

Answer: ISO-8859-1

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

The first 256 code points were made identical to the content of <hl> ISO-8859-1 <hl> 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.


Question: Why were the first 256 code points made identical to ISO-8859-1?

Answer: to make it trivial to convert existing western text

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

The first 256 code points were made identical to the content of ISO-8859-1 so as <hl> to make it trivial to convert existing western text <hl>. 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.

The first 256 code points were made identical to the content of ISO-8859-1 so as <hl> to make it trivial to convert existing western text <hl> .


Question: What does the "fullwidth forms" section of code points encompass?

Answer: a full Latin alphabet that is separate from the main Latin alphabet

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. <hl> 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. <hl> For other examples, see Duplicate characters in Unicode.

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 <hl> a full Latin alphabet that is separate from the main Latin alphabet <hl> 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.


Question: What are the CJK languages referenced?

Answer: Chinese, Japanese, and Korean

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. <hl> 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. <hl> For other examples, see Duplicate characters in Unicode.

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 <hl> Chinese, Japanese, and Korean <hl> (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.


Question: When was a surrogate character mechanism implemented in Unicode 2.0?

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.

Answer: 1996

<hl> In 1996 , a surrogate character mechanism was implemented in Unicode 2.0, so that Unicode was no longer restricted to 16 bits. <hl> 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.

In <hl> 1996 <hl>, 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.

In <hl> 1996 <hl> , a surrogate character mechanism was implemented in Unicode 2.0, so that Unicode was no longer restricted to 16 bits.


Question: Why was a surrogate character mechanism implemented?

Answer: so that Unicode was no longer restricted to 16 bits

<hl> In 1996, a surrogate character mechanism was implemented in Unicode 2.0, so that Unicode was no longer restricted to 16 bits . <hl> 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.

In 1996, a surrogate character mechanism was implemented in Unicode 2.0, <hl> so that Unicode was no longer restricted to 16 bits <hl>. 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.

In 1996, a surrogate character mechanism was implemented in Unicode 2.0, <hl> so that Unicode was no longer restricted to 16 bits <hl> .


Question: What are some characters not originally intended for Unicode?

Answer: rarely used Kanji or Chinese characters

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

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 <hl> rarely used Kanji or Chinese characters <hl>, 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.

Among the characters not originally intended for Unicode are <hl> rarely used Kanji or Chinese characters <hl> , 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.


Question: Why are some foreign characters rarely used?

Answer: many of which are part of personal and place names

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

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, <hl> many of which are part of personal and place names <hl>, making them rarely used, but much more essential than envisioned in the original architecture of Unicode.

Among the characters not originally intended for Unicode are rarely used Kanji or Chinese characters, <hl> many of which are part of personal and place names <hl> , making them rarely used, but much more essential than envisioned in the original architecture of Unicode.


Question: Why was the Unicode 2.0 codespace increased?

Answer: allowed for the encoding of many historic scripts

In 1996, a surrogate character mechanism was implemented in Unicode 2.0, so that Unicode was no longer restricted to 16 bits. <hl> 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. <hl> 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.

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 <hl> allowed for the encoding of many historic scripts <hl> (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.


Question: What are the General Categories of Unicode?

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:

Answer: Letter, Mark, Number, Punctuation, Symbol, Separator and Other

Each code point has a single General Category property. <hl> The major categories are: Letter, Mark, Number, Punctuation, Symbol, Separator and Other . <hl> 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:

Each code point has a single General Category property. The major categories are: <hl> Letter, Mark, Number, Punctuation, Symbol, Separator and Other <hl>. 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:

The major categories are: <hl> Letter, Mark, Number, Punctuation, Symbol, Separator and Other <hl> .


Question: What type of use is the General Category not helpful for?

Answer: not useful for every use, since legacy encodings have used multiple characteristics per single code point

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. <hl> The General Category is not useful for every use, since legacy encodings have used multiple characteristics per single code point . <hl> 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:

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 <hl> not useful for every use, since legacy encodings have used multiple characteristics per single code point <hl>. 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:

The General Category is <hl> not useful for every use, since legacy encodings have used multiple characteristics per single code point <hl> .


Question: What is the General Category in Unicode?

Answer: Other, Control

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. <hl> 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 ". <hl> Often, other properties must be used to specify the characteristics and behaviour of a code point. The possible General Categories are:

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 "<hl> Other, Control <hl>". Often, other properties must be used to specify the characteristics and behaviour of a code point. The possible General Categories are:

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 " <hl> Other, Control <hl> ".


Question: How many General Category properties does each code point have?

Answer: a single General Category property

<hl> Each code point has a single General Category property . <hl> 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:

Each code point has <hl> a single General Category property <hl>. 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:

Each code point has <hl> a single General Category property <hl> .


Question: What exists within the main Unicode categories?

Answer: subdivisions

Each code point has a single General Category property. The major categories are: Letter, Mark, Number, Punctuation, Symbol, Separator and Other. <hl> Within these categories, there are subdivisions . <hl> 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:

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 <hl> subdivisions <hl>. 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:

Within these categories, there are <hl> subdivisions <hl> .


Question: What are code points in the range U+D800-U+DBFF known as?

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.

Answer: high-surrogate code points

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

Code points in the range U+D800–U+DBFF (1,024 code points) are known as <hl> high-surrogate code points <hl>, 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.

Code points in the range U+D800–U+DBFF (1,024 code points) are known as <hl> high-surrogate code points <hl> , and code points in the range U+DC00–U+DFFF (1,024 code points) are known as low-surrogate code points.


Question: What are code points in the range U+DC00-U+DFFF known as?

Answer: low-surrogate code points

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

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 <hl> low-surrogate code points <hl>. 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.

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 <hl> low-surrogate code points <hl> .


Question: what is another name for a high-surrogate code point?

Answer: leading surrogate

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

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 <hl> leading surrogate <hl>) 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.

A high-surrogate code point (also known as a <hl> leading surrogate <hl> ) 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.


Question: what is another name for a low-surrogate code point?

Answer: trailing surrogate

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

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 <hl> trailing surrogate <hl>) 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.

A high-surrogate code point (also known as a leading surrogate) followed by a low-surrogate code point (also known as a <hl> trailing surrogate <hl> ) together form a surrogate pair used in UTF-16 to represent 1,048,576 code points outside BMP.


Question: What is known as a character's scalar value?

Answer: the range of code points that are available for use as characters

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. <hl> 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). <hl> The value of these code points (i.e., excluding surrogates) is sometimes referred to as the character's scalar value.

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 <hl> the range of code points that are available for use as characters <hl> 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.


Question: What is an ogonek?

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.

Answer: a dot above

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. <hl> 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. <hl> Unicode maintains a list of uniquely named character sequences for abstract characters that are not directly encoded in Unicode.

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, <hl> a dot above <hl>, 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.

For example, a Latin small letter "i" with an ogonek, <hl> a dot above <hl> , and an acute accent, which is required in Lithuanian, is represented by the character sequence U+012F, U+0307, U+0301.


Question: How does Unicode encode characters?

Answer: associating an abstract character with a particular code point

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. <hl> Unicode encodes characters by associating an abstract character with a particular code point . <hl> 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.

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 <hl> associating an abstract character with a particular code point <hl>. 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.

Unicode encodes characters by <hl> associating an abstract character with a particular code point <hl> .


Question: How are some abstract characters represented in Unicode?

Answer: a sequence of two or more characters

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

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 <hl> a sequence of two or more characters <hl>. 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.

However, not all abstract characters are encoded as a single Unicode character, and some abstract characters may be represented in Unicode by <hl> a sequence of two or more characters <hl> .


Question: What policy guaranteed that characters have a unique and immutable name?

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.

Answer: Name Stability policy

All graphic, format, and private use characters have a unique and immutable name by which they may be identified. <hl> This immutability has been guaranteed since Unicode version 2.0 by the Name Stability policy . <hl> 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.

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 <hl> Name Stability policy <hl>. 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.

This immutability has been guaranteed since Unicode version 2.0 by the <hl> Name Stability policy <hl> .


Question: What happens when a name is defective or misleading?

Answer: a formal alias may be defined

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

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, <hl> a formal alias may be defined <hl>, 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.

In cases where the name is seriously defective and misleading, or has a serious typographical error, <hl> a formal alias may be defined <hl> , and applications are encouraged to use the formal alias in place of the official character name.


Question: How long has this name immutability been guaranteed?

Answer: since Unicode version 2.0

All graphic, format, and private use characters have a unique and immutable name by which they may be identified. <hl> This immutability has been guaranteed since Unicode version 2.0 by the Name Stability policy. <hl> 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.

All graphic, format, and private use characters have a unique and immutable name by which they may be identified. This immutability has been guaranteed <hl> since Unicode version 2.0 <hl> 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.


Question: Who was Unicode developed in conjunction with?

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.

Answer: International Organization for Standardization

<hl> Unicode is developed in conjunction with the International Organization for Standardization and shares the character repertoire with ISO/IEC 10646: the Universal Character Set. <hl> 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.

Unicode is developed in conjunction with the <hl> International Organization for Standardization <hl> 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.


Question: What does Unicode share a character repertoire with?

Answer: the Universal Character Set

<hl> Unicode is developed in conjunction with the International Organization for Standardization and shares the character repertoire with ISO/IEC 10646: the Universal Character Set . <hl> 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.

Unicode is developed in conjunction with the International Organization for Standardization and shares the character repertoire with ISO/IEC 10646: <hl> the Universal Character Set <hl>. 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.

Unicode is developed in conjunction with the International Organization for Standardization and shares the character repertoire with ISO/IEC 10646: <hl> the Universal Character Set <hl> .


Question: What includes topics like bitwise encoding, collation, and rendering?

Answer: The Unicode Standard

Unicode is developed in conjunction with the International Organization for Standardization and shares the character repertoire with ISO/IEC 10646: the Universal Character Set. <hl> 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. <hl> The Unicode Standard enumerates a multitude of character properties, including those needed for supporting bidirectional text. The two standards do use slightly different terminology.

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 <hl> The Unicode Standard <hl> 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.


Question: What do the two standards differ in?

Answer: slightly different terminology

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. <hl> The two standards do use slightly different terminology . <hl>

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 <hl> slightly different terminology <hl>.

The two standards do use <hl> slightly different terminology <hl> .


Question: What does the print on demand, core version not include?

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.

Answer: any code charts or standard annexes

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

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 <hl> any code charts or standard annexes <hl>, but the entire standard, including the core specification, will still remain freely available on the Unicode website.

Unlike the previous major version printings of the Standard, the print-on-demand core specification does not include <hl> any code charts or standard annexes <hl> , but the entire standard, including the core specification, will still remain freely available on the Unicode website.


Question: When was the Unicode Standard first published?

Answer: 1991

<hl> The Consortium first published The Unicode Standard (ISBN 0-321-18578-1) in 1991 and continues to develop standards based on that original work. <hl> 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.

The Consortium first published The Unicode Standard (ISBN 0-321-18578-1) in <hl> 1991 <hl> 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.


Question: When was the latest version, Unicode 8.0, released?

Answer: June 2015

The Consortium first published The Unicode Standard (ISBN 0-321-18578-1) in 1991 and continues to develop standards based on that original work. <hl> The latest version of the standard, Unicode 8.0, was released in June 2015 and is available from the consortium's website. <hl> 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.

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 <hl> June 2015 <hl> 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.