-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
Fix wrong lang code of Chinese,and clean up useless strings.xml #2865
Conversation
…ally update the lang file.
/values-b+zh+HANS+CN was updated. Action: copy file in /values-b+zh+HANS+CN to /values-zh-rCN
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for the effort! I think this is almost good to go, just two minor things which need to be fixed first.
@B0pol Thanks for the review 👍
It takes time to find all mistakes. please wait |
@@ -1,457 +1,539 @@ | |||
<?xml version='1.0' encoding='UTF-8'?> | |||
<?xml version="1.0" encoding="utf-8"?> | |||
<resources> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please update your branch and test if it works to manually select Simplified Chinese through Settings -> Content -> App language
.
It should not work as you moved b+zh+HANS+CN
to zh-CN
, then edit this line, change zh-hans
into zh-cn
and test again, it should be fine.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
O K
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works because b+zh+HANS+CN
is in the value folder. But it will select the file in b+zh+HANS+CN
, and not in zh-CN
.
I don't understand why do you keep b+zh+HANS+CN
, because if I understood the reason of the PR, b+zh+HANS+CN
is a duplicate of zh-CN
? If b+zh+HANS+CN
is the same as zh-CN
, you should delete the folder, because Weblate will still update b+zh+HANS+CN
, not zh-CN
, and also change zh-hans here into zh-cn.
btw, can you check if these lines are good? The first should be traditionnal chinese, the second simplified chinese, the third hong-kong chinese, then cantonese I guess.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That is a historic problem.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It works because
b+zh+HANS+CN
is in the value folder. But it will select the file inb+zh+HANS+CN
, and not inzh-CN
.I don't understand why do you keep
b+zh+HANS+CN
, because if I understood the reason of the PR,b+zh+HANS+CN
is a duplicate ofzh-CN
? Ifb+zh+HANS+CN
is the same aszh-CN
, you should delete the folder, because Weblate will still updateb+zh+HANS+CN
, notzh-CN
, and also change zh-hans here into zh-cn
I'm afraid that it will influence Weblate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm afraid that it will influence Weblate.
But that's the goal, all translations have to be done through Weblate. You won't be able to make PRs every updates to update zh-CN. So it has to be fixed once and then use Weblate.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm afraid that it will influence Weblate.
But that's the goal, all translations have to be done through Weblate. You won't be able to make PRs every updates to update zh-CN. So it has to be fixed once and then use Weblate.
The problems I(we) faced is:
there are two various that take effect—zh-rCN(this file),b+zh-hans-cn . Weblate always updated the first one, b+zh-hans-cn won't be updated,and is old.
System will check zh-rCn first,if the target string existed,it will fetch it,if the target string doesn't existed in zh-rCn,it will try b+zh-hans-cn and do same action.And if it doesn't exist either,it will just fetch target string in English.
But zh-rCn is out date in master Branch now ,if strings in zh-rCn exist, System won't check b+zh-hans-cn then, however,many strings in zh-rCn is wrong, and even you change them in b+zh-hans-cn using Weblate, it doesn't take effect (because zh-rCn is as same as before)!
so, I moved b+zh-hans-cn to zh-rCN. if merging successfully, then delete b+zh-hans-cn (also try to let Weblate update zh-rCn ,so I(we) can directly use Weblate to translate Newpipe)
BTW, does every language in Weblate have a source file,and Weblate just edit them?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
btw, can you check if these lines are good? The first should be traditionnal chinese, the second simplified chinese, the third hong-kong chinese, then cantonese I guess.
Yes , but we usually don't say them in our language.
And the " Hong Kong Chinese" is also called as Cantonese!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
btw, can you check if these lines are good? The first should be traditionnal chinese, the second simplified chinese, the third hong-kong chinese, then cantonese I guess.
Yes , but we usually don't say them in our language.
And the " Hong Kong Chinese" is also called as Cantonese!
No!the lang code is wrong in fact.
It seems that there are some other problems since language selector was introduced. |
commit 7568af4 :Problems you referred to were fixed all. @TobiGr However Update:Well, in the latest dev build, I changed app language ,it didn't crash, and switched to the Chinese ,but I recommend that you (we) should use correct code and formal name. |
Let's explain how I made this selector : I picked all the languages from weblate, pick the language code, search on Wikipedia for the language name. On Weblate, there was hans, simple zh, and zh taiwan. So I put them in the selector. Indeed if the language name are informal, I'm sorry for not having deeply verified. The codes have to be lowercase, language-region, with -region optionnal, sorted by alphabetical order. So, maybe you should do
Or
Or
And then, make the language name matching language code, with the formal version. |
Now, conflicts were solved. |
sure |
Ok, here it is. |
So why the Now the translation in the Related: |
I am not sure. However, it seems this problem has still been existing after merging. |
Yeah, apparently the problem of simplified Chinese is still existing. The Should I mention someone else? |
No, I will create an another PR. |
@Geeyun-JY3 |
See issue #2819 first.
The action contains:
This will make Newpipe app have a up-to-date translation of Simplified Chinese.
closes #2819