|
| 1 | +# SOME DESCRIPTIVE TITLE. |
| 2 | +# Copyright (C) 2001-2018, Python Software Foundation |
| 3 | +# This file is distributed under the same license as the Python package. |
| 4 | +# |
| 5 | +# Translators: |
| 6 | +# Asoul Yang <azx754@gmail.com>, 2016 |
| 7 | +# Ching-Lung Chuang, 2015 |
| 8 | +# aminzai <lagunawang@gmail.com>, 2015 |
| 9 | +# Liang-Bo Wang <me@liang2.tw>, 2015 |
| 10 | +# sammy huang <sammy.huang@kkday.com>, 2017 |
| 11 | +msgid "" |
| 12 | +msgstr "" |
| 13 | +"Project-Id-Version: Python 3.5 TW\n" |
| 14 | +"Report-Msgid-Bugs-To: \n" |
| 15 | +"POT-Creation-Date: 2018-05-23 22:00+0800\n" |
| 16 | +"PO-Revision-Date: 2017-09-22 18:26+0000\n" |
| 17 | +"Last-Translator: sammy huang <sammy.huang@kkday.com>\n" |
| 18 | +"Language-Team: Chinese Traditional (http://www.transifex.com/python-tw-doc/python-35-tw/language/zh-Hant/)\n" |
| 19 | +"MIME-Version: 1.0\n" |
| 20 | +"Content-Type: text/plain; charset=UTF-8\n" |
| 21 | +"Content-Transfer-Encoding: 8bit\n" |
| 22 | +"Language: zh-Hant\n" |
| 23 | +"Plural-Forms: nplurals=1; plural=0;\n" |
| 24 | + |
| 25 | +#: ../../bugs.rst:5 |
| 26 | +msgid "Dealing with Bugs" |
| 27 | +msgstr "處理bug" |
| 28 | + |
| 29 | +#: ../../bugs.rst:7 |
| 30 | +msgid "" |
| 31 | +"Python is a mature programming language which has established a reputation " |
| 32 | +"for stability. In order to maintain this reputation, the developers would " |
| 33 | +"like to know of any deficiencies you find in Python." |
| 34 | +msgstr "Python 已經是一個以穩定著稱的成熟程式語言。為了維持「穩定」此信譽，開發者們想知道任何您發現的缺失。" |
| 35 | + |
| 36 | +#: ../../bugs.rst:11 |
| 37 | +msgid "" |
| 38 | +"It can be sometimes faster to fix bugs yourself and contribute patches to " |
| 39 | +"Python as it streamlines the process and involves less people. Learn how to " |
| 40 | +":ref:`contribute <contributing-to-python>`." |
| 41 | +msgstr "" |
| 42 | + |
| 43 | +#: ../../bugs.rst:16 |
| 44 | +msgid "Documentation bugs" |
| 45 | +msgstr "說明文件錯誤" |
| 46 | + |
| 47 | +#: ../../bugs.rst:18 |
| 48 | +msgid "" |
| 49 | +"If you find a bug in this documentation or would like to propose an " |
| 50 | +"improvement, please submit a bug report on the :ref:`tracker <using-the-" |
| 51 | +"tracker>`. If you have a suggestion how to fix it, include that as well." |
| 52 | +msgstr "" |
| 53 | + |
| 54 | +#: ../../bugs.rst:22 |
| 55 | +msgid "" |
| 56 | +"If you're short on time, you can also email documentation bug reports to " |
| 57 | +"docs@python.org (behavioral bugs can be sent to python-list@python.org). " |
| 58 | +"'docs@' is a mailing list run by volunteers; your request will be noticed, " |
| 59 | +"though it may take a while to be processed." |
| 60 | +msgstr "" |
| 61 | + |
| 62 | +#: ../../bugs.rst:28 |
| 63 | +msgid "`Documentation bugs`_ on the Python issue tracker" |
| 64 | +msgstr "Python issue tracker 上\\ `文件相關的錯誤 <Documentation bugs_>`_" |
| 65 | + |
| 66 | +#: ../../bugs.rst:33 |
| 67 | +msgid "Using the Python issue tracker" |
| 68 | +msgstr "使用 Python 議題追蹤" |
| 69 | + |
| 70 | +#: ../../bugs.rst:35 |
| 71 | +msgid "" |
| 72 | +"Bug reports for Python itself should be submitted via the Python Bug Tracker" |
| 73 | +" (https://bugs.python.org/). The bug tracker offers a Web form which allows" |
| 74 | +" pertinent information to be entered and submitted to the developers." |
| 75 | +msgstr "" |
| 76 | + |
| 77 | +#: ../../bugs.rst:39 |
| 78 | +msgid "" |
| 79 | +"The first step in filing a report is to determine whether the problem has " |
| 80 | +"already been reported. The advantage in doing so, aside from saving the " |
| 81 | +"developers time, is that you learn what has been done to fix it; it may be " |
| 82 | +"that the problem has already been fixed for the next release, or additional " |
| 83 | +"information is needed (in which case you are welcome to provide it if you " |
| 84 | +"can!). To do this, search the bug database using the search box on the top " |
| 85 | +"of the page." |
| 86 | +msgstr "" |
| 87 | + |
| 88 | +#: ../../bugs.rst:46 |
| 89 | +msgid "" |
| 90 | +"If the problem you're reporting is not already in the bug tracker, go back " |
| 91 | +"to the Python Bug Tracker and log in. If you don't already have a tracker " |
| 92 | +"account, select the \"Register\" link or, if you use OpenID, one of the " |
| 93 | +"OpenID provider logos in the sidebar. It is not possible to submit a bug " |
| 94 | +"report anonymously." |
| 95 | +msgstr "" |
| 96 | + |
| 97 | +#: ../../bugs.rst:51 |
| 98 | +msgid "" |
| 99 | +"Being now logged in, you can submit a bug. Select the \"Create New\" link " |
| 100 | +"in the sidebar to open the bug reporting form." |
| 101 | +msgstr "" |
| 102 | + |
| 103 | +#: ../../bugs.rst:54 |
| 104 | +msgid "" |
| 105 | +"The submission form has a number of fields. For the \"Title\" field, enter " |
| 106 | +"a *very* short description of the problem; less than ten words is good. In " |
| 107 | +"the \"Type\" field, select the type of your problem; also select the " |
| 108 | +"\"Component\" and \"Versions\" to which the bug relates." |
| 109 | +msgstr "" |
| 110 | + |
| 111 | +#: ../../bugs.rst:59 |
| 112 | +msgid "" |
| 113 | +"In the \"Comment\" field, describe the problem in detail, including what you" |
| 114 | +" expected to happen and what did happen. Be sure to include whether any " |
| 115 | +"extension modules were involved, and what hardware and software platform you" |
| 116 | +" were using (including version information as appropriate)." |
| 117 | +msgstr "" |
| 118 | + |
| 119 | +#: ../../bugs.rst:64 |
| 120 | +msgid "" |
| 121 | +"Each bug report will be assigned to a developer who will determine what " |
| 122 | +"needs to be done to correct the problem. You will receive an update each " |
| 123 | +"time action is taken on the bug." |
| 124 | +msgstr "" |
| 125 | + |
| 126 | +#: ../../bugs.rst:73 |
| 127 | +msgid "" |
| 128 | +"`How to Report Bugs Effectively " |
| 129 | +"<http://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_" |
| 130 | +msgstr "" |
| 131 | + |
| 132 | +#: ../../bugs.rst:72 |
| 133 | +msgid "" |
| 134 | +"Article which goes into some detail about how to create a useful bug report." |
| 135 | +" This describes what kind of information is useful and why it is useful." |
| 136 | +msgstr "" |
| 137 | + |
| 138 | +#: ../../bugs.rst:76 |
| 139 | +msgid "" |
| 140 | +"`Bug Writing Guidelines <https://developer.mozilla.org/en-" |
| 141 | +"US/docs/Mozilla/QA/Bug_writing_guidelines>`_" |
| 142 | +msgstr "" |
| 143 | + |
| 144 | +#: ../../bugs.rst:76 |
| 145 | +msgid "" |
| 146 | +"Information about writing a good bug report. Some of this is specific to " |
| 147 | +"the Mozilla project, but describes general good practices." |
| 148 | +msgstr "" |
| 149 | + |
| 150 | +#: ../../bugs.rst:82 |
| 151 | +msgid "Getting started contributing to Python yourself" |
| 152 | +msgstr "開始讓自己貢獻 Python" |
| 153 | + |
| 154 | +#: ../../bugs.rst:84 |
| 155 | +msgid "" |
| 156 | +"Beyond just reporting bugs that you find, you are also welcome to submit " |
| 157 | +"patches to fix them. You can find more information on how to get started " |
| 158 | +"patching Python in the `Python Developer's Guide`_. If you have questions, " |
| 159 | +"the `core-mentorship mailing list`_ is a friendly place to get answers to " |
| 160 | +"any and all questions pertaining to the process of fixing issues in Python." |
| 161 | +msgstr "" |
0 commit comments