From f565805c6c30ab43e1d136145511f7f65b335be2 Mon Sep 17 00:00:00 2001 From: Yan Gao Date: Fri, 2 Feb 2024 12:33:34 +0000 Subject: [PATCH] Translated using Weblate (Chinese (Simplified)) Currently translated at 95.0% (2018 of 2123 strings) Translation: Flower Docs/Framework Translate-URL: https://hosted.weblate.org/projects/flower-docs/framework/zh_Hans/ --- .../zh_Hans/LC_MESSAGES/framework-docs.po | 277 ++++++++---------- 1 file changed, 129 insertions(+), 148 deletions(-) diff --git a/doc/locales/zh_Hans/LC_MESSAGES/framework-docs.po b/doc/locales/zh_Hans/LC_MESSAGES/framework-docs.po index aaea4c761ac1..4c4951cd5194 100644 --- a/doc/locales/zh_Hans/LC_MESSAGES/framework-docs.po +++ b/doc/locales/zh_Hans/LC_MESSAGES/framework-docs.po @@ -8,7 +8,7 @@ msgstr "" "Project-Id-Version: Flower main\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date: 2023-11-23 18:31+0100\n" -"PO-Revision-Date: 2023-11-25 19:00+0000\n" +"PO-Revision-Date: 2024-02-03 13:01+0000\n" "Last-Translator: Yan Gao \n" "Language-Team: Chinese (Simplified) \n" @@ -17,7 +17,7 @@ msgstr "" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=1; plural=0;\n" -"X-Generator: Weblate 5.2.1-rc\n" +"X-Generator: Weblate 5.4-dev\n" "Generated-By: Babel 2.13.1\n" #: ../../source/contributor-explanation-architecture.rst:2 @@ -1083,13 +1083,12 @@ msgid "" "We wish we had more time to write usage examples because we believe they " "help users to get started with building what they want to build. Here are a " "few ideas where we'd be happy to accept a PR:" -msgstr "" -"我们希望有更多的时间来撰写使用示例，因为我们相信这些示例可以帮助用户开始构建" -"他们想要构建的东西。以下是我们乐意接受 PR 的几个想法：" +msgstr "我们希望有更多的时间来撰写使用示例，因为我们相信这些示例可以帮助用户开始构建" +"他们想要的东西。以下是我们乐意接受的 PR ：" #: ../../source/contributor-ref-good-first-contributions.rst:40 msgid "Llama 2 fine-tuning, with Hugging Face Transformers and PyTorch" -msgstr "微调 \"拉玛 2\"，使用 \"抱脸变形金刚 \"和 PyTorch" +msgstr "使用Hugging Face Transformers和PyTorch对Llama 2进行微调" #: ../../source/contributor-ref-good-first-contributions.rst:41 msgid "XGBoost" @@ -1097,7 +1096,7 @@ msgstr "XGBoost" #: ../../source/contributor-ref-good-first-contributions.rst:42 msgid "Android ONNX on-device training" -msgstr "安卓 ONNX 设备上培训" +msgstr "安卓 ONNX 的端训练" #: ../../source/contributor-ref-secure-aggregation-protocols.rst:2 msgid "Secure Aggregation Protocols" @@ -1110,12 +1109,13 @@ msgid "" "accurate in practice. The SecAgg protocol can be considered as a special " "case of the SecAgg+ protocol." msgstr "" -"包括 SecAgg、SecAgg+ 和 LightSecAgg 协议。LightSecAgg 协议尚未实施，因此其图" -"表和抽象在实践中可能并不准确。SecAgg 协议可视为 SecAgg+ 协议的特例。" +"包括 SecAgg、SecAgg+ 和 LightSecAgg 协议。LightSecAgg " +"协议尚未完成，因此其图表和抽象属性可能并不准确。SecAgg 协议可视为 SecAgg+ " +"协议的特例。" #: ../../source/contributor-ref-secure-aggregation-protocols.rst:8 msgid "The :code:`SecAgg+` abstraction" -msgstr "代码：`SecAgg+` 抽象" +msgstr ":code:`SecAgg+` 的抽象属性" #: ../../source/contributor-ref-secure-aggregation-protocols.rst:10 #: ../../source/contributor-ref-secure-aggregation-protocols.rst:161 @@ -1136,7 +1136,7 @@ msgstr "Flower 服务器将按以下顺序执行和处理收到的结果：" #: ../../source/contributor-ref-secure-aggregation-protocols.rst:159 msgid "The :code:`LightSecAgg` abstraction" -msgstr "代码：`LightSecAgg` 抽象" +msgstr ":code:`LightSecAgg` 的抽象属性" #: ../../source/contributor-ref-secure-aggregation-protocols.rst:271 msgid "Types" @@ -1144,13 +1144,13 @@ msgstr "类型" #: ../../source/contributor-tutorial-contribute-on-github.rst:2 msgid "Contribute on GitHub" -msgstr "在 GitHub 上投稿" +msgstr "在 GitHub 上贡献代码" #: ../../source/contributor-tutorial-contribute-on-github.rst:4 msgid "" "This guide is for people who want to get involved with Flower, but who are " "not used to contributing to GitHub projects." -msgstr "本指南适用于想参与 Flower，但不习惯为 GitHub 项目贡献的人。" +msgstr "本指南适用于想参与 Flower，但不熟悉为 GitHub 项目贡献代码的朋友。" #: ../../source/contributor-tutorial-contribute-on-github.rst:6 msgid "" @@ -1159,9 +1159,9 @@ msgid "" "docs/getting-started-for-contributors.html>`_ and examples of `good first " "contributions `_." msgstr "" -"如果您熟悉如何在 GitHub 上贡献，可以直接查看我们的 \"贡献者入门指南\" " -"`_ 和 \"优秀的" -"首次贡献示例\" `_。" +"如果您熟悉如何在 GitHub 上贡献代码，可以直接查看我们的 \"贡献者入门指南\" " +"`_ 和 " +"\"首次贡献示例\" `_。" #: ../../source/contributor-tutorial-contribute-on-github.rst:12 msgid "Setting up the repository" @@ -1196,8 +1196,7 @@ msgstr "" msgid "" "If you haven't already, you will need to create an account on `GitHub " "`_." -msgstr "" -"如果还没有，您需要在 `GitHub `_ 上创建一个账户。" +msgstr "您需要在 `GitHub `_ 上创建一个账户。" #: ../../source/contributor-tutorial-contribute-on-github.rst:22 msgid "" @@ -1211,7 +1210,7 @@ msgstr "" #: ../../source/contributor-tutorial-contribute-on-github.rst:34 msgid "**Forking the Flower repository**" -msgstr "**叉花仓库**" +msgstr "**Fork Flower的仓库**" #: ../../source/contributor-tutorial-contribute-on-github.rst:26 msgid "" @@ -1220,9 +1219,9 @@ msgid "" "GitHub account) and click the ``Fork`` button situated on the top right of " "the page." msgstr "" -"fork 是 GitHub 仓库的个人副本。要为 Flower 创建一个 fork，您必须导航到 " -"https://github.com/adap/flower（同时连接到您的 GitHub 账户），然后点击页面右" -"上方的 ``Fork`` 按钮。" +"Fork(分叉) 是指 GitHub 仓库的个人副本。要为 Flower 创建一个 fork，" +"您需要导航到 https://github.com/adap/flower（同时连接到您的 GitHub 账户），" +"然后点击页面右上方的 ``Fork`` 按钮。" #: ../../source/contributor-tutorial-contribute-on-github.rst:31 msgid "" @@ -1231,13 +1230,13 @@ msgid "" "in your own list of repositories). Once created, you should see on the top " "left corner that you are looking at your own version of Flower." msgstr "" -"您可以更改名称，但没有必要，因为这个版本的 Flower 将是您自己的，并位于您自己" -"的账户中（即，在您自己的版本库列表中）。创建完成后，您会在左上角看到自己的 " -"Flower 版本。" +"您可以更改名称，但没有必要，因为这个版本的 Flower " +"将是您自己的，并位于您自己的账户中（即在您自己的版本库列表中）。创建完成后，" +"您会在左上角看到自己的 Flower 版本。" #: ../../source/contributor-tutorial-contribute-on-github.rst:49 msgid "**Cloning your forked repository**" -msgstr "**克隆你的分叉仓库**" +msgstr "**克隆你的fork（分叉）仓库**" #: ../../source/contributor-tutorial-contribute-on-github.rst:37 msgid "" @@ -1246,32 +1245,30 @@ msgid "" "click on the ``Code`` button on the right, this will give you the ability to " "copy the HTTPS link of the repository." msgstr "" -"下一步是在你的机器上下载分叉版本库，以便对其进行修改。在分叉版本库页面上，首" -"先点击右侧的 \"代码 \"按钮，这样就能复制版本库的 HTTPS 链接。" +"下一步是在你的机器上下载分叉版仓库，以便对其进行修改。在分叉版本库页面上，" +"首先点击右侧的 ``Code`` 按钮，这样就能复制版本库的 HTTPS 链接。" #: ../../source/contributor-tutorial-contribute-on-github.rst:43 msgid "" "Once you copied the \\, you can open a terminal on your machine, " "navigate to the place you want to download the repository to and type:" -msgstr "" -"一旦复制了 （），你就可以在你的机器上打开一个终端，导航到你想下载软件" -"源的地方，然后键入：" +msgstr "一旦复制了这个 \\，你就可以在你的电脑上打开一个终端，导航到你想下载软件源的地方，然后键入：" #: ../../source/contributor-tutorial-contribute-on-github.rst:49 msgid "" "This will create a `flower/` (or the name of your fork if you renamed it) " "folder in the current working directory." -msgstr "" -"这将在当前工作目录下创建一个 `flower/`（如果重命名了，则使用 fork 的名称）文" -"件夹。" +msgstr "这将在当前工作目录下创建一个 `flower/` 文件夹（如果重命名了，则会使用 fork " +"的名称）。" #: ../../source/contributor-tutorial-contribute-on-github.rst:68 msgid "**Add origin**" -msgstr "**添加原产地**" +msgstr "**添加 origin**" #: ../../source/contributor-tutorial-contribute-on-github.rst:52 msgid "You can then go into the repository folder:" -msgstr "然后，您就可以进入存储库文件夹：" +msgstr "然后，您就可以进入仓库文件夹：" #: ../../source/contributor-tutorial-contribute-on-github.rst:58 msgid "" @@ -1280,9 +1277,9 @@ msgid "" "previously mentioned by going to our fork repository on our GitHub account " "and copying the link." msgstr "" -"在这里，我们需要为我们的版本库添加一个 origin。origin 是远程 fork 仓库的 " -"\\。要获得它，我们可以像前面提到的那样，访问 GitHub 账户上的分叉仓库并" -"复制链接。" +"在这里，我们需要为我们的版本库添加一个 origin。origin 是远程分叉仓库的 \\<" +"URL\\>。要获得它，我们可以像前面提到的那样，访问 GitHub " +"账户上的分叉仓库并复制链接。" #: ../../source/contributor-tutorial-contribute-on-github.rst:63 msgid "" @@ -1292,15 +1289,14 @@ msgstr "一旦复制了 \\ ，我们就可以在终端中键入以下命 #: ../../source/contributor-tutorial-contribute-on-github.rst:92 msgid "**Add upstream**" -msgstr "**增加上游**" +msgstr "**添加 upstream**" #: ../../source/contributor-tutorial-contribute-on-github.rst:71 msgid "" "Now we will add an upstream address to our repository. Still in the same " "directroy, we must run the following command:" -msgstr "" -"现在，我们要为版本库添加一个上游地址。还是在同一目录下，我们必须运行以下命" -"令：" +msgstr "现在，我们要为版本库添加一个上游(upstream)地址。还是在同一目录下，我们需要运" +"行以下命令：" #: ../../source/contributor-tutorial-contribute-on-github.rst:78 msgid "" @@ -1314,43 +1310,41 @@ msgid "" "need an up-to-date history of. The origin is just the GitHub remote address " "of the forked repository we created, i.e. the copy (fork) in our own account." msgstr "" -"上游是父版本库（这里是 Flower）的 GitHub 远程地址，即我们最终要贡献的版本库，" -"因此需要最新的历史记录。origin 只是我们创建的分叉仓库的 GitHub 远程地址，即我" -"们自己账户中的副本（分叉）。" +"上游 (upstream) 是父版本库的 GitHub " +"远程地址，即我们最终要提交的版本库，因此需要最新的历史记录。origin " +"只是我们创建的分叉仓库的 GitHub 远程地址，即我们自己账户中的副本（分叉）。" #: ../../source/contributor-tutorial-contribute-on-github.rst:86 msgid "" "To make sure our local version of the fork is up-to-date with the latest " "changes from the Flower repository, we can execute the following command:" -msgstr "" -"为了确保本地版本的分叉程序与 Flower 代码库的最新更改保持一致，我们可以执行以" -"下命令：" +msgstr "为了确保本地版本的分叉与 Flower " +"代码库的最新更改保持一致，我们可以执行以下命令：" #: ../../source/contributor-tutorial-contribute-on-github.rst:95 msgid "Setting up the coding environment" -msgstr "设置编码环境" +msgstr "设置代码环境" #: ../../source/contributor-tutorial-contribute-on-github.rst:97 msgid "" "This can be achieved by following this `getting started guide for " "contributors`_ (note that you won't need to clone the repository). Once you " "are able to write code and test it, you can finally start making changes!" -msgstr "" -"您可以按照这份 \"贡献者入门指南\"__（注意，您不需要克隆版本库）来实现这一点。" -"一旦您能够编写代码并进行测试，您就可以开始修改了！" +msgstr "您可以按照这份 \"`贡献者入门指南\"`_来实现（注意，您不需要克隆版本库）。一旦" +"您能够编写代码并进行测试，您就可以开始修改了！" #: ../../source/contributor-tutorial-contribute-on-github.rst:102 msgid "Making changes" -msgstr "做出改变" +msgstr "做出修改" #: ../../source/contributor-tutorial-contribute-on-github.rst:104 msgid "" "Before making any changes make sure you are up-to-date with your repository:" -msgstr "在进行任何更改之前，请确保您的版本库是最新的：" +msgstr "在进行任何修改之前，请确保您的版本库是最新的：" #: ../../source/contributor-tutorial-contribute-on-github.rst:110 msgid "And with Flower's repository:" -msgstr "还有Flower的存储库：" +msgstr "还有Flower的仓库：" #: ../../source/contributor-tutorial-contribute-on-github.rst:124 msgid "**Create a new branch**" @@ -1360,9 +1354,8 @@ msgstr "**创建一个新分支**" msgid "" "To make the history cleaner and easier to work with, it is good practice to " "create a new branch for each feature/project that needs to be implemented." -msgstr "" -"为了使历史记录更简洁、更易于操作，为每个需要实现的功能/项目创建一个新分支是个" -"不错的做法。" +msgstr "为了使历史记录更简洁、更易于操作，我们可以为每个需要实现的功能/项目创建一个新" +"分支。" #: ../../source/contributor-tutorial-contribute-on-github.rst:120 msgid "" @@ -1376,20 +1369,19 @@ msgstr "**进行修改**" #: ../../source/contributor-tutorial-contribute-on-github.rst:127 msgid "" "Write great code and create wonderful changes using your favorite editor!" -msgstr "使用您最喜欢的编辑器编写优秀的代码并创建精彩的更改！" +msgstr "使用您最喜欢的编辑器来进行编码！" #: ../../source/contributor-tutorial-contribute-on-github.rst:140 msgid "**Test and format your code**" -msgstr "**测试并格式化您的代码**" +msgstr "**测试并规范您的代码**" #: ../../source/contributor-tutorial-contribute-on-github.rst:130 msgid "" "Don't forget to test and format your code! Otherwise your code won't be able " "to be merged into the Flower repository. This is done so the codebase stays " "consistent and easy to understand." -msgstr "" -"不要忘记测试和格式化您的代码！否则您的代码将无法并入 Flower 代码库。这样做是" -"为了使代码库保持一致并易于理解。" +msgstr "不要忘记测试和规范您的代码！否则您的代码将无法并入 Flower " +"代码库。这样做是为了使代码库保持一致并易于理解。" #: ../../source/contributor-tutorial-contribute-on-github.rst:133 msgid "To do so, we have written a few scripts that you can execute:" @@ -1397,7 +1389,7 @@ msgstr "为此，我们编写了一些脚本供您执行：" #: ../../source/contributor-tutorial-contribute-on-github.rst:152 msgid "**Stage changes**" -msgstr "**舞台变化**" +msgstr "**添加修改**" #: ../../source/contributor-tutorial-contribute-on-github.rst:143 msgid "" @@ -1407,7 +1399,7 @@ msgstr "在创建更新历史记录的提交之前，必须向 Git 说明需要 #: ../../source/contributor-tutorial-contribute-on-github.rst:145 msgid "This can be done with:" -msgstr "这可以通过：" +msgstr "这可以通过一下操作来完成：" #: ../../source/contributor-tutorial-contribute-on-github.rst:151 msgid "" @@ -1435,21 +1427,21 @@ msgid "" "It should be written in an imperative style and be concise. An example would " "be :code:`git commit -m \"Add images to README\"`." msgstr "" -" 用于向他人解释提交的作用。它应该以命令式风格书写，并且简明" -"扼要。例如 :code:`git commit -m \"Add images to README\"`。" +"\\ " +"用于向他人解释这次提交的内容。最好以命令式风格书写，并且简明扼要。例如 " +":code:`git commit -m \"Add images to README\"`。" #: ../../source/contributor-tutorial-contribute-on-github.rst:173 msgid "**Push the changes to the fork**" -msgstr "**将更改推送到分叉**" +msgstr "**将更改推送到fork(分叉)**" #: ../../source/contributor-tutorial-contribute-on-github.rst:165 msgid "" "Once we have committed our changes, we have effectively updated our local " "history, but GitHub has no way of knowing this unless we push our changes to " "our origin's remote address:" -msgstr "" -"一旦提交了修改，我们就有效地更新了本地历史记录，但除非我们将修改推送到原点的" -"远程地址，否则 GitHub 无法得知：" +msgstr "一旦提交了修改，我们就更新了本地历史记录。我们必须将这次修改推送到origin的远" +"程地址，否则 GitHub 无法得知：" #: ../../source/contributor-tutorial-contribute-on-github.rst:172 msgid "" @@ -1470,17 +1462,17 @@ msgstr "**创建 PR**" msgid "" "Once you have pushed changes, on the GitHub webpage of your repository you " "should see the following message:" -msgstr "推送更改后，在仓库的 GitHub 网页上应该会看到以下信息：" +msgstr "推送了更改后，在您仓库的 GitHub 网页上应该会看到以下信息：" #: ../../source/contributor-tutorial-contribute-on-github.rst:183 msgid "Otherwise you can always find this option in the `Branches` page." -msgstr "否则，您可以在 \"分支 \"页面找到该选项。" +msgstr "否则，您可以在 `分支` 页面找到该选项。" #: ../../source/contributor-tutorial-contribute-on-github.rst:185 msgid "" "Once you click the `Compare & pull request` button, you should see something " "similar to this:" -msgstr "点击 \"比较和拉取请求 \"按钮后，您应该会看到类似下面的内容：" +msgstr "点击 `Compare & pull request`按钮后，您应该会看到类似下面的内容：" #: ../../source/contributor-tutorial-contribute-on-github.rst:189 msgid "" @@ -1493,8 +1485,8 @@ msgid "" "fixes`` from my forked repository to branch ``main`` from the Flower " "repository." msgstr "" -"在这个例子中，你可以看到请求将我分叉的版本库中的分支 ``doc-fixes`` 合并到 " -"Flower 版本库中的分支 ``main``。" +"在这个例子中，您可以看到请求将我分叉(fork)的版本库中的分支 ``doc-fixes`` " +"合并到 Flower 版本库中的分支 ``main``。" #: ../../source/contributor-tutorial-contribute-on-github.rst:195 msgid "" @@ -1502,17 +1494,17 @@ msgid "" "and to link it to existing issues. We have placed comments (that won't be " "rendered once the PR is opened) to guide you through the process." msgstr "" -"中间的输入框供您描述 PR 的作用，并将其与现有问题联系起来。我们在此放置了注释" -"（一旦 PR 打开，注释将不会显示），以指导您完成整个过程。" +"中间的输入框用来描述 您PR " +"的作用，并将其与现有问题(issues)联系起来。我们在这里加了注释（一旦 PR " +"打开，注释将不会显示），以指导您完成整个过程。" #: ../../source/contributor-tutorial-contribute-on-github.rst:198 msgid "" "At the bottom you will find the button to open the PR. This will notify " "reviewers that a new PR has been opened and that they should look over it to " "merge or to request changes." -msgstr "" -"在底部，您可以找到打开 PR 的按钮。这将通知审核人员新的 PR 已经打开，他们应该" -"查看该 PR 以进行合并或要求修改。" +msgstr "在底部，您可以找到开放 PR 的按钮。这将通知审核人员新的 PR 已经开放，" +"他们将会查看该 PR 以进行合并或要求修改。" #: ../../source/contributor-tutorial-contribute-on-github.rst:201 msgid "" @@ -1524,26 +1516,25 @@ msgstr "" #: ../../source/contributor-tutorial-contribute-on-github.rst:206 msgid "**Making new changes**" -msgstr "**作出新的改变**" +msgstr "**作出新的修改**" #: ../../source/contributor-tutorial-contribute-on-github.rst:206 msgid "" "Once the PR has been opened (as draft or not), you can still push new " "commits to it the same way we did before, by making changes to the branch " "associated with the PR." -msgstr "" -"一旦 PR 被打开（无论是否作为草案），你仍然可以像以前一样，通过修改与 PR 关联" -"的分支来推送新的提交。" +msgstr "一旦 PR 被开放（无论是否作为草案），你仍然可以像以前一样，通过修改与 PR " +"关联的分支来推送新的提交。" #: ../../source/contributor-tutorial-contribute-on-github.rst:228 msgid "**Review the PR**" -msgstr "**审查 PR**" +msgstr "**审核 PR**" #: ../../source/contributor-tutorial-contribute-on-github.rst:209 msgid "" "Once the PR has been opened or once the draft PR has been marked as ready, a " "review from code owners will be automatically requested:" -msgstr "一旦 PR 被打开或 PR 草案被标记为就绪，就会自动要求代码所有者进行审核：" +msgstr "一旦 PR 被开放或 PR 草案被标记为就绪，就会自动要求代码所有者进行审核：" #: ../../source/contributor-tutorial-contribute-on-github.rst:213 msgid "" @@ -1563,7 +1554,7 @@ msgstr "要解决这些问题，只需将必要的更改推送到与 PR 关联 #: ../../source/contributor-tutorial-contribute-on-github.rst:223 msgid "And resolve the conversation:" -msgstr "并解决对话：" +msgstr "并解决对话内容：" #: ../../source/contributor-tutorial-contribute-on-github.rst:227 msgid "" @@ -1592,11 +1583,11 @@ msgstr "" #: ../../source/contributor-tutorial-contribute-on-github.rst:242 msgid "Then you should update your forked repository by doing:" -msgstr "然后，你应该更新你的分叉仓库：" +msgstr "然后，您可以更新您的的分叉仓库：" #: ../../source/contributor-tutorial-contribute-on-github.rst:251 msgid "Example of first contribution" -msgstr "首次捐款实例" +msgstr "首次代码贡献的示例" #: ../../source/contributor-tutorial-contribute-on-github.rst:254 msgid "Problem" @@ -1606,45 +1597,40 @@ msgstr "问题" msgid "" "For our documentation, we’ve started to use the `Diàtaxis framework `_." -msgstr "" -"对于我们的文档，我们已经开始使用 \"Diàtaxis 框架 `_\"。" +msgstr "我们的文档已经开始使用 `Diàtaxis framework `_。" #: ../../source/contributor-tutorial-contribute-on-github.rst:258 msgid "" "Our “How to” guides should have titles that continue the sencence “How to " "…”, for example, “How to upgrade to Flower 1.0”." -msgstr "" -"我们的 \"如何 \"指南的标题应延续 \"如何...... \"的句式，例如 \"如何升级到 " -"Flower 1.0\"。" +msgstr "我们指南的标题应延续 \"如何...... \"的句式，例如 \"如何升级到 Flower 1.0\"。" #: ../../source/contributor-tutorial-contribute-on-github.rst:260 msgid "" "Most of our guides do not follow this new format yet, and changing their " "title is (unfortunately) more involved than one might think." -msgstr "" -"我们的大多数指南还没有采用这种新格式，而更改其标题（不幸的是）比人们想象的要" -"复杂得多。" +msgstr "我们的大多数指南还没有采用这种新格式，而更改其标题比人们想象的要复杂得多。" #: ../../source/contributor-tutorial-contribute-on-github.rst:262 msgid "" "This issue is about changing the title of a doc from present continious to " "present simple." -msgstr "这个问题是关于将文档标题从现在进行时改为现在进行时。" +msgstr "这个问题是关于将文档标题从现在进行时改为一般现在时。" #: ../../source/contributor-tutorial-contribute-on-github.rst:264 msgid "" "Let's take the example of “Saving Progress” which we changed to “Save " "Progress”. Does this pass our check?" -msgstr "" -"以 \"保存进度 \"为例，我们将其改为 \"保存进度\"。这是否通过了我们的检查？" +msgstr "以 \"Saving Progress \"为例，我们将其改为 \"Save Progress\"" +"。这是否通过了我们的检查？" #: ../../source/contributor-tutorial-contribute-on-github.rst:266 msgid "Before: ”How to saving progress” ❌" -msgstr "之前： \"如何保存进度\" ❌" +msgstr "之前： \"How to saving progress\" ❌" #: ../../source/contributor-tutorial-contribute-on-github.rst:268 msgid "After: ”How to save progress” ✅" -msgstr "之后： \"如何保存进度\"✅" +msgstr "之后： \"How to save progress\"✅" #: ../../source/contributor-tutorial-contribute-on-github.rst:271 msgid "Solution" @@ -1687,9 +1673,9 @@ msgid "" "**very important** to avoid that, breaking links can harm our search engine " "ranking." msgstr "" -"您可能已经注意到，文件名仍然反映了旧的措辞。如果我们只是更改文件，那么就会破" -"坏与该文件的所有现有链接--避免这种情况是***重要的，破坏链接会损害我们的搜索引" -"擎排名。" +"您可能已经注意到，文件名仍然是旧的措辞。如果我们只是更改文件，那么就会破坏与" +"该文件的所有现有链接--" +"我们一定要避免这种情况，破坏链接会损害我们的搜索引擎排名。" #: ../../source/contributor-tutorial-contribute-on-github.rst:285 msgid "Here’s how to change the file name:" @@ -1730,13 +1716,13 @@ msgstr "查找并修改 `index.rst` 中的文件名" #: ../../source/contributor-tutorial-contribute-on-github.rst:301 msgid "Open PR" -msgstr "开放式 PR" +msgstr "开放 PR" #: ../../source/contributor-tutorial-contribute-on-github.rst:303 msgid "" "Commit the changes (commit messages are always imperative: “Do something”, " "in this case “Change …”)" -msgstr "提交更改（提交信息总是命令式的：\"做某事\"，这里是 \"更改......\"）" +msgstr "提交更改（提交信息总是以祈使句的形式：\"Do something\"，这里是 \"Change …\"）" #: ../../source/contributor-tutorial-contribute-on-github.rst:304 msgid "Push the changes to your fork" @@ -1744,7 +1730,7 @@ msgstr "将更改推送到分叉" #: ../../source/contributor-tutorial-contribute-on-github.rst:305 msgid "Open a PR (as shown above)" -msgstr "打开 PR（如上图所示）" +msgstr "开放 PR（如上图所示）" #: ../../source/contributor-tutorial-contribute-on-github.rst:306 msgid "Wait for it to be approved!" @@ -1752,20 +1738,19 @@ msgstr "等待审批！" #: ../../source/contributor-tutorial-contribute-on-github.rst:307 msgid "Congrats! 🥳 You're now officially a Flower contributor!" -msgstr "祝贺你 🥳 您现在正式成为 \"Flower \"贡献者！" +msgstr "祝贺！ 🥳 您现在正式成为 \"Flower \"贡献者！" #: ../../source/contributor-tutorial-contribute-on-github.rst:311 msgid "How to write a good PR title" -msgstr "如何撰写好的公关标题" +msgstr "如何撰写PR标题" #: ../../source/contributor-tutorial-contribute-on-github.rst:313 msgid "" "A well-crafted PR title helps team members quickly understand the purpose " "and scope of the changes being proposed. Here's a guide to help you write a " "good GitHub PR title:" -msgstr "" -"一个精心撰写的公关标题能帮助团队成员迅速了解所提修改的目的和范围。以下指南可" -"帮助您撰写一个好的 GitHub PR 标题：" +msgstr "一个好的PR标题能帮助团队成员迅速了解所提修改的目的和范围。" +"以下指南可帮助您撰写一个好的 GitHub PR 标题：" #: ../../source/contributor-tutorial-contribute-on-github.rst:315 msgid "" @@ -1776,20 +1761,20 @@ msgid "" "titles for easy readability. 1. Use Proper Capitalization and Punctuation: " "Follow grammar rules for clarity." msgstr "" -"1. 简明扼要： 以简明扼要的方式清楚地概述变化。1. 使用可操作的动词： 使用 \"添" -"加\"、\"更新 \"或 \"修复 \"等动词来表明目的。1. 包含相关信息： 提及受影响的功" -"能或模块以了解上下文。1. 简短：避免冗长的标题，以方便阅读。1. 使用正确的大小" -"写和标点符号： 遵守语法规则，以确保清晰。" +"1. 简明扼要： 以简明扼要的方式清楚地概述要做的修改。1. 使用可操作的动词： " +"使用 \"Add\"、\"Update \"或 \"Fix \"等动词来表明目的。1. 包含相关信息： " +"阐明受影响的功能或模块。1. 简短：避免冗长的标题，以方便阅读。1. " +"使用正确的大小写和标点符号： 遵守语法规则，以确保清晰。" #: ../../source/contributor-tutorial-contribute-on-github.rst:321 msgid "" "Let's start with a few examples for titles that should be avoided because " "they do not provide meaningful information:" -msgstr "让我们先举例说明几个应该避免使用的标题，因为它们不能提供有意义的信息：" +msgstr "让我们先举例说明几个应该避免使用的标题，因为它们不能提供有用的信息：" #: ../../source/contributor-tutorial-contribute-on-github.rst:323 msgid "Implement Algorithm" -msgstr "执行算法" +msgstr "实现算法" #: ../../source/contributor-tutorial-contribute-on-github.rst:324 msgid "Database" @@ -1812,17 +1797,15 @@ msgid "" "Here are a few positive examples which provide helpful information without " "repeating how they do it, as that is already visible in the \"Files " "changed\" section of the PR:" -msgstr "" -"这里有几个正面的例子，提供了有用的信息，但没有重复他们是如何做的，因为在 PR " -"的 \"已更改文件 \"部分已经可以看到：" +msgstr "这里有几个例子提供了有用的信。在 PR 的 \"Files changed\"栏可以看到：" #: ../../source/contributor-tutorial-contribute-on-github.rst:331 msgid "Update docs banner to mention Flower Summit 2023" -msgstr "更新文件横幅，提及 2023 年 Flower 峰会" +msgstr "更新文件横幅并提及 Flower Summit 2023" #: ../../source/contributor-tutorial-contribute-on-github.rst:332 msgid "Remove unnecessary XGBoost dependency" -msgstr "移除不必要的 XGBoost 依赖性" +msgstr "移除不必要的 XGBoost 关联包" #: ../../source/contributor-tutorial-contribute-on-github.rst:333 msgid "Remove redundant attributes in strategies subclassing FedAvg" @@ -1830,12 +1813,12 @@ msgstr "删除 FedAvg 子类化策略中的多余属性" #: ../../source/contributor-tutorial-contribute-on-github.rst:334 msgid "Add CI job to deploy the staging system when the `main` branch changes" -msgstr "添加 CI 作业，以便在 \"主 \"分支发生变化时部署暂存系统" +msgstr "添加 CI ，以便在`main`分支发生变化时部署暂存系统" #: ../../source/contributor-tutorial-contribute-on-github.rst:335 msgid "" "Add new amazing library which will be used to improve the simulation engine" -msgstr "添加新的惊人库，用于改进模拟引擎" +msgstr "添加新的函数库，用于改进模拟引擎" #: ../../source/contributor-tutorial-contribute-on-github.rst:339 #: ../../source/tutorial-series-build-a-strategy-from-scratch-pytorch.ipynb:548 @@ -1850,7 +1833,7 @@ msgstr "接下来的步骤" msgid "" "Once you have made your first PR, and want to contribute more, be sure to " "check out the following :" -msgstr "一旦您完成了第一份 PR，并希望做出更多贡献，请务必查看以下内容：" +msgstr "您完成了第一次 PR 后，如果希望做出更多贡献，请务必查看以下内容：" #: ../../source/contributor-tutorial-contribute-on-github.rst:343 msgid "" @@ -1858,8 +1841,9 @@ msgid "" "good-first-contributions.html>`_, where you should particularly look into " "the :code:`baselines` contributions." msgstr "" -"好的第一批贡献 `_，在这里你应该特别看看 :code:`baselines` 的贡献。" +"优秀的第一次代码贡献 `_，在这里您可以特别看看对 :code:`baselines` " +"的贡献。" #: ../../source/contributor-tutorial-get-started-as-a-contributor.rst:2 msgid "Get started as a contributor" @@ -1893,20 +1877,19 @@ msgid "" "development tools (the ones which support it). Poetry is a build tool which " "supports `PEP 517 `_." msgstr "" -"Flower 使用 :code:`pyproject.toml` 来管理依赖关系和配置开发工具（支持它的）。" -"Poetry 是一种支持 `PEP 517 `_ 的构" -"建工具。" +"Flower 使用 :code:`pyproject.toml` 来管理关联包和配置开发工具。Poetry " +"是一种支持 `PEP 517 `_ " +"的构建工具。" #: ../../source/contributor-tutorial-get-started-as-a-contributor.rst:18 msgid "Developer Machine Setup" -msgstr "开发者机器设置" +msgstr "开发者环境的设置" #: ../../source/contributor-tutorial-get-started-as-a-contributor.rst:20 msgid "" "First, clone the `Flower repository `_ from " "GitHub::" -msgstr "" -"首先，从 GitHub 克隆 \"Flower 存储库 `_\"：" +msgstr "首先，从 GitHub 克隆 \"Flower 仓库 `_\"：" #: ../../source/contributor-tutorial-get-started-as-a-contributor.rst:26 msgid "" @@ -1916,10 +1899,10 @@ msgid "" "use :code:`Python 3.8.17`, but you can change it by providing a specific :" "code:``)::" msgstr "" -"其次，创建虚拟环境（并激活它）。如果您选择使用 :code:`pyenv`（使用 :code:" -"`pyenv-virtualenv`插件），并且已经安装了该插件，则可以使用下面的便捷脚本（默" -"认情况下使用 :code:`Python3.8.17`，但您可以通过提供特定的 :code:`<版本>`来更" -"改）：：" +"其次，创建虚拟环境（并激活它）。如果您选择使用 :code:`pyenv`（ :code:`pyenv-" +"virtualenv`插件），并且已经安装了该插件，则可以使用下面的便捷脚本（" +"默认情况下使用 :code:`Python3.8.17`，但您可以通过提供特定的 :code:`< version " +">`来更改）：：" #: ../../source/contributor-tutorial-get-started-as-a-contributor.rst:33 msgid "" @@ -1934,9 +1917,8 @@ msgstr "" msgid "" "Third, install the Flower package in development mode (think :code:`pip " "install -e`) along with all necessary dependencies::" -msgstr "" -"第三，在开发模式下安装 Flower 软件包（想想 :code:`pip install -e`）以及所有必" -"要的依赖项：：" +msgstr "第三，在开发模式下安装 Flower 软件包（ :code:`pip install " +"-e`）以及所有必要的依赖项：：" #: ../../source/contributor-tutorial-get-started-as-a-contributor.rst:46 msgid "Convenience Scripts" @@ -1958,7 +1940,7 @@ msgstr "创建/删除虚拟环境" #: ../../source/contributor-tutorial-get-started-as-a-contributor.rst:62 msgid "Compile ProtoBuf Definitions" -msgstr "编译 ProtoBuf 定义" +msgstr "编译 ProtoBuf 的定义" #: ../../source/contributor-tutorial-get-started-as-a-contributor.rst:69 msgid "Auto-Format Code" @@ -1997,14 +1979,13 @@ msgstr "版本发布" msgid "" "Flower uses Poetry to build releases. The necessary command is wrapped in a " "simple script::" -msgstr "Flower 使用 Poetry 创建发布版本。必要的命令封装在一个简单的脚本中：：" +msgstr "Flower 使用 Poetry 创建发布版本。必要的命令封装在一个简单的脚本中：" #: ../../source/contributor-tutorial-get-started-as-a-contributor.rst:104 msgid "" "The resulting :code:`.whl` and :code:`.tar.gz` releases will be stored in " "the :code:`/dist` subdirectory." -msgstr "" -"生成的 :code:`.whl` 和 :code:`.tar.gz` 版本将存储在 :code:`/dist` 子目录中。" +msgstr "生成的 :code:`.whl` 和 :code:`.tar.gz` 将存储在 :code:`/dist` 子目录中。" #: ../../source/contributor-tutorial-get-started-as-a-contributor.rst:109 msgid "Build Documentation"