CLDR-14276 Updating ku_arab (ckb) to match official character #823
Conversation
The one that provided is wrong and not used yet for ku_arab (ckb) central kurdish language, The problem with ە and ك is resolved with government statments which i will mention below. This code (U+0647) used for ھ And (U+06D5) used for ە, And changing ك to ک which is reperesents by (U+06A9). https://unicode.ekrg.org/index.html Best Regards.
|
Hi, the commit will need to start with And, the ticket will need to be accepted. |
|
Thank you, You mean the title ? |
Not just the title, but also the actual commit message. The commit has:
Can you amend the commit, and force-push an updated commit? |
|
The Jira ticket needs to be explicit as to the exact changes being requested. |
I Already mentioned that two character changed which are (ە) and (ک).
I dont know how to do edit my commit. |
|
Can I help here? @macchiati |
|
Does We have to wait when world will end? @macchiati @srl295 |
|
@jwtiyar I've moved the ticket back to New since it now has a specific list of characters |
|
In the current pull request, it seems that (in the file exemplars/main/ku_Arab.xml): In CLDR-14276: Updating ckb (ku_arab) characters for exemplarsNEW you mention U+0647 (Arabic letter heh) and U+06D5 (Arabic letter ae), but those seem to exist in both the existing ku_Arab.xml file and the one in this pull request, so it's not clear why these characters are mentioned in the CLDR ticket. But on another level, I'm wondering if the correct file is being targeted. (I know that my understanding of how macrolanguages are handled is incomplete, so I don't know the answer to the questions I raise, and I certainly could be totally mistaken!) "ku" is a macrolanguage for Kurdish and includes: It seems that "kmr" is the representative language for "ku" (based on finding "ckb", "sdh" and "ku" in likelySubtags.xml, but not "kmr", however perhaps that is not a valid conclusion?). Also, common/main/ku.xml has: Currently in CLDR there are a number of files related to Kurdish: common/annotations/ku.xml common/annotations/ckb.xml seed/main/sdh.xml Perhaps this PR should introduce a new file: exemplars/main/ckb_Arab.xml, rather than modify ku_Arab.xml? |
|
Also, I notice a difference in the order of the characters between the document https://unicode.ekrg.org/ku_unicodes.html: and this pull request: I don't know if this difference is significant or not. Also, I note that there is no index exemplar. |
Thank you, @DavidLRowe For targeting the correct language, I agree with you the correct one is ckb_arab(or just ckb) but I didn't change the file name because ku_arab was already exist in CLDR, If it can be changed would be better and recognizable for us as Kurdish. KU is a macro language for Kurdish. KU should not be used for any of them. |
|
I do not fully understand how the complexities of how macrolanguages are handled. @macchiati will need to comment. |
|
@jwtiyar Hi. you mention ckb and 'central kurdish' - my understanding is that Central or Sorani Kurdish should be in Update: Oh, you are updating the |
|
Yes, see
https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code
ku_Arab is the equivalent of kmr_Arab, and would *not* be Central or
Soprani Kurdish.
Mark
…On Thu, Dec 2, 2021 at 7:36 AM Steven R. Loomis ***@***.***> wrote:
@jwtiyar <https://github.com/jwtiyar> Hi. you mention ckb and 'central
kurdish' - my understanding is that Central or Sorani Kurdish should be in
ckb.xml and not ku_Arab.xml
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#823 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMGMGA5AEVQBZCKK23TUO6G6ZANCNFSM4TIOLIWQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I know but ckb was not exist in exemplars/main folder. |
Correct. Please redo this PR to apply to https://github.com/unicode-org/cldr/blob/main/common/main/ckb.xml |
Hey @macchiati Conclusion : Ckb = Central kurdish (sorani) |
|
The choice of ku = kmr is deliberate. The standard usage in CLDR is as
described on
https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code.
So we will not accept PRs that violate that policy.
Note, however, that a client that needs to use kmr instead of ku can do
that by remapping CLDR data as they need to. That is done, for example,
with iw and he by some clients.
Mark
On Thu, Dec 2, 2021 at 10:46 AM Jwtiyar Nariman ***@***.***>
wrote:
… Yes, see
https://cldr.unicode.org/index/cldr-spec/picking-the-right-language-code
ku_Arab is the equivalent of kmr_Arab, and would *not* be Central or
Soprani Kurdish.
Mark
On Thu, Dec 2, 2021 at 7:36 AM Steven R. Loomis *@*.***>
wrote:
@jwtiyar <https://github.com/jwtiyar> https://github.com/jwtiyar Hi. you
mention ckb and 'central
kurdish' - my understanding is that Central or Sorani Kurdish should be in
ckb.xml and not ku_Arab.xml
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#823 (comment)
<#823 (comment)>, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ACJLEMGMGA5AEVQBZCKK23TUO6G6ZANCNFSM4TIOLIWQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub
.
Hey @macchiati <https://github.com/macchiati>
Thank you for your comment, No ku_arab is not kmr_arab, if you do this
it's completely wrong, ku should not refer to kurmanju kurdish (kmr),
Ku_arab is wrong also but it's provided by cldr, i did ku_arab because
gnu-linux distros ku_arab refer to ckb not kmr_arab.
Conclusion :
If you you agree i can help to fix language names because its very
complicated here some time you mention ckb, ckb_iq, ku_arab for same
language.
Ckb = Central kurdish (sorani)
Kmr = Northern kurdish (kurmanji)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#823 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ACJLEMDOYNW42NFHTVP4RHDUO65HDANCNFSM4TIOLIWQ>
.
Triage notifications on the go with GitHub Mobile for iOS
<https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>
or Android
<https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
So it means we can't work like that, As I said using ku for kmr is wrong and its my language. Also you can check here Unicode uses ku for kurdish not Northern Kurdish |
|
Another suggestion would be like that This does make sense and correct. |
Maybe I made a mistake to merge this file with the one from OSX folder. This file has independent PR Here: unicode-org#823
|
The policy on use of macrolanguages is not going to change. If the goal is to affect the exemplar characters for ckb, then the right target is ckb.xml |
|
@jwtiyar let me know if you need any help. Looks like another PR on a ckb.xml target? |
So what will happen to ku_arab? |
سوپاس کاک هیوا بەڵام بەخوا دەهرییان کردووم ئەمانە، هەر شوێنە و ناوێکیان بۆ کوردی داناوە و ناشیگۆڕن. نازانم چییان لیبکەم، تۆ هیچ بیرۆکەیەکت هەیە؟ |
CLDR-14276
The one that provided is wrong and not used yet for ku_arab (ckb) central kurdish language, The problem with ە and ك is resolved with government statments which i will mention below.
This code (U+0647) used for ھ And (U+06D5) used for ە, And changing ك to ک which is reperesents by (U+06A9).
https://unicode.ekrg.org/index.html
Best Regards.