Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Commit 6284a89

Browse files
github-actions[bot]github-actions[bot]
authored
sync with cpython a05dae23
1 parent 6ba7aec commit 6284a89

File tree

3 files changed

+274
-267
lines changed

3 files changed

+274
-267
lines changed

‎bugs.po

Lines changed: 51 additions & 37 deletions
Original file line numberDiff line numberDiff line change
@@ -13,7 +13,7 @@ msgid ""
1313
msgstr ""
1414
"Project-Id-Version: Python 3.10\n"
1515
"Report-Msgid-Bugs-To: \n"
16-
"POT-Creation-Date: 2022-04-17 00:15+0000\n"
16+
"POT-Creation-Date: 2022-08-04 00:16+0000\n"
1717
"PO-Revision-Date: 2022-06-08 11:49+0800\n"
1818
"Last-Translator: Adrian Liaw <[email protected]>\n"
1919
"Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"
@@ -126,64 +126,66 @@ msgid "Using the Python issue tracker"
126126
msgstr "使用 Python 問題追蹤系統"
127127

128128
#: ../../bugs.rst:47
129+
#, fuzzy
129130
msgid ""
130-
"Bug reports for Python itself should be submitted via the Python Bug Tracker "
131-
"(https://bugs.python.org/). The bug tracker offers a web form which allows "
132-
"pertinent information to be entered and submitted to the developers."
131+
"Issue reports for Python itself should be submitted via the GitHub issues "
132+
"tracker (https://github.com/python/cpython/issues). The GitHub issues "
133+
"tracker offers a web form which allows pertinent information to be entered "
134+
"and submitted to the developers."
133135
msgstr ""
134136
"對於 Python 本身的錯誤報告，應該透過 Python 錯誤追蹤系統 (https://bugs."
135137
"python.org/) 提交。這個錯誤追蹤系統提供了一個網頁表單，可以輸入並提交相關資訊"
136138
"給開發者。"
137139

138-
#: ../../bugs.rst:51
140+
#: ../../bugs.rst:52
141+
#, fuzzy
139142
msgid ""
140143
"The first step in filing a report is to determine whether the problem has "
141144
"already been reported. The advantage in doing so, aside from saving the "
142-
"developers time, is that you learn what has been done to fix it; it may be "
145+
"developers' time, is that you learn what has been done to fix it; it may be "
143146
"that the problem has already been fixed for the next release, or additional "
144147
"information is needed (in which case you are welcome to provide it if you "
145-
"can!). To do this, search the bug database using the search box on the top "
146-
"of the page."
148+
"can!). To do this, search the tracker using the search box at the top of the "
149+
"page."
147150
msgstr ""
148151
"填寫報告的第一步，是確認該問題是否已經被回報過了。這樣做的好處，除了可以節省"
149152
"開發者的時間，也能讓您了解目前關於該問題的處理進度；有可能已經在下一個發行版"
150153
"本中修正了這個問題，也有可能需要更詳細的資訊（在這種情況下，如果可以，非常歡"
151154
"迎您提供資訊！）。要確認是否重複回報，請使用頁面頂端的搜尋框來搜尋錯誤資料"
152155
"庫。"
153156

154-
#: ../../bugs.rst:58
157+
#: ../../bugs.rst:59
158+
#, fuzzy
155159
msgid ""
156-
"If the problem you're reporting is not already in the bug tracker, go back "
157-
"to the Python Bug Tracker and log in. If you don't already have a tracker "
158-
"account, select the \"Register\" link or, if you use OpenID, one of the "
159-
"OpenID provider logos in the sidebar. It is not possible to submit a bug "
160-
"report anonymously."
160+
"If the problem you're reporting is not already in the list, log in to "
161+
"GitHub. If you don't already have a GitHub account, create a new account "
162+
"using the \"Sign up\" link. It is not possible to submit a bug report "
163+
"anonymously."
161164
msgstr ""
162165
"如果您想回報的問題還沒有在錯誤追蹤系統出現過，請返回並登入 Python 錯誤追蹤系"
163166
"統。如果您還沒有系統的帳號，請點選「註冊 (Register)」，如果您有 OpenID，也可"
164167
"以在側邊欄中點選其中一個 OpenID 的提供者圖示。您無法以匿名方式提交錯誤報告。"
165168

166-
#: ../../bugs.rst:63
169+
#: ../../bugs.rst:64
170+
#, fuzzy
167171
msgid ""
168-
"Being now logged in, you can submit a bug. Select the \"Create New\" link "
169-
"in the sidebar to open the bug reporting form."
172+
"Being now logged in, you can submit an issue. Click on the \"New issue\" "
173+
"button in the top bar to report a new issue."
170174
msgstr ""
171175
"如果已經登入，那您就可以提交一個錯誤。請點選側邊欄中的「新建 (Create New)」連"
172176
"結，開啟錯誤回報表單。"
173177

