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

Archaic cuneiform numerals #939

Draft
wants to merge 14 commits into
base: main
Choose a base branch
from

Conversation

eggrobin
Copy link
Member

@eggrobin eggrobin commented Sep 20, 2024

L2/24-210 Archaic cuneiform numerals

https://github.com/unicode-org/sah/issues/542
https://github.com/unicode-org/utc-release-management/issues/152

[UTC-181-C31] Consensus: Provisionally assign 311 code points U+12550..U+12686 in a new Archaic Cuneiform Numerals block at U+12550..U+1268F, as described in L2/24-210R. [Ref: 2.4 in L2/24-228]

@eggrobin eggrobin force-pushed the 𒁾𒊬𒊑𒉈𒂵𒁺 branch 2 times, most recently from 5974df6 to f1c47cb Compare September 22, 2024 11:55
Copy link
Contributor

@nedley nedley left a comment

Choose a reason for hiding this comment

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

LGTM in general but maybe you could explain to me the missing ranges in ScriptExtensions.txt and Scripts.txt? I’m assuming it has to do with Pcun not being encoded yet?

@eggrobin
Copy link
Member Author

eggrobin commented Oct 4, 2024

could explain to me the missing ranges in ScriptExtensions.txt and Scripts.txt?

Scripts.txt has no missing ranges (if anything were missing, it would violate an invariant test that assigned characters are not Script=Unknown):
12550..125A7 ; Cuneiform
125A8..1264B ; Proto_Cuneiform
1264C..12686 ; Cuneiform

ScriptExtensions.txt only has entries for characters that have more than one script in its Script_Extensions, thus the scx={Xsux} character and the scx={Pcun} characters are gaps.

@nedley
Copy link
Contributor

nedley commented Oct 4, 2024

Scripts.txt has no missing ranges

You’re right, I was thinking about ScriptExtensions.txt but my brain expanded the set.

nedley
nedley previously approved these changes Oct 5, 2024
@eggrobin
Copy link
Member Author

eggrobin commented Oct 5, 2024

ScriptExtensions.txt only has entries for characters that have more than one script in its Script_Extensions, thus the scx={Xsux} character and the scx={Pcun} characters are gaps.

The scx situation is as follows, where red stands for Xsux only, white for Pcun only, and pink for both (apologies for the outrageously ugly MS Paint highlighting, but hopefully this gives a scannable summary.)

image image image image image image

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