Repository navigation
[Mbstring] Use big-endian UCS-2 like ext/mbstring - #721
Merged
Merged
Conversation
There was a problem hiding this comment.
Copilot was unable to review this pull request because the user who requested the review has insufficient remaining quota.
An organization owner can choose the repository organization as the billing source for reviews requested by members with a paid Copilot license. Learn about Copilot code review billing.
Member
|
Thank you @wleeaf. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
ext/mbstring encodes and decodes
UCS-2as big-endian. The polyfill passes the name to iconv unchanged. glibc's iconv treatsUCS-2without a BOM as host byte order, so on x86 the polyfill produces and reads little-endian data:Decoding big-endian UCS-2 produced by ext/mbstring or another system gives the wrong characters as well.
getEncoding()already mapsUTF-16andUTF-32to their big-endian names for the same reason. This addsUCS-2to that list.The new assertions in
testConvertEncoding()cover both directions with the polyfill. They fail without the change on glibc and pass with it. Converting BMP text to UCS-2 and back now gives the same bytes as PHP 8.5's mbstring../phpunit tests/Mbstringpasses.