174-
#: ../../bugs.rst:66
178+
#: ../../bugs.rst:67
179+
msgid "The submission form has two fields, \"Title\" and \"Comment\"."
180+
msgstr ""
181+
182+
#: ../../bugs.rst:69
175183
msgid ""
176-
"The submission form has a number of fields. For the \"Title\" field, enter "
177-
"a *very* short description of the problem; less than ten words is good. In "
178-
"the \"Type\" field, select the type of your problem; also select the "
179-
"\"Component\" and \"Versions\" to which the bug relates."
184+
"For the \"Title\" field, enter a *very* short description of the problem; "
185+
"less than ten words is good."
180186
msgstr ""
181-
"提交的表單中有幾個欄位。（譯者註：所有欄位請皆用英文輸入。）在「標題 "
182-
"(Title)」欄位，輸入對該問題\\ *非常*\\ 簡短的描述；最好少於十個單字。在「類"
183-
"型 (Type)」欄位，選擇您的問題類型；也要選擇與錯誤相關的「Component（組件）」"
184-
"和「Versions（版本）」。"
185187

186-
#: ../../bugs.rst:71
188+
#: ../../bugs.rst:72
187189
msgid ""
188190
"In the \"Comment\" field, describe the problem in detail, including what you "
189191
"expected to happen and what did happen. Be sure to include whether any "
@@ -194,51 +196,52 @@ msgstr ""
194196
"情況。請確定說明中包含了涉及到的任何擴充模組，以及您當時所使用的硬體和軟體平"
195197
"台（視情況而定，可以附上版本資訊）。"
196198

197-
#: ../../bugs.rst:76
199+
#: ../../bugs.rst:77
200+
#, fuzzy
198201
msgid ""
199-
"Each bug report will be assigned to a developer who will determine what "
200-
"needs to be done to correct the problem. You will receive an update each "
201-
"time action is taken on the bug."
202+
"Each issue report will be reviewed by a developer who will determine what "
203+
"needs to be done to correct the problem. You will receive an update each "
204+
"time an action is taken on the issue."
202205
msgstr ""
203206
"每一份錯誤報告會被分派給一位開發者，並由他決定要做出什麼變更來修正這個問題。"
204207
"每當該錯誤有修正動作時，您會收到更新回報。"
205208

206-
#: ../../bugs.rst:85
209+
#: ../../bugs.rst:86
207210
msgid ""
208211
"`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/"
209212
"~sgtatham/bugs.html>`_"
210213
msgstr ""
211214
"`如何有效地回報錯誤 <https://www.chiark.greenend.org.uk/~sgtatham/bugs."
212215
"html>`_"
213216

214-
#: ../../bugs.rst:84
217+
#: ../../bugs.rst:85
215218
msgid ""
216219
"Article which goes into some detail about how to create a useful bug report. "
217220
"This describes what kind of information is useful and why it is useful."
218221
msgstr ""
219222
"這篇文章詳細說明如何建立一份有用的錯誤報告。它描述了什麼樣的資訊是有用的，以"
220223
"及這些資訊為什麼有用。"
221224

222-
#: ../../bugs.rst:88
225+
#: ../../bugs.rst:89
223226
msgid ""
224227
"`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-"
225228
"writing.html>`_"
226229
msgstr ""
227230
"`錯誤撰寫指南 <https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html>`_"
228231

229-
#: ../../bugs.rst:88
232+
#: ../../bugs.rst:89
230233
msgid ""
231234
"Information about writing a good bug report. Some of this is specific to "
232235
"the Mozilla project, but describes general good practices."
233236
msgstr ""
234237
"撰寫一份優良錯誤報告的相關資訊。部分的文章內容是針對 Mozilla 專案，但它也描述"
235238
"了通用的好習慣。"
236239

237-
#: ../../bugs.rst:94
240+
#: ../../bugs.rst:95
238241
msgid "Getting started contributing to Python yourself"
239242
msgstr "開始讓自己貢獻 Python"
240243

241-
#: ../../bugs.rst:96
244+
#: ../../bugs.rst:97
242245
msgid ""
243246
"Beyond just reporting bugs that you find, you are also welcome to submit "
244247
"patches to fix them. You can find more information on how to get started "
@@ -250,3 +253,14 @@ msgstr ""
250253
"您可以在 `Python 開發者指南`_\\ 中找到如何開始修補 Python 的更多資訊。如果您"
251254
"有任何問題，\\ `核心導師郵寄清單`_\\ 是一個友善的地方，您可以在那裡得到，關"
252255
"於 Python 修正錯誤的過程中，所有問題的答案。"
256+
257+
#~ msgid ""
258+
#~ "The submission form has a number of fields. For the \"Title\" field, "
259+
#~ "enter a *very* short description of the problem; less than ten words is "
260+
#~ "good. In the \"Type\" field, select the type of your problem; also "
261+
#~ "select the \"Component\" and \"Versions\" to which the bug relates."
262+
#~ msgstr ""
263+
#~ "提交的表單中有幾個欄位。（譯者註：所有欄位請皆用英文輸入。）在「標題 "
264+
#~ "(Title)」欄位，輸入對該問題\\ *非常*\\ 簡短的描述；最好少於十個單字。在"
265+
#~ "「類型 (Type)」欄位，選擇您的問題類型；也要選擇與錯誤相關的「Component（組"
266+
#~ "件）」和「Versions（版本）」。"

0 commit comments

Comments
 (0)