Doc #80325 [Com]: contradictory definitions with endian-ness
[email protected] ("kimialamo9881 at gmail dot com") Tue, 03 Jan 2023 06:27:37 +0000
| Newsgroups | php.doc.bugs |
|---|---|
| Message-ID | <[email protected]> |
Edit report at https://bugs.php.net/bug.php?id=80325&edit=1 ID: 80325 Comment by: kimialamo9881 at gmail dot com Reported by: nedelcescuradu at gmail dot com Summary: contradictory definitions with endian-ness Status: Verified Type: Documentation Problem Package: mbstring related Operating System: - PHP Version: 7.4.12 Block user comment: N Private report: N New Comment: That was so amazing. (https://www.myinsite.biz/)github.com Previous Comments: ------------------------------------------------------------------------ [2020-12-18 16:15:37] [email protected] > The whole table on that page is just screwy. Plus has quite some overlap with <https://www.php.net/manual/en/mbstring.supported-encodings.php>. ------------------------------------------------------------------------ [2020-11-05 23:24:05] [email protected] I only just did a cursory reading of the source, but in the case of UCS-2, what the table needs to say is: * "UCS-2" comes with byte-order detection * "ISO-10646-UCS-2" and "UCS2" (and "UNICODE") are aliases for "UCS-2" * "UCS-2BE" is always big-endian * "UCS-2LE" is always little-endian The whole table on that page is just screwy. ------------------------------------------------------------------------ [2020-11-05 23:17:30] nedelcescuradu at gmail dot com Description: ------------ --- From manual page: https://php.net/mbstring.encodings --- Quote: ISO-10646-UCS-2 UCS-2 In contrast to UCS-2, strings are always assumed to be in BIG endian form. ISO-10646-UCS-2 UCS-2 In contrast to UCS-2, strings are always assumed to be in LITTLE endian form. ISO-10646-UCS-2 has 3 definitions, different one from another ------------------------------------------------------------------------ -- Edit this bug report at https://bugs.php.net/bug.php?id=80325&edit=1