11# SOME DESCRIPTIVE TITLE.
2- # Copyright (C) 2001-2021 , Python Software Foundation
2+ # Copyright (C) 2001-2024 , Python Software Foundation
33# This file is distributed under the same license as the Python package.
44# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
55#
66# Translators:
77# provefar <[email protected] >, 20208- # Yinian Chin <[email protected] >, 202098# Shengjing Zhu <[email protected] >, 2020109# ww song <[email protected] >, 202011- # df2dc1c92e792f7ae8417c51df43db8f_594d92a <0f49be28017426edb1db1a2ab6e67088_717605>, 2020
12- # Freesand Leo <[email protected] >, 20201310# ppcfish <[email protected] >, 202011+ # Freesand Leo <[email protected] >, 202212+ # Rafael Fontenelle <[email protected] >, 20241413#
1514#, fuzzy
1615msgid ""
1716msgstr ""
1817"Project-Id-Version : Python 3.8\n "
1918"Report-Msgid-Bugs-To : \n "
20- "POT-Creation-Date : 2021-01-01 16:06 +0000\n "
19+ "POT-Creation-Date : 2024-06-28 17:09 +0000\n "
2120"PO-Revision-Date : 2020-05-30 11:46+0000\n "
22- "Last-Translator : ppcfish <ppcfish @gmail.com>, 2020 \n "
23- "Language-Team : Chinese (China) (https://www .transifex.com/python-doc/teams/5390/zh_CN/)\n "
21+ "Last-Translator : Rafael Fontenelle <rffontenelle @gmail.com>, 2024 \n "
22+ "Language-Team : Chinese (China) (https://app .transifex.com/python-doc/teams/5390/zh_CN/)\n "
2423"MIME-Version : 1.0\n "
2524"Content-Type : text/plain; charset=UTF-8\n "
2625"Content-Transfer-Encoding : 8bit\n "
@@ -44,23 +43,21 @@ msgid ""
4443"Python as it streamlines the process and involves less people. Learn how to "
4544":ref:`contribute <contributing-to-python>`."
4645msgstr ""
47- "有时候自己修复漏洞并将补丁提交给 Python 能更快地解决问题,因为它简化了流程并且减少了参与的人力 。 请参阅如何 :ref:`提交补丁 "
46+ "有时候自己修复漏洞并将补丁提交给 Python 能更快地解决问题,因为它简化了处理过程并且减少了参与的人力 。 请参阅如何 :ref:`提交补丁 "
4847"<contributing-to-python>`。"
4948
5049#: ../../bugs.rst:16
5150msgid "Documentation bugs"
52- msgstr "文档 Bug "
51+ msgstr "文档错误 "
5352
5453#: ../../bugs.rst:18
5554msgid ""
5655"If you find a bug in this documentation or would like to propose an "
5756"improvement, please submit a bug report on the :ref:`tracker <using-the-"
5857"tracker>`. If you have a suggestion on how to fix it, include that as well."
5958msgstr ""
60- "如果您在本文档中发现了错误并打算帮助我们改进,请将错误提交到 :ref:`追踪系统 <using-the-tracker>`。 "
61- "如果您有相应的修正建议,请一并提交。 (译者注:如果是中文文档翻译相关的错误,请务必提交到 "
62- "https://github.com/python/python-docs-zh-"
63- "cn/issues。如果将翻译问题反馈到了其他地方,可能会因为语言不通而不能及时处理。)"
59+ "如果你在这篇文档中找到了一个错误或是想指出一个可改进的地方,请在 :ref:`tracker <using-the-tracker>` "
60+ "上提交一个错误报告。 如果你有关于改进该问题的建议,请与报告一并提交。"
6461
6562#: ../../bugs.rst:22
6663msgid ""
@@ -74,7 +71,7 @@ msgstr ""
7471
7572#: ../../bugs.rst:30
7673msgid "`Documentation bugs`_"
77- msgstr "`Documentation bugs `_"
74+ msgstr "`文档错误 `_"
7875
7976#: ../../bugs.rst:30
8077msgid ""
@@ -110,53 +107,56 @@ msgstr "使用 Python 的问题追踪系统"
110107
111108#: ../../bugs.rst:43
112109msgid ""
113- "Bug reports for Python itself should be submitted via the Python Bug Tracker"
114- " (https://bugs.python.org/). The bug tracker offers a Web form which allows"
115- " pertinent information to be entered and submitted to the developers."
110+ "Issue reports for Python itself should be submitted via the GitHub issues "
111+ "tracker (https://github.com/python/cpython/issues). The GitHub issues "
112+ "tracker offers a web form which allows pertinent information to be entered "
113+ "and submitted to the developers."
116114msgstr ""
117- "对于 Python 本身的错误报告应当通过 Python "
118- "错误追踪系统(https://bugs.python.org/)进行提交。该错误追踪系统提供了一个可以输入并提交相关信息给开发者的网页表单。"
115+ "针对 Python 本身的问题报告应当通过 GitHub 问题追踪系统 "
116+ "(https://github.com/python/cpython/issues) 来提交。 GitHub "
117+ "问题追踪系统提供了一个网页表单用来输入并提交相关信息给开发者。"
119118
120- #: ../../bugs.rst:47
119+ #: ../../bugs.rst:48
121120msgid ""
122121"The first step in filing a report is to determine whether the problem has "
123122"already been reported. The advantage in doing so, aside from saving the "
124- "developers time, is that you learn what has been done to fix it; it may be "
123+ "developers' time, is that you learn what has been done to fix it; it may be "
125124"that the problem has already been fixed for the next release, or additional "
126125"information is needed (in which case you are welcome to provide it if you "
127- "can!). To do this, search the bug database using the search box on the top "
128- "of the page."
126+ "can!). To do this, search the tracker using the search box at the top of the "
127+ " page."
129128msgstr ""
130- "第一步是确认是否有重复的报告。这样做除了可以节省开发者的时间,也能让您从中了解到我们做出了怎样的努力;我们有可能已经在下个版本中修复了这个问题,也有可能需要更详细的信息(在这种情况下,非常欢迎您提供!)。要查找重复的报告,请使用顶部的搜索栏进行搜索。"
129+ "第一步是确定问题是否已经被报告了。 "
130+ "这样做的好处除了可以节省开发者的时间,还可以让你了解该问题是如何解决的;有可能该问题已在下一发布版中被修复,或者还需要额外的信息(在此情况下非常欢迎你来提供信息!)。"
131+ " 要确定这一点,请使用页面顶部的搜索框来搜索问题追踪系统。"
131132
132- #: ../../bugs.rst:54
133+ #: ../../bugs.rst:55
133134msgid ""
134- "If the problem you're reporting is not already in the bug tracker, go back "
135- "to the Python Bug Tracker and log in. If you don't already have a tracker "
136- "account, select the \" Register\" link or, if you use OpenID, one of the "
137- "OpenID provider logos in the sidebar. It is not possible to submit a bug "
138- "report anonymously."
135+ "If the problem you're reporting is not already in the list, log in to "
136+ "GitHub. If you don't already have a GitHub account, create a new account "
137+ "using the \" Sign up\" link. It is not possible to submit a bug report "
138+ "anonymously."
139139msgstr ""
140- "如果您没有搜索到您想报告的问题,请返回并登录 Python "
141- "错误追踪系统。如果您没有账号,请点击“注册(Register)”链接,或者在侧边栏中选择任何一个 OpenID 登录方式。您不能匿名提交一份错误报告 。"
140+ "如果你要报告的问题未出现在列表中,请登录 GitHub 报告。 如果你还没有 GitHub 账号,请使用 \" Sign up \" 链接新建一个账号。 "
141+ "错误报告是不可能自动被提交的 。"
142142
143- #: ../../bugs.rst:59
143+ #: ../../bugs.rst:60
144144msgid ""
145- "Being now logged in, you can submit a bug. Select the \" Create New\" link "
146- "in the sidebar to open the bug reporting form ."
147- msgstr "如果已经登录, 那您就可以提交错误报告了。请点击侧边栏中的“新建(Create New)”链接,打开报告表单 。"
145+ "Being now logged in, you can submit an issue. Click on the \" New issue \" "
146+ "button in the top bar to report a new issue ."
147+ msgstr "当你登录之后,就可以提交问题了。 请点击顶端栏的 \" New issue \" 按钮来报告新问题 。"
148148
149- #: ../../bugs.rst:62
149+ #: ../../bugs.rst:63
150+ msgid "The submission form has two fields, \" Title\" and \" Comment\" ."
151+ msgstr "提交表单有两个字段,\" Title\" 和 \" Comment\" 。"
152+
153+ #: ../../bugs.rst:65
150154msgid ""
151- "The submission form has a number of fields. For the \" Title\" field, enter "
152- "a *very* short description of the problem; less than ten words is good. In "
153- "the \" Type\" field, select the type of your problem; also select the "
154- "\" Component\" and \" Versions\" to which the bug relates."
155- msgstr ""
156- "表单中有几个空栏(译者注:请用英语填写)。请在 “标题(Title)”栏填入对问题 *非常* 简短的描述;一个好的描述应当少于十个单词。在 "
157- "“类型(Type)”栏,选择您的问题的类型;同样地,选择 bug 相对应的“组件(Component)”和“版本(Versions)”。"
155+ "For the \" Title\" field, enter a *very* short description of the problem; "
156+ "less than ten words is good."
157+ msgstr "对于 \" Title\" 字段,请输入一段 *非常* 简短的问题描述;最好是少于十个单词。"
158158
159- #: ../../bugs.rst:67
159+ #: ../../bugs.rst:68
160160msgid ""
161161"In the \" Comment\" field, describe the problem in detail, including what you"
162162" expected to happen and what did happen. Be sure to include whether any "
@@ -165,44 +165,44 @@ msgid ""
165165msgstr ""
166166"在“说明(Comment)”栏,请详细描述问题,包括您预期的情况和实际的情况。请确保包含任何涉及的拓展模块,以及您当时所使用的硬件和软件平台(如果可能,请附上版本信息)。"
167167
168- #: ../../bugs.rst:72
168+ #: ../../bugs.rst:73
169169msgid ""
170- "Each bug report will be assigned to a developer who will determine what "
171- "needs to be done to correct the problem. You will receive an update each "
172- "time action is taken on the bug ."
173- msgstr "每一份错误报告将被分派给一名开发者,并由这名开发者决定如何修正这个问题。每当有相关的进展时,您都会收到通知 。"
170+ "Each issue report will be reviewed by a developer who will determine what "
171+ "needs to be done to correct the problem. You will receive an update each "
172+ "time an action is taken on the issue ."
173+ msgstr "每个问题报告将由一位开发者进行审查并决定要以何种方式来修正该问题。 每当对该问题有新的处理措施时你都会收到更新的消息 。"
174174
175- #: ../../bugs.rst:81
175+ #: ../../bugs.rst:82
176176msgid ""
177177"`How to Report Bugs Effectively "
178178"<https://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_"
179179msgstr "`如何有效地报告错误 <https://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_"
180180
181- #: ../../bugs.rst:80
181+ #: ../../bugs.rst:81
182182msgid ""
183183"Article which goes into some detail about how to create a useful bug report."
184184" This describes what kind of information is useful and why it is useful."
185185msgstr "该文章详细介绍了如何创建一份有用的错误报告。它描述了什么样的信息是有用的,以及为什么是有用的。"
186186
187- #: ../../bugs.rst:84
187+ #: ../../bugs.rst:85
188188msgid ""
189189"`Bug Report Writing Guidelines <https://developer.mozilla.org/en-"
190190"US/docs/Mozilla/QA/Bug_writing_guidelines>`_"
191191msgstr ""
192192"`错误报告编写指南 <https://developer.mozilla.org/en-"
193193"US/docs/Mozilla/QA/Bug_writing_guidelines>`_"
194194
195- #: ../../bugs.rst:84
195+ #: ../../bugs.rst:85
196196msgid ""
197197"Information about writing a good bug report. Some of this is specific to "
198198"the Mozilla project, but describes general good practices."
199199msgstr "关于写一份好的错误报告。部分仅针对 Mozilla 项目,不过其描述了通用的恰当做法。"
200200
201- #: ../../bugs.rst:90
201+ #: ../../bugs.rst:91
202202msgid "Getting started contributing to Python yourself"
203203msgstr "开始为 Python 贡献您的知识"
204204
205- #: ../../bugs.rst:92
205+ #: ../../bugs.rst:93
206206msgid ""
207207"Beyond just reporting bugs that you find, you are also welcome to submit "
208208"patches to fix them. You can find more information on how to get started "
0 commit comments