|
| 1 | +# SOME DESCRIPTIVE TITLE. |
| 2 | +# Copyright (C) 2001 Python Software Foundation |
| 3 | +# This file is distributed under the same license as the Python package. |
| 4 | +# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR. |
| 5 | +# |
| 6 | +#,fuzzy |
| 7 | +msgid "" |
| 8 | +msgstr "" |
| 9 | +"Project-Id-Version:Python 3.14\n" |
| 10 | +"Report-Msgid-Bugs-To:\n" |
| 11 | +"POT-Creation-Date:2025-05-22 14:20+0200\n" |
| 12 | +"PO-Revision-Date:YEAR-MO-DA HO:MI+ZONE\n" |
| 13 | +"Last-Translator:FULL NAME <EMAIL@ADDRESS>\n" |
| 14 | +"Language-Team:LANGUAGE <LL@li.org>\n" |
| 15 | +"MIME-Version:1.0\n" |
| 16 | +"Content-Type:text/plain; charset=UTF-8\n" |
| 17 | +"Content-Transfer-Encoding:8bit\n" |
| 18 | + |
| 19 | +#:bugs.rst:5 |
| 20 | +msgid"Dealing with Bugs" |
| 21 | +msgstr"" |
| 22 | + |
| 23 | +#:bugs.rst:7 |
| 24 | +msgid"" |
| 25 | +"Python is a mature programming language which has established a reputation " |
| 26 | +"for stability. In order to maintain this reputation, the developers would " |
| 27 | +"like to know of any deficiencies you find in Python." |
| 28 | +msgstr"" |
| 29 | + |
| 30 | +#:bugs.rst:11 |
| 31 | +msgid"" |
| 32 | +"It can be sometimes faster to fix bugs yourself and contribute patches to " |
| 33 | +"Python as it streamlines the process and involves less people. Learn how " |
| 34 | +"to :ref:`contribute <contributing-to-python>`." |
| 35 | +msgstr"" |
| 36 | + |
| 37 | +#:bugs.rst:16 |
| 38 | +msgid"Documentation bugs" |
| 39 | +msgstr"" |
| 40 | + |
| 41 | +#:bugs.rst:18 |
| 42 | +msgid"" |
| 43 | +"If you find a bug in this documentation or would like to propose an " |
| 44 | +"improvement, please submit a bug report on the :ref:`issue tracker <using-" |
| 45 | +"the-tracker>`. If you have a suggestion on how to fix it, include that as " |
| 46 | +"well." |
| 47 | +msgstr"" |
| 48 | + |
| 49 | +#:bugs.rst:22 |
| 50 | +msgid"" |
| 51 | +"You can also open a discussion item on our `Documentation Discourse forum " |
| 52 | +"<https://discuss.python.org/c/documentation/26>`_." |
| 53 | +msgstr"" |
| 54 | + |
| 55 | +#:bugs.rst:25 |
| 56 | +msgid"" |
| 57 | +"If you find a bug in the theme (HTML / CSS / JavaScript) of the " |
| 58 | +"documentation, please submit a bug report on the `python-doc-theme issue " |
| 59 | +"tracker <https://github.com/python/python-docs-theme>`_." |
| 60 | +msgstr"" |
| 61 | + |
| 62 | +#:bugs.rst:31 |
| 63 | +msgid"`Documentation bugs`_" |
| 64 | +msgstr"" |
| 65 | + |
| 66 | +#:bugs.rst:32 |
| 67 | +msgid"" |
| 68 | +"A list of documentation bugs that have been submitted to the Python issue " |
| 69 | +"tracker." |
| 70 | +msgstr"" |
| 71 | + |
| 72 | +#:bugs.rst:34 |
| 73 | +msgid"`Issue Tracking <https://devguide.python.org/tracker/>`_" |
| 74 | +msgstr"" |
| 75 | + |
| 76 | +#:bugs.rst:35 |
| 77 | +msgid"" |
| 78 | +"Overview of the process involved in reporting an improvement on the tracker." |
| 79 | +msgstr"" |
| 80 | + |
| 81 | +#:bugs.rst:37 |
| 82 | +msgid"" |
| 83 | +"`Helping with Documentation <https://devguide.python.org/docquality/#helping-" |
| 84 | +"with-documentation>`_" |
| 85 | +msgstr"" |
| 86 | + |
| 87 | +#:bugs.rst:38 |
| 88 | +msgid"" |
| 89 | +"Comprehensive guide for individuals that are interested in contributing to " |
| 90 | +"Python documentation." |
| 91 | +msgstr"" |
| 92 | + |
| 93 | +#:bugs.rst:40 |
| 94 | +msgid"" |
| 95 | +"`Documentation Translations <https://devguide.python.org/documentation/" |
| 96 | +"translating/>`_" |
| 97 | +msgstr"" |
| 98 | + |
| 99 | +#:bugs.rst:41 |
| 100 | +msgid"" |
| 101 | +"A list of GitHub pages for documentation translation and their primary " |
| 102 | +"contacts." |
| 103 | +msgstr"" |
| 104 | + |
| 105 | +#:bugs.rst:47 |
| 106 | +msgid"Using the Python issue tracker" |
| 107 | +msgstr"" |
| 108 | + |
| 109 | +#:bugs.rst:49 |
| 110 | +msgid"" |
| 111 | +"Issue reports for Python itself should be submitted via the GitHub issues " |
| 112 | +"tracker (https://github.com/python/cpython/issues). The GitHub issues " |
| 113 | +"tracker offers a web form which allows pertinent information to be entered " |
| 114 | +"and submitted to the developers." |
| 115 | +msgstr"" |
| 116 | + |
| 117 | +#:bugs.rst:54 |
| 118 | +msgid"" |
| 119 | +"The first step in filing a report is to determine whether the problem has " |
| 120 | +"already been reported. The advantage in doing so, aside from saving the " |
| 121 | +"developers' time, is that you learn what has been done to fix it; it may be " |
| 122 | +"that the problem has already been fixed for the next release, or additional " |
| 123 | +"information is needed (in which case you are welcome to provide it if you " |
| 124 | +"can!). To do this, search the tracker using the search box at the top of the " |
| 125 | +"page." |
| 126 | +msgstr"" |
| 127 | + |
| 128 | +#:bugs.rst:61 |
| 129 | +msgid"" |
| 130 | +"If the problem you're reporting is not already in the list, log in to " |
| 131 | +"GitHub. If you don't already have a GitHub account, create a new account " |
| 132 | +"using the\"Sign up\" link. It is not possible to submit a bug report " |
| 133 | +"anonymously." |
| 134 | +msgstr"" |
| 135 | + |
| 136 | +#:bugs.rst:66 |
| 137 | +msgid"" |
| 138 | +"Being now logged in, you can submit an issue. Click on the\"New issue\" " |
| 139 | +"button in the top bar to report a new issue." |
| 140 | +msgstr"" |
| 141 | + |
| 142 | +#:bugs.rst:69 |
| 143 | +msgid"The submission form has two fields,\"Title\" and\"Comment\"." |
| 144 | +msgstr"" |
| 145 | + |
| 146 | +#:bugs.rst:71 |
| 147 | +msgid"" |
| 148 | +"For the\"Title\" field, enter a *very* short description of the problem; " |
| 149 | +"fewer than ten words is good." |
| 150 | +msgstr"" |
| 151 | + |
| 152 | +#:bugs.rst:74 |
| 153 | +msgid"" |
| 154 | +"In the\"Comment\" field, describe the problem in detail, including what you " |
| 155 | +"expected to happen and what did happen. Be sure to include whether any " |
| 156 | +"extension modules were involved, and what hardware and software platform you " |
| 157 | +"were using (including version information as appropriate)." |
| 158 | +msgstr"" |
| 159 | + |
| 160 | +#:bugs.rst:79 |
| 161 | +msgid"" |
| 162 | +"Each issue report will be reviewed by a developer who will determine what " |
| 163 | +"needs to be done to correct the problem. You will receive an update each " |
| 164 | +"time an action is taken on the issue." |
| 165 | +msgstr"" |
| 166 | + |
| 167 | +#:bugs.rst:86 |
| 168 | +msgid"" |
| 169 | +"`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/" |
| 170 | +"~sgtatham/bugs.html>`_" |
| 171 | +msgstr"" |
| 172 | + |
| 173 | +#:bugs.rst:87 |
| 174 | +msgid"" |
| 175 | +"Article which goes into some detail about how to create a useful bug report. " |
| 176 | +"This describes what kind of information is useful and why it is useful." |
| 177 | +msgstr"" |
| 178 | + |
| 179 | +#:bugs.rst:90 |
| 180 | +msgid"" |
| 181 | +"`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-" |
| 182 | +"writing.html>`_" |
| 183 | +msgstr"" |
| 184 | + |
| 185 | +#:bugs.rst:91 |
| 186 | +msgid"" |
| 187 | +"Information about writing a good bug report. Some of this is specific to " |
| 188 | +"the Mozilla project, but describes general good practices." |
| 189 | +msgstr"" |
| 190 | + |
| 191 | +#:bugs.rst:97 |
| 192 | +msgid"Getting started contributing to Python yourself" |
| 193 | +msgstr"" |
| 194 | + |
| 195 | +#:bugs.rst:99 |
| 196 | +msgid"" |
| 197 | +"Beyond just reporting bugs that you find, you are also welcome to submit " |
| 198 | +"patches to fix them. You can find more information on how to get started " |
| 199 | +"patching Python in the `Python Developer's Guide`_. If you have questions, " |
| 200 | +"the `core-mentorship mailing list`_ is a friendly place to get answers to " |
| 201 | +"any and all questions pertaining to the process of fixing issues in Python." |
| 202 | +msgstr"" |