kubernetes/website

[ja] update the term "Node" in glossary

Open

#46,248 opened on May 7, 2024

View on GitHub
 (7 comments) (1 reaction) (1 assignee)HTML (13,918 forks)batch import
area/localizationhelp wantedkind/featurelanguage/jatriage/accepted

Repository metrics

Stars
 (4,127 stars)
PR merge metrics
 (Avg merge 16d 13h) (160 merged PRs in 30d)

Description

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

Contributor guide

Research direction
Edit the glossary term in the Japanese localization file for nodes. The task involves two changes: 1) Replace the existing term 'ノード' with 'Node' in the Node section of the Japanese glossary. 2) Add a new term 'ノード' to the glossary (likely as a separate entry). Follow the issue instructions and the standard glossary formatting.
Tech stack
html
Domain
documentation
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90