@@ -10,16 +10,16 @@ msgid ""
1010msgstr ""
1111"Project-Id-Version : Python 3.8\n "
1212"Report-Msgid-Bugs-To : \n "
13- "POT-Creation-Date : 2021 -10-16 21:42 +0200\n "
13+ "POT-Creation-Date : 2022 -10-25 19:47 +0200\n "
1414"PO-Revision-Date : 2020-06-28 01:03+0200\n "
1515"Last-Translator : \n "
16- "Language-Team : python-doc-es\n "
1716"Language : es\n "
17+ "Language-Team : python-doc-es\n "
18+ "Plural-Forms : nplurals=2; plural=(n != 1);\n "
1819"MIME-Version : 1.0\n "
1920"Content-Type : text/plain; charset=utf-8\n "
2021"Content-Transfer-Encoding : 8bit\n "
21- "Plural-Forms : nplurals=2; plural=(n != 1)\n "
22- "Generated-By : Babel 2.9.1\n "
22+ "Generated-By : Babel 2.10.3\n "
2323
2424#: ../Doc/bugs.rst:5
2525msgid "Dealing with Bugs"
@@ -96,7 +96,7 @@ msgid ""
9696msgstr ""
9797"Resumen general del proceso necesario para reportar una mejora en el tracker."
9898
99- #: ../Doc/bugs.rst:35
99+ #: ../Doc/bugs.rst:36
100100msgid ""
101101"`Helping with Documentation <https://devguide.python.org/docquality/#helping-"
102102"with-documentation>`_"
@@ -112,30 +112,43 @@ msgstr ""
112112"Guía detallada para gente interesada en contribuir a la documentación de "
113113"Python."
114114
115- #: ../Doc/bugs.rst:41
115+ #: ../Doc/bugs.rst:38
116+ #, fuzzy
117+ msgid ""
118+ "`Documentation Translations <https://devguide.python.org/documenting/"
119+ "#translating>`_"
120+ msgstr ""
121+ "`Ayudar con la documentación <https://devguide.python.org/docquality/"
122+ "#helping-with-documentation>`_"
123+
124+ #: ../Doc/bugs.rst:39
125+ msgid ""
126+ "A list of GitHub pages for documentation translation and their primary "
127+ "contacts."
128+ msgstr ""
129+
130+ #: ../Doc/bugs.rst:45
116131msgid "Using the Python issue tracker"
117132msgstr "Utilizar el issue tracker de Python"
118133
119- #: ../Doc/bugs.rst:43
134+ #: ../Doc/bugs.rst:47
120135msgid ""
121- "Bug reports for Python itself should be submitted via the Python Bug Tracker "
122- "(https://bugs.python.org/). The bug tracker offers a web form which allows "
123- "pertinent information to be entered and submitted to the developers."
136+ "Issue reports for Python itself should be submitted via the GitHub issues "
137+ "tracker (https://github.com/python/cpython/issues). The GitHub issues "
138+ "tracker offers a web form which allows pertinent information to be entered "
139+ "and submitted to the developers."
124140msgstr ""
125- "Los informes de errores para Python en sí deben enviarse a través de Python "
126- "Bug Tracker (https://bugs.python.org/). El rastreador de errores ofrece un "
127- "formulario web que permite ingresar y enviar la información pertinente a los "
128- "desarrolladores."
129141
130- #: ../Doc/bugs.rst:47
142+ #: ../Doc/bugs.rst:52
143+ #, fuzzy
131144msgid ""
132145"The first step in filing a report is to determine whether the problem has "
133146"already been reported. The advantage in doing so, aside from saving the "
134- "developers time, is that you learn what has been done to fix it; it may be "
147+ "developers' time, is that you learn what has been done to fix it; it may be "
135148"that the problem has already been fixed for the next release, or additional "
136149"information is needed (in which case you are welcome to provide it if you "
137- "can!). To do this, search the bug database using the search box on the top "
138- "of the page."
150+ "can!). To do this, search the tracker using the search box at the top of the "
151+ "page."
139152msgstr ""
140153"El primer paso para rellenar un informe es determinar si el problema ya ha "
141154"sido descrito previamente. La ventaja de hacer esto, aparte de ahorrar "
@@ -146,42 +159,34 @@ msgstr ""
146159"en la base de datos de errores usando la zona de búsqueda al principio de "
147160"esta página."
148161
149- #: ../Doc/bugs.rst:54
162+ #: ../Doc/bugs.rst:59
150163msgid ""
151- "If the problem you're reporting is not already in the bug tracker, go back "
152- "to the Python Bug Tracker and log in. If you don't already have a tracker "
153- "account, select the \" Register\" link or, if you use OpenID, one of the "
154- "OpenID provider logos in the sidebar. It is not possible to submit a bug "
155- "report anonymously."
164+ "If the problem you're reporting is not already in the list, log in to "
165+ "GitHub. If you don't already have a GitHub account, create a new account "
166+ "using the \" Sign up\" link. It is not possible to submit a bug report "
167+ "anonymously."
156168msgstr ""
157- "Si el problema que estás describiendo no está todavía en el rastreador de "
158- "errores, vuelve al Python Bug Tracker e inicia sesión. Si no tienes una "
159- "cuenta en el rastreador, selecciona el enlace \" Register\" o, si usas "
160- "OpenID, selecciona uno de los logos de los proveedores OpenID en la barra "
161- "lateral. No es posible el envío de informes de errores de manera anónima."
162169
163- #: ../Doc/bugs.rst:59
170+ #: ../Doc/bugs.rst:64
171+ #, fuzzy
164172msgid ""
165- "Being now logged in, you can submit a bug. Select the \" Create New\" link "
166- "in the sidebar to open the bug reporting form ."
173+ "Being now logged in, you can submit an issue. Click on the \" New issue \" "
174+ "button in the top bar to report a new issue ."
167175msgstr ""
168176"Una vez dentro, puedes enviar el error. Selecciona el enlace \" Create New\" "
169177"en la barra lateral para abrir el formulario del informe de errores."
170178
171- #: ../Doc/bugs.rst:62
179+ #: ../Doc/bugs.rst:67
180+ msgid "The submission form has two fields, \" Title\" and \" Comment\" ."
181+ msgstr ""
182+
183+ #: ../Doc/bugs.rst:69
172184msgid ""
173- "The submission form has a number of fields. For the \" Title\" field, enter "
174- "a *very* short description of the problem; less than ten words is good. In "
175- "the \" Type\" field, select the type of your problem; also select the "
176- "\" Component\" and \" Versions\" to which the bug relates."
185+ "For the \" Title\" field, enter a *very* short description of the problem; "
186+ "less than ten words is good."
177187msgstr ""
178- "El formulario de envío tiene un número de campos. Para el campo \" Title\" , "
179- "introduce una descripción *muy* corta del problema; menos de diez palabras "
180- "está bien. En el campo \" Type\" , selecciona el tipo de problema; selecciona "
181- "también el \" Component\" y \" Versions\" con los que el error está "
182- "relacionado."
183188
184- #: ../Doc/bugs.rst:67
189+ #: ../Doc/bugs.rst:72
185190msgid ""
186191"In the \" Comment\" field, describe the problem in detail, including what you "
187192"expected to happen and what did happen. Be sure to include whether any "
@@ -193,41 +198,42 @@ msgstr ""
193198"si cualquier módulo de extensión está involucrado, y qué plataformas de "
194199"hardware y software estás usando (incluyendo las versiones correspondientes)."
195200
196- #: ../Doc/bugs.rst:72
201+ #: ../Doc/bugs.rst:77
202+ #, fuzzy
197203msgid ""
198- "Each bug report will be assigned to a developer who will determine what "
199- "needs to be done to correct the problem. You will receive an update each "
200- "time action is taken on the bug ."
204+ "Each issue report will be reviewed by a developer who will determine what "
205+ "needs to be done to correct the problem. You will receive an update each "
206+ "time an action is taken on the issue ."
201207msgstr ""
202208"Cada informe de errores será asignado a un desarrollador que determinará qué "
203209"es necesario hacer para corregir el problema. Recibirás una actualización "
204210"cada vez que una acción nueva sea aplicada."
205211
206- #: ../Doc/bugs.rst:81
212+ #: ../Doc/bugs.rst:86
207213msgid ""
208214"`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/"
209215"~sgtatham/bugs.html>`_"
210216msgstr ""
211217"`Cómo informar de errores de manera efectiva <https://www.chiark.greenend."
212218"org.uk/~sgtatham/bugs.html>`_"
213219
214- #: ../Doc/bugs.rst:80
220+ #: ../Doc/bugs.rst:85
215221msgid ""
216222"Article which goes into some detail about how to create a useful bug report. "
217223"This describes what kind of information is useful and why it is useful."
218224msgstr ""
219225"Artículo que detalla cómo crear un informe de errores útil. Describe qué "
220226"tipo de información es útil y por qué lo es."
221227
222- #: ../Doc/bugs.rst:84
228+ #: ../Doc/bugs.rst:89
223229msgid ""
224230"`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-"
225231"writing.html>`_"
226232msgstr ""
227233"`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-"
228234"writing.html>`_"
229235
230- #: ../Doc/bugs.rst:84
236+ #: ../Doc/bugs.rst:89
231237msgid ""
232238"Information about writing a good bug report. Some of this is specific to "
233239"the Mozilla project, but describes general good practices."
@@ -236,11 +242,11 @@ msgstr ""
236242"información es específica al proyecto Mozilla, pero en general describe "
237243"buenas prácticas."
238244
239- #: ../Doc/bugs.rst:90
245+ #: ../Doc/bugs.rst:95
240246msgid "Getting started contributing to Python yourself"
241247msgstr "Para empezar a contribuir en Python"
242248
243- #: ../Doc/bugs.rst:92
249+ #: ../Doc/bugs.rst:97
244250msgid ""
245251"Beyond just reporting bugs that you find, you are also welcome to submit "
246252"patches to fix them. You can find more information on how to get started "
@@ -254,3 +260,39 @@ msgstr ""
254260"Guide`_. Si tienes preguntas, el `core-mentorship mailing list`_ es un "
255261"agradable lugar para obtener respuestas a cualquiera y a todas las preguntas "
256262"pertenecientes al proceso de corrección de problemas en Python."
263+
264+ #~ msgid ""
265+ #~ "Bug reports for Python itself should be submitted via the Python Bug "
266+ #~ "Tracker (https://bugs.python.org/). The bug tracker offers a web form "
267+ #~ "which allows pertinent information to be entered and submitted to the "
268+ #~ "developers."
269+ #~ msgstr ""
270+ #~ "Los informes de errores para Python en sí deben enviarse a través de "
271+ #~ "Python Bug Tracker (https://bugs.python.org/). El rastreador de errores "
272+ #~ "ofrece un formulario web que permite ingresar y enviar la información "
273+ #~ "pertinente a los desarrolladores."
274+
275+ #~ msgid ""
276+ #~ "If the problem you're reporting is not already in the bug tracker, go "
277+ #~ "back to the Python Bug Tracker and log in. If you don't already have a "
278+ #~ "tracker account, select the \"Register\" link or, if you use OpenID, one "
279+ #~ "of the OpenID provider logos in the sidebar. It is not possible to "
280+ #~ "submit a bug report anonymously."
281+ #~ msgstr ""
282+ #~ "Si el problema que estás describiendo no está todavía en el rastreador de "
283+ #~ "errores, vuelve al Python Bug Tracker e inicia sesión. Si no tienes una "
284+ #~ "cuenta en el rastreador, selecciona el enlace \"Register\" o, si usas "
285+ #~ "OpenID, selecciona uno de los logos de los proveedores OpenID en la barra "
286+ #~ "lateral. No es posible el envío de informes de errores de manera anónima."
287+
288+ #~ msgid ""
289+ #~ "The submission form has a number of fields. For the \"Title\" field, "
290+ #~ "enter a *very* short description of the problem; less than ten words is "
291+ #~ "good. In the \"Type\" field, select the type of your problem; also "
292+ #~ "select the \"Component\" and \"Versions\" to which the bug relates."
293+ #~ msgstr ""
294+ #~ "El formulario de envío tiene un número de campos. Para el campo "
295+ #~ "\"Title\", introduce una descripción *muy* corta del problema; menos de "
296+ #~ "diez palabras está bien. En el campo \"Type\", selecciona el tipo de "
297+ #~ "problema; selecciona también el \"Component\" y \"Versions\" con los que "
298+ #~ "el error está relacionado."
0 commit comments