Charset: Add explanatory note about what constitutes “valid” UTF-8#9716
Closed
dmsnell wants to merge 2 commits intoWordPress:trunkfrom
Closed
Charset: Add explanatory note about what constitutes “valid” UTF-8#9716dmsnell wants to merge 2 commits intoWordPress:trunkfrom
dmsnell wants to merge 2 commits intoWordPress:trunkfrom
Conversation
Trac ticket: Core-38044 This patch adds a clarifying note about what constitutes a valid UTF-8 byte stream. Co-authored-by: Arnt Gulbrandsen <arnt@gulbrandsen.priv.no>
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Model-used: Qwen/Qwen3-32B-4bit Model-usage: Suggested edits to wording of comment. Github-pr: 9716 Githbu-pr-link: WordPress#9716 Trac-ticket: 38044 Track-ticket-link: https://core.trac.wordpress.org/ticket/38044
dmsnell
force-pushed
the
charset/add-validity-note-in-docblock
branch
from
5336004 to
d188354
Compare
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
pento
pushed a commit
that referenced
this pull request
Sep 2, 2025
This patch adds a clarifying note about what constitutes a valid UTF-8 byte stream. This was brought up in review as a potentially ambiguous term, so a link to the spec has been provided to fix the behavior to the standard. Developed in #9716 Discussed in https://core.trac.wordpress.org/ticket/38044 Follow-up to [60630]. Props dmsnell, agulbra. See #38044. git-svn-id: https://develop.svn.wordpress.org/trunk@60702 602fd350-edb4-49c9-b593-d223f7449a82
Member
Author
|
Merged in [60702] |
markjaquith
pushed a commit
to markjaquith/WordPress
that referenced
this pull request
Sep 2, 2025
This patch adds a clarifying note about what constitutes a valid UTF-8 byte stream. This was brought up in review as a potentially ambiguous term, so a link to the spec has been provided to fix the behavior to the standard. Developed in WordPress/wordpress-develop#9716 Discussed in https://core.trac.wordpress.org/ticket/38044 Follow-up to [60630]. Props dmsnell, agulbra. See #38044. Built from https://develop.svn.wordpress.org/trunk@60702 git-svn-id: http://core.svn.wordpress.org/trunk@60038 1a063a9b-81f0-0310-95a4-ce76da25c4cd
github-actions bot
pushed a commit
to platformsh/wordpress-performance
that referenced
this pull request
Sep 3, 2025
This patch adds a clarifying note about what constitutes a valid UTF-8 byte stream. This was brought up in review as a potentially ambiguous term, so a link to the spec has been provided to fix the behavior to the standard. Developed in WordPress/wordpress-develop#9716 Discussed in https://core.trac.wordpress.org/ticket/38044 Follow-up to [60630]. Props dmsnell, agulbra. See #38044. Built from https://develop.svn.wordpress.org/trunk@60702 git-svn-id: https://core.svn.wordpress.org/trunk@60038 1a063a9b-81f0-0310-95a4-ce76da25c4cd
jonnynews
pushed a commit
to spacedmonkey/wordpress-develop
that referenced
this pull request
Sep 24, 2025
This patch adds a clarifying note about what constitutes a valid UTF-8 byte stream. This was brought up in review as a potentially ambiguous term, so a link to the spec has been provided to fix the behavior to the standard. Developed in WordPress#9716 Discussed in https://core.trac.wordpress.org/ticket/38044 Follow-up to [60630]. Props dmsnell, agulbra. See #38044. git-svn-id: https://develop.svn.wordpress.org/trunk@60702 602fd350-edb4-49c9-b593-d223f7449a82
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
1 participant
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.
Trac ticket: Core-38044
This patch adds a clarifying note about what constitutes a valid UTF-8 byte stream.