[nerdbin]

Fixes #66093

Trac ticket: https://core.trac.wordpress.org/ticket/66093

Summary

• Normalize output from the_content() and get_the_excerpt() to Unicode NFC when the intl extension is available.
• Preserve output when normalization is unavailable or the input is not valid UTF-8.
• Add regression tests for both public output paths.

Testing

• vendor/bin/phpunit -c phpunit.xml.dist tests/phpunit/tests/post/getTheExcerpt.php
• vendor/bin/phpunit -c phpunit.xml.dist tests/phpunit/tests/post/getTheContent.php
• vendor/bin/phpcs --standard=phpcs.xml.dist on all four changed files
• git diff --check

The focused PHPUnit files passed: 18 tests, 26 assertions total.

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs.

Core Committers: Use this line as a base for the props when committing in SVN:

Props testerrahul.

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

---

Props Bot commands

You can trigger Props Bot actions by commenting on this PR:

• @propsbot add <username> to give props to a GitHub user. Requires write access.
• @propsbot remove <username> to leave a user out of the props. Requires write access.
• @propsbot refresh to refresh this list. Adding the props-bot label works too.

[github-actions]

Test using WordPress Playground

The 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

• All changes will be lost when closing a tab with a Playground instance.
• All changes will be lost when refreshing the page.
• A fresh instance is created each time the link below is clicked.
• Every time this pull request is updated, a new ZIP file containing all changes is created. If changes are not reflected in the Playground instance,
  it's possible that the most recent build failed, or has not completed. Check the list of workflow runs to be sure.

For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation.

Test this pull request with WordPress Playground.

[nerdbin]

Gentle follow-up on #14105 / Trac #66093. The patch and regular code-quality/test checks pass. Two upgrade-test jobs fail before testing because WP-CLI could not be provisioned (wp: command not found). Could someone please review the patch or rerun those jobs? Thanks