@@ -13,7 +13,7 @@ msgid ""
13
13
msgstr ""
14
14
"Project-Id-Version : Python 3.11\n "
15
15
"Report-Msgid-Bugs-To : \n "
16
- "POT-Creation-Date : 2022-08-04 00:16 +0000\n "
16
+ "POT-Creation-Date : 2023-02-07 00:17 +0000\n "
17
17
"PO-Revision-Date : 2022-08-31 12:34+0800\n "
18
18
"Last-Translator : Steven Hsu <hsuhaochun@gmail.com>\n "
19
19
"Language-Team : Chinese - TAIWAN (https://github.com/python/python-docs-zh- "
@@ -65,6 +65,12 @@ msgstr ""
65
65
66
66
#: ../../bugs.rst:22
67
67
msgid ""
68
+ "You can also open a discussion item on our `Documentation Discourse forum "
69
+ "<https://discuss.python.org/c/documentation/26>`_."
70
+ msgstr ""
71
+
72
+ #: ../../bugs.rst:25
73
+ msgid ""
68
74
"If you're short on time, you can also email documentation bug reports to "
69
75
"docs@python.org (behavioral bugs can be sent to python-list@python.org). "
70
76
"'docs@' is a mailing list run by volunteers; your request will be noticed, "
@@ -74,58 +80,58 @@ msgstr ""
74
80
"(程式碼執行的錯誤可以寄到 python-list@python.org)。「docs@」是一個由志工們"
75
81
"所運行的郵寄清單;您的請求會被注意到,但可能需要一些時間才會被處理。"
76
82
77
- #: ../../bugs.rst:30
83
+ #: ../../bugs.rst:33
78
84
msgid "`Documentation bugs`_"
79
85
msgstr "`說明文件錯誤`_"
80
86
81
- #: ../../bugs.rst:30
87
+ #: ../../bugs.rst:33
82
88
msgid ""
83
89
"A list of documentation bugs that have been submitted to the Python issue "
84
90
"tracker."
85
91
msgstr "一系列已被提交至 Python 問題追蹤系統的有關說明文件的錯誤。"
86
92
87
- #: ../../bugs.rst:33
93
+ #: ../../bugs.rst:36
88
94
msgid "`Issue Tracking <https://devguide.python.org/tracker/>`_"
89
95
msgstr "`問題追蹤系統 <https://devguide.python.org/tracker/>`_"
90
96
91
- #: ../../bugs.rst:33
97
+ #: ../../bugs.rst:36
92
98
msgid ""
93
99
"Overview of the process involved in reporting an improvement on the tracker."
94
100
msgstr "在追蹤系統上回報改進建議的過程簡介。"
95
101
96
- #: ../../bugs.rst:36
102
+ #: ../../bugs.rst:39
97
103
msgid ""
98
104
"`Helping with Documentation <https://devguide.python.org/docquality/#helping-"
99
105
"with-documentation>`_"
100
106
msgstr ""
101
107
"`貢獻說明文件 <https://devguide.python.org/docquality/#helping-with-"
102
108
"documentation>`_"
103
109
104
- #: ../../bugs.rst:36
110
+ #: ../../bugs.rst:39
105
111
msgid ""
106
112
"Comprehensive guide for individuals that are interested in contributing to "
107
113
"Python documentation."
108
114
msgstr "給有意成為 Python 說明文件貢獻者的綜合指南。"
109
115
110
- #: ../../bugs.rst:38
116
+ #: ../../bugs.rst:41
111
117
msgid ""
112
118
"`Documentation Translations <https://devguide.python.org/documenting/"
113
119
"#translating>`_"
114
120
msgstr "`說明文件翻譯 <https://devguide.python.org/documenting/#translating>`_"
115
121
116
- #: ../../bugs.rst:39
122
+ #: ../../bugs.rst:42
117
123
msgid ""
118
124
"A list of GitHub pages for documentation translation and their primary "
119
125
"contacts."
120
126
msgstr ""
121
127
"一份 GitHub 網頁的清單,裡面有各個說明文件翻譯團隊的連結,以及他們的主要聯絡"
122
128
"人。"
123
129
124
- #: ../../bugs.rst:45
130
+ #: ../../bugs.rst:48
125
131
msgid "Using the Python issue tracker"
126
132
msgstr "使用 Python 問題追蹤系統"
127
133
128
- #: ../../bugs.rst:47
134
+ #: ../../bugs.rst:50
129
135
msgid ""
130
136
"Issue reports for Python itself should be submitted via the GitHub issues "
131
137
"tracker (https://github.com/python/cpython/issues). The GitHub issues "
@@ -136,7 +142,7 @@ msgstr ""
136
142
"python/cpython/issues) 提交。這個 GitHub 問題追蹤系統提供了一個網頁表單,可以"
137
143
"輸入並提交相關資訊給開發者。"
138
144
139
- #: ../../bugs.rst:52
145
+ #: ../../bugs.rst:55
140
146
msgid ""
141
147
"The first step in filing a report is to determine whether the problem has "
142
148
"already been reported. The advantage in doing so, aside from saving the "
@@ -151,7 +157,7 @@ msgstr ""
151
157
"本中修正了這個問題,也有可能需要更詳細的資訊(在這種情況下,如果可以,非常歡"
152
158
"迎您提供資訊!)。要確認是否重複回報,請使用頁面頂端的搜尋框來搜尋追蹤系統。"
153
159
154
- #: ../../bugs.rst:59
160
+ #: ../../bugs.rst:62
155
161
msgid ""
156
162
"If the problem you're reporting is not already in the list, log in to "
157
163
"GitHub. If you don't already have a GitHub account, create a new account "
@@ -161,26 +167,26 @@ msgstr ""
161
167
"如果您想回報的問題還沒有在問題列表出現過,請登入 GitHub。如果您還沒有 GitHub "
162
168
"帳戶,請點選「Sign up」連結來建立一個新的帳戶。您無法以匿名方式提交錯誤報告。"
163
169
164
- #: ../../bugs.rst:64
170
+ #: ../../bugs.rst:67
165
171
msgid ""
166
172
"Being now logged in, you can submit an issue. Click on the \" New issue\" "
167
173
"button in the top bar to report a new issue."
168
174
msgstr ""
169
175
"如果已經登入,那您就可以提交問題了。請點選列表頂端區域的「New issue」按鈕,來"
170
176
"回報一個新的問題。"
171
177
172
- #: ../../bugs.rst:67
178
+ #: ../../bugs.rst:70
173
179
msgid "The submission form has two fields, \" Title\" and \" Comment\" ."
174
180
msgstr "提交的表單中有兩個欄位,「Title」及「Comment」。"
175
181
176
- #: ../../bugs.rst:69
182
+ #: ../../bugs.rst:72
177
183
msgid ""
178
184
"For the \" Title\" field, enter a *very* short description of the problem; "
179
185
"less than ten words is good."
180
186
msgstr ""
181
187
"在「Title」欄位,輸入對該問題\\ *非常*\\ 簡短的描述;最好少於十個單字。"
182
188
183
- #: ../../bugs.rst:72
189
+ #: ../../bugs.rst:75
184
190
msgid ""
185
191
"In the \" Comment\" field, describe the problem in detail, including what you "
186
192
"expected to happen and what did happen. Be sure to include whether any "
@@ -191,7 +197,7 @@ msgstr ""
191
197
"確定說明中包含了涉及到的任何擴充模組,以及您當時所使用的硬體和軟體平台(視情"
192
198
"況而定,可以附上版本資訊)。"
193
199
194
- #: ../../bugs.rst:77
200
+ #: ../../bugs.rst:80
195
201
msgid ""
196
202
"Each issue report will be reviewed by a developer who will determine what "
197
203
"needs to be done to correct the problem. You will receive an update each "
@@ -200,42 +206,42 @@ msgstr ""
200
206
"每一份問題報告都會被一位開發人員查核,並由他決定要做出什麼變更來修正這個問"
201
207
"題。每當該問題有修正動作時,您會收到更新回報。"
202
208
203
- #: ../../bugs.rst:86
209
+ #: ../../bugs.rst:89
204
210
msgid ""
205
211
"`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/"
206
212
"~sgtatham/bugs.html>`_"
207
213
msgstr ""
208
214
"`如何有效地回報錯誤 <https://www.chiark.greenend.org.uk/~sgtatham/bugs."
209
215
"html>`_"
210
216
211
- #: ../../bugs.rst:85
217
+ #: ../../bugs.rst:88
212
218
msgid ""
213
219
"Article which goes into some detail about how to create a useful bug report. "
214
220
"This describes what kind of information is useful and why it is useful."
215
221
msgstr ""
216
222
"這篇文章詳細說明如何建立一份有用的錯誤報告。它描述了什麼樣的資訊是有用的,以"
217
223
"及這些資訊為什麼有用。"
218
224
219
- #: ../../bugs.rst:89
225
+ #: ../../bugs.rst:92
220
226
msgid ""
221
227
"`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-"
222
228
"writing.html>`_"
223
229
msgstr ""
224
230
"`錯誤撰寫指南 <https://bugzilla.mozilla.org/page.cgi?id=bug-writing.html>`_"
225
231
226
- #: ../../bugs.rst:89
232
+ #: ../../bugs.rst:92
227
233
msgid ""
228
234
"Information about writing a good bug report. Some of this is specific to "
229
235
"the Mozilla project, but describes general good practices."
230
236
msgstr ""
231
237
"撰寫一份優良錯誤報告的相關資訊。部分的文章內容是針對 Mozilla 專案,但它也描述"
232
238
"了通用的好習慣。"
233
239
234
- #: ../../bugs.rst:95
240
+ #: ../../bugs.rst:98
235
241
msgid "Getting started contributing to Python yourself"
236
242
msgstr "開始讓自己貢獻 Python"
237
243
238
- #: ../../bugs.rst:97
244
+ #: ../../bugs.rst:100
239
245
msgid ""
240
246
"Beyond just reporting bugs that you find, you are also welcome to submit "
241
247
"patches to fix them. You can find more information on how to get started "
0 commit comments