Myanmar Extended-C

[eggrobin]

For unicode-org/properties#57, according to L2/22-046, per 171-C20:

[171-C20] Consensus: Accept 20 Myanmar numerals (U+116D0…U+116E3) for Eastern Pwo Karen and Pa’O in a new Myanmar Extended-C block, with range U+116D0..U+116FF for a future version of the standard. (Reference L2/22-046)

The proposal did not supply information for LineBreak.txt, so I inferred that from the GC (GC=Nd is almost always LB=NU).

116D0..116E3   ; NU # Nd    [20] MYANMAR PAO DIGIT ZERO..MYANMAR EASTERN PWO KAREN DIGIT NINE

Generated files updated as follows.

mvn compile exec:java '-Dexec.mainClass="org.unicode.text.UCD.Main"'  '-Dexec.args="build MakeUnicodeFiles"' -am -pl unicodetools  "-DCLDR_DIR=..\cldr\"  "-DUNICODETOOLS_GEN_DIR=Generated"  "-DUNICODETOOLS_REPO_DIR=."
cp .\Generated\UCD\15.1.0\* .\unicodetools\data\ucd\dev -recurse -force
rm unicodetools\data\ucd\dev\zzz-unchanged-*
rm unicodetools\data\ucd\dev\*\zzz-unchanged-*
rm .\unicodetools\data\ucd\dev\extra\*
rm .\unicodetools\data\ucd\dev\cldr\*

[eggrobin]

(The CI failure is from UCA validation checking.)

[markusicu]

Nice start!

I am surprised that there is no CI failure about having to run GenerateEnums.java.

The second commit looks like it mixes inputs and generated outputs. I suspect that for rebasing and conflict resolution it will be useful to separate those.

[eggrobin]

The second commit looks like it mixes inputs and generated outputs. I suspect that for rebasing and conflict resolution it will be useful to separate those.

I don’t think it does? At least I have tried to keep that separation.

[markusicu]

The second commit looks like it mixes inputs and generated outputs.

I don’t think it does?

It seems like PropertyValueAliases.txt should be an input (while maybe also getting reformatted). I see that you first changed ShortBlockNames.txt, I guess that PVA.txt gets it from there. Ideally, I think the tools should just parse PVA.txt and we should be able to delete ShortBlockNames.txt. One of many things that should get cleaned up...

I see now that ScriptExtensions.txt is just reformatted/reordered. (I wonder if the tool is flaky for that order.)

[eggrobin]

Checked consistency with Ken’s UnicodeData-16.0.0d6.txt and LineBreak-16.0.0d2.txt.

[eggrobin]

CI does not pass because of collation.

[markusicu]

lgtm

Once you merge the new main into another PR I can look at that.