-
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 zh translation #5684
update zh translation #5684
Conversation
Codecov Report
@@ Coverage Diff @@
## master #5684 +/- ##
==========================================
+ Coverage 44.36% 44.39% +0.02%
==========================================
Files 214 214
Lines 9119 9119
Branches 113 113
==========================================
+ Hits 4046 4048 +2
+ Misses 4798 4797 -1
+ Partials 275 274 -1
Continue to review full report at Codecov.
|
I would rather keep it in English than translate it into Chinese. It's more like our manipulation of kubectl. |
This kind version has some problem: some items are english, some are Chinese. it‘s realy confused Other reason is that the members in k8smeetup community translated all kubernetes documents to Chinese, and those words are all translated to Chinese. you guys can find here https://kubernetes.io/zh/docs. So I think we should translate it as well |
These translations look good, but there is still confusion about things like configmap and secrets. not sure if there is a good solution for this. @tanjunchen @tengqm @chenrui333 |
On website, we don't translate the resource names such as ConfigMap, Secret, Deployment etc. When we are talking about generic terms such as namespace, roles, volumes, we do translate where appropriate. In this context, I'd vote for not translating the resource names. Strictly speaking, the English source needs some changes as well, because in Kubernetes, nothing is called "Daemon Sets", we only have "DaemonSets". We may want to treat "RoleBindings" as a single term rather than two words "Role Bindings". Take "Roles" and "ClusterRoles" as examples. If we split the second term into "Cluster Roles", users may see it as a special case of "Roles", so it should be put under the "Roles" group. However, the fact is that "Role" and "ClusterRole" are two separate concepts. If we really want to use "Cluster Roles", we should say "Generic Roles" rather "Roles". Just my two cents. |
@tanjunchen @tengqm @chenrui333 @zehuaiWANG |
@tanjunchen @tengqm @chenrui333 @zehuaiWANG |
/lgtm Thanks for your contributions! |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: helight, hwdef The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
2.translation some word we haven't
3.we did't translate some words because we think we should't do it and those words show keep. but I find that those has already translated in the kubernetes doc, here is some url for kubernetes zh doc:
You can find more here : https://kubernetes.io/zh/docs
before this pr, the old UI is like this:
now with this pr it is like this: