@@ -12,7 +12,7 @@ msgid ""
1212msgstr ""
1313"Project-Id-Version : Python 3.10\n "
1414"Report-Msgid-Bugs-To : \n "
15- "POT-Creation-Date : 2022-06-16 06 :28+0000\n "
15+ "POT-Creation-Date : 2022-11-04 14 :28+0000\n "
1616"PO-Revision-Date : 2021-06-28 00:47+0000\n "
1717"Last-Translator : Maciej Olko <maciej.olko@gmail.com>, 2022\n "
1818"Language-Team : Polish (https://www.transifex.com/python-doc/teams/5390/pl/)\n "
@@ -118,60 +118,41 @@ msgid "Using the Python issue tracker"
118118msgstr "Używanie systemu zgłoszeń Pythona"
119119
120120msgid ""
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."
121+ "Issue reports for Python itself should be submitted via the GitHub issues "
122+ "tracker (https://github.com/python/cpython/issues). The GitHub issues "
123+ "tracker offers a web form which allows pertinent information to be entered "
124+ "and submitted to the developers."
124125msgstr ""
125- "Zgłoszenia błędów w Pythonie powinny być zgłaszane przez Python Bug Tracker "
126- "(https://bugs.python.org/). System zgłoszeń posiada formularz, który pozwala "
127- "wprowadzić stosowne informacje i wysłać je deweloperom."
128126
129127msgid ""
130128"The first step in filing a report is to determine whether the problem has "
131129"already been reported. The advantage in doing so, aside from saving the "
132- "developers time, is that you learn what has been done to fix it; it may be "
130+ "developers' time, is that you learn what has been done to fix it; it may be "
133131"that the problem has already been fixed for the next release, or additional "
134132"information is needed (in which case you are welcome to provide it if you "
135- "can!). To do this, search the bug database using the search box on the top "
136- "of the page."
133+ "can!). To do this, search the tracker using the search box at the top of the "
134+ "page."
137135msgstr ""
138- "Pierwszym krokiem przy wypełnianiu zgłoszenia jest ustalenie, czy problem "
139- "został już zgłoszony. Zaletą tego ustalenia, oprócz oszczędzenia czasu "
140- "deweloperów, jest to, że dowiesz się, co zostało zrobione, aby go naprawić; "
141- "być może problem został już naprawiony na następne wydanie lub potrzebne są "
142- "dodatkowe informacje (w tym przypadku zapraszamy cię, żebyś je podał, jeśli "
143- "możesz!). Aby to zrobić, przeszukaj bazę zgłoszeń używając pola wyszukiwania "
144- "na górze strony."
145136
146137msgid ""
147- "If the problem you're reporting is not already in the bug tracker, go back "
148- "to the Python Bug Tracker and log in. If you don't already have a tracker "
149- "account, select the \" Register\" link or, if you use OpenID, one of the "
150- "OpenID provider logos in the sidebar. It is not possible to submit a bug "
151- "report anonymously."
138+ "If the problem you're reporting is not already in the list, log in to "
139+ "GitHub. If you don't already have a GitHub account, create a new account "
140+ "using the \" Sign up\" link. It is not possible to submit a bug report "
141+ "anonymously."
152142msgstr ""
153- "Jeśli problemu, który zgłaszasz, nie ma jeszcze w bug trackerze, wróć do "
154- "Python Bug Trackera i zaloguj się. Jeśli nie masz jeszcze konta w trackerze, "
155- "wybierz link „Register” lub, jeśli używasz OpenID, jedno z logo providerów "
156- "OpenID w sidebarze. Nie da się wysłać zgłoszenia błędu anonimowo."
157143
158144msgid ""
159- "Being now logged in, you can submit a bug. Select the \" Create New\" link "
160- "in the sidebar to open the bug reporting form."
145+ "Being now logged in, you can submit an issue. Click on the \" New issue\" "
146+ "button in the top bar to report a new issue."
147+ msgstr ""
148+
149+ msgid "The submission form has two fields, \" Title\" and \" Comment\" ."
161150msgstr ""
162- "Będąc teraz zalogowanym, możesz zgłosić buga. Wybierz link „Create New” w "
163- "sidebarze, aby otworzyć formularz zgłaszania błędu."
164151
165152msgid ""
166- "The submission form has a number of fields. For the \" Title\" field, enter "
167- "a *very* short description of the problem; less than ten words is good. In "
168- "the \" Type\" field, select the type of your problem; also select the "
169- "\" Component\" and \" Versions\" to which the bug relates."
153+ "For the \" Title\" field, enter a *very* short description of the problem; "
154+ "less than ten words is good."
170155msgstr ""
171- "Formularz zgłoszeniowy ma wiele pól. W polu „Title” wprowadź *bardzo* krótki "
172- "opis problemu; mniej niż dziesięć słów jest dobrze. W polu „Type” wybierz "
173- "typ swojego problemu; wybierz również „Component” i „Versions”, z którymi "
174- "bug jest związany."
175156
176157msgid ""
177158"In the \" Comment\" field, describe the problem in detail, including what you "
@@ -186,13 +167,10 @@ msgstr ""
186167"wersjach)."
187168
188169msgid ""
189- "Each bug report will be assigned to a developer who will determine what "
190- "needs to be done to correct the problem. You will receive an update each "
191- "time action is taken on the bug ."
170+ "Each issue report will be reviewed by a developer who will determine what "
171+ "needs to be done to correct the problem. You will receive an update each "
172+ "time an action is taken on the issue ."
192173msgstr ""
193- "Każde zgłoszenie błędu zostanie przypisane do dewelopera, który zdecyduje, "
194- "co należy zrobić, aby naprawić problem. Dostaniesz aktualizację za każdym "
195- "razem, gdy na bugu zostanie wykonana jakaś akcja."
196174
197175msgid ""
198176"`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/"
0 commit comments