Expand Up @@ -10,16 +10,16 @@ msgid "" msgstr "" "Project-Id-Version: Python 3.8\n" "Report-Msgid-Bugs-To: \n" "POT-Creation-Date:2021 -10-16 21:42 +0200\n" "POT-Creation-Date:2022 -10-25 19:47 +0200\n" "PO-Revision-Date: 2020-06-28 01:03+0200\n" "Last-Translator: \n" "Language-Team: python-doc-es\n" "Language: es\n" "Language-Team: python-doc-es\n" "Plural-Forms: nplurals=2; plural=(n != 1);\n" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" "Plural-Forms: nplurals=2; plural=(n != 1)\n" "Generated-By: Babel 2.9.1\n" "Generated-By: Babel 2.10.3\n" #: ../Doc/bugs.rst:5 msgid "Dealing with Bugs" Expand Down Expand Up @@ -96,7 +96,7 @@ msgid "" msgstr "" "Resumen general del proceso necesario para reportar una mejora en el tracker." #: ../Doc/bugs.rst:35 #: ../Doc/bugs.rst:36 msgid "" "`Helping with Documentation <https://devguide.python.org/docquality/#helping-" "with-documentation>`_" Expand All @@ -112,30 +112,43 @@ msgstr "" "Guía detallada para gente interesada en contribuir a la documentación de " "Python." #: ../Doc/bugs.rst:41 #: ../Doc/bugs.rst:38 #, fuzzy msgid "" "`Documentation Translations <https://devguide.python.org/documenting/" "#translating>`_" msgstr "" "`Ayudar con la documentación <https://devguide.python.org/docquality/" "#helping-with-documentation>`_" #: ../Doc/bugs.rst:39 msgid "" "A list of GitHub pages for documentation translation and their primary " "contacts." msgstr "" #: ../Doc/bugs.rst:45 msgid "Using the Python issue tracker" msgstr "Utilizar el issue tracker de Python" #: ../Doc/bugs.rst:43 #: ../Doc/bugs.rst:47 msgid "" "Bug reports for Python itself should be submitted via the Python Bug Tracker " "(https://bugs.python.org/). The bug tracker offers a web form which allows " "pertinent information to be entered and submitted to the developers." "Issue reports for Python itself should be submitted via the GitHub issues " "tracker (https://github.com/python/cpython/issues). The GitHub issues " "tracker offers a web form which allows pertinent information to be entered " "and submitted to the developers." msgstr "" "Los informes de errores para Python en sí deben enviarse a través de Python " "Bug Tracker (https://bugs.python.org/). El rastreador de errores ofrece un " "formulario web que permite ingresar y enviar la información pertinente a los " "desarrolladores." #: ../Doc/bugs.rst:47 #: ../Doc/bugs.rst:52 #, fuzzy msgid "" "The first step in filing a report is to determine whether the problem has " "already been reported. The advantage in doing so, aside from saving the " "developers time, is that you learn what has been done to fix it; it may be " "developers' time, is that you learn what has been done to fix it; it may be " "that the problem has already been fixed for the next release, or additional " "information is needed (in which case you are welcome to provide it if you " "can!). To do this, search thebug database using the search boxon the top " "of the page." "can!). To do this, search thetracker using the search boxat the top of the " "page." msgstr "" "El primer paso para rellenar un informe es determinar si el problema ya ha " "sido descrito previamente. La ventaja de hacer esto, aparte de ahorrar " Expand All @@ -146,42 +159,34 @@ msgstr "" "en la base de datos de errores usando la zona de búsqueda al principio de " "esta página." #: ../Doc/bugs.rst:54 #: ../Doc/bugs.rst:59 msgid "" "If the problem you're reporting is not already in the bug tracker, go back " "to the Python Bug Tracker and log in. If you don't already have a tracker " "account, select the \"Register\" link or, if you use OpenID, one of the " "OpenID provider logos in the sidebar. It is not possible to submit a bug " "report anonymously." "If the problem you're reporting is not already in the list, log in to " "GitHub. If you don't already have a GitHub account, create a new account " "using the \"Sign up\" link. It is not possible to submit a bug report " "anonymously." msgstr "" "Si el problema que estás describiendo no está todavía en el rastreador de " "errores, vuelve al Python Bug Tracker e inicia sesión. Si no tienes una " "cuenta en el rastreador, selecciona el enlace \"Register\" o, si usas " "OpenID, selecciona uno de los logos de los proveedores OpenID en la barra " "lateral. No es posible el envío de informes de errores de manera anónima." #: ../Doc/bugs.rst:59 #: ../Doc/bugs.rst:64 #, fuzzy msgid "" "Being now logged in, you can submita bug. Select the \"Create New\" link " "in thesidebar toopen the bug reporting form ." "Being now logged in, you can submitan issue. Click on the \"New issue\" " "button in thetop bar toreport a new issue ." msgstr "" "Una vez dentro, puedes enviar el error. Selecciona el enlace \"Create New\" " "en la barra lateral para abrir el formulario del informe de errores." #: ../Doc/bugs.rst:62 #: ../Doc/bugs.rst:67 msgid "The submission form has two fields, \"Title\" and \"Comment\"." msgstr "" #: ../Doc/bugs.rst:69 msgid "" "The submission form has a number of fields. For the \"Title\" field, enter " "a *very* short description of the problem; less than ten words is good. In " "the \"Type\" field, select the type of your problem; also select the " "\"Component\" and \"Versions\" to which the bug relates." "For the \"Title\" field, enter a *very* short description of the problem; " "less than ten words is good." msgstr "" "El formulario de envío tiene un número de campos. Para el campo \"Title\", " "introduce una descripción *muy* corta del problema; menos de diez palabras " "está bien. En el campo \"Type\", selecciona el tipo de problema; selecciona " "también el \"Component\" y \"Versions\" con los que el error está " "relacionado." #: ../Doc/bugs.rst:67 #: ../Doc/bugs.rst:72 msgid "" "In the \"Comment\" field, describe the problem in detail, including what you " "expected to happen and what did happen. Be sure to include whether any " Expand All @@ -193,41 +198,42 @@ msgstr "" "si cualquier módulo de extensión está involucrado, y qué plataformas de " "hardware y software estás usando (incluyendo las versiones correspondientes)." #: ../Doc/bugs.rst:72 #: ../Doc/bugs.rst:77 #, fuzzy msgid "" "Eachbug report will beassigned to a developer who will determine what " "needs to be done to correct the problem. You will receive an update each " "time action is taken on thebug ." "Eachissue report will bereviewed by a developer who will determine what " "needs to be done to correct the problem. You will receive an update each " "timean action is taken on theissue ." msgstr "" "Cada informe de errores será asignado a un desarrollador que determinará qué " "es necesario hacer para corregir el problema. Recibirás una actualización " "cada vez que una acción nueva sea aplicada." #: ../Doc/bugs.rst:81 #: ../Doc/bugs.rst:86 msgid "" "`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/" "~sgtatham/bugs.html>`_" msgstr "" "`Cómo informar de errores de manera efectiva <https://www.chiark.greenend." "org.uk/~sgtatham/bugs.html>`_" #: ../Doc/bugs.rst:80 #: ../Doc/bugs.rst:85 msgid "" "Article which goes into some detail about how to create a useful bug report. " "This describes what kind of information is useful and why it is useful." msgstr "" "Artículo que detalla cómo crear un informe de errores útil. Describe qué " "tipo de información es útil y por qué lo es." #: ../Doc/bugs.rst:84 #: ../Doc/bugs.rst:89 msgid "" "`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-" "writing.html>`_" msgstr "" "`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-" "writing.html>`_" #: ../Doc/bugs.rst:84 #: ../Doc/bugs.rst:89 msgid "" "Information about writing a good bug report. Some of this is specific to " "the Mozilla project, but describes general good practices." Expand All @@ -236,11 +242,11 @@ msgstr "" "información es específica al proyecto Mozilla, pero en general describe " "buenas prácticas." #: ../Doc/bugs.rst:90 #: ../Doc/bugs.rst:95 msgid "Getting started contributing to Python yourself" msgstr "Para empezar a contribuir en Python" #: ../Doc/bugs.rst:92 #: ../Doc/bugs.rst:97 msgid "" "Beyond just reporting bugs that you find, you are also welcome to submit " "patches to fix them. You can find more information on how to get started " Expand All @@ -254,3 +260,39 @@ msgstr "" "Guide`_. Si tienes preguntas, el `core-mentorship mailing list`_ es un " "agradable lugar para obtener respuestas a cualquiera y a todas las preguntas " "pertenecientes al proceso de corrección de problemas en Python." #~ msgid "" #~ "Bug reports for Python itself should be submitted via the Python Bug " #~ "Tracker (https://bugs.python.org/). The bug tracker offers a web form " #~ "which allows pertinent information to be entered and submitted to the " #~ "developers." #~ msgstr "" #~ "Los informes de errores para Python en sí deben enviarse a través de " #~ "Python Bug Tracker (https://bugs.python.org/). El rastreador de errores " #~ "ofrece un formulario web que permite ingresar y enviar la información " #~ "pertinente a los desarrolladores." #~ msgid "" #~ "If the problem you're reporting is not already in the bug tracker, go " #~ "back to the Python Bug Tracker and log in. If you don't already have a " #~ "tracker account, select the \"Register\" link or, if you use OpenID, one " #~ "of the OpenID provider logos in the sidebar. It is not possible to " #~ "submit a bug report anonymously." #~ msgstr "" #~ "Si el problema que estás describiendo no está todavía en el rastreador de " #~ "errores, vuelve al Python Bug Tracker e inicia sesión. Si no tienes una " #~ "cuenta en el rastreador, selecciona el enlace \"Register\" o, si usas " #~ "OpenID, selecciona uno de los logos de los proveedores OpenID en la barra " #~ "lateral. No es posible el envío de informes de errores de manera anónima." #~ msgid "" #~ "The submission form has a number of fields. For the \"Title\" field, " #~ "enter a *very* short description of the problem; less than ten words is " #~ "good. In the \"Type\" field, select the type of your problem; also " #~ "select the \"Component\" and \"Versions\" to which the bug relates." #~ msgstr "" #~ "El formulario de envío tiene un número de campos. Para el campo " #~ "\"Title\", introduce una descripción *muy* corta del problema; menos de " #~ "diez palabras está bien. En el campo \"Type\", selecciona el tipo de " #~ "problema; selecciona también el \"Component\" y \"Versions\" con los que " #~ "el error está relacionado."