5
5
msgstr ""
6
6
"Project-Id-Version : Python 3\n "
7
7
"Report-Msgid-Bugs-To : \n "
8
- "POT-Creation-Date : 2023-04-14 13:19+0200 \n "
8
+ "POT-Creation-Date : 2024-10-29 21:40+0100 \n "
9
9
"PO-Revision-Date : 2023-10-21 08:46-0400\n "
10
10
"Last-Translator : Edith Viau <info@eviau.net>\n "
11
11
"Language-Team : FRENCH <traductions@lists.afpy.org>\n "
@@ -69,6 +69,13 @@ msgstr ""
69
69
70
70
#: bugs.rst:25
71
71
msgid ""
72
+ "If you find a bug in the theme (HTML / CSS / JavaScript) of the "
73
+ "documentation, please submit a bug report on the `python-doc-theme bug "
74
+ "tracker <https://github.com/python/python-docs-theme>`_."
75
+ msgstr ""
76
+
77
+ #: bugs.rst:29
78
+ msgid ""
72
79
"If you're short on time, you can also email documentation bug reports to "
73
80
"docs@python.org (behavioral bugs can be sent to python-list@python.org). "
74
81
"'docs@' is a mailing list run by volunteers; your request will be noticed, "
@@ -80,64 +87,65 @@ msgstr ""
80
87
"volontaires, votre requête sera vue, mais elle peut prendre un moment pour "
81
88
"être traitée."
82
89
83
- #: bugs.rst:33
90
+ #: bugs.rst:36
84
91
msgid "`Documentation bugs`_"
85
92
msgstr "`Bogues de documentation`_"
86
93
87
- #: bugs.rst:33
94
+ #: bugs.rst:37
88
95
msgid ""
89
96
"A list of documentation bugs that have been submitted to the Python issue "
90
97
"tracker."
91
98
msgstr ""
92
99
"Liste des bogues de documentation soumis à l'outil de suivi des problèmes "
93
100
"Python."
94
101
95
- #: bugs.rst:36
102
+ #: bugs.rst:39
96
103
msgid "`Issue Tracking <https://devguide.python.org/tracker/>`_"
97
104
msgstr "`Outil de suivi des problèmes <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
"Vue d'ensemble du processus pour proposer une amélioration avec l'outil de "
104
111
"suivi."
105
112
106
- #: bugs.rst:39
113
+ #: bugs.rst:42
107
114
msgid ""
108
115
"`Helping with Documentation <https://devguide.python.org/docquality/#helping-"
109
116
"with-documentation>`_"
110
117
msgstr ""
111
118
"`Aider avec la documentation <https://devguide.python.org/docquality/"
112
119
"#helping-with-documentation>`_"
113
120
114
- #: bugs.rst:39
121
+ #: bugs.rst:43
115
122
msgid ""
116
123
"Comprehensive guide for individuals that are interested in contributing to "
117
124
"Python documentation."
118
125
msgstr "Guide complet pour qui souhaite contribuer à la documentation Python."
119
126
120
- #: bugs.rst:41
127
+ #: bugs.rst:45
128
+ #, fuzzy
121
129
msgid ""
122
- "`Documentation Translations <https://devguide.python.org/documenting /"
123
- "# translating>`_"
130
+ "`Documentation Translations <https://devguide.python.org/documentation /"
131
+ "translating/ >`_"
124
132
msgstr ""
125
133
"`Aider avec la documentation <https://devguide.python.org/documenting/"
126
134
"#translating>`_"
127
135
128
- #: bugs.rst:42
136
+ #: bugs.rst:46
129
137
msgid ""
130
138
"A list of GitHub pages for documentation translation and their primary "
131
139
"contacts."
132
140
msgstr ""
133
141
"Liste de dépôts GitHub où la documentation est traduite, avec les personnes "
134
142
"à contacter."
135
143
136
- #: bugs.rst:48
144
+ #: bugs.rst:52
137
145
msgid "Using the Python issue tracker"
138
146
msgstr "Utilisation du gestionnaire de tickets Python"
139
147
140
- #: bugs.rst:50
148
+ #: bugs.rst:54
141
149
msgid ""
142
150
"Issue reports for Python itself should be submitted via the GitHub issues "
143
151
"tracker (https://github.com/python/cpython/issues). The GitHub issues "
@@ -150,7 +158,7 @@ msgstr ""
150
158
"permettant de saisir des informations pertinentes à soumettre aux "
151
159
"développeurs."
152
160
153
- #: bugs.rst:55
161
+ #: bugs.rst:59
154
162
msgid ""
155
163
"The first step in filing a report is to determine whether the problem has "
156
164
"already been reported. The advantage in doing so, aside from saving the "
@@ -168,7 +176,7 @@ msgstr ""
168
176
"contribution est la bienvenue !). Pour ce faire, cherchez dans le "
169
177
"gestionnaire de tickets grâce à la boîte de recherche en haut de la page."
170
178
171
- #: bugs.rst:62
179
+ #: bugs.rst:66
172
180
msgid ""
173
181
"If the problem you're reporting is not already in the list, log in to "
174
182
"GitHub. If you don't already have a GitHub account, create a new account "
@@ -180,7 +188,7 @@ msgstr ""
180
188
"compte en cliquant sur le lien « Sign Up ». Il n'est pas possible de "
181
189
"soumettre un rapport de bogue de manière anonyme."
182
190
183
- #: bugs.rst:67
191
+ #: bugs.rst:71
184
192
msgid ""
185
193
"Being now logged in, you can submit an issue. Click on the \" New issue\" "
186
194
"button in the top bar to report a new issue."
@@ -189,19 +197,19 @@ msgstr ""
189
197
"*New issue* dans la barre en haut pour ouvrir un nouveau formulaire de "
190
198
"rapport."
191
199
192
- #: bugs.rst:70
200
+ #: bugs.rst:74
193
201
msgid "The submission form has two fields, \" Title\" and \" Comment\" ."
194
202
msgstr "Le formulaire de rapport contient deux champs, *Title* et *Comment*."
195
203
196
- #: bugs.rst:72
204
+ #: bugs.rst:76
197
205
msgid ""
198
206
"For the \" Title\" field, enter a *very* short description of the problem; "
199
207
"fewer than ten words is good."
200
208
msgstr ""
201
209
"Dans le champ *Title*, entrez une *très* brève description du problème "
202
210
"rencontré : dix mots ou moins suffiront."
203
211
204
- #: bugs.rst:75
212
+ #: bugs.rst:79
205
213
msgid ""
206
214
"In the \" Comment\" field, describe the problem in detail, including what you "
207
215
"expected to happen and what did happen. Be sure to include whether any "
@@ -214,7 +222,7 @@ msgstr ""
214
222
"plateforme matérielle et logicielle vous utilisiez (en incluant les "
215
223
"informations de versions)."
216
224
217
- #: bugs.rst:80
225
+ #: bugs.rst:84
218
226
msgid ""
219
227
"Each issue report will be reviewed by a developer who will determine what "
220
228
"needs to be done to correct the problem. You will receive an update each "
@@ -224,15 +232,15 @@ msgstr ""
224
232
"nécessaire d'entreprendre pour corriger le problème. Vous recevrez une "
225
233
"notification à chaque action concernant le rapport."
226
234
227
- #: bugs.rst:89
235
+ #: bugs.rst:91
228
236
msgid ""
229
237
"`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/"
230
238
"~sgtatham/bugs.html>`_"
231
239
msgstr ""
232
240
"`Comment signaler des bogues de manière efficace <https://www.chiark."
233
241
"greenend.org.uk/~sgtatham/bugs.html>`_ (en anglais)"
234
242
235
- #: bugs.rst:88
243
+ #: bugs.rst:92
236
244
msgid ""
237
245
"Article which goes into some detail about how to create a useful bug report. "
238
246
"This describes what kind of information is useful and why it is useful."
@@ -241,27 +249,27 @@ msgstr ""
241
249
"bogue utile. Il décrit quel genre d'information est utile et pourquoi elle "
242
250
"est utile."
243
251
244
- #: bugs.rst:92
252
+ #: bugs.rst:95
245
253
msgid ""
246
254
"`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-"
247
255
"writing.html>`_"
248
256
msgstr ""
249
257
"`Guide pour la rédaction de rapports de bogues <https://bugzilla.mozilla.org/"
250
258
"page.cgi?id=bug-writing.html>`_"
251
259
252
- #: bugs.rst:92
260
+ #: bugs.rst:96
253
261
msgid ""
254
262
"Information about writing a good bug report. Some of this is specific to "
255
263
"the Mozilla project, but describes general good practices."
256
264
msgstr ""
257
265
"Conseils pour écrire un bon rapport de bogue. Certains sont spécifiques au "
258
266
"projet Mozilla mais présentent des bonnes pratiques générales."
259
267
260
- #: bugs.rst:98
268
+ #: bugs.rst:102
261
269
msgid "Getting started contributing to Python yourself"
262
270
msgstr "Commencer à contribuer à Python vous-même"
263
271
264
- #: bugs.rst:100
272
+ #: bugs.rst:104
265
273
msgid ""
266
274
"Beyond just reporting bugs that you find, you are also welcome to submit "
267
275
"patches to fix them. You can find more information on how to get started "
0 commit comments