Skip to content
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

[ja] update the term "Node" in glossary #46248

Open
Okabe-Junya opened this issue May 7, 2024 · 6 comments
Open

[ja] update the term "Node" in glossary #46248

Okabe-Junya opened this issue May 7, 2024 · 6 comments
Labels
area/localization General issues or PRs related to localization help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. language/ja Issues or PRs related to Japanese language triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@Okabe-Junya
Copy link
Member

Okabe-Junya commented May 7, 2024

This is a Feature Request

What would you like to be added

  • Replace the term "ノード" (written in Ja) with "Node" in Node section
  • Add the term "ノード" to the Glossary (標準化用語集).
    • Note that this is original content in Japanese

Why is this needed

In Japanese l10n, the word "Node" refers to two different things:

  1. A Kubernetes-specific resource, such as kind: Node or kubectl get node
  2. A more general term for a group of computers, as defined at https://glossary.cncf.io/ja/nodes/

When translating, we use “Node” for the first case and “ノード” (the Japanese word for node) for the second case. However, in the Japanese glossary, despite "Node" referring to the first case, it is written using the notation for the second case.

Therefore, we want to

  1. replace the existing "ノード" section with "Node"
  2. define a new term "ノード"

Comments

/area localization
/language ja
/help

@Okabe-Junya Okabe-Junya added the kind/feature Categorizes issue or PR as related to a new feature. label May 7, 2024
@k8s-ci-robot
Copy link
Contributor

@Okabe-Junya:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

  • Why are we solving this issue?
  • To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
  • Does this issue have zero to low barrier of entry?
  • How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

This is a Feature Request

What would you like to be added

  • Replace the term "ノード" (written in Ja) with "Node" in Node section
  • Add the term "ノード" to the Glossary (標準化用語集).
    • Note that this is original content in Japanese

Why is this needed

In Japanese l10n, the word "Node" refers to two different things:

  1. A Kubernetes-specific resource, such as kind: Node or kubectl get node
  2. A more general term for a group of computers, as defined at https://glossary.cncf.io/ja/nodes/

When translating, we use “Node” for the first case and “ノード” (the Japanese word for node) for the second case. However, in the Japanese glossary, despite "Node" referring to a proper noun, it is written using the notation for the second case.

Therefore, we want to replace the existing "ノード" section with "Node" and define a new term.

Comments

/area localization
/language ja
/help

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-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added area/localization General issues or PRs related to localization help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. language/ja Issues or PRs related to Japanese language needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 7, 2024
@Okabe-Junya
Copy link
Member Author

Okabe-Junya commented May 7, 2024

This is a following up information written in Japanese


Background

現在 k/websiteの用語集 では、k8s固有リソースとしての "ノード" が用語として登録されています。しかし、この "ノード" という表記は以下のl10nのルールと矛盾しています(本来はルールに基づいて "Node" と表記すべき)

FYI: https://kubernetes.io/ja/docs/contribute/localization/

ただし、ノード(Node)に関しては明確にKubernetesとしてのNodeリソース(例: kind: Nodeやkubectl get nodes)を指していないのであれば、「ノード」と表記してください

TODO

  1. 現在の用語集の "ノード" のページを "Node" 表記に置き換える
  2. 新規に(より一般的な意味の; k8sリソースとしての固有名詞ではない) "ノード" という用語を追加する
    a. 日本語l10n独自に追加します ref. Slack archive

@Okabe-Junya
Copy link
Member Author

cc @bells17

#46076 #46247 に関連して、こちらにもメンションさせていただきます)

@bells17
Copy link
Contributor

bells17 commented May 7, 2024

/triage accept

@k8s-ci-robot
Copy link
Contributor

@bells17: The label(s) triage/accept cannot be applied, because the repository doesn't have them.

In response to this:

/triage accept

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-sigs/prow repository.

@bells17
Copy link
Contributor

bells17 commented May 7, 2024

/triage accepted

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels May 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/localization General issues or PRs related to localization help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/feature Categorizes issue or PR as related to a new feature. language/ja Issues or PRs related to Japanese language triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

No branches or pull requests

3 participants