8000 Update bugs.po (#311) · python/python-docs-zh-tw@6e99e94 · GitHub
[go: up one dir, main page]
Skip to content

Commit 6e99e94

Browse files
StevenHsuYLStevenHsuYL
authored
Update bugs.po (#311)
Sync with CPython 3.10.
1 parent 46f8499 commit 6e99e94

File tree

1 file changed

+53
-56
lines changed

1 file changed

+53
-56
lines changed

‎bugs.po

Lines changed: 53 additions & 56 deletions
Original file line numberDiff line numberDiff line change
@@ -8,22 +8,22 @@
88
# aminzai <lagunawang@gmail.com>, 2015
99
# Liang-Bo Wang <me@liang2.tw>, 2015
1010
# sammy huang <sammy.huang@kkday.com>, 2017
11-
# Steven Hsu <hsuhaochun@gmail.com>, 2021
11+
# Steven Hsu <hsuhaochun@gmail.com>, 2021-2022
1212
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"
17-
"PO-Revision-Date: 2022-06-08 11:49+0800\n"
18-
"Last-Translator: Adrian Liaw <adrianliaw2000@gmail.com>\n"
16+
"POT-Creation-Date: 2022-08-04 00:16+0000\n"
17+
"PO-Revision-Date: 2022-08-31 12:34+0800\n"
18+
"Last-Translator: Steven Hsu <hsuhaochun@gmail.com>\n"
1919
"Language-Team: Chinese - TAIWAN (https://github.com/python/python-docs-zh-"
2020
"tw)\n"
2121
"Language: zh_TW\n"
2222
"MIME-Version: 1.0\n"
2323
"Content-Type: text/plain; charset=UTF-8\n"
2424
"Content-Transfer-Encoding: 8bit\n"
2525
"Plural-Forms: nplurals=1; plural=0;\n"
26-
"X-Generator: Poedit 3.0.1\n"
26+
"X-Generator: Poedit 3.1.1\n"
2727

2828
#: ../../bugs.rst:5
2929
msgid "Dealing with Bugs"
@@ -127,118 +127,115 @@ msgstr "使用 Python 問題追蹤系統"
127127

128128
#: ../../bugs.rst:47
129129
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."
130+
"Issue reports for Python itself should be submitted via the GitHub issues "
131+
"tracker (https://github.com/python/cpython/issues). The GitHub issues "
132+
"tracker offers a web form which allows pertinent information to be entered "
133+
"and submitted to the developers."
133134
msgstr ""
134-
"對於 Python 本身的錯誤報告，應該透過 Python 錯誤追蹤系統 (https://bugs."
135-
"python.org/) 提交。這個錯誤追蹤系統提供了一個網頁表單，可以輸入並提交相關資訊"
136-
"給開發者。"
135+
"對於 Python 本身的問題報告，應該透過 GitHub 問題追蹤系統 (https://github.com/"
136+
"python/cpython/issues) 提交。這個 GitHub 問題追蹤系統提供了一個網頁表單，可以"
137+
"輸入並提交相關資訊給開發者。"
137138

138-
#: ../../bugs.rst:51
139+
#: ../../bugs.rst:52
139140
msgid ""
140141
"The first step in filing a report is to determine whether the problem has "
141142
"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 "
143+
"developers' time, is that you learn what has been done to fix it; it may be "
143144
"that the problem has already been fixed for the next release, or additional "
144145
"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."
146+
"can!). To do this, search the tracker using the search box at the top of the "
147+
"page."
147148
msgstr ""
148149
"填寫報告的第一步，是確認該問題是否已經被回報過了。這樣做的好處，除了可以節省"
149150
"開發者的時間，也能讓您了解目前關於該問題的處理進度；有可能已經在下一個發行版"
150151
"本中修正了這個問題，也有可能需要更詳細的資訊（在這種情況下，如果可以，非常歡"
151-
"迎您提供資訊！）。要確認是否重複回報，請使用頁面頂端的搜尋框來搜尋錯誤資料"
152-
"庫。"
152+
"迎您提供資訊！）。要確認是否重複回報，請使用頁面頂端的搜尋框來搜尋追蹤系統。"
153153

154-
#: ../../bugs.rst:58
154+
#: ../../bugs.rst:59
155155
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."
156+
"If the problem you're reporting is not already in the list, log in to "
157+
"GitHub. If you don't already have a GitHub account, create a new account "
158+
"using the \"Sign up\" link. It is not possible to submit a bug report "
159+
"anonymously."
161160
msgstr ""
162-
"如果您想回報的問題還沒有在錯誤追蹤系統出現過，請返回並登入 Python 錯誤追蹤系"
163-
"統。如果您還沒有系統的帳號，請點選「註冊 (Register)」，如果您有 OpenID，也可"
164-
"以在側邊欄中點選其中一個 OpenID 的提供者圖示。您無法以匿名方式提交錯誤報告。"
161+
"如果您想回報的問題還沒有在問題列表出現過，請登入 GitHub。如果您還沒有 GitHub "
162+
"帳戶，請點選「Sign up」連結來建立一個新的帳戶。您無法以匿名方式提交錯誤報告。"
165163

166-
#: ../../bugs.rst:63
164+
#: ../../bugs.rst:64
167165
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."
166+
"Being now logged in, you can submit an issue. Click on the \"New issue\" "
167+
"button in the top bar to report a new issue."
170168
msgstr ""
171-
"如果已經登入，那您就可以提交一個錯誤。請點選側邊欄中的「新建 (Create New)」連"
172-
"結，開啟錯誤回報表單。"
169+
"如果已經登入，那您就可以提交問題了。請點選列表頂端區域的「New issue」按鈕，來"
170+
"回報一個新的問題。"
173171

174-
#: ../../bugs.rst:66
172+
#: ../../bugs.rst:67
173+
msgid "The submission form has two fields, \"Title\" and \"Comment\"."
174+
msgstr "提交的表單中有兩個欄位，「Title」及「Comment」。"
175+
176+
#: ../../bugs.rst:69
175177
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."
178+
"For the \"Title\" field, enter a *very* short description of the problem; "
179+
"less than ten words is good."
180180
msgstr ""
181-
"提交的表單中有幾個欄位。（譯者註：所有欄位請皆用英文輸入。）在「標題 "
182-
"(Title)」欄位，輸入對該問題\\ *非常*\\ 簡短的描述；最好少於十個單字。在「類"
183-
"型 (Type)」欄位，選擇您的問題類型；也要選擇與錯誤相關的「Component（組件）」"
184-
"和「Versions（版本）」。"
181+
"在「Title」欄位，輸入對該問題\\ *非常*\\ 簡短的描述；最好少於十個單字。"
185182

186-
#: ../../bugs.rst:71
183+
#: ../../bugs.rst:72
187184
msgid ""
188185
"In the \"Comment\" field, describe the problem in detail, including what you "
189186
"expected to happen and what did happen. Be sure to include whether any "
190187
"extension modules were involved, and what hardware and software platform you "
191188
"were using (including version information as appropriate)."
192189
msgstr ""
193-
"在「Comment（說明）」欄位，請詳細描述該問題，包括您預期發生的情況和實際發生的"
194-
"情況。請確定說明中包含了涉及到的任何擴充模組，以及您當時所使用的硬體和軟體平"
195-
"台（視情況而定，可以附上版本資訊）。"
190+
"在「Comment」欄位，請詳細描述該問題，包括您預期發生的情況和實際發生的情況。請"
191+
"確定說明中包含了涉及到的任何擴充模組，以及您當時所使用的硬體和軟體平台（視情"
192+
"況而定，可以附上版本資訊）。"
196193

197-
#: ../../bugs.rst:76
194+
#: ../../bugs.rst:77
198195
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."
196+
"Each issue report will be reviewed by a developer who will determine what "
197+
"needs to be done to correct the problem. You will receive an update each "
198+
"time an action is taken on the issue."
202199
msgstr ""
203-
"每一份錯誤報告會被分派給一位開發者，並由他決定要做出什麼變更來修正這個問題。"
204-
"每當該錯誤有修正動作時，您會收到更新回報。"
200+
"每一份問題報告都會被一位開發人員查核，並由他決定要做出什麼變更來修正這個問"
201+
"題。每當該問題有修正動作時，您會收到更新回報。"
205202

206-
#: ../../bugs.rst:85
203+
#: ../../bugs.rst:86
207204
msgid ""
208205
"`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/"
209206
"~sgtatham/bugs.html>`_"
210207
msgstr ""
211208
"`如何有效地回報錯誤 <https://www.chiark.greenend.org.uk/~sgtatham/bugs."
212209
"html>`_"
213210

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

222-
#: ../../bugs.rst:88
219+
#: ../../bugs.rst:89
223220
msgid ""
224221
"`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-"
225222
"writing.html>`_"
226223
msgstr ""
227224
"`錯誤撰寫指南 <https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html>`_"
228225

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

237-
#: ../../bugs.rst:94
234+
#: ../../bugs.rst:95
238235
msgid "Getting started contributing to Python yourself"
239236
msgstr "開始讓自己貢獻 Python"
240237

241-
#: ../../bugs.rst:96
238+
#: ../../bugs.rst:97
242239
msgid ""
243240
"Beyond just reporting bugs that you find, you are also welcome to submit "
244241
"patches to fix them. You can find more information on how to get started "

0 commit comments

Comments
 (0)
0