tmp/tmpbx5io2_6/{from.md → to.md}
RENAMED
|
@@ -15,24 +15,26 @@ For each of the three code conversion facets `codecvt_utf8`,
|
|
| 15 |
header sequence when writing a multibyte sequence to advertise the
|
| 16 |
endianness of the subsequent multibyte sequence to be written.
|
| 17 |
- If `(Mode & little_endian)`, the facet shall generate a multibyte
|
| 18 |
sequence in little-endian order, as opposed to the default big-endian
|
| 19 |
order.
|
|
|
|
|
|
|
| 20 |
|
| 21 |
For the facet `codecvt_utf8`:
|
| 22 |
|
| 23 |
- The facet shall convert between UTF-8 multibyte sequences and UCS-2 or
|
| 24 |
-
UTF-32 (depending on the size of `Elem`)
|
| 25 |
- Endianness shall not affect how multibyte sequences are read or
|
| 26 |
written.
|
| 27 |
- The multibyte sequences may be written as either a text or a binary
|
| 28 |
file.
|
| 29 |
|
| 30 |
For the facet `codecvt_utf16`:
|
| 31 |
|
| 32 |
- The facet shall convert between UTF-16 multibyte sequences and UCS-2
|
| 33 |
-
or UTF-32 (depending on the size of `Elem`)
|
| 34 |
- Multibyte sequences shall be read or written according to the `Mode`
|
| 35 |
flag, as set out above.
|
| 36 |
- The multibyte sequences may be written only as a binary file.
|
| 37 |
Attempting to write to a text file produces undefined behavior.
|
| 38 |
|
|
@@ -43,8 +45,5 @@ For the facet `codecvt_utf8_utf16`:
|
|
| 43 |
- Endianness shall not affect how multibyte sequences are read or
|
| 44 |
written.
|
| 45 |
- The multibyte sequences may be written as either a text or a binary
|
| 46 |
file.
|
| 47 |
|
| 48 |
-
The encoding forms UTF-8, UTF-16, and UTF-32 are specified in ISO/IEC
|
| 49 |
-
10646. The encoding form UCS-2 is specified in ISO/IEC 10646-1:1993.
|
| 50 |
-
|
|
|
|
| 15 |
header sequence when writing a multibyte sequence to advertise the
|
| 16 |
endianness of the subsequent multibyte sequence to be written.
|
| 17 |
- If `(Mode & little_endian)`, the facet shall generate a multibyte
|
| 18 |
sequence in little-endian order, as opposed to the default big-endian
|
| 19 |
order.
|
| 20 |
+
- UCS-2 is the same encoding as UTF-16, except that it encodes scalar
|
| 21 |
+
values in the range `U+0000`–`U+ffff` (Basic Multilingual Plane) only.
|
| 22 |
|
| 23 |
For the facet `codecvt_utf8`:
|
| 24 |
|
| 25 |
- The facet shall convert between UTF-8 multibyte sequences and UCS-2 or
|
| 26 |
+
UTF-32 (depending on the size of `Elem`).
|
| 27 |
- Endianness shall not affect how multibyte sequences are read or
|
| 28 |
written.
|
| 29 |
- The multibyte sequences may be written as either a text or a binary
|
| 30 |
file.
|
| 31 |
|
| 32 |
For the facet `codecvt_utf16`:
|
| 33 |
|
| 34 |
- The facet shall convert between UTF-16 multibyte sequences and UCS-2
|
| 35 |
+
or UTF-32 (depending on the size of `Elem`).
|
| 36 |
- Multibyte sequences shall be read or written according to the `Mode`
|
| 37 |
flag, as set out above.
|
| 38 |
- The multibyte sequences may be written only as a binary file.
|
| 39 |
Attempting to write to a text file produces undefined behavior.
|
| 40 |
|
|
|
|
| 45 |
- Endianness shall not affect how multibyte sequences are read or
|
| 46 |
written.
|
| 47 |
- The multibyte sequences may be written as either a text or a binary
|
| 48 |
file.
|
| 49 |
|
|
|
|
|
|
|
|
|