tmp/tmp1rxi9ndy/{from.md → to.md}
RENAMED
|
@@ -56,21 +56,21 @@ For each of the three code conversion facets `codecvt_utf8`,
|
|
| 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
|
| 62 |
-
|
| 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
|
| 71 |
-
|
| 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,7 +81,8 @@ 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 |
-
ISO/IEC
|
|
|
|
| 87 |
|
|
|
|
| 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`) within the program.
|
| 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`) within the program.
|
| 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 |
- 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 |
|