cldr
cldr copied to clipboard
CLDR-13980 v46 ddl: Seed data for Kazakh (Arabic)
Checklist
- [x] Issue filed: https://unicode-org.atlassian.net/browse/CLDR-13980
- [x] Updated PR title and link in previous line to include Issue number
New locale request for Kazakh (Arabic)
ALLOW_MANY_COMMITS=true
@srl295 please look at the request
@srl295 For kk-Latn and changing kk in kk-Cyrl, do I need to create a new branch, or can I add in this branch?
@srl295 For kk-Latn and changing kk in kk-Cyrl, do I need to create a new branch, or can I add in this branch?
There's no need to create a new branch. Actually, fix the suggestion I made above, and the rest will probably need to be discussed in committee
There's no need to create a new branch. Actually, fix the suggestion I made above, and the rest will probably need to be discussed in committee
Please check
@srl295 now I need to merge all the commits into a single commit?
@srl295 can I add keyboard data, annotation, and romanization to this branch? And you can find out when to add the kk_Arab locale and how long it will take?
@macchiati can I get permission to edit kk_Arab locale data in the Survey Tool? I have a guest account.
Hooray! The files in the branch are the same across the force-push. 😃
~ Your Friendly Jira-GitHub PR Checker Bot
@srl295 please can you answer the questions listed above?
- minimalPairs go under
(submitted a requested change) - there's a
kk_Arabin the exemplars/main directory. Please compare to that as well and delete it from your branch.- kk needs to be made multi script, so
kkwill need to change to bekk-Cyrl. This is more complex, and is why there are default content issues.- This also relates to the upcoming
kk-Latnhttps://unicode-org.atlassian.net/browse/CLDR-10736
@srl295 please can you check?
@MuratKaribay I think this should be post 38. I think we need to look closely at the kk-Latn effect here - as we add kk-Arab, I think we should see if we can also add kk-Latn at the same time.
@MuratKaribay can you rebase?
can I add keyboard data, annotation, and romanization to this branch?
make it separate.
@MuratKaribay PR still needs rebase. Will move this to v42
@MuratKaribai ping? can you rebase this?
@MuratKaribai this will need to move to v43 if it isn't rebased in the next few days
@MuratKaribai Closing this. Note that 'seed' is going away, so when you reopen this, just update common/main not seed/main.
@MuratKaribai can you rebase this into common/main?
hi @MuratKaribai it's rebased, let's make it work!