-
Notifications
You must be signed in to change notification settings - Fork 387
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
CLDR-17192 kbd: v45 Normalization docs #3445
CLDR-17192 kbd: v45 Normalization docs #3445
Conversation
|
774e8c2
to
585e729
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
585e729
to
b8e1fb5
Compare
Hooray! The files in the branch are the same across the force-push. 😃 ~ Your Friendly Jira-GitHub PR Checker Bot |
- split from PR unicode-org#3445
Co-authored-by: Joshua Horton <[email protected]>
Update with beginning of algorithm
- also discuss reorders
Co-authored-by: Mark Davis <[email protected]>
- includes review feedback Co-authored-by: Mark Davis <[email protected]> Co-authored-by: Marc Durdin <[email protected]>
- update to wording Co-authored-by: Joshua Horton <[email protected]>
Co-authored-by: Jan Kučera <[email protected]>
Co-authored-by: Marc Durdin <[email protected]>
Co-authored-by: Mark Davis <[email protected]>
- updates per review
- regen ToC - fix hyphens
- updates per review
- update to reorder processing discussion per review
- reorders -> reorder elements - regenerate ToC
2475aee
to
1b9619e
Compare
Notice: the branch changed across the force-push!
~ Your Friendly Jira-GitHub PR Checker Bot |
- fix for rebase
I need another review due to having to rebase this because of conflicts. Thanks |
@unicode-org/cldr-tc can I get an approval for this rebase? |
CLDR-17192
Updates to the section on Normalization, with updates to other sections which link there.
ALLOW_MANY_COMMITS=true