|
8 | 8 | # aminzai <lagunawang@gmail.com>, 2015 |
9 | 9 | # Liang-Bo Wang <me@liang2.tw>, 2015 |
10 | 10 | # sammy huang <sammy.huang@kkday.com>, 2017 |
11 | | -# Steven Hsu <hsuhaochun@gmail.com>, 2021 |
| 11 | +# Steven Hsu <hsuhaochun@gmail.com>, 2021-2022 |
12 | 12 | msgid "" |
13 | 13 | msgstr "" |
14 | 14 | "Project-Id-Version:Python 3.10\n" |
15 | 15 | "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" |
19 | 19 | "Language-Team:Chinese - TAIWAN (https://github.com/python/python-docs-zh-" |
20 | 20 | "tw)\n" |
21 | 21 | "Language:zh_TW\n" |
22 | 22 | "MIME-Version:1.0\n" |
23 | 23 | "Content-Type:text/plain; charset=UTF-8\n" |
24 | 24 | "Content-Transfer-Encoding:8bit\n" |
25 | 25 | "Plural-Forms:nplurals=1; plural=0;\n" |
26 | | -"X-Generator:Poedit 3.0.1\n" |
| 26 | +"X-Generator:Poedit 3.1.1\n" |
27 | 27 |
|
28 | 28 | #:../../bugs.rst:5 |
29 | 29 | msgid"Dealing with Bugs" |
@@ -127,118 +127,115 @@ msgstr "使用 Python 問題追蹤系統" |
127 | 127 |
|
128 | 128 | #:../../bugs.rst:47 |
129 | 129 | 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." |
133 | 134 | msgstr"" |
134 | | -"對於 Python本身的錯誤報告，應該透過Python 錯誤追蹤系統 (https://bugs." |
135 | | -"python.org/) 提交。這個錯誤追蹤系統提供了一個網頁表單，可以輸入並提交相關資訊" |
136 | | -"給開發者。" |
| 135 | +"對於 Python本身的問題報告，應該透過GitHub 問題追蹤系統 (https://github.com/" |
| 136 | +"python/cpython/issues) 提交。這個 GitHub 問題追蹤系統提供了一個網頁表單，可以" |
| 137 | +"輸入並提交相關資訊給開發者。" |
137 | 138 |
|
138 | | -#:../../bugs.rst:51 |
| 139 | +#:../../bugs.rst:52 |
139 | 140 | msgid"" |
140 | 141 | "The first step in filing a report is to determine whether the problem has " |
141 | 142 | "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 " |
143 | 144 | "that the problem has already been fixed for the next release, or additional " |
144 | 145 | "information is needed (in which case you are welcome to provide it if you " |
145 | | -"can!). To do this, search thebug databaseusing the search boxon the top " |
146 | | -"of thepage." |
| 146 | +"can!). To do this, search thetrackerusing the search boxat the top of the " |
| 147 | +"page." |
147 | 148 | msgstr"" |
148 | 149 | "填寫報告的第一步，是確認該問題是否已經被回報過了。這樣做的好處，除了可以節省" |
149 | 150 | "開發者的時間，也能讓您了解目前關於該問題的處理進度；有可能已經在下一個發行版" |
150 | 151 | "本中修正了這個問題，也有可能需要更詳細的資訊（在這種情況下，如果可以，非常歡" |
151 | | -"迎您提供資訊！）。要確認是否重複回報，請使用頁面頂端的搜尋框來搜尋錯誤資料" |
152 | | -"庫。" |
| 152 | +"迎您提供資訊！）。要確認是否重複回報，請使用頁面頂端的搜尋框來搜尋追蹤系統。" |
153 | 153 |
|
154 | | -#:../../bugs.rst:58 |
| 154 | +#:../../bugs.rst:59 |
155 | 155 | 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." |
161 | 160 | msgstr"" |
162 | | -"如果您想回報的問題還沒有在錯誤追蹤系統出現過，請返回並登入 Python 錯誤追蹤系" |
163 | | -"統。如果您還沒有系統的帳號，請點選「註冊 (Register)」，如果您有 OpenID，也可" |
164 | | -"以在側邊欄中點選其中一個 OpenID 的提供者圖示。您無法以匿名方式提交錯誤報告。" |
| 161 | +"如果您想回報的問題還沒有在問題列表出現過，請登入 GitHub。如果您還沒有 GitHub " |
| 162 | +"帳戶，請點選「Sign up」連結來建立一個新的帳戶。您無法以匿名方式提交錯誤報告。" |
165 | 163 |
|
166 | | -#:../../bugs.rst:63 |
| 164 | +#:../../bugs.rst:64 |
167 | 165 | msgid"" |
168 | | -"Being now logged in, you can submita bug. Select the\"CreateNew\" link " |
169 | | -"in thesidebartoopen the bug reporting form." |
| 166 | +"Being now logged in, you can submitan issue. Click on the\"New issue\" " |
| 167 | +"buttonin thetop bartoreport a new issue." |
170 | 168 | msgstr"" |
171 | | -"如果已經登入，那您就可以提交一個錯誤。請點選側邊欄中的「新建 (CreateNew)」連" |
172 | | -"結，開啟錯誤回報表單。" |
| 169 | +"如果已經登入，那您就可以提交問題了。請點選列表頂端區域的「New issue」按鈕，來" |
| 170 | +"回報一個新的問題。" |
173 | 171 |
|
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 |
175 | 177 | 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." |
180 | 180 | msgstr"" |
181 | | -"提交的表單中有幾個欄位。（譯者註：所有欄位請皆用英文輸入。）在「標題 " |
182 | | -"(Title)」欄位，輸入對該問題\\ *非常*\\ 簡短的描述；最好少於十個單字。在「類" |
183 | | -"型 (Type)」欄位，選擇您的問題類型；也要選擇與錯誤相關的「Component（組件）」" |
184 | | -"和「Versions（版本）」。" |
| 181 | +"在「Title」欄位，輸入對該問題\\ *非常*\\ 簡短的描述；最好少於十個單字。" |
185 | 182 |
|
186 | | -#:../../bugs.rst:71 |
| 183 | +#:../../bugs.rst:72 |
187 | 184 | msgid"" |
188 | 185 | "In the\"Comment\" field, describe the problem in detail, including what you " |
189 | 186 | "expected to happen and what did happen. Be sure to include whether any " |
190 | 187 | "extension modules were involved, and what hardware and software platform you " |
191 | 188 | "were using (including version information as appropriate)." |
192 | 189 | msgstr"" |
193 | | -"在「Comment（說明）」欄位，請詳細描述該問題，包括您預期發生的情況和實際發生的" |
194 | | -"情況。請確定說明中包含了涉及到的任何擴充模組，以及您當時所使用的硬體和軟體平" |
195 | | -"台（視情況而定，可以附上版本資訊）。" |
| 190 | +"在「Comment」欄位，請詳細描述該問題，包括您預期發生的情況和實際發生的情況。請" |
| 191 | +"確定說明中包含了涉及到的任何擴充模組，以及您當時所使用的硬體和軟體平台（視情" |
| 192 | +"況而定，可以附上版本資訊）。" |
196 | 193 |
|
197 | | -#:../../bugs.rst:76 |
| 194 | +#:../../bugs.rst:77 |
198 | 195 | msgid"" |
199 | | -"Eachbug report will beassigned 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 thebug." |
| 196 | +"Eachissue report will bereviewed by a developer who will determine what " |
| 197 | +"needs to be done to correct the problem. You will receive an update each " |
| 198 | +"timeanaction is taken on theissue." |
202 | 199 | msgstr"" |
203 | | -"每一份錯誤報告會被分派給一位開發者，並由他決定要做出什麼變更來修正這個問題。" |
204 | | -"每當該錯誤有修正動作時，您會收到更新回報。" |
| 200 | +"每一份問題報告都會被一位開發人員查核，並由他決定要做出什麼變更來修正這個問" |
| 201 | +"題。每當該問題有修正動作時，您會收到更新回報。" |
205 | 202 |
|
206 | | -#:../../bugs.rst:85 |
| 203 | +#:../../bugs.rst:86 |
207 | 204 | msgid"" |
208 | 205 | "`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/" |
209 | 206 | "~sgtatham/bugs.html>`_" |
210 | 207 | msgstr"" |
211 | 208 | "`如何有效地回報錯誤 <https://www.chiark.greenend.org.uk/~sgtatham/bugs." |
212 | 209 | "html>`_" |
213 | 210 |
|
214 | | -#:../../bugs.rst:84 |
| 211 | +#:../../bugs.rst:85 |
215 | 212 | msgid"" |
216 | 213 | "Article which goes into some detail about how to create a useful bug report. " |
217 | 214 | "This describes what kind of information is useful and why it is useful." |
218 | 215 | msgstr"" |
219 | 216 | "這篇文章詳細說明如何建立一份有用的錯誤報告。它描述了什麼樣的資訊是有用的，以" |
220 | 217 | "及這些資訊為什麼有用。" |
221 | 218 |
|
222 | | -#:../../bugs.rst:88 |
| 219 | +#:../../bugs.rst:89 |
223 | 220 | msgid"" |
224 | 221 | "`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-" |
225 | 222 | "writing.html>`_" |
226 | 223 | msgstr"" |
227 | 224 | "`錯誤撰寫指南 <https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html>`_" |
228 | 225 |
|
229 | | -#:../../bugs.rst:88 |
| 226 | +#:../../bugs.rst:89 |
230 | 227 | msgid"" |
231 | 228 | "Information about writing a good bug report. Some of this is specific to " |
232 | 229 | "the Mozilla project, but describes general good practices." |
233 | 230 | msgstr"" |
234 | 231 | "撰寫一份優良錯誤報告的相關資訊。部分的文章內容是針對 Mozilla 專案，但它也描述" |
235 | 232 | "了通用的好習慣。" |
236 | 233 |
|
237 | | -#:../../bugs.rst:94 |
| 234 | +#:../../bugs.rst:95 |
238 | 235 | msgid"Getting started contributing to Python yourself" |
239 | 236 | msgstr"開始讓自己貢獻 Python" |
240 | 237 |
|
241 | | -#:../../bugs.rst:96 |
| 238 | +#:../../bugs.rst:97 |
242 | 239 | msgid"" |
243 | 240 | "Beyond just reporting bugs that you find, you are also welcome to submit " |
244 | 241 | "patches to fix them. You can find more information on how to get started " |
|