Merge pull request #43727 from my-git9/path-1162

[zh-cn] sync contribute/*
pull/43770/head
Kubernetes Prow Robot 2023-11-01 04:14:18 +01:00 committed by GitHub
commit 845ccefb0a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 26 additions and 12 deletions

View File

@ -5,9 +5,9 @@
- You need to have these tools installed: - You need to have these tools installed:
- [Python](https://www.python.org/downloads/) v3.7.x - [Python](https://www.python.org/downloads/) v3.7.x+
- [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
- [Golang](https://golang.org/doc/install) version 1.13+ - [Golang](https://go.dev/dl/) version 1.13+
- [Pip](https://pypi.org/project/pip/) used to install PyYAML - [Pip](https://pypi.org/project/pip/) used to install PyYAML
- [PyYAML](https://pyyaml.org/) v5.1.2 - [PyYAML](https://pyyaml.org/) v5.1.2
- [make](https://www.gnu.org/software/make/) - [make](https://www.gnu.org/software/make/)
@ -21,9 +21,9 @@
- 你需要安装以下工具: - 你需要安装以下工具:
- [Python](https://www.python.org/downloads/) v3.7.x - [Python](https://www.python.org/downloads/) v3.7.x+
- [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git) - [Git](https://git-scm.com/book/en/v2/Getting-Started-Installing-Git)
- [Golang](https://golang.org/doc/install) 1.13+ 版本 - [Golang](https://go.dev/dl/) 1.13+ 版本
- 用来安装 PyYAML 的 [Pip](https://pypi.org/project/pip/) - 用来安装 PyYAML 的 [Pip](https://pypi.org/project/pip/)
- [PyYAML](https://pyyaml.org/) v5.1.2 - [PyYAML](https://pyyaml.org/) v5.1.2
- [make](https://www.gnu.org/software/make/) - [make](https://www.gnu.org/software/make/)
@ -42,4 +42,3 @@
- 你需要知道如何为一个 GitHub 仓库创建拉取请求PR - 你需要知道如何为一个 GitHub 仓库创建拉取请求PR
这牵涉到创建仓库的派生fork副本。 这牵涉到创建仓库的派生fork副本。
有关信息可进一步查看[基于本地副本开展工作](/zh-cn/docs/contribute/new-content/open-a-pr/#fork-the-repo)。 有关信息可进一步查看[基于本地副本开展工作](/zh-cn/docs/contribute/new-content/open-a-pr/#fork-the-repo)。

View File

@ -5,7 +5,7 @@ weight: 50
card: card:
name: contribute name: contribute
weight: 50 weight: 50
title: 翻译文档 title: 本地化文档
--- ---
<!-- <!--
title: Localizing Kubernetes documentation title: Localizing Kubernetes documentation
@ -17,7 +17,7 @@ weight: 50
card: card:
name: contribute name: contribute
weight: 50 weight: 50
title: Translating the docs title: Localizing the docs
--> -->
<!-- overview --> <!-- overview -->
@ -717,7 +717,7 @@ have the exact font used in the original SVG.
5. **Reviewing and testing**: After making the necessary translations and 5. **Reviewing and testing**: After making the necessary translations and
converting text to curves, save and review the updated SVG image to ensure converting text to curves, save and review the updated SVG image to ensure
the text is properly displayed and aligned. Check the text is properly displayed and aligned. Check
[Preview your changes locally](https://kubernetes.io/docs/contribute/new-content/open-a-pr/#preview-locally). [Preview your changes locally](/docs/contribute/new-content/open-a-pr/#preview-locally).
--> -->
5. **检查和测试**:完成必要的翻译并将文本转换为曲线后,保存并检查更新后的 SVG 图片,确保文本正确显示和对齐。 5. **检查和测试**:完成必要的翻译并将文本转换为曲线后,保存并检查更新后的 SVG 图片,确保文本正确显示和对齐。
参考[在本地预览你的变更](/zh-cn/docs/contribute/new-content/open-a-pr/#preview-locally)。 参考[在本地预览你的变更](/zh-cn/docs/contribute/new-content/open-a-pr/#preview-locally)。
@ -755,9 +755,9 @@ The `main` branch holds content for the current release `{{< latest-version >}}`
The release team creates a `{{< release-branch >}}` branch before the next The release team creates a `{{< release-branch >}}` branch before the next
release: v{{< skew nextMinorVersion >}}. release: v{{< skew nextMinorVersion >}}.
--> -->
目标版本 | 分支 目标版本 | 分支
-----|----- ----------|-----
最新版本 | [`main`](https://github.com/kubernetes/website/tree/main) 最新版本 | [`main`](https://github.com/kubernetes/website/tree/main)
上一个版本 | [`release-{{< skew prevMinorVersion >}}`](https://github.com/kubernetes/website/tree/release-{{< skew prevMinorVersion >}}) 上一个版本 | [`release-{{< skew prevMinorVersion >}}`](https://github.com/kubernetes/website/tree/release-{{< skew prevMinorVersion >}})
下一个版本 | [`dev-{{< skew nextMinorVersion >}}`](https://github.com/kubernetes/website/tree/dev-{{< skew nextMinorVersion >}}) 下一个版本 | [`dev-{{< skew nextMinorVersion >}}`](https://github.com/kubernetes/website/tree/dev-{{< skew nextMinorVersion >}})
@ -980,7 +980,7 @@ permissions are required.
For more information about working from forks or directly from the repository, For more information about working from forks or directly from the repository,
see ["fork and clone the repo"](#fork-and-clone-the-repo). see ["fork and clone the repo"](#fork-and-clone-the-repo).
--> -->
有关基于派生或直接从仓库开展工作的更多信息,请参见 ["派生和克隆"](#fork-and-clone-the-repo)。 有关基于派生或直接从仓库开展工作的更多信息,请参见["派生和克隆"](#fork-and-clone-the-repo)。
<!-- <!--
## Upstream contributions ## Upstream contributions

View File

@ -946,6 +946,21 @@ structure of content in a code editor better.
两行的留白有助于在代码编辑器中查看整个内容的结构组织。 两行的留白有助于在代码编辑器中查看整个内容的结构组织。
<!--
Manually wrap paragraphs in the Markdown source when appropriate. Since the git
tool and the GitHub website generate file diffs on a line-by-line basis,
manually wrapping long lines helps the reviewers to easily find out the changes
made in a PR and provide feedback. It also helps the downstream localization
teams where people track the upstream changes on a per-line basis. Line
wrapping can happen at the end of a sentence or a punctuation character, for
example. One exception to this is that a Markdown link or a shortcode is
expected to be in a single line.
-->
适当时在 Markdown 文档中手动换行。由于 git 工具和 GitHub
网站是逐行生成文件差异的,手动换行可以帮助审阅者轻松找到 PR 中所做的更改并提供反馈。
它还可以帮助下游本地化团队,使其按行跟踪上游更改。例如,换行可以发生在句子或标点符号的末尾。
一个例外是 Markdown 链接或短代码应位于一行中。
<!-- <!--
### Headings and titles {#headings} ### Headings and titles {#headings}