@@ -12,7 +12,7 @@ msgid ""
12
12
msgstr ""
13
13
"Project-Id-Version : Python 3.7\n "
14
14
"Report-Msgid-Bugs-To : \n "
15
- "POT-Creation-Date : 2018 -06-26 18:54 +0800\n "
15
+ "POT-Creation-Date : 2020 -06-20 18:08 +0800\n "
16
16
"PO-Revision-Date : 2018-10-13 16:29+0800\n "
17
17
"
Last-Translator :
Adrian Liaw <[email protected] >\n "
18
18
"Language-Team : Chinese - TAIWAN (https://github.com/python/python-docs-zh- "
@@ -55,7 +55,7 @@ msgstr "說明文件錯誤"
55
55
msgid ""
56
56
"If you find a bug in this documentation or would like to propose an "
57
57
"improvement, please submit a bug report on the :ref:`tracker <using-the-"
58
- "tracker>`. If you have a suggestion how to fix it, include that as well."
58
+ "tracker>`. If you have a suggestion on how to fix it, include that as well."
59
59
msgstr ""
60
60
61
61
#: ../../bugs.rst:22
@@ -66,22 +66,51 @@ msgid ""
66
66
"though it may take a while to be processed."
67
67
msgstr ""
68
68
69
- #: ../../bugs.rst:28
70
- msgid "`Documentation bugs`_ on the Python issue tracker"
69
+ #: ../../bugs.rst:30
70
+ #, fuzzy
71
+ msgid "`Documentation bugs`_"
72
+ msgstr "說明文件錯誤"
73
+
74
+ #: ../../bugs.rst:30
75
+ #, fuzzy
76
+ msgid ""
77
+ "A list of documentation bugs that have been submitted to the Python issue "
78
+ "tracker."
71
79
msgstr "Python issue tracker 上\\ `文件相關的錯誤 <Documentation bugs_>`_"
72
80
73
81
#: ../../bugs.rst:33
82
+ msgid "`Issue Tracking <https://devguide.python.org/tracker/>`_"
83
+ msgstr ""
84
+
85
+ #: ../../bugs.rst:33
86
+ msgid ""
87
+ "Overview of the process involved in reporting an improvement on the tracker."
88
+ msgstr ""
89
+
90
+ #: ../../bugs.rst:35
91
+ msgid ""
92
+ "`Helping with Documentation <https://devguide.python.org/docquality/#helping-"
93
+ "with-documentation>`_"
94
+ msgstr ""
95
+
96
+ #: ../../bugs.rst:36
97
+ msgid ""
98
+ "Comprehensive guide for individuals that are interested in contributing to "
99
+ "Python documentation."
100
+ msgstr ""
101
+
102
+ #: ../../bugs.rst:41
74
103
msgid "Using the Python issue tracker"
75
104
msgstr "使用 Python 議題追蹤"
76
105
77
- #: ../../bugs.rst:35
106
+ #: ../../bugs.rst:43
78
107
msgid ""
79
108
"Bug reports for Python itself should be submitted via the Python Bug Tracker "
80
109
"(https://bugs.python.org/). The bug tracker offers a Web form which allows "
81
110
"pertinent information to be entered and submitted to the developers."
82
111
msgstr ""
83
112
84
- #: ../../bugs.rst:39
113
+ #: ../../bugs.rst:47
85
114
msgid ""
86
115
"The first step in filing a report is to determine whether the problem has "
87
116
"already been reported. The advantage in doing so, aside from saving the "
@@ -92,7 +121,7 @@ msgid ""
92
121
"of the page."
93
122
msgstr ""
94
123
95
- #: ../../bugs.rst:46
124
+ #: ../../bugs.rst:54
96
125
msgid ""
97
126
"If the problem you're reporting is not already in the bug tracker, go back "
98
127
"to the Python Bug Tracker and log in. If you don't already have a tracker "
@@ -101,64 +130,64 @@ msgid ""
101
130
"report anonymously."
102
131
msgstr ""
103
132
104
- #: ../../bugs.rst:51
133
+ #: ../../bugs.rst:59
105
134
msgid ""
106
135
"Being now logged in, you can submit a bug. Select the \" Create New\" link "
107
136
"in the sidebar to open the bug reporting form."
108
137
msgstr ""
109
138
110
- #: ../../bugs.rst:54
139
+ #: ../../bugs.rst:62
111
140
msgid ""
112
141
"The submission form has a number of fields. For the \" Title\" field, enter "
113
142
"a *very* short description of the problem; less than ten words is good. In "
114
143
"the \" Type\" field, select the type of your problem; also select the "
115
144
"\" Component\" and \" Versions\" to which the bug relates."
116
145
msgstr ""
117
146
118
- #: ../../bugs.rst:59
147
+ #: ../../bugs.rst:67
119
148
msgid ""
120
149
"In the \" Comment\" field, describe the problem in detail, including what you "
121
150
"expected to happen and what did happen. Be sure to include whether any "
122
151
"extension modules were involved, and what hardware and software platform you "
123
152
"were using (including version information as appropriate)."
124
153
msgstr ""
125
154
126
- #: ../../bugs.rst:64
155
+ #: ../../bugs.rst:72
127
156
msgid ""
128
157
"Each bug report will be assigned to a developer who will determine what "
129
158
"needs to be done to correct the problem. You will receive an update each "
130
159
"time action is taken on the bug."
131
160
msgstr ""
132
161
133
- #: ../../bugs.rst:73
162
+ #: ../../bugs.rst:81
134
163
msgid ""
135
164
"`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/"
136
165
"~sgtatham/bugs.html>`_"
137
166
msgstr ""
138
167
139
- #: ../../bugs.rst:72
168
+ #: ../../bugs.rst:80
140
169
msgid ""
141
170
"Article which goes into some detail about how to create a useful bug report. "
142
171
"This describes what kind of information is useful and why it is useful."
143
172
msgstr ""
144
173
145
- #: ../../bugs.rst:76
174
+ #: ../../bugs.rst:84
146
175
msgid ""
147
- "`Bug Writing Guidelines <https://developer.mozilla.org/en-US/docs/Mozilla/QA /"
148
- "Bug_writing_guidelines>`_"
176
+ "`Bug Report Writing Guidelines <https://developer.mozilla.org/en-US/docs/"
177
+ "Mozilla/QA/ Bug_writing_guidelines>`_"
149
178
msgstr ""
150
179
151
- #: ../../bugs.rst:76
180
+ #: ../../bugs.rst:84
152
181
msgid ""
153
182
"Information about writing a good bug report. Some of this is specific to "
154
183
"the Mozilla project, but describes general good practices."
155
184
msgstr ""
156
185
157
- #: ../../bugs.rst:82
186
+ #: ../../bugs.rst:90
158
187
msgid "Getting started contributing to Python yourself"
159
188
msgstr "開始讓自己貢獻 Python"
160
189
161
- #: ../../bugs.rst:84
190
+ #: ../../bugs.rst:92
162
191
msgid ""
163
192
"Beyond just reporting bugs that you find, you are also welcome to submit "
164
193
"patches to fix them. You can find more information on how to get started "
0 commit comments