-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Update translation files before releasing 2.0.0 #4259
Comments
@maciaszczykm @floreks @jeefy please let translators know the best timing they should update. |
@feloy @fuergaosi233 @seokho-son BTW, if you would get permission to approve translation files, i.e. if directories for each languages with OWNERS file that includes you would be added, would you guys be happy? |
Yes, that's ok for me. Thanks |
Sure :) Thank you. |
Thanks guys, I submited another issue for it. Then let's talk about it in #4280. 😉 |
It seems like most of the work is complete. Should we close this issue or is there still some remaining effort? |
Hi @jeefy. Including how to watch updates, our i18n framework has been completed already. But we need to confirm each i18n teams whether i18n files should update before 2.0.0 release. This issue aims to inform them time to release 2.0.0. If the time comes, could maintainers let i18n teams know here? |
@feloy @shu-mutou @fuergaosi233 @seokho-son Could you please take a look on translations and add missing ones? We're about to release v2. |
@maciaszczykm Thank you for the notification. I will check it for Korean localization. When is the target date for release? |
We want to do it as soon as possible. We need some more tests and to merge 3-4 existing pull requests. Translations are important part too. |
@pengx17 @riverzhang @zouyee @fuergaosi233 Hello guys, you were helping us with Chinese translations before, could you take a look on current state of the files? We were having some issues with finding an agreement (#4694) and any additional opinion could help us. |
@maciaszczykm We have updated translation for all of implemented language. Although we have discussion(#4705) that should be done widely, i.e. with SIG-docs, WG-UX or someplaces, it's enough for now, I think. 😉 |
Thank you a lot. |
Updated situations for each locales. We need to update translations again. |
@feloy @seokho-son Could you create PR for updating translations? |
We should do final check this before new release. I'll do that at mid March. |
@feloy @seokho-son @gochist @hwdef @tanjunchen @chenrui333 @zehuaiWANG
|
@shu-mutou |
What would you like to be added
Before releasing 2.0.0, update translation files, i.e.
i18n/[locale]/messages.[locale].xlf
, for new releases.Why is this needed
Since the last translation, new commits for frontend have been made and translation files have updated.
Comments
To add or update translation file, see this document.
Translation files to be updated (2020-1-22)
[WIP] update zh and zh-cn translation #4806update HPA translation #4856zh
Support multi locales in one translation file #4814zh
update HPA translation #4856PRs that require translation
Implement the front end of clusterrole Implement the front end of clusterrole #4622holdEnable to switch context in kubeconfig Enable to switch context in kubeconfig #4534hold, >2.0.0String fix (2020-2-28)
Above PRs that need translation would be putted off to next release.
Translation files to be merged (should be merged until 2020-3-6)
Angular 9 support (starts at 2020-3-9, until 2020-3-13)
zh-cn -> zh-Hans, zh-sg -> remove, zh-tw -> zh-Hant, zh-hk -> zh-Hant-HK, zh -> remove
Translation files to be checked (starts at 2020-3-16, until 2020-3-20)
Translation files to be checked (starts at 2020-3-23, until 2020-3-27)
status="new"
and updatelinenumber
s) @shu-mutou Fix locale mapping #4969The text was updated successfully, but these errors were encountered: