search

unicode-org / unicodetools

home of unicodetools and https://util.unicode.org JSPs
https://util.unicode.org
Other
52 stars 41 forks source link

The most ancient script from the future #941

Closed eggrobin closed 2 months ago

eggrobin commented 2 months ago

Same procedure as https://github.com/unicode-org/unicodetools/pull/888, as this one already has a script code.

roozbehp commented 2 months ago

I don't understand why you need this. Proto-cuneiform isn't planned for 17.0, is it?

eggrobin commented 2 months ago

I don't understand why you need this.

Because I am drafting properties for the Archaic Cuneiform Numerals proposal, which introduces sc=Pcun and scx=Xsux Pcun characters, and I do not want to deal with divergent versions of these Java files (it is only in the actual data files that I can do automated conflict resolution).

Adding these to the enumeration several versions ahead has been standard procedure, see https://github.com/unicode-org/unicodetools/pull/888, https://github.com/unicode-org/unicodetools/pull/660, https://github.com/unicode-org/unicodetools/pull/546, and https://github.com/unicode-org/unicodetools/pull/443. See the last one of those for more explanations.

roozbehp commented 2 months ago

I see. I thought these were sc=Xsux.

eggrobin commented 2 months ago

I thought these were sc=Xsux.

The proposal has all three of scx=Xsux, scx=Xsux Pcun, and scx=Pcun (where Xsux « wins » for the Script property). See §§1, 2.3.3, and 2.3.4.