Ucdxml 17v1

[jowilco]

1. Addresses https://www.unicode.org/L2/L2019/19270.htm#160-A10 by consuming the RegEx syntax for Unihan directly from UAX38.
2. Resolved https://www.unicode.org/L2/L2024/24221.htm#181-A43 by removing kGB7.
3. Resolved https://www.unicode.org/L2/L2024/24221.htm#181-A131 by updating the RegEx for the na attribute.
4. Addresses https://www.unicode.org/L2/L2024/24221.htm#181-A133 by adding support for Unicode Version 17.0
5. Resolved https://www.unicode.org/L2/L2025/25085.htm#183-A100 by removing kJa.
6. Resolved https://www.unicode.org/L2/L2025/25085.htm#183-A127 by adding kTayNumeric.
7. Resolved https://www.unicode.org/L2/L2025/25085.htm#183-A180. All Unihan syntaxes are sourced directly from UAX38.
8. Addresses UCDXML: add Unikemet properties #921 by adding support for Unikemet.
9. Resolved Update UAX42 to document that common Unihan attributes are grouped starting with Unicode 17 #1071 by adding a comment indicating that "Unihan attributes are applied at the group where applicable, similar to how non-Unihan attributes are applied at the group."
10. Partially addresses Update UAX42 to document which UCDXML fields correspond to UCD properties (UAX44) vs. which are “just data” corresponding to various UCD files #1049 by removing Deprecated properties, Normalization Corrections, and Emoji Sources.

[markusicu]

Hi @jowilco the CI failures suggest that you need to run GenerateEnums again, and also mvn spotless:apply.

[jowilco]

Hi @jowilco the CI failures suggest that you need to run GenerateEnums again, and also mvn spotless:apply.

Agreed. This is still a draft pending the fixes for TR57. I'll definitely clean everything up before removing the draft status.

[markusicu]

@jowilco there are merge conflicts. Please update from main and fix as necessary.

I suspect that it's because both you and @eggrobin are adding extra properties.

[jowilco]

@jowilco there are merge conflicts. Please update from main and fix as necessary.

I suspect that it's because both you and @eggrobin are adding extra properties.

@markusicu -- I just merged upstream/main again to this branch, but I didn't get any merge conflicts. Not sure why you are seeing a conflict.

[eggrobin]

Not sure why you are seeing a conflict.

I think this is because Markus has his merge button set to Rebase and merge (which is often a conflict party). You probably don’t want to rebase merge anyway, and squash and merge has no conflicts, so all is well.

[markusicu]

sorry for the noise about conflicts...