tmp/tmpknw48wsh/{from.md → to.md}
RENAMED
|
@@ -1,7 +1,9 @@
|
|
| 1 |
## Deprecated standard code conversion facets <a id="depr.locale.stdcvt">[[depr.locale.stdcvt]]</a>
|
| 2 |
|
|
|
|
|
|
|
| 3 |
The header `<codecvt>` provides code conversion facets for various
|
| 4 |
character encodings.
|
| 5 |
|
| 6 |
### Header `<codecvt>` synopsis <a id="depr.codecvt.syn">[[depr.codecvt.syn]]</a>
|
| 7 |
|
|
@@ -53,24 +55,26 @@ For each of the three code conversion facets `codecvt_utf8`,
|
|
| 53 |
header sequence when writing a multibyte sequence to advertise the
|
| 54 |
endianness of the subsequent multibyte sequence to be written.
|
| 55 |
- If `(Mode & little_endian)`, the facet shall generate a multibyte
|
| 56 |
sequence in little-endian order, as opposed to the default big-endian
|
| 57 |
order.
|
|
|
|
|
|
|
| 58 |
|
| 59 |
For the facet `codecvt_utf8`:
|
| 60 |
|
| 61 |
- The facet shall convert between UTF-8 multibyte sequences and UCS-2 or
|
| 62 |
-
UTF-32 (depending on the size of `Elem`)
|
| 63 |
- Endianness shall not affect how multibyte sequences are read or
|
| 64 |
written.
|
| 65 |
- The multibyte sequences may be written as either a text or a binary
|
| 66 |
file.
|
| 67 |
|
| 68 |
For the facet `codecvt_utf16`:
|
| 69 |
|
| 70 |
- The facet shall convert between UTF-16 multibyte sequences and UCS-2
|
| 71 |
-
or UTF-32 (depending on the size of `Elem`)
|
| 72 |
- Multibyte sequences shall be read or written according to the `Mode`
|
| 73 |
flag, as set out above.
|
| 74 |
- The multibyte sequences may be written only as a binary file.
|
| 75 |
Attempting to write to a text file produces undefined behavior.
|
| 76 |
|
|
@@ -81,8 +85,5 @@ For the facet `codecvt_utf8_utf16`:
|
|
| 81 |
- Endianness shall not affect how multibyte sequences are read or
|
| 82 |
written.
|
| 83 |
- The multibyte sequences may be written as either a text or a binary
|
| 84 |
file.
|
| 85 |
|
| 86 |
-
The encoding forms UTF-8, UTF-16, and UTF-32 are specified in ISO/IEC
|
| 87 |
-
10646. The encoding form UCS-2 is specified in ISO/IEC 10646-1:1993.
|
| 88 |
-
|
|
|
|
| 1 |
## Deprecated standard code conversion facets <a id="depr.locale.stdcvt">[[depr.locale.stdcvt]]</a>
|
| 2 |
|
| 3 |
+
### General <a id="depr.locale.stdcvt.general">[[depr.locale.stdcvt.general]]</a>
|
| 4 |
+
|
| 5 |
The header `<codecvt>` provides code conversion facets for various
|
| 6 |
character encodings.
|
| 7 |
|
| 8 |
### Header `<codecvt>` synopsis <a id="depr.codecvt.syn">[[depr.codecvt.syn]]</a>
|
| 9 |
|
|
|
|
| 55 |
header sequence when writing a multibyte sequence to advertise the
|
| 56 |
endianness of the subsequent multibyte sequence to be written.
|
| 57 |
- If `(Mode & little_endian)`, the facet shall generate a multibyte
|
| 58 |
sequence in little-endian order, as opposed to the default big-endian
|
| 59 |
order.
|
| 60 |
+
- UCS-2 is the same encoding as UTF-16, except that it encodes scalar
|
| 61 |
+
values in the range `U+0000`–`U+ffff` (Basic Multilingual Plane) only.
|
| 62 |
|
| 63 |
For the facet `codecvt_utf8`:
|
| 64 |
|
| 65 |
- The facet shall convert between UTF-8 multibyte sequences and UCS-2 or
|
| 66 |
+
UTF-32 (depending on the size of `Elem`).
|
| 67 |
- Endianness shall not affect how multibyte sequences are read or
|
| 68 |
written.
|
| 69 |
- The multibyte sequences may be written as either a text or a binary
|
| 70 |
file.
|
| 71 |
|
| 72 |
For the facet `codecvt_utf16`:
|
| 73 |
|
| 74 |
- The facet shall convert between UTF-16 multibyte sequences and UCS-2
|
| 75 |
+
or UTF-32 (depending on the size of `Elem`).
|
| 76 |
- Multibyte sequences shall be read or written according to the `Mode`
|
| 77 |
flag, as set out above.
|
| 78 |
- The multibyte sequences may be written only as a binary file.
|
| 79 |
Attempting to write to a text file produces undefined behavior.
|
| 80 |
|
|
|
|
| 85 |
- Endianness shall not affect how multibyte sequences are read or
|
| 86 |
written.
|
| 87 |
- The multibyte sequences may be written as either a text or a binary
|
| 88 |
file.
|
| 89 |
|
|
|
|
|
|
|
|
|