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

Tulu-Tigalari gemination mark and pluta #566

Merged
merged 16 commits into from
Nov 10, 2023
Merged

Conversation

eggrobin
Copy link
Member

@eggrobin eggrobin commented Oct 9, 2023

[173-C27] Consensus: Accept U+113D2 TULU-TIGALARI GEMINATION MARK and U+113D3 TULU-TIGALARI SIGN PLUTA, with names, glyphs, and properties as given in L2/22-260, for a future version of the standard. (Ref. section 7 of L2/22-248).

Inconsistencies with Ken’s drafts: Ken’s UnicodeData d8 is missing a trailing semicolon on U+113D3 (like the proposal).
Ken's LineBreak d3 gives Pluta lb=ID rather than BA.

@eggrobin
Copy link
Member Author

I made them both diacritic extenders, since that felt appropriate for a gemination mark and a vowel length mark.

The Grantha pluta is extender but not diacritic, but that seems like an oddity (the sort of things that feel to me like they should be non-diacritic extenders are reduplication/iteration/repetition marks etc.)

@markusicu
Copy link
Member

It looks like this one wants to be reviewed after the script as a whole is merged. Or maybe its changes want to be added to the main script addition PR.

@eggrobin
Copy link
Member Author

It looks like this one wants to be reviewed after the script as a whole is merged.

Probably.

@eggrobin
Copy link
Member Author

The Pluta should probably be LB=ID after all. See Norbert's comment on the avagraha:

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
markusicu previously approved these changes Nov 10, 2023
unicodetools/data/ucd/dev/PropertyValueAliases.txt Outdated Show resolved Hide resolved
@eggrobin eggrobin merged commit 690af45 into unicode-org:main Nov 10, 2023
9 of 10 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