Difference between revisions of "cpp/string/multibyte"
From cppreference.com
m (Update links.) |
Andreas Krug (Talk | contribs) m (fmt) |
||
| (7 intermediate revisions by 6 users not shown) | |||
| Line 4: | Line 4: | ||
A null-terminated multibyte string (NTMBS), or "multibyte string", is a sequence of nonzero bytes followed by a byte with value zero (the terminating null character). | A null-terminated multibyte string (NTMBS), or "multibyte string", is a sequence of nonzero bytes followed by a byte with value zero (the terminating null character). | ||
| − | Each character stored in the string may occupy more than one byte. The encoding used to represent characters in a multibyte character string is locale-specific: it may be UTF-8, GB18030, EUC-JP, Shift-JIS, etc. For example, the char array {{c|{'\xe4','\xbd','\xa0','\xe5','\xa5','\xbd','\0'}}} is an NTMBS holding the string {{c|"你好"}} in UTF-8 multibyte encoding: the first three bytes encode the character 你, the next three bytes encode the character 好. The same string encoded in GB18030 is the char array {{c|{'\xc4', '\xe3', '\xba', '\xc3', '\0'}}}, where each of the two characters is encoded as a two-byte sequence. | + | Each character stored in the string may occupy more than one byte. The encoding used to represent characters in a multibyte character string is locale-specific: it may be UTF-8, GB18030, EUC-JP, Shift-JIS, etc. For example, the char array {{c|{'\xe4','\xbd','\xa0','\xe5','\xa5','\xbd','\0'}<!---->}} is an NTMBS holding the string {{c|"你好"}} in UTF-8 multibyte encoding: the first three bytes encode the character 你, the next three bytes encode the character 好. The same string encoded in GB18030 is the char array {{c|{'\xc4', '\xe3', '\xba', '\xc3', '\0'}<!---->}}, where each of the two characters is encoded as a two-byte sequence. |
| − | In some multibyte encodings, any given multibyte character sequence may represent different characters depending on the previous byte sequences, known as "shift sequences". Such encodings are known as state-dependent: knowledge of the current shift state is required to interpret each character. An NTMBS is only valid if it begins and ends in the initial shift state: if a shift sequence was used, the corresponding unshift sequence has to be present before the terminating null character. Examples of such encodings are the 7-bit JIS, BOCU-1 and SCSU. | + | In some multibyte encodings, any given multibyte character sequence may represent different characters depending on the previous byte sequences, known as "shift sequences". Such encodings are known as state-dependent: knowledge of the current shift state is required to interpret each character. An NTMBS is only valid if it begins and ends in the initial shift state: if a shift sequence was used, the corresponding unshift sequence has to be present before the terminating null character. Examples of such encodings are the 7-bit JIS, BOCU-1 and [https://www.unicode.org/reports/tr6 SCSU]. |
A multibyte character string is layout-compatible with null-terminated byte string (NTBS), that is, can be stored, copied, and examined using the same facilities, except for calculating the number of characters. If the correct locale is in effect, I/O functions also handle multibyte strings. Multibyte strings can be converted to and from wide strings using the {{lc|std::codecvt}} member functions, {{lc|std::wstring_convert}}, or the following locale-dependent conversion functions: | A multibyte character string is layout-compatible with null-terminated byte string (NTBS), that is, can be stored, copied, and examined using the same facilities, except for calculating the number of characters. If the correct locale is in effect, I/O functions also handle multibyte strings. Multibyte strings can be converted to and from wide strings using the {{lc|std::codecvt}} member functions, {{lc|std::wstring_convert}}, or the following locale-dependent conversion functions: | ||
| Line 12: | Line 12: | ||
===Multibyte/wide character conversions=== | ===Multibyte/wide character conversions=== | ||
{{dsc begin}} | {{dsc begin}} | ||
| − | {{dsc header | cstdlib}} | + | {{dsc header|cstdlib}} |
| − | {{dsc inc | cpp/string/multibyte/dsc mblen}} | + | {{dsc inc|cpp/string/multibyte/dsc mblen}} |
| − | {{dsc inc | cpp/string/multibyte/dsc mbtowc}} | + | {{dsc inc|cpp/string/multibyte/dsc mbtowc}} |
| − | {{dsc inc | cpp/string/multibyte/dsc wctomb}} | + | {{dsc inc|cpp/string/multibyte/dsc wctomb}} |
| − | {{dsc inc | cpp/string/multibyte/dsc mbstowcs}} | + | {{dsc inc|cpp/string/multibyte/dsc mbstowcs}} |
| − | {{dsc inc | cpp/string/multibyte/dsc wcstombs}} | + | {{dsc inc|cpp/string/multibyte/dsc wcstombs}} |
| − | {{dsc header | cwchar}} | + | {{dsc header|cwchar}} |
| − | {{dsc inc | cpp/string/multibyte/dsc mbsinit}} | + | {{dsc inc|cpp/string/multibyte/dsc mbsinit}} |
| − | {{dsc inc | cpp/string/multibyte/dsc btowc}} | + | {{dsc inc|cpp/string/multibyte/dsc btowc}} |
| − | {{dsc inc | cpp/string/multibyte/dsc wctob}} | + | {{dsc inc|cpp/string/multibyte/dsc wctob}} |
| − | {{dsc inc | cpp/string/multibyte/dsc mbrlen}} | + | {{dsc inc|cpp/string/multibyte/dsc mbrlen}} |
| − | {{dsc inc | cpp/string/multibyte/dsc mbrtowc}} | + | {{dsc inc|cpp/string/multibyte/dsc mbrtowc}} |
| − | {{dsc inc | cpp/string/multibyte/dsc wcrtomb}} | + | {{dsc inc|cpp/string/multibyte/dsc wcrtomb}} |
| − | {{dsc inc | cpp/string/multibyte/dsc mbsrtowcs}} | + | {{dsc inc|cpp/string/multibyte/dsc mbsrtowcs}} |
| − | {{dsc inc | cpp/string/multibyte/dsc wcsrtombs}} | + | {{dsc inc|cpp/string/multibyte/dsc wcsrtombs}} |
| − | {{dsc header | cuchar}} | + | {{dsc header|cuchar}} |
| − | {{dsc inc | cpp/string/multibyte/dsc mbrtoc16}} | + | {{dsc inc|cpp/string/multibyte/dsc mbrtoc8}} |
| − | {{dsc inc | cpp/string/multibyte/dsc c16rtomb}} | + | {{dsc inc|cpp/string/multibyte/dsc c8rtomb}} |
| − | {{dsc inc | cpp/string/multibyte/dsc mbrtoc32}} | + | {{dsc inc|cpp/string/multibyte/dsc mbrtoc16}} |
| − | {{dsc inc | cpp/string/multibyte/dsc c32rtomb}} | + | {{dsc inc|cpp/string/multibyte/dsc c16rtomb}} |
| + | {{dsc inc|cpp/string/multibyte/dsc mbrtoc32}} | ||
| + | {{dsc inc|cpp/string/multibyte/dsc c32rtomb}} | ||
{{dsc end}} | {{dsc end}} | ||
===Types=== | ===Types=== | ||
{{dsc begin}} | {{dsc begin}} | ||
| − | {{dsc header | cwchar}} | + | {{dsc header|cwchar}} |
| − | {{dsc inc | cpp/string/multibyte/dsc mbstate_t}} | + | {{dsc inc|cpp/string/multibyte/dsc mbstate_t}} |
{{dsc end}} | {{dsc end}} | ||
===Macros=== | ===Macros=== | ||
{{dsc begin}} | {{dsc begin}} | ||
| − | {{dsc header | climits}} | + | {{dsc header|climits}} |
| − | {{dsc inc | cpp/string/multibyte/dsc MB_LEN_MAX}} | + | {{dsc inc|cpp/string/multibyte/dsc MB_LEN_MAX}} |
| − | {{dsc header | cstdlib}} | + | {{dsc header|cstdlib}} |
| − | {{dsc inc | cpp/string/multibyte/dsc MB_CUR_MAX}} | + | {{dsc inc|cpp/string/multibyte/dsc MB_CUR_MAX}} |
| − | {{dsc header | cuchar}} | + | {{dsc header|cuchar}} |
| − | {{dsc macro const | __STDC_UTF_16__ | | + | {{dsc macro const|__STDC_UTF_16__|notes={{mark c++11}}|nolink=true|indicates that UTF-16 encoding is used by mbrtoc16 and c16rtomb}} |
| − | {{dsc macro const | __STDC_UTF_32__ | | + | {{dsc macro const|__STDC_UTF_32__|notes={{mark c++11}}|nolink=true|indicates that UTF-32 encoding is used by mbrtoc32 and c32rtomb}} |
{{dsc end}} | {{dsc end}} | ||
| − | + | ===See also=== | |
| − | + | {{dsc begin}} | |
| − | + | {{dsc see c|c/string/multibyte|Null-terminated multibyte strings}} | |
| − | + | {{dsc end}} | |
| − | + | ||
| − | + | {{langlinks|de|es|fr|it|ja|pt|ru|zh}} | |
| − | + | ||
| − | + | ||
Latest revision as of 04:48, 26 December 2023
A null-terminated multibyte string (NTMBS), or "multibyte string", is a sequence of nonzero bytes followed by a byte with value zero (the terminating null character).
Each character stored in the string may occupy more than one byte. The encoding used to represent characters in a multibyte character string is locale-specific: it may be UTF-8, GB18030, EUC-JP, Shift-JIS, etc. For example, the char array {'\xe4','\xbd','\xa0','\xe5','\xa5','\xbd','\0'} is an NTMBS holding the string "你好" in UTF-8 multibyte encoding: the first three bytes encode the character 你, the next three bytes encode the character 好. The same string encoded in GB18030 is the char array {'\xc4', '\xe3', '\xba', '\xc3', '\0'}, where each of the two characters is encoded as a two-byte sequence.
In some multibyte encodings, any given multibyte character sequence may represent different characters depending on the previous byte sequences, known as "shift sequences". Such encodings are known as state-dependent: knowledge of the current shift state is required to interpret each character. An NTMBS is only valid if it begins and ends in the initial shift state: if a shift sequence was used, the corresponding unshift sequence has to be present before the terminating null character. Examples of such encodings are the 7-bit JIS, BOCU-1 and SCSU.
A multibyte character string is layout-compatible with null-terminated byte string (NTBS), that is, can be stored, copied, and examined using the same facilities, except for calculating the number of characters. If the correct locale is in effect, I/O functions also handle multibyte strings. Multibyte strings can be converted to and from wide strings using the std::codecvt member functions, std::wstring_convert, or the following locale-dependent conversion functions:
Contents |
[edit] Multibyte/wide character conversions
| Defined in header
<cstdlib> | |
| returns the number of bytes in the next multibyte character (function) | |
| converts the next multibyte character to wide character (function) | |
| converts a wide character to its multibyte representation (function) | |
| converts a narrow multibyte character string to wide string (function) | |
| converts a wide string to narrow multibyte character string (function) | |
| Defined in header
<cwchar> | |
| checks if the std::mbstate_t object represents initial shift state (function) | |
| widens a single-byte narrow character to wide character, if possible (function) | |
| narrows a wide character to a single-byte narrow character, if possible (function) | |
| returns the number of bytes in the next multibyte character, given state (function) | |
| converts the next multibyte character to wide character, given state (function) | |
| converts a wide character to its multibyte representation, given state (function) | |
| converts a narrow multibyte character string to wide string, given state (function) | |
| converts a wide string to narrow multibyte character string, given state (function) | |
| Defined in header
<cuchar> | |
| (C++20) |
converts a narrow multibyte character to UTF-8 encoding (function) |
| (C++20) |
converts UTF-8 string to narrow multibyte encoding (function) |
| (C++11) |
converts a narrow multibyte character to UTF-16 encoding (function) |
| (C++11) |
convert a 16-bit wide character to narrow multibyte string (function) |
| (C++11) |
converts a narrow multibyte character to UTF-32 encoding (function) |
| (C++11) |
convert a 32-bit wide character to narrow multibyte string (function) |
[edit] Types
| Defined in header
<cwchar> | |
| conversion state information necessary to iterate multibyte character strings (class) | |
[edit] Macros
| Defined in header
<climits> | |
| MB_LEN_MAX |
maximum number of bytes in a multibyte character (macro constant) |
| Defined in header
<cstdlib> | |
| MB_CUR_MAX |
maximum number of bytes in a multibyte character in the current C locale (macro variable) |
| Defined in header
<cuchar> | |
| __STDC_UTF_16__ (C++11) |
indicates that UTF-16 encoding is used by mbrtoc16 and c16rtomb (macro constant) |
| __STDC_UTF_32__ (C++11) |
indicates that UTF-32 encoding is used by mbrtoc32 and c32rtomb (macro constant) |
[edit] See also
| C documentation for Null-terminated multibyte strings
|
