Tulu-Tigalari

[eggrobin]

UTC-170-C9 Consensus: UTC accepts 78 Tulu-Tigalari characters in a new Tulu-Tigalari block U+11380..U+113FF as documented in L2/22-031, for encoding in a future version of the standard.

UTC-176-C16 Consensus: The UTC approves the code point change for TULU-TIGALARI LETTER DHA to U+113A4, from the conflicting U+113A5 approved by UTC-170-C9. TULU-TIGALARI LETTER NA remains at U+113A5.

Plus correcting a typo in the InSC data from L2/22-031.

LineBreak according to L2/22-080.

[eggrobin]

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

[eggrobin]

CI fails because of an invariant test which probably stems from the InPC and InSC files being garbled. (Nevermind, I misunderstood the test failure) I should try to regenerate them like I did for UnicodeData, LineBreak, etc.

[eggrobin]

CI does not pass because of collation.

[eggrobin]

Ken noted that the avagraha should probably be LB=BA like Grantha, but L2/22-080R2 recommends LB=ID.
Sent an email to Norbert to see if the discrepancy was intentional.

[eggrobin]

The discrepancy was intentional.

Scripsit Norbert:

For Tulu-Tigalari, one of the experts told us that line breaks can occur pretty much at any spacing character. OpenType doesn’t let you reorder characters across line breaks, and doesn’t deal well with line breaks before combining marks, so we can’t quite replicate that. But avagrahas with gc=Lo are treated as a base, so there’s no problem with breaking before them.

[markusicu]

Several non-UCA CI failures...

[roozbehp]

LGTM