11# SOME DESCRIPTIVE TITLE.
2- # Copyright (C) 2001-2021 , Python Software Foundation
2+ # Copyright (C) 2001-2023 , 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# hanfeng <[email protected] >, 201988# Yinian Chin <[email protected] >, 201999# ww song <[email protected] >, 201910- # df2dc1c92e792f7ae8417c51df43db8f_594d92a <0f49be28017426edb1db1a2ab6e67088_717605>, 2019
11- # Freesand Leo <[email protected] >, 20191210# Larry Wang <[email protected] >, 201913- 14111512# rpish yao <[email protected] >, 20191613# ppcfish <[email protected] >, 201914+ # Freesand Leo <[email protected] >, 20221715#
1816#, fuzzy
1917msgid ""
2018msgstr ""
2119"Project-Id-Version : Python 3.7\n "
2220"Report-Msgid-Bugs-To : \n "
23- "POT-Creation-Date : 2021-01-01 16:02 +0000\n
21+ "POT-Creation-Date : 2023-02-24 14:40 +0000\n
2422"PO-Revision-Date : 2019-09-01 02:40+0000\n "
25- "Last-Translator : ppcfish <ppcfish@gmail .com>, 2019 \n
23+ "Last-Translator : Freesand Leo <yuqinju@163 .com>, 2022 \n
2624"Language-Team : Chinese (China) (https://www.transifex.com/python-doc/teams/5390/zh_CN/)\n "
2725"MIME-Version : 1.0\n "
2826"Content-Type : text/plain; charset=UTF-8\n "
2927"Content-Transfer-Encoding : 8bit\n "
3028"Language : zh_CN\n "
3129"Plural-Forms : nplurals=1; plural=0;\n "
3230
33- #: ../.. /bugs.rst:5
31+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc /bugs.rst:5
3432msgid "Dealing with Bugs"
3533msgstr "解决 Bug"
3634
37- #: ../.. /bugs.rst:7
35+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc /bugs.rst:7
3836msgid ""
3937"Python is a mature programming language which has established a reputation "
4038"for stability. In order to maintain this reputation, the developers would "
4139"like to know of any deficiencies you find in Python."
4240msgstr "Python 是一门以稳定著称的编程语言。为了保持它的稳定性，开发者们想了解您在 Python 中发现的任何缺陷。"
4341
44- #: ../.. /bugs.rst:11
42+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc /bugs.rst:11
4543msgid ""
4644"It can be sometimes faster to fix bugs yourself and contribute patches to "
4745"Python as it streamlines the process and involves less people. Learn how to "
@@ -50,11 +48,11 @@ msgstr ""
5048"有时候自己修复漏洞并将补丁提交给 Python 能更快地解决问题，因为它简化了流程并且减少了参与的人力。 请参阅如何 :ref:`提交补丁 "
5149"<contributing-to-python>`。"
5250
53- #: ../.. /bugs.rst:16
51+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc /bugs.rst:16
5452msgid "Documentation bugs"
5553msgstr "文档 Bug"
5654
57- #: ../.. /bugs.rst:18
55+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc /bugs.rst:18
5856msgid ""
5957"If you find a bug in this documentation or would like to propose an "
6058"improvement, please submit a bug report on the :ref:`tracker <using-the-"
@@ -65,7 +63,7 @@ msgstr ""
6563"https://github.com/python/python-docs-zh-"
6664"cn/issues。如果将翻译问题反馈到了其他地方，可能会因为语言不通而不能及时处理。）"
6765
68- #: ../.. /bugs.rst:22
66+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc /bugs.rst:22
6967msgid ""
7068"If you're short on time, you can also email documentation bug reports to "
7169"[email protected] (behavioral bugs can be sent to [email protected] ). " @@ -75,64 +73,66 @@ msgstr ""
7573"如果您时间有限，还可以通过电子邮件将文档的错误报告发送至 [email protected] （代码运行错误请发送至 python-" 7674"[email protected] ）。“docs@”是一个由志愿者运作的邮件列表；您的请求会得到关注，但可能需要一些时间才会被处理。" 7775
78- #: ../.. /bugs.rst:28
76+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc /bugs.rst:28
7977msgid "`Documentation bugs`_ on the Python issue tracker"
8078msgstr "在 Python 的错误追踪系统上的 `Documentation bugs`_"
8179
82- #: ../.. /bugs.rst:33
80+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc /bugs.rst:33
8381msgid "Using the Python issue tracker"
8482msgstr "使用 Python 的问题追踪系统"
8583
86- #: ../.. /bugs.rst:35
84+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc /bugs.rst:35
8785msgid ""
88- "Bug reports for Python itself should be submitted via the Python Bug Tracker"
89- " (https://bugs.python.org/). The bug tracker offers a Web form which allows"
90- " pertinent information to be entered and submitted to the developers."
86+ "Issue reports for Python itself should be submitted via the GitHub issues "
87+ "tracker (https://github.com/python/cpython/issues). The GitHub issues "
88+ "tracker offers a web form which allows pertinent information to be entered "
89+ "and submitted to the developers."
9190msgstr ""
92- "对于 Python 本身的错误报告应当通过 Python "
93- "错误追踪系统（https://bugs.python.org/）进行提交。该错误追踪系统提供了一个可以输入并提交相关信息给开发者的网页表单。"
91+ "针对 Python 本身的问题报告应当通过 GitHub 问题追踪系统 "
92+ "(https://github.com/python/cpython/issues) 来提交。 GitHub "
93+ "问题追踪系统提供了一个网页表单用来输入并提交相关信息给开发者。"
9494
95- #: ../../ bugs.rst:39
95+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/ bugs.rst:40
9696msgid ""
9797"The first step in filing a report is to determine whether the problem has "
9898"already been reported. The advantage in doing so, aside from saving the "
99- "developers time, is that you learn what has been done to fix it; it may be "
99+ "developers' time, is that you learn what has been done to fix it; it may be "
100100"that the problem has already been fixed for the next release, or additional "
101101"information is needed (in which case you are welcome to provide it if you "
102- "can!). To do this, search the bug database using the search box on the top "
103- "of the page."
102+ "can!). To do this, search the tracker using the search box at the top of the "
103+ " page."
104104msgstr ""
105- "填写报告的第一步是确认是否有重复的报告。这样做除了可以节省开发者的时间，也能让您从中为了解决这个问题我们做出了怎样的努力；我们有可能我们已经在下个版本中修复了这个问题，也有可能需要更详细的信息来搞定它（在这种情况下，如果可以，非常欢迎您提供这些信息！）。要查找重复的报告，请使用错误数据库页面顶部的搜索栏进行搜索。"
105+ "第一步是确定问题是否已经被报告了。 "
106+ "这样做的好处除了可以节省开发者的时间，还可以让你了解该问题是如何解决的；有可能该问题已在下一发布版中被修复，或者还需要额外的信息（在此情况下非常欢迎你来提供信息！）。"
107+ " 要确定这一点，请使用页面顶部的搜索框来搜索问题追踪系统。"
106108
107- #: ../../ bugs.rst:46
109+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/ bugs.rst:47
108110msgid ""
109- "If the problem you're reporting is not already in the bug tracker, go back "
110- "to the Python Bug Tracker and log in. If you don't already have a tracker "
111- "account, select the \" Register\" link or, if you use OpenID, one of the "
112- "OpenID provider logos in the sidebar. It is not possible to submit a bug "
113- "report anonymously."
111+ "If the problem you're reporting is not already in the list, log in to "
112+ "GitHub. If you don't already have a GitHub account, create a new account "
113+ "using the \" Sign up\" link. It is not possible to submit a bug report "
114+ "anonymously."
114115msgstr ""
115- "如果您正在报告的问题并没有记录在错误追踪系统中，请返回并登录 Python "
116- "错误追踪系统。如果您没有一个错误追踪系统的账号，请选择“注册（Register）”链接，或者如果您想使用 OpenID 的话，请选择侧边栏中任何一个 "
117- "OpenID 提供方的标识。您不能匿名提交一份错误报告。"
116+ "如果你要报告的问题未出现在列表中，请登录 GitHub 报告。 如果你还没有 GitHub 账号，请使用 \" Sign up\" 链接新建一个账号。 "
117+ "错误报告是不可能自动被提交的。"
118118
119- #: ../../ bugs.rst:51
119+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/ bugs.rst:52
120120msgid ""
121- "Being now logged in, you can submit a bug. Select the \" Create New\" link "
122- "in the sidebar to open the bug reporting form ."
123- msgstr "如果已经登录， 那您就可以提交错误报告了。请点击侧边栏中的“新建（Create New）”链接，打开错误报告表单 。"
121+ "Being now logged in, you can submit an issue. Click on the \" New issue \" "
122+ "button in the top bar to report a new issue ."
123+ msgstr "当你登录之后，就可以提交问题了。 请点击顶端栏的 \" New issue \" 按钮来报告新问题 。"
124124
125- #: ../../bugs.rst:54
125+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/bugs.rst:55
126+ msgid "The submission form has two fields, \" Title\" and \" Comment\" ."
127+ msgstr "提交表单有两个字段，\" Title\" 和 \" Comment\" 。"
128+
129+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/bugs.rst:57
126130msgid ""
127- "The submission form has a number of fields. For the \" Title\" field, enter "
128- "a *very* short description of the problem; less than ten words is good. In "
129- "the \" Type\" field, select the type of your problem; also select the "
130- "\" Component\" and \" Versions\" to which the bug relates."
131- msgstr ""
132- "表单中有几个空栏。请在 “标题” 栏填入一个对问题的非常简短的描述；一个好的描述应当少于十个字。在 “类型” "
133- "栏，选择您的问题的类型；同样地，选择bug相对应的 “组件” 和 “版本” 。"
131+ "For the \" Title\" field, enter a *very* short description of the problem; "
132+ "less than ten words is good."
133+ msgstr "对于 \" Title\" 字段，请输入一段 *非常* 简短的问题描述；最好是少于十个单词。"
134134
135- #: ../../ bugs.rst:59
135+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/ bugs.rst:60
136136msgid ""
137137"In the \" Comment\" field, describe the problem in detail, including what you"
138138" expected to happen and what did happen. Be sure to include whether any "
@@ -141,44 +141,44 @@ msgid ""
141141msgstr ""
142142"在”说明“栏，请详细描述问题，包括您预期的情况和实际的情况。请确保信息包含任何涉及的拓展模块，以及您当时所使用的硬件和软件平台(如果可能，请附上版本信息)。"
143143
144- #: ../../ bugs.rst:64
144+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/ bugs.rst:65
145145msgid ""
146- "Each bug report will be assigned to a developer who will determine what "
147- "needs to be done to correct the problem. You will receive an update each "
148- "time action is taken on the bug ."
149- msgstr "每一份错误报告将被分派给一名开发者，并由这名开发者决定如何更正这个问题。每当有针对该错误的进展时，您都会收到一个更新通知 。"
146+ "Each issue report will be reviewed by a developer who will determine what "
147+ "needs to be done to correct the problem. You will receive an update each "
148+ "time an action is taken on the issue ."
149+ msgstr "每个问题报告将由一位开发者进行审查并决定要以何种方式来修正该问题。 每当对该问题有新的处理措施时你都会收到更新的消息 。"
150150
151- #: ../../ bugs.rst:73
151+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/ bugs.rst:74
152152msgid ""
153153"`How to Report Bugs Effectively "
154154"<https://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_"
155155msgstr "`如何高效地报告错误 <http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_"
156156
157- #: ../../ bugs.rst:72
157+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/ bugs.rst:73
158158msgid ""
159159"Article which goes into some detail about how to create a useful bug report."
160160" This describes what kind of information is useful and why it is useful."
161161msgstr "文章详细描述了如何创建一份有用的错误报告。同时描述了什么样的信息是有用的以及为什么是有用的。"
162162
163- #: ../../ bugs.rst:76
163+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/ bugs.rst:77
164164msgid ""
165165"`Bug Report Writing Guidelines <https://developer.mozilla.org/en-"
166166"US/docs/Mozilla/QA/Bug_writing_guidelines>`_"
167167msgstr ""
168168"`错误报告编写指南 <https://developer.mozilla.org/en-"
169169"US/docs/Mozilla/QA/Bug_writing_guidelines>`_"
170170
171- #: ../../ bugs.rst:76
171+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/ bugs.rst:77
172172msgid ""
173173"Information about writing a good bug report. Some of this is specific to "
174174"the Mozilla project, but describes general good practices."
175175msgstr "有关书写一份好的错误报告的信息。部分仅针对 Mozilla 项目，不过其描述了通用的恰当做法。"
176176
177- #: ../../ bugs.rst:82
177+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/ bugs.rst:83
178178msgid "Getting started contributing to Python yourself"
179179msgstr "开始为 Python 贡献您的知识"
180180
181- #: ../../ bugs.rst:84
181+ #: /home/runner/work/docspush-transifex/docspush-transifex/cpython/Doc/ bugs.rst:85
182182msgid ""
183183"Beyond just reporting bugs that you find, you are also welcome to submit "
184184"patches to fix them. You can find more information on how to get started "
0 commit comments