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