8305681: Allow additional characters for GB18030-2022 (Level 2) support

[naotoj]

This is a backport of GB18030 Level 2 part of the JSR337 MR5 (https://jcp.org/aboutJava/communityprocess/mrel/jsr337/index5.html) Reference Implementation

---

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

Issue

• JDK-8305681: Allow additional characters for GB18030-2022 (Level 2) support

Reviewers

• Lance Andersen (@LanceAndersen - Reviewer) ⚠️ Review applies to 79ea0a42
• Iris Clark (@irisclark - Author) ⚠️ Review applies to 79ea0a42
• Roger Riggs (@RogerRiggs - Committer) ⚠️ Review applies to 79ea0a42

Contributors

• Justin Lu <jlu@openjdk.org>

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev.git pull/315/head:pull/315
$ git checkout pull/315

Update a local copy of the PR:
$ git checkout pull/315
$ git pull https://git.openjdk.org/jdk8u-dev.git pull/315/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 315

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/315.diff

Webrev

Link to Webrev Comment

[bridgekeeper]

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

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 02: Full - Incremental (ec84d957)
• 01: Full - Incremental (79ea0a42)
• 00: Full (79ea0a42)

[naotoj]

/contributor add jlu

[openjdk]

@naotoj
Contributor Justin Lu <jlu@openjdk.org> successfully added.

[openjdk-notifier]

The parent pull request that this pull request depends on has now been integrated and the target branch of this pull request has been updated. This means that changes from the dependent pull request can start to show up as belonging to this pull request, which may be confusing for reviewers. To remedy this situation, simply merge the latest changes from the new target branch into this pull request by running commands similar to these in the local repository for your personal fork:

git checkout 8305681
git fetch https://git.openjdk.org/jdk8u-dev.git master
git merge FETCH_HEAD
# if there are conflicts, follow the instructions given by git merge
git commit -m "Merge master"
git push

[openjdk]

@naotoj This change now passes all automated pre-integration checks.

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

8305681: Allow additional characters for GB18030-2022 (Level 2) support

Co-authored-by: Justin Lu <jlu@openjdk.org>
Reviewed-by: lancea, iris, rriggs

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 no new commits pushed to the master branch. If another commit should be pushed before you perform the /integrate command, your PR will be automatically rebased. If you prefer to avoid any potential 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.

[naotoj]

/integrate

[openjdk]

Going to push as commit 3d9e8d0.

[openjdk]

@naotoj Pushed as commit 3d9e8d0.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.