Formatting: Handle Unicode whitespace in wp_trim_words()#11258
Formatting: Handle Unicode whitespace in wp_trim_words()#11258dan-zakirov wants to merge 1 commit intoWordPress:trunkfrom
Conversation
Use a Unicode-aware whitespace pattern for UTF-8 sites so that ideographic spaces (U+3000), non-breaking spaces (U+00A0), and other Unicode whitespace characters are treated as word separators, matching the behavior of the Gutenberg editor. Non-UTF-8 sites retain the previous regex as a fallback. Props SirLouen, wildworks. Fixes #64552.
|
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. |
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. |
1 participant
This updates the word boundary handling on UTF-8 sites to use a Unicode-aware whitespace pattern, so ideographic spaces (U+3000), non-breaking spaces (U+00A0), and other Unicode whitespace characters are treated as word separators. This matches the behavior already used in the Gutenberg editor.
For non-UTF-8 sites, the previous regex is kept as a fallback.
Props sirlouen, wildworks.
Fixes #64552.
Trac ticket: https://core.trac.wordpress.org/ticket/64552