-
-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
impr: Correct Uzbek okina and more (@Sonotoki-da) #6116
base: master
Are you sure you want to change the base?
Conversation
Continuous integration check(s) failed. Please review the failing check's logs and make the necessary changes. |
|
Continuous integration check(s) failed. Please review the failing check's logs and make the necessary changes. |
1k and 70k have some duplicate words now, please remove them. |
Continuous integration check(s) failed. Please review the failing check's logs and make the necessary changes. |
I'm sorry for the mess. I shouldn't have been doing any editing with a completely unconfigured environment. I just yesterday started learning about developer productivity tools like ansible because I was a little hurt and frustrated. Haste made waste |
Somehow the files have conflicts all of a sudden, plus i can't figure out why the diff on the 70k file is pretty much the whole file.. |
I probably messed up the whole thing by my incompetence. I'm sorry :'( Will you let me reopen another PR real quick, if we're to delete this one? But this time, everything will be clean |
You can hard reset your master branch, then push the changes to it again and it will not require opening another PR. |
Oh, okay. Thank you, I'll try right away |
1. Converting all the weird quotes to the simple quote first, using regex: [’`ʼ‘'] -> ' 2. Then, regex: ([OoGg])[’`ʼ‘'] -> \1ʻ 3. Finally, regex: [’`ʼ‘'] -> ʼ
Continuous integration check(s) failed. Please review the failing check's logs and make the necessary changes. |
This is my first PR ever. I never took this collab/coop thing seriously before, but now this is definitely a wake-up call for me. I will learn all the details properly. Thank you for this great opportunity! Please let me know if I need to do anything to merge the PR. I'll await further instructions, if any 🙏 |
Description
Uzbek words contain incorrect okina characters. I'm an Uzbek who does professional proofreading, and there's an easy fix for this:
It's not ' (quotes), it's not ` (backticks), and it's definitely not the non-okina characters that the Google folks mistakenly abuse in their Gboard. Only #Oʻzbekiston and #masʼuliyat can be properly hashtagged, because ʻ and ʼ are counted as a part of the words, not as delimiters.
For reference: https://t.me/xatoliklar/855 (Please use a machine translator. It's a public Uzbek Telegram channel dedicated to highlighting the ill-treated Uzbek language)
Checks
_list.json
,_groups.json
and addlanguages.json
?Closes #