Skip to content

[zh-tw] Translate docs/setup/learning-environment/#54937

Open
xoxonut wants to merge 1 commit intokubernetes:dev-1.35-zh-tw.1from
xoxonut:dev-1.35-zh-tw.1-learning-environment
Open

[zh-tw] Translate docs/setup/learning-environment/#54937
xoxonut wants to merge 1 commit intokubernetes:dev-1.35-zh-tw.1from
xoxonut:dev-1.35-zh-tw.1-learning-environment

Conversation

@xoxonut
Copy link

@xoxonut xoxonut commented Mar 17, 2026

Description

This PR provides the Traditional Chinese (zh-tw) translation for the content/zh-tw/docs/setup/learning-environment/

Issue

Part of #54645

/kind documentation
/area localization
/language zh-tw

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. area/localization General issues or PRs related to localization language/zh-tw Issues or PRs related to Traditional Chinese language labels Mar 17, 2026
@k8s-ci-robot k8s-ci-robot requested a review from a-mccarthy March 17, 2026 03:18
@k8s-ci-robot k8s-ci-robot added the sig/docs Categorizes an issue or PR as relevant to SIG Docs. label Mar 17, 2026
@k8s-ci-robot k8s-ci-robot requested a review from salaxander March 17, 2026 03:18
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign natalisucks for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Mar 17, 2026
@k8s-ci-robot
Copy link
Contributor

Welcome @xoxonut!

It looks like this is your first PR to kubernetes/website 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/website has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

@k8s-ci-robot k8s-ci-robot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Mar 17, 2026
@netlify
Copy link

netlify bot commented Mar 17, 2026

Pull request preview available for checking

Built without sensitive environment variables

Name Link
🔨 Latest commit 90efdcc
🔍 Latest deploy log https://app.netlify.com/projects/kubernetes-io-main-staging/deploys/69bc050b46bb8b00080f2b1c
😎 Deploy Preview https://deploy-preview-54937--kubernetes-io-main-staging.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.


These platforms are useful for quick experiments and following tutorials without local setup. -->

## 使用線上練習場

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Perhaps "線上練習環境" or "線上實驗環境"?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "線上練習環境" is better.

@@ -0,0 +1,3 @@
---
title: 術語表
Copy link

@apullo777 apullo777 Mar 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: 術語表
title: 詞彙表

We used "標準詞彙表" for “glossary” elsewhere (ref: #54853 (comment)).

Or maybe could just call it "詞彙表"?

"術語" is closer to “terminology”, so it might be better to keep the wording consistent.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Agreed. "術語" feels closer to "terminology".

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I prefer '標準詞彙表' to stay consistent with the previous discussion in #54853

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We ended up changing it to "詞彙表", since it is closer to the idea of "字典". In that case, adding "標準" feels unnecessary, as we normally would not say "標準字典".

@@ -0,0 +1,3 @@
---
title: 術語表
Copy link

@apullo777 apullo777 Mar 18, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
title: 術語表
title: 詞彙表

@tengqm
Copy link
Contributor

tengqm commented Mar 19, 2026

Team, another common practice in this project is to 'squash your PR into a single commit'.
Merging PRs with 18 commits could be a headache considering that we have dev-1.xx branch that periodically sync changes from main branch.

@tengqm
Copy link
Contributor

tengqm commented Mar 19, 2026

Hint

Always do a git commit --amend followed by a git push -f after you have revised your PR based on feedback and you have done git commit add ***. You will always have a single commit for your PR.

Multiple commits for a PR is acceptable when say, two commits are logically independent but they have to be merged together.

…_index.md

Co-authored-by: Peter Chang <peter.yaochen.chang@gmail.com>
@xoxonut xoxonut force-pushed the dev-1.35-zh-tw.1-learning-environment branch from 76ba23f to 90efdcc Compare March 19, 2026 14:15
@xoxonut
Copy link
Author

xoxonut commented Mar 19, 2026

Hint

Always do a git commit --amend followed by a git push -f after you have revised your PR based on feedback and you have done git commit add ***. You will always have a single commit for your PR.

Multiple commits for a PR is acceptable when say, two commits are logically independent but they have to be merged together.

Thanks for the tip. I've squashed the PR into a single commit and updated the message.

@apullo777 apullo777 mentioned this pull request Mar 23, 2026
22 tasks
@k8s-ci-robot k8s-ci-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Mar 26, 2026
@k8s-ci-robot
Copy link
Contributor

PR needs rebase.

Details

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.

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 cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. language/zh-tw Issues or PRs related to Traditional Chinese language needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. sig/docs Categorizes an issue or PR as relevant to SIG Docs. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants