8387259: Clarify extlang in Locale composition description

[justin-curtis-lu]

This PR corrects the Locale language field description to clarify that extlang subtags are accepted and normalized into the language field, not excluded altogether.

---

• I confirm that I make this contribution in accordance with the OpenJDK Interim AI Policy.

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue
• Change requires CSR request JDK-8387316 to be approved

Issues

• JDK-8387259: Clarify extlang in Locale composition description (Bug - P4)
• JDK-8387316: Clarify extlang in Locale composition description (CSR)

Reviewers

• Naoto Sato (@naotoj - Reviewer)
• Iris Clark (@irisclark - Reviewer)

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/31696/head:pull/31696
$ git checkout pull/31696

Update a local copy of the PR:
$ git checkout pull/31696
$ git pull https://git.openjdk.org/jdk.git pull/31696/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 31696

View PR using the GUI difftool:
$ git pr show -t 31696

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/31696.diff

Using Webrev

Link to Webrev Comment

[bridgekeeper]

👋 Welcome back jlu! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

@justin-curtis-lu This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8387259: Clarify extlang in Locale composition description

Reviewed-by: naoto, iris

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 18 new commits pushed to the master branch:

• c289cf5: 8377102: cacerts jlink plugin
• b6e7b2b: 8385420: C2: SIGSEGV in compiled code due to missing ctrl
• fea0c22: 8387215: On-demand attribution of a record constructor body causes javac to emit an invalid diagnostic
• ... and 15 more: https://git.openjdk.org/jdk/compare/193de1b1c78ed1cc29a747cc3ca979f219692a5c...master

As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

➡️ To integrate this PR with the above commit message to the master branch, type /integrate in a new comment.

[openjdk]

@justin-curtis-lu The following labels will be automatically applied to this pull request:

• core-libs
• i18n

When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command.

[mlbridge]

Webrevs

• 00: Full (4233d8f4)

[naotoj]

LGTM

[irisclark]

Confirmed that changes match corresponding CSR.