Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CJK extension J #883

Merged
merged 16 commits into from
Nov 14, 2024
Merged

CJK extension J #883

merged 16 commits into from
Nov 14, 2024

Conversation

eggrobin
Copy link
Member

@eggrobin eggrobin commented Jul 24, 2024

UTC-180-C1 Consensus: Accept 4,300 CJK Unified Ideographs in a new CJK Unified Ideographs Extension J block with code point range U+323B0..U+3347B (block: U+323B0..U+3347F), based on document L2/24-138 (aka WG2 N5254) and Section 07 of document L2/24-165, for Unicode Version 17.0.

[181-C11] Consensus: Accept the proposal to remove U+32E11 (kIRG_TSource = TE-2725) and U+33281 (kIRG_UKSource = UK-20710) from the CJK Unified Ideographs Extension J block, based on UTC discussion of US NB ballot comments on ISO/IEC 10646 7th Edition CD1, for Unicode Version 17.0.

See L2/24-138 Recommendation M71.14.
From CJK: L2/24-165 §07.
https://github.com/unicode-org/utc-release-management/issues/133

@markusicu
Copy link
Member

minus 2:
[181-C11] Consensus: Accept the proposal to remove U+32E11 (kIRG_TSource = TE-2725) and U+33281 (kIRG_UKSource = UK-20710) from the CJK Unified Ideographs Extension J block, based on UTC discussion of US NB ballot comments on ISO/IEC 10646 7th Edition CD1, for Unicode Version 17.0.

@eggrobin
Copy link
Member Author

Should be good répertoire-wise, but still draft as it needs Unihan.

@eggrobin
Copy link
Member Author

We have Unihan as one block rather than per-proposal, and I do not want to start doing Unihan surgery to split it. On the other hand, the invariant tests will not be green unless Unihan is consistent with the répertoire. I do not want to merge things into main without invariants passing, since they just caught a mistake here (See 9a30e59).

So: I will create a unihan-17 branch in unicode-org, retarget this PR and #884 to it, and then create a PR from unihan-17 to main; this one should be green.
@markusicu, does that sound reasonable?

@markusicu
Copy link
Member

One way or another, it makes sense to update Unihan all in one PR, because that's how KenL delivers the data files.
And I would start with his data files, as before, and adjust other properties and constants to match.

@eggrobin eggrobin changed the base branch from main to unihan-17 November 14, 2024 15:28
@eggrobin eggrobin marked this pull request as ready for review November 14, 2024 15:45
@eggrobin eggrobin merged commit b0c8783 into unicode-org:unihan-17 Nov 14, 2024
15 of 17 checks passed
eggrobin added a commit that referenced this pull request Nov 16, 2024
* Unihan 17.0

Co-authored-by: kenlunde <[email protected]>

* CJK extension J (#883)

* Java changes for CJK Extension J

* UnicodeData.txt lines according to L2/24-165

* Script=Han

* Blocks.txt and ShortBlockNames.txt for Extension J

* Ideographic, Unified_Ideograph

* Do not refer to versions from the future (also fix a typo)

* Regenerate UCD

* GenerateEnums

* Regenerate UCD again

* drop 2, for Unicode Version 0x11

* Regenerate UCD

* Remove stray 3347B

* Regenerate UCD

* More remnants

* Regenerate UCD

* 5 UNCs, including disunifications of 峀 and 𣍟 (#884)

* Java change for U+2B73A

* Extend extension C in UnicodeData.txt

* sc=Han

* Ideographic, Unified_Ideograph

* Regenerate UCD

* Four more UNCs, for Unicode Version 0x11.

* Regenerate UCD

---------

Co-authored-by: kenlunde <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants