Update translations

[fangweilovelife]

Environment

Installation method:
Kubernetes version: v1.19.0
Dashboard version: v2.0.4
Operating system: centos
Node.js version ('node --version' output): v12.19.0
Go version ('go version' output):

Steps to reproduce

Observed result

Expected result

all be chinese

Comments

i have edit deployment.yml
like this

and tried <value: zh/zh-CN> didn't work

[floreks]

Language is based on your browser locale and presented Accept-Language request header. Recognized codes are defined here. ACCEPT_LANGUAGE env var should override it. You can also try clearing the cache and removing all cookies. If only some strings are localized then it might be our localization that needs an update. There were some major changes and some of the localization might have been lost.

UPDATE

From what I see our localization files indeed have lost some translated strings. Can some of our translators take a look and update it when they have some time?

@hwdef @zehuaiWANG @tanjunchen @shu-mutou @gochist

Feel free to call some more people that were responsible for providing previous translations.

[hwdef]

in #4705, translator decided that some words would not be translated, such as pod and service, If you have other suggestions, please discuss with us.

But your browser is indeed incorrect, please try to clear the cache. I will also try to reproduce this problem.

@floreks I will check for missing translated strings. The translation will be updated in a day or two.

[shu-mutou]

At first, please see https://github.com/kubernetes/dashboard/blob/master/docs/developer/internationalization.md in detail. We don't support zh as a result of long discussions. You can use zh-CN, zh-TW or zh-HK for Chinese and these codes will be replaced at here
Each translation underneeth in i18n directory has OWNERS who are responsible in its translation. Please ask them for each translation.

[fangweilovelife]

my chrome version :85.0.4183.121（release） （64 位）

And my language settings like this:
move Chinese to the top

And this is requst headers:

I have deleted cache & cookies , remove the env arg from the deployment.yaml, restart pod. but it didn't work

the result is :

and i see dashborad v1.10.0 , most words have been translated

[shu-mutou]

Also, each language team has each policy about whether k8s object name should be translated or not. So this issue relates Chinese traslation team.

But un-translated words are increased now.
@headcr4sh @kgroschoff @mkorbi @feloy @gochist @seokho-son @chenrui333 @zehuaiWANG @hwdef @tanjunchen Please update your translations. Thanks!

[hwdef]

@EvansFW
Thanks for you replay ,I reproduced the problem, it's not a bug, it's due to a missing translation.
I will update these translation.

But honestly, it wouldn't change much. Proper nouns will not be translated.

[zehuaiWANG]

@EvansFW According to issue #4705 , the word such like 'namespace', 'node' will no be translated.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten

[headcr4sh]

The German translation (DE) has been updated in PR #5672.
All technical Kubernetes-specific terms should now be in English without a translation.

/remove-language de

[maciaszczykm]

/lifecycle frozen

[shu-mutou]

/close
If we need translation work for a new release, creates a new issue and manages it there.

[k8s-ci-robot]

@shu-mutou: Closing this issue.

In response to this:

/close
If we need translation work for a new release, creates a new issue and manages it there.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.