gem_id
stringlengths 20
25
| id
stringlengths 24
24
| title
stringlengths 3
59
| context
stringlengths 151
3.71k
| question
stringlengths 1
270
| target
stringlengths 1
270
| references
list | answers
dict |
|---|---|---|---|---|---|---|---|
gem-squad_v2-train-102800
|
5727b28f2ca10214002d9432
|
Unicode
|
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.
|
Unicode contains how many thousands of characters in its repertoire?
|
Unicode contains how many thousands of characters in its repertoire?
|
[
"Unicode contains how many thousands of characters in its repertoire? "
] |
{
"text": [
"120,000 characters"
],
"answer_start": [
340
]
}
|
gem-squad_v2-train-102801
|
5acd0dff07355d001abf3290
|
Unicode
|
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.
|
What is the Universal Coded Character set published as?
|
What is the Universal Coded Character set published as?
|
[
"What is the Universal Coded Character set published as?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102802
|
5acd0dff07355d001abf3291
|
Unicode
|
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.
|
How many characters does Arabic have?
|
How many characters does Arabic have?
|
[
"How many characters does Arabic have?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102803
|
5acd0dff07355d001abf3292
|
Unicode
|
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.
|
How many scripts does UCS cover?
|
How many scripts does UCS cover?
|
[
"How many scripts does UCS cover?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102804
|
5acd0dff07355d001abf3293
|
Unicode
|
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.
|
What is the acronym for Unicode?
|
What is the acronym for Unicode?
|
[
"What is the acronym for Unicode?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102805
|
5acd0dff07355d001abf3294
|
Unicode
|
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.
|
What is an example of a left-to-right script?
|
What is an example of a left-to-right script?
|
[
"What is an example of a left-to-right script?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102806
|
5727b3022ca10214002d9438
|
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.
|
What are the most commonly used encodings of Unicode?
|
What are the most commonly used encodings of Unicode?
|
[
"What are the most commonly used encodings of Unicode?"
] |
{
"text": [
"UTF-8, UTF-16 and the now-obsolete UCS-2"
],
"answer_start": [
98
]
}
|
gem-squad_v2-train-102807
|
5727b3022ca10214002d9439
|
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.
|
What does UTF-8 use in terms of bytes?
|
What does UTF-8 use in terms of bytes?
|
[
"What does UTF-8 use in terms of bytes? "
] |
{
"text": [
"UTF-8 uses one byte for any ASCII character"
],
"answer_start": [
140
]
}
|
gem-squad_v2-train-102808
|
5727b3022ca10214002d943a
|
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.
|
What type of code does UCS-2 use?
|
What type of code does UCS-2 use?
|
[
"What type of code does UCS-2 use?"
] |
{
"text": [
"16-bit code unit"
],
"answer_start": [
314
]
}
|
gem-squad_v2-train-102809
|
5727b3022ca10214002d943b
|
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.
|
What does UTF-16 expand?
|
What does UTF-16 expand?
|
[
"What does UTF-16 expand? "
] |
{
"text": [
"UCS-2"
],
"answer_start": [
450
]
}
|
gem-squad_v2-train-102810
|
5727b3022ca10214002d943c
|
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.
|
How are two 16-bit units used?
|
How are two 16-bit units used?
|
[
"How are two 16-bit units used? "
] |
{
"text": [
"(4 × 8 bits"
],
"answer_start": [
552
]
}
|
gem-squad_v2-train-102811
|
5acd0ee707355d001abf32b8
|
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.
|
What are character encodings implemented by?
|
What are character encodings implemented by?
|
[
"What are character encodings implemented by?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102812
|
5acd0ee707355d001abf32b9
|
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.
|
Which two encodings are now obsolete?
|
Which two encodings are now obsolete?
|
[
"Which two encodings are now obsolete?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102813
|
5acd0ee707355d001abf32ba
|
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.
|
What did UCS-2 expand?
|
What did UCS-2 expand?
|
[
"What did UCS-2 expand?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102814
|
5acd0ee707355d001abf32bb
|
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.
|
How many ASCII characters are used to make one UTF-8?
|
How many ASCII characters are used to make one UTF-8?
|
[
"How many ASCII characters are used to make one UTF-8?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102815
|
5acd0ee707355d001abf32bc
|
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.
|
What system has a minimum of four bytes?
|
What system has a minimum of four bytes?
|
[
"What system has a minimum of four bytes?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102816
|
5727b3b72ca10214002d9448
|
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).
|
What is the aim of Unicode?
|
What is the aim of Unicode?
|
[
"What is the aim of Unicode?"
] |
{
"text": [
"transcending the limitations of traditional character encodings"
],
"answer_start": [
32
]
}
|
gem-squad_v2-train-102817
|
5727b3b72ca10214002d9449
|
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).
|
Traditional character encodings don't allow what type of computer processing?
|
Traditional character encodings don't allow what type of computer processing?
|
[
"Traditional character encodings don't allow what type of computer processing?"
] |
{
"text": [
"multilingual computer processing"
],
"answer_start": [
422
]
}
|
gem-squad_v2-train-102818
|
5727b3b72ca10214002d944a
|
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).
|
What is multilingual computer processing?
|
What is multilingual computer processing?
|
[
"What is multilingual computer processing?"
] |
{
"text": [
"(computer processing of arbitrary scripts mixed with each other"
],
"answer_start": [
455
]
}
|
gem-squad_v2-train-102819
|
5727b3b72ca10214002d944b
|
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).
|
Bilingual computer processing uses what characters?
|
Bilingual computer processing uses what characters?
|
[
"Bilingual computer processing uses what characters?"
] |
{
"text": [
"usually using Latin characters"
],
"answer_start": [
360
]
}
|
gem-squad_v2-train-102820
|
5727b3b72ca10214002d944c
|
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).
|
What is the major limitation of traditional character encodings?
|
What is the major limitation of traditional character encodings?
|
[
"What is the major limitation of traditional character encodings?"
] |
{
"text": [
"wide usage in various countries of the world but remain largely incompatible with each other"
],
"answer_start": [
156
]
}
|
gem-squad_v2-train-102821
|
5acd0faf07355d001abf32cc
|
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).
|
What was Unicode defined in?
|
What was Unicode defined in?
|
[
"What was Unicode defined in?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102822
|
5acd0faf07355d001abf32cd
|
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).
|
What characters does multilingual processors use?
|
What characters does multilingual processors use?
|
[
"What characters does multilingual processors use?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102823
|
5acd0faf07355d001abf32ce
|
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).
|
What type of encodings do not allow bilingual computer processing?
|
What type of encodings do not allow bilingual computer processing?
|
[
"What type of encodings do not allow bilingual computer processing?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102824
|
5acd0faf07355d001abf32cf
|
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).
|
What is the limitation of unicode globally?
|
What is the limitation of unicode globally?
|
[
"What is the limitation of unicode globally?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102825
|
5acd0faf07355d001abf32d0
|
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).
|
What are traditional character encodings attempting to surpass?
|
What are traditional character encodings attempting to surpass?
|
[
"What are traditional character encodings attempting to surpass?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102826
|
5727b735ff5b5019007d933e
|
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 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.
|
What were the first 256 code points of Unicode made identical to?
|
What were the first 256 code points of Unicode made identical to?
|
[
"What were the first 256 code points of Unicode made identical to? "
] |
{
"text": [
"ISO-8859-1"
],
"answer_start": [
64
]
}
|
gem-squad_v2-train-102827
|
5727b735ff5b5019007d933f
|
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 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.
|
Why were the first 256 code points made identical to ISO-8859-1?
|
Why were the first 256 code points made identical to ISO-8859-1?
|
[
"Why were the first 256 code points made identical to ISO-8859-1?"
] |
{
"text": [
"to make it trivial to convert existing western text"
],
"answer_start": [
81
]
}
|
gem-squad_v2-train-102828
|
5727b735ff5b5019007d9340
|
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 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.
|
What does the "fullwidth forms" section of code points encompass?
|
What does the "fullwidth forms" section of code points encompass?
|
[
"What does the \"fullwidth forms\" section of code points encompass?"
] |
{
"text": [
"a full Latin alphabet that is separate from the main Latin alphabet"
],
"answer_start": [
452
]
}
|
gem-squad_v2-train-102829
|
5727b735ff5b5019007d9341
|
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 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.
|
What are the CJK languages referenced?
|
What are the CJK languages referenced?
|
[
"What are the CJK languages referenced?"
] |
{
"text": [
"Chinese, Japanese, and Korean"
],
"answer_start": [
539
]
}
|
gem-squad_v2-train-102830
|
5acd10bc07355d001abf32f4
|
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 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.
|
What did ISO-8859-1 copy?
|
What did ISO-8859-1 copy?
|
[
"What did ISO-8859-1 copy?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102831
|
5acd10bc07355d001abf32f5
|
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 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.
|
Latin is what kind of language?
|
Latin is what kind of language?
|
[
"Latin is what kind of language?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102832
|
5acd10bc07355d001abf32f6
|
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 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.
|
What are Latin characters called when they are half width?
|
What are Latin characters called when they are half width?
|
[
"What are Latin characters called when they are half width?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102833
|
5acd10bc07355d001abf32f7
|
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 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.
|
Why do coders avoid duplicate characters?
|
Why do coders avoid duplicate characters?
|
[
"Why do coders avoid duplicate characters?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102834
|
5acd10bc07355d001abf32f8
|
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 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 256 initial points make it difficult to translate what kind of text?
|
The 256 initial points make it difficult to translate what kind of text?
|
[
"The 256 initial points make it difficult to translate what kind of text?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102835
|
5727b7c62ca10214002d94ae
|
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 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.
|
When was a surrogate character mechanism implemented in Unicode 2.0?
|
When was a surrogate character mechanism implemented in Unicode 2.0?
|
[
"When was a surrogate character mechanism implemented in Unicode 2.0?"
] |
{
"text": [
"1996"
],
"answer_start": [
3
]
}
|
gem-squad_v2-train-102836
|
5727b7c62ca10214002d94af
|
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 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.
|
Why was a surrogate character mechanism implemented?
|
Why was a surrogate character mechanism implemented?
|
[
"Why was a surrogate character mechanism implemented?"
] |
{
"text": [
"so that Unicode was no longer restricted to 16 bits"
],
"answer_start": [
73
]
}
|
gem-squad_v2-train-102837
|
5727b7c62ca10214002d94b0
|
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 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.
|
What are some characters not originally intended for Unicode?
|
What are some characters not originally intended for Unicode?
|
[
"What are some characters not originally intended for Unicode? "
] |
{
"text": [
"rarely used Kanji or Chinese characters"
],
"answer_start": [
443
]
}
|
gem-squad_v2-train-102838
|
5727b7c62ca10214002d94b1
|
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 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.
|
Why are some foreign characters rarely used?
|
Why are some foreign characters rarely used?
|
[
"Why are some foreign characters rarely used? "
] |
{
"text": [
"many of which are part of personal and place names"
],
"answer_start": [
484
]
}
|
gem-squad_v2-train-102839
|
5727b7c62ca10214002d94b2
|
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 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.
|
Why was the Unicode 2.0 codespace increased?
|
Why was the Unicode 2.0 codespace increased?
|
[
"Why was the Unicode 2.0 codespace increased? "
] |
{
"text": [
"allowed for the encoding of many historic scripts"
],
"answer_start": [
200
]
}
|
gem-squad_v2-train-102840
|
5acd118107355d001abf3326
|
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 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.
|
When was Unicode restricted to 16 bits?
|
When was Unicode restricted to 16 bits?
|
[
"When was Unicode restricted to 16 bits?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102841
|
5acd118107355d001abf3327
|
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 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.
|
What types of egyptian hieroglyphs are rarely used?
|
What types of egyptian hieroglyphs are rarely used?
|
[
"What types of egyptian hieroglyphs are rarely used?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102842
|
5acd118107355d001abf3328
|
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 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.
|
What are the extra Unicode characters called?
|
What are the extra Unicode characters called?
|
[
"What are the extra Unicode characters called?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102843
|
5acd118107355d001abf3329
|
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 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.
|
What types of characters were removed with Unicode 2.0?
|
What types of characters were removed with Unicode 2.0?
|
[
"What types of characters were removed with Unicode 2.0?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102844
|
5acd118107355d001abf332a
|
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 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.
|
What was removed in 1996?
|
What was removed in 1996?
|
[
"What was removed in 1996?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102845
|
5727dfedff5b5019007d9740
|
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:
|
What are the General Categories of Unicode?
|
What are the General Categories of Unicode?
|
[
"What are the General Categories of Unicode?"
] |
{
"text": [
"Letter, Mark, Number, Punctuation, Symbol, Separator and Other"
],
"answer_start": [
82
]
}
|
gem-squad_v2-train-102846
|
5727dfedff5b5019007d9741
|
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:
|
What type of use is the General Category not helpful for?
|
What type of use is the General Category not helpful for?
|
[
"What type of use is the General Category not helpful for?"
] |
{
"text": [
"not useful for every use, since legacy encodings have used multiple characteristics per single code point"
],
"answer_start": [
219
]
}
|
gem-squad_v2-train-102847
|
5727dfedff5b5019007d9742
|
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:
|
What is the General Category in Unicode?
|
What is the General Category in Unicode?
|
[
"What is the General Category in Unicode?"
] |
{
"text": [
"Other, Control"
],
"answer_start": [
460
]
}
|
gem-squad_v2-train-102848
|
5727dfedff5b5019007d9743
|
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:
|
How many General Category properties does each code point have?
|
How many General Category properties does each code point have?
|
[
"How many General Category properties does each code point have?"
] |
{
"text": [
"a single General Category property"
],
"answer_start": [
20
]
}
|
gem-squad_v2-train-102849
|
5727dfedff5b5019007d9744
|
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:
|
What exists within the main Unicode categories?
|
What exists within the main Unicode categories?
|
[
"What exists within the main Unicode categories? "
] |
{
"text": [
"subdivisions"
],
"answer_start": [
181
]
}
|
gem-squad_v2-train-102850
|
5acd126d07355d001abf334c
|
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:
|
What subcategories are found in the category Other?
|
What subcategories are found in the category Other?
|
[
"What subcategories are found in the category Other?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102851
|
5acd126d07355d001abf334d
|
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:
|
Which category can always be used?
|
Which category can always be used?
|
[
"Which category can always be used?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102852
|
5acd126d07355d001abf334e
|
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:
|
Why is Symbol not useful for all instances?
|
Why is Symbol not useful for all instances?
|
[
"Why is Symbol not useful for all instances?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102853
|
5acd126d07355d001abf334f
|
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:
|
What is the title of the Separator category in Unicode?
|
What is the title of the Separator category in Unicode?
|
[
"What is the title of the Separator category in Unicode?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102854
|
5acd126d07355d001abf3350
|
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:
|
"Other, Symbol" represents what unicode category?
|
"Other, Symbol" represents what unicode category?
|
[
"\"Other, Symbol\" represents what unicode category?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102855
|
5727e25f3acd2414000deef7
|
Unicode
|
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.
|
What are code points in the range U+D800-U+DBFF known as?
|
What are code points in the range U+D800-U+DBFF known as?
|
[
"What are code points in the range U+D800-U+DBFF known as? "
] |
{
"text": [
"high-surrogate code points"
],
"answer_start": [
72
]
}
|
gem-squad_v2-train-102856
|
5727e25f3acd2414000deef8
|
Unicode
|
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.
|
What are code points in the range U+DC00-U+DFFF known as?
|
What are code points in the range U+DC00-U+DFFF known as?
|
[
"What are code points in the range U+DC00-U+DFFF known as? "
] |
{
"text": [
"low-surrogate code points"
],
"answer_start": [
176
]
}
|
gem-squad_v2-train-102857
|
5727e25f3acd2414000deef9
|
Unicode
|
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.
|
what is another name for a high-surrogate code point?
|
what is another name for a high-surrogate code point?
|
[
"what is another name for a high-surrogate code point? "
] |
{
"text": [
"leading surrogate"
],
"answer_start": [
248
]
}
|
gem-squad_v2-train-102858
|
5727e25f3acd2414000deefa
|
Unicode
|
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.
|
what is another name for a low-surrogate code point?
|
what is another name for a low-surrogate code point?
|
[
"what is another name for a low-surrogate code point? "
] |
{
"text": [
"trailing surrogate"
],
"answer_start": [
323
]
}
|
gem-squad_v2-train-102859
|
5727e25f3acd2414000deefb
|
Unicode
|
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.
|
What is known as a character's scalar value?
|
What is known as a character's scalar value?
|
[
"What is known as a character's scalar value? "
] |
{
"text": [
"the range of code points that are available for use as characters"
],
"answer_start": [
506
]
}
|
gem-squad_v2-train-102860
|
5acd131507355d001abf3368
|
Unicode
|
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.
|
What is a low-surrogate followed by a high-surrogate called?
|
What is a low-surrogate followed by a high-surrogate called?
|
[
"What is a low-surrogate followed by a high-surrogate called?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102861
|
5acd131507355d001abf3369
|
Unicode
|
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.
|
What is another name for a surrogate pair?
|
What is another name for a surrogate pair?
|
[
"What is another name for a surrogate pair?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102862
|
5acd131507355d001abf336a
|
Unicode
|
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.
|
How many points are represented inside of BMP?
|
How many points are represented inside of BMP?
|
[
"How many points are represented inside of BMP?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102863
|
5acd131507355d001abf336b
|
Unicode
|
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.
|
Which kinds of code points are valid by themselves?
|
Which kinds of code points are valid by themselves?
|
[
"Which kinds of code points are valid by themselves?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102864
|
5acd131507355d001abf336c
|
Unicode
|
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.
|
What is the individual number of code points called?
|
What is the individual number of code points called?
|
[
"What is the individual number of code points called?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102865
|
5727e7e12ca10214002d992e
|
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, 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.
|
What is an ogonek?
|
What is an ogonek?
|
[
"What is an ogonek? "
] |
{
"text": [
"a dot above"
],
"answer_start": [
495
]
}
|
gem-squad_v2-train-102866
|
5727e7e12ca10214002d992f
|
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, 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.
|
How does Unicode encode characters?
|
How does Unicode encode characters?
|
[
"How does Unicode encode characters?"
] |
{
"text": [
"associating an abstract character with a particular code point"
],
"answer_start": [
197
]
}
|
gem-squad_v2-train-102867
|
5727e7e12ca10214002d9930
|
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, 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.
|
How are some abstract characters represented in Unicode?
|
How are some abstract characters represented in Unicode?
|
[
"How are some abstract characters represented in Unicode?"
] |
{
"text": [
"a sequence of two or more characters"
],
"answer_start": [
403
]
}
|
gem-squad_v2-train-102868
|
5acd142f07355d001abf3390
|
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, 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.
|
What is another name for an acute accent?
|
What is another name for an acute accent?
|
[
"What is another name for an acute accent?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102869
|
5acd142f07355d001abf3391
|
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, 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.
|
What does Latin require?
|
What does Latin require?
|
[
"What does Latin require?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102870
|
5acd142f07355d001abf3392
|
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, 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.
|
What are format characters associated with?
|
What are format characters associated with?
|
[
"What are format characters associated with?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102871
|
5acd142f07355d001abf3393
|
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, 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.
|
What do sets of graphic characters directly correspond to?
|
What do sets of graphic characters directly correspond to?
|
[
"What do sets of graphic characters directly correspond to?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102872
|
5acd142f07355d001abf3394
|
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, 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.
|
What are all encoded as singular unicode characters?
|
What are all encoded as singular unicode characters?
|
[
"What are all encoded as singular unicode characters?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102873
|
5727e8362ca10214002d9934
|
Unicode
|
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.
|
What policy guaranteed that characters have a unique and immutable name?
|
What policy guaranteed that characters have a unique and immutable name?
|
[
"What policy guaranteed that characters have a unique and immutable name?"
] |
{
"text": [
"Name Stability policy"
],
"answer_start": [
185
]
}
|
gem-squad_v2-train-102874
|
5727e8362ca10214002d9935
|
Unicode
|
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.
|
What happens when a name is defective or misleading?
|
What happens when a name is defective or misleading?
|
[
"What happens when a name is defective or misleading?"
] |
{
"text": [
"a formal alias may be defined"
],
"answer_start": [
309
]
}
|
gem-squad_v2-train-102875
|
5727e8362ca10214002d9936
|
Unicode
|
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.
|
How long has this name immutability been guaranteed?
|
How long has this name immutability been guaranteed?
|
[
"How long has this name immutability been guaranteed? "
] |
{
"text": [
"since Unicode version 2.0"
],
"answer_start": [
152
]
}
|
gem-squad_v2-train-102876
|
5acd157607355d001abf33de
|
Unicode
|
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.
|
What policy identified misleading characters?
|
What policy identified misleading characters?
|
[
"What policy identified misleading characters?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102877
|
5acd157607355d001abf33df
|
Unicode
|
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.
|
When an error is found, what is used in place of a formal alias?
|
When an error is found, what is used in place of a formal alias?
|
[
"When an error is found, what is used in place of a formal alias?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102878
|
5acd157607355d001abf33e0
|
Unicode
|
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.
|
When was the formal alias yi created?
|
When was the formal alias yi created?
|
[
"When was the formal alias yi created?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102879
|
5acd157607355d001abf33e1
|
Unicode
|
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.
|
What is an example of a symbol that does not use a formal alias?
|
What is an example of a symbol that does not use a formal alias?
|
[
"What is an example of a symbol that does not use a formal alias?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102880
|
5acd157607355d001abf33e2
|
Unicode
|
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.
|
Which types of characters do not have unique names?
|
Which types of characters do not have unique names?
|
[
"Which types of characters do not have unique names?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102881
|
5727e8cc4b864d1900163fcc
|
Unicode
|
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.
|
Who was Unicode developed in conjunction with?
|
Who was Unicode developed in conjunction with?
|
[
"Who was Unicode developed in conjunction with?"
] |
{
"text": [
"International Organization for Standardization"
],
"answer_start": [
45
]
}
|
gem-squad_v2-train-102882
|
5727e8cc4b864d1900163fcd
|
Unicode
|
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.
|
What does Unicode share a character repertoire with?
|
What does Unicode share a character repertoire with?
|
[
"What does Unicode share a character repertoire with?"
] |
{
"text": [
"the Universal Character Set"
],
"answer_start": [
148
]
}
|
gem-squad_v2-train-102883
|
5727e8cc4b864d1900163fce
|
Unicode
|
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.
|
What includes topics like bitwise encoding, collation, and rendering?
|
What includes topics like bitwise encoding, collation, and rendering?
|
[
"What includes topics like bitwise encoding, collation, and rendering?"
] |
{
"text": [
"The Unicode Standard"
],
"answer_start": [
253
]
}
|
gem-squad_v2-train-102884
|
5727e8cc4b864d1900163fcf
|
Unicode
|
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.
|
What do the two standards differ in?
|
What do the two standards differ in?
|
[
"What do the two standards differ in? "
] |
{
"text": [
"slightly different terminology"
],
"answer_start": [
551
]
}
|
gem-squad_v2-train-102885
|
5acd15fa07355d001abf3404
|
Unicode
|
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.
|
Who created the character repertoire for IOS/IEC 10646?
|
Who created the character repertoire for IOS/IEC 10646?
|
[
"Who created the character repertoire for IOS/IEC 10646?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102886
|
5acd15fa07355d001abf3405
|
Unicode
|
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.
|
What is another name for Unicode?
|
What is another name for Unicode?
|
[
"What is another name for Unicode?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102887
|
5acd15fa07355d001abf3406
|
Unicode
|
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.
|
What is developed alongside the UCS?
|
What is developed alongside the UCS?
|
[
"What is developed alongside the UCS?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102888
|
5acd15fa07355d001abf3407
|
Unicode
|
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.
|
Unicode has more information regarding what?
|
Unicode has more information regarding what?
|
[
"Unicode has more information regarding what?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102889
|
5acd15fa07355d001abf3408
|
Unicode
|
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.
|
What have different character repertoires?
|
What have different character repertoires?
|
[
"What have different character repertoires?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102890
|
5727e93b4b864d1900163fd4
|
Unicode
|
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.
|
When was the Unicode Standard first published?
|
When was the Unicode Standard first published?
|
[
"When was the Unicode Standard first published? "
] |
{
"text": [
"1991"
],
"answer_start": [
76
]
}
|
gem-squad_v2-train-102891
|
5727e93b4b864d1900163fd5
|
Unicode
|
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.
|
When was the latest version, Unicode 8.0, released?
|
When was the latest version, Unicode 8.0, released?
|
[
"When was the latest version, Unicode 8.0, released?"
] |
{
"text": [
"June 2015"
],
"answer_start": [
210
]
}
|
gem-squad_v2-train-102892
|
5727e93b4b864d1900163fd6
|
Unicode
|
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.
|
What was the last major version of Unicode to be published in book form?
|
What was the last major version of Unicode to be published in book form?
|
[
"What was the last major version of Unicode to be published in book form? "
] |
{
"text": [
"Unicode 5.0"
],
"answer_start": [
347
]
}
|
gem-squad_v2-train-102893
|
5727e93b4b864d1900163fd7
|
Unicode
|
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.
|
What year was it announced that only the core specification for Unicode would be printed in physical form?
|
What year was it announced that only the core specification for Unicode would be printed in physical form?
|
[
"What year was it announced that only the core specification for Unicode would be printed in physical form?"
] |
{
"text": [
"2012"
],
"answer_start": [
479
]
}
|
gem-squad_v2-train-102894
|
5727e93b4b864d1900163fd8
|
Unicode
|
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.
|
What does the print on demand, core version not include?
|
What does the print on demand, core version not include?
|
[
"What does the print on demand, core version not include? "
] |
{
"text": [
"any code charts or standard annexes"
],
"answer_start": [
750
]
}
|
gem-squad_v2-train-102895
|
5acd1b1d07355d001abf3542
|
Unicode
|
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.
|
When was the Consortium founded?
|
When was the Consortium founded?
|
[
"When was the Consortium founded?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102896
|
5acd1b1d07355d001abf3543
|
Unicode
|
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.
|
What month did the Consortium first publish Unicode?
|
What month did the Consortium first publish Unicode?
|
[
"What month did the Consortium first publish Unicode?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102897
|
5acd1b1d07355d001abf3544
|
Unicode
|
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.
|
When was it announced that Unicode would no longer be available in book form?
|
When was it announced that Unicode would no longer be available in book form?
|
[
"When was it announced that Unicode would no longer be available in book form?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102898
|
5acd1b1d07355d001abf3545
|
Unicode
|
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.
|
How many pages was the original Unicode standard?
|
How many pages was the original Unicode standard?
|
[
"How many pages was the original Unicode standard?"
] |
{
"text": [],
"answer_start": []
}
|
gem-squad_v2-train-102899
|
5acd1b1d07355d001abf3546
|
Unicode
|
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.
|
What extra sections are not included on the Unicode website?
|
What extra sections are not included on the Unicode website?
|
[
"What extra sections are not included on the Unicode website?"
] |
{
"text": [],
"answer_start": []
}
|
Subsets and Splits
No community queries yet
The top public SQL queries from the community will appear here once available.