Skip to content

Conversation

@eggrobin
Copy link
Member

@eggrobin eggrobin commented Nov 30, 2025

[179-C54] Consensus: Provisionally assign 2 Oriya code points U+0B53 ORIYA SIGN DOT ABOVE and U+0B54 ORIYA SIGN DOUBLE DOT ABOVE in the Oriya block as described in document L2/24-106. [Ref. Section 8 of document L2/24-068]

[181-C60] Consensus: UTC accepts for encoding in Unicode Version 17.0 the following 297 Arabic, Bengali, Han, Kannada, Latin, Oriya, phonetic, Sharada, Tangut, Telugu, and symbol characters for which the code points have previously been provisionally assigned:

    Arabic (40 characters): 088F, FBC3..FBD2, FD90..FD91, FDC8..FDCE, 10EC5..10EC7, 10ED0..10ED8, 10EFA..10EFB
    Bengali (1 character): 09FF
    Han (5 characters): 16FF2..16FF6
    Kannada (1 character): 0CDC
    Latin (2 characters): A7D2, A7D4
    Oriya (2 characters): 0B53..0B54
    Phonetic (30 characters): 1ACF, 1AD0..1ADD, 1AE0..1AEB, A7CE..A7CF, A7F1
    Sharada (8 characters): 11B60..11B67
    Tangut (145 characters): 187F8..187FF, 18D09..18D1E, 18D80..18DF2
    Telugu (1 character): 0C5C
    Symbols (62 characters): 2B96, 1CCFA..1CCFC, 1CEBA..1CED0, 1CEE0..1CEF0, 1F777..1F77A, 1F8D0..1F8D8, 1FA54..1FA57, 1FBFA

[184-C2] Consensus: Of characters approved for encoding in Unicode 17.0 (ref. 181-C60, 181-C61), the following 43 characters are removed from Unicode 17.0 and are targeted instead for Unicode 18.0:

  1. 09FF BENGALI LETTER SANSKRIT BA
  2. 0B53 ORIYA SIGN DOT ABOVE and 0B54 ORIYA SIGN DOUBLE DOT ABOVE
  3. 40 Chisoi script characters at 16D80..16DA9 and the Chisoi block at 16D80..16DAF.

@markusicu
Copy link
Member

Huh, I assumed you would do others first that are not in danger of being revised...

@eggrobin
Copy link
Member Author

I would really like to do #877 first, but that one is waiting for PAG review. Do we want to merge ahead of that review?

I am never quite sure what it takes to get the emoji properties in a row (I think this might take CLDR-side work) and they seem unlikely to interact with anything else, so that one will probably wait.

Copy link
Member

@markusicu markusicu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm but let's please also restore the NamesList lines:

https://github.com/unicode-org/unicodetools/pull/1165/files#diff-d5fdef68244e9d7b9531a38c70da3268e81f78b8f060123cc6c27956cba1b568

0B53	ORIYA SIGN DOT ABOVE
	* Kui
0B54	ORIYA SIGN DOUBLE DOT ABOVE
	* Kui

That would cleanly restore the UCD. We would "only" leave uca, security, idna for later.

@markusicu
Copy link
Member

I would really like to do #877 first, but that one is waiting for PAG review.

Ok. Is its https://github.com/unicode-org/sah/issues/497 ready for status=review?
Please respond to my July 10 questions there.

I am never quite sure what it takes to get the emoji properties in a row (I think this might take CLDR-side work)

I just pinged Ned & Mark on those.

and they seem unlikely to interact with anything else, so that one will probably wait.

ok

@eggrobin
Copy link
Member Author

Is its https://github.com/unicode-org/sah/issues/497 ready for status=review?

I moved it to Status=Review on November 10th, and then we looked at it in PAG on November 13th and Roozbeh asked for more time to stare at the property comparison tests.

@eggrobin
Copy link
Member Author

I just pinged Ned & Mark on those.

It looks like last year this was easy, but back then I do not think we were testing for non-emoji ExtPict, so I just had those as non-emoji until Ned worked his magic. I did just regenerate emoji-data today, so I could try it…

@markusicu
Copy link
Member

tests pass here

@eggrobin
Copy link
Member Author

I did just regenerate emoji-data today, so I could try it…

Yeah it’s not pretty. I could probably hammer on it until it works, but it seems a lot of the emoji file generation is entangled with emoji ordering, which is an art beyond my ken.

@eggrobin eggrobin merged commit cd5418f into unicode-org:main Nov 30, 2025
15 of 16 checks passed
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