Skip to content

Commit 2e155e4

Browse files
methanemethane
committed
Update translations from Transifex
1 parent ff06042 commit 2e155e4

File tree

490 files changed

+74168
-62935
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

490 files changed

+74168
-62935
lines changed

‎about.po

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -4,16 +4,16 @@
44
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
55
#
66
# Translators:
7-
# tomo, 2021
7+
# Rafael Fontenelle <rffontenelle@gmail.com>, 2022
88
#
99
#, fuzzy
1010
msgid ""
1111
msgstr ""
1212
"Project-Id-Version: Python 3.10\n"
1313
"Report-Msgid-Bugs-To: \n"
14-
"POT-Creation-Date: 2022-06-16 06:28+0000\n"
15-
"PO-Revision-Date: 2021-06-28 00:47+0000\n"
16-
"Last-Translator: tomo, 2021\n"
14+
"POT-Creation-Date: 2022-12-30 14:59+0000\n"
15+
"PO-Revision-Date: 2022-11-05 17:21+0000\n"
16+
"Last-Translator: Rafael Fontenelle <rffontenelle@gmail.com>, 2022\n"
1717
"Language-Team: Japanese (https://www.transifex.com/python-doc/teams/5390/"
1818
"ja/)\n"
1919
"MIME-Version: 1.0\n"
@@ -63,17 +63,17 @@ msgstr ""
6363

6464
#: ../../about.rst:24
6565
msgid ""
66-
"the `Docutils <http://docutils.sourceforge.net/>`_ project for creating "
66+
"the `Docutils <https://docutils.sourceforge.io/>`_ project for creating "
6767
"reStructuredText and the Docutils suite;"
6868
msgstr ""
69-
"`Docutils <http://docutils.sourceforge.net/>`_ プロジェクト. "
70-
"reStructuredText と docutils ツールセットを作成しました。"
7169

7270
#: ../../about.rst:26
7371
msgid ""
7472
"Fredrik Lundh for his Alternative Python Reference project from which Sphinx "
7573
"got many good ideas."
7674
msgstr ""
75+
"Fredrik Lundh の Alternative Python Reference プロジェクトから Sphinx は多く"
76+
"のアイデアを得ました。"
7777

7878
#: ../../about.rst:31
7979
msgid "Contributors to the Python Documentation"

‎bugs.po

Lines changed: 112 additions & 81 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,21 @@
11
# SOME DESCRIPTIVE TITLE.
2-
# Copyright (C) 2001-2021, Python Software Foundation
2+
# Copyright (C) 2001-2022, Python Software Foundation
33
# This file is distributed under the same license as the Python package.
44
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
5-
#
5+
#
66
# Translators:
7-
# tomo, 2021
8-
#
7+
# Rafael Fontenelle <rffontenelle@gmail.com>, 2022
8+
#
99
#, fuzzy
1010
msgid ""
1111
msgstr ""
1212
"Project-Id-Version: Python 3.10\n"
1313
"Report-Msgid-Bugs-To: \n"
14-
"POT-Creation-Date: 2021-08-16 13:43+0000\n"
15-
"PO-Revision-Date: 2021-06-28 00:47+0000\n"
16-
"Last-Translator: tomo, 2021\n"
17-
"Language-Team: Japanese (https://www.transifex.com/python-doc/teams/5390/ja/)\n"
14+
"POT-Creation-Date: 2022-12-30 14:59+0000\n"
15+
"PO-Revision-Date: 2022-11-05 17:21+0000\n"
16+
"Last-Translator: Rafael Fontenelle <rffontenelle@gmail.com>, 2022\n"
17+
"Language-Team: Japanese (https://www.transifex.com/python-doc/teams/5390/"
18+
"ja/)\n"
1819
"MIME-Version: 1.0\n"
1920
"Content-Type: text/plain; charset=UTF-8\n"
2021
"Content-Transfer-Encoding: 8bit\n"
@@ -31,16 +32,17 @@ msgid ""
3132
"for stability. In order to maintain this reputation, the developers would "
3233
"like to know of any deficiencies you find in Python."
3334
msgstr ""
34-
"Python は安定性について高い評価を得た、成熟した言語です。この評価を守るために、開発者たちはあなたが見つけた Python "
35-
"の不備を知りたいと思っています。"
35+
"Python は安定性について高い評価を得た、成熟した言語です。この評価を守るため"
36+
"に、開発者たちはあなたが見つけた Python の不備を知りたいと思っています。"
3637

3738
#: ../../bugs.rst:11
3839
msgid ""
3940
"It can be sometimes faster to fix bugs yourself and contribute patches to "
40-
"Python as it streamlines the process and involves less people. Learn how to "
41-
":ref:`contribute <contributing-to-python>`."
41+
"Python as it streamlines the process and involves less people. Learn how to :"
42+
"ref:`contribute <contributing-to-python>`."
4243
msgstr ""
43-
"バグを自分で直して Python にパッチを送る方が、やり取りに無駄が無く関わる人数も少なく済むこともあります。\n"
44+
"バグを自分で直して Python にパッチを送る方が、やり取りに無駄が無く関わる人数"
45+
"も少なく済むこともあります。\n"
4446
"ぜひ :ref:`貢献 <contributing-to-python>` する方法を学んでください。"
4547

4648
#: ../../bugs.rst:16
@@ -53,8 +55,11 @@ msgid ""
5355
"improvement, please submit a bug report on the :ref:`tracker <using-the-"
5456
"tracker>`. If you have a suggestion on how to fix it, include that as well."
5557
msgstr ""
56-
"このドキュメントの不備を発見したとき、または、改善を提案したいときは、問題点を :ref:`tracker <using-the-tracker>` に報告してください。修正方法の案があるならば、それも含めて。\n"
57-
"（訳注: 日本語訳の問題については、 GitHub 上の `Issue Tracker <https://github.com/python-doc-ja/python-doc-ja/issues>`_ で報告をお願いします。）"
58+
"このドキュメントの不備を発見したとき、または、改善を提案したいときは、問題点"
59+
"を :ref:`tracker <using-the-tracker>` に報告してください。修正方法の案がある"
60+
"ならば、それも含めて。\n"
61+
"（訳注: 日本語訳の問題については、 GitHub 上の `Issue Tracker <https://"
62+
"github.com/python-doc-ja/python-doc-ja/issues>`_ で報告をお願いします。）"
5863

5964
#: ../../bugs.rst:22
6065
msgid ""
@@ -63,7 +68,9 @@ msgid ""
6368
"'docs@' is a mailing list run by volunteers; your request will be noticed, "
6469
"though it may take a while to be processed."
6570
msgstr ""
66-
"時間がない場合、ドキュメントの問題を docs@python.org 宛て、メールで報告することもできます。 (Python の動作に関するバグ報告は python-list@python.org 宛になります。)\n"
71+
"時間がない場合、ドキュメントの問題を docs@python.org 宛て、メールで報告するこ"
72+
"ともできます。 (Python の動作に関するバグ報告は python-list@python.org 宛にな"
73+
"ります。)\n"
6774
"'docs@' はボランティアで運営されているメーリングリストです。\n"
6875
"報告が伝わっていても、対応への時間がかかることもあります。"
6976

@@ -86,119 +93,143 @@ msgid ""
8693
"Overview of the process involved in reporting an improvement on the tracker."
8794
msgstr "issue tracker への改善報告に関する作業過程の概観。"
8895

89-
#: ../../bugs.rst:35
96+
#: ../../bugs.rst:36
9097
msgid ""
91-
"`Helping with Documentation <https://devguide.python.org/docquality"
92-
"/#helping-with-documentation>`_"
98+
"`Helping with Documentation <https://devguide.python.org/docquality/#helping-"
99+
"with-documentation>`_"
93100
msgstr ""
94-
"`Helping with Documentation <https://devguide.python.org/docquality"
95-
"/#helping-with-documentation>`_"
101+
"`Helping with Documentation <https://devguide.python.org/docquality/#helping-"
102+
"with-documentation>`_"
96103

97104
#: ../../bugs.rst:36
98105
msgid ""
99106
"Comprehensive guide for individuals that are interested in contributing to "
100107
"Python documentation."
101108
msgstr "Python ドキュメントへの貢献に興味がある個人へ向けた包括的なガイド。"
102109

103-
#: ../../bugs.rst:41
110+
#: ../../bugs.rst:38
111+
msgid ""
112+
"`Documentation Translations <https://devguide.python.org/documenting/"
113+
"#translating>`_"
114+
msgstr "`Documenting Python <https://devguide.python.org/documenting/>`__"
115+
116+
#: ../../bugs.rst:39
117+
msgid ""
118+
"A list of GitHub pages for documentation translation and their primary "
119+
"contacts."
120+
msgstr ""
121+
122+
#: ../../bugs.rst:45
104123
msgid "Using the Python issue tracker"
105124
msgstr "Python の課題管理システムを使う"
106125

107-
#: ../../bugs.rst:43
126+
#: ../../bugs.rst:47
108127
msgid ""
109-
"Bug reports for Python itself should be submitted via the Python Bug Tracker"
110-
" (https://bugs.python.org/). The bug tracker offers a web form which allows"
111-
" pertinent information to be entered and submitted to the developers."
128+
"Issue reports for Python itself should be submitted via the GitHub issues "
129+
"tracker (https://github.com/python/cpython/issues). The GitHub issues "
130+
"tracker offers a web form which allows pertinent information to be entered "
131+
"and submitted to the developers."
112132
msgstr ""
113133

114-
#: ../../bugs.rst:47
134+
#: ../../bugs.rst:52
115135
msgid ""
116136
"The first step in filing a report is to determine whether the problem has "
117137
"already been reported. The advantage in doing so, aside from saving the "
118-
"developers time, is that you learn what has been done to fix it; it may be "
138+
"developers' time, is that you learn what has been done to fix it; it may be "
119139
"that the problem has already been fixed for the next release, or additional "
120140
"information is needed (in which case you are welcome to provide it if you "
121-
"can!). To do this, search the bug database using the search box on the top "
122-
"of the page."
123-
msgstr ""
124-
"報告ではまず、その問題が既に報告済みかどうかを判断してください。そうすることで、開発者の時間を節約できるほか、問題解決に係る経緯を知ることができます。と言うのは、その問題は次のリリースでは解決済みとなっているか、または、さらに情報を必要としているかもしれません。 (そういったとき、可能なら是非、提供をお願いします！)\n"
125-
"判断するには、ページ先頭の検索ボックスでバグデータベースを検索してください。"
126-
127-
#: ../../bugs.rst:54
128-
msgid ""
129-
"If the problem you're reporting is not already in the bug tracker, go back "
130-
"to the Python Bug Tracker and log in. If you don't already have a tracker "
131-
"account, select the \"Register\" link or, if you use OpenID, one of the "
132-
"OpenID provider logos in the sidebar. It is not possible to submit a bug "
133-
"report anonymously."
141+
"can!). To do this, search the tracker using the search box at the top of the "
142+
"page."
134143
msgstr ""
135-
"問題がまだバグトラッカーに登録されていない場合は、Python Bug Tracker "
136-
"のトップページに戻ってログインしてください。まだトラッカーのアカウントをもっていない場合は、サイドバーの \"Register\" "
137-
"リンクを選んでください。また、OpenID を使っている場合はサイドバーの OpenID "
138-
"プロバイダのロゴをクリックしてください。匿名での問題報告はできません。"
139144

140145
#: ../../bugs.rst:59
141146
msgid ""
142-
"Being now logged in, you can submit a bug. Select the \"Create New\" link "
143-
"in the sidebar to open the bug reporting form."
144-
msgstr "ログインできたら、バグを登録できます。サイドバーの \"Create New\" リンクからバグ報告フォームを開きます。"
147+
"If the problem you're reporting is not already in the list, log in to "
148+
"GitHub. If you don't already have a GitHub account, create a new account "
149+
"using the \"Sign up\" link. It is not possible to submit a bug report "
150+
"anonymously."
151+
msgstr ""
145152

146-
#: ../../bugs.rst:62
153+
#: ../../bugs.rst:64
147154
msgid ""
148-
"The submission form has a number of fields. For the \"Title\" field, enter "
149-
"a *very* short description of the problem; less than ten words is good. In "
150-
"the \"Type\" field, select the type of your problem; also select the "
151-
"\"Component\" and \"Versions\" to which the bug relates."
155+
"Being now logged in, you can submit an issue. Click on the \"New issue\" "
156+
"button in the top bar to report a new issue."
152157
msgstr ""
153-
"バグ報告フォームには幾つかのフィールドがあります。\"Title\" フィールドには、問題の説明を *非常に* "
154-
"簡潔に書いてください。10語以下くらいが目安です。\"Type\" フィールドでは、問題の種類を選択してください。バグに関係する "
155-
"\"Component\" と \"Versions\" も選択してください。"
156158

157159
#: ../../bugs.rst:67
160+
msgid "The submission form has two fields, \"Title\" and \"Comment\"."
161+
msgstr ""
162+
163+
#: ../../bugs.rst:69
158164
msgid ""
159-
"In the \"Comment\" field, describe the problem in detail, including what you"
160-
" expected to happen and what did happen. Be sure to include whether any "
161-
"extension modules were involved, and what hardware and software platform you"
162-
" were using (including version information as appropriate)."
165+
"For the \"Title\" field, enter a *very* short description of the problem; "
166+
"less than ten words is good."
163167
msgstr ""
164-
"\"Comment\" "
165-
"フィールドで、あなたが期待した結果と実際の結果も含め、問題の詳細を説明してください。拡張モジュールが関与しているかどうかと、使用しているハードウェアとソフトウェアプラットフォームも"
166-
" (必要に応じてバージョン情報も) 必ず報告に含めてください。"
167168

168169
#: ../../bugs.rst:72
169170
msgid ""
170-
"Each bug report will be assigned to a developer who will determine what "
171-
"needs to be done to correct the problem. You will receive an update each "
172-
"time action is taken on the bug."
171+
"In the \"Comment\" field, describe the problem in detail, including what you "
172+
"expected to happen and what did happen. Be sure to include whether any "
173+
"extension modules were involved, and what hardware and software platform you "
174+
"were using (including version information as appropriate)."
173175
msgstr ""
174-
"各バグ報告は開発者に割り当てられ、その問題を解決するのに何が必要かが決定されます。そのバグ報告に対して何かアクションがあるたびに、更新情報があなたに届きます。"
176+
"\"Comment\" フィールドで、あなたが期待した結果と実際の結果も含め、問題の詳細"
177+
"を説明してください。拡張モジュールが関与しているかどうかと、使用しているハー"
178+
"ドウェアとソフトウェアプラットフォームも (必要に応じてバージョン情報も) 必ず"
179+
"報告に含めてください。"
175180

176-
#: ../../bugs.rst:80
181+
#: ../../bugs.rst:77
177182
msgid ""
178-
"`How to Report Bugs Effectively "
179-
"<https://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_"
183+
"Each issue report will be reviewed by a developer who will determine what "
184+
"needs to be done to correct the problem. You will receive an update each "
185+
"time an action is taken on the issue."
180186
msgstr ""
181-
"`How to Report Bugs Effectively "
182-
"<https://www.chiark.greenend.org.uk/~sgtatham/bugs.html>`_"
183187

184-
#: ../../bugs.rst:80
188+
#: ../../bugs.rst:86
185189
msgid ""
186-
"Article which goes into some detail about how to create a useful bug report."
187-
" This describes what kind of information is useful and why it is useful."
188-
msgstr "有益なバグ報告について詳しく説明した記事です。どんな情報が、なぜ有益なのかを説明しています。"
190+
"`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/"
191+
"~sgtatham/bugs.html>`_"
192+
msgstr ""
193+
"`How to Report Bugs Effectively <https://www.chiark.greenend.org.uk/"
194+
"~sgtatham/bugs.html>`_"
189195

190-
#: ../../bugs.rst:86
196+
#: ../../bugs.rst:85
197+
msgid ""
198+
"Article which goes into some detail about how to create a useful bug report. "
199+
"This describes what kind of information is useful and why it is useful."
200+
msgstr ""
201+
"有益なバグ報告について詳しく説明した記事です。どんな情報が、なぜ有益なのかを"
202+
"説明しています。"
203+
204+
#: ../../bugs.rst:89
205+
msgid ""
206+
"`Bug Writing Guidelines <https://bugzilla.mozilla.org/page.cgi?id=bug-"
207+
"writing.html>`_"
208+
msgstr ""
209+
"`Bug Writing Guidelines <http://developer.mozilla.org/en/docs/"
210+
"Bug_writing_guidelines>`_"
211+
212+
#: ../../bugs.rst:89
213+
msgid ""
214+
"Information about writing a good bug report. Some of this is specific to "
215+
"the Mozilla project, but describes general good practices."
216+
msgstr ""
217+
"良いバグ報告を書くための情報です。この情報の一部はMozillaプロジェクト独自のも"
218+
"のですが、一般的に良い習慣を解説しています。"
219+
220+
#: ../../bugs.rst:95
191221
msgid "Getting started contributing to Python yourself"
192222
msgstr "Python への貢献をはじめる"
193223

194-
#: ../../bugs.rst:88
224+
#: ../../bugs.rst:97
195225
msgid ""
196226
"Beyond just reporting bugs that you find, you are also welcome to submit "
197227
"patches to fix them. You can find more information on how to get started "
198228
"patching Python in the `Python Developer's Guide`_. If you have questions, "
199229
"the `core-mentorship mailing list`_ is a friendly place to get answers to "
200230
"any and all questions pertaining to the process of fixing issues in Python."
201231
msgstr ""
202-
"見つけたバグの報告だけでなく、修正パッチの提出も歓迎します。`Python Developer's Guide`_ には Python "
203-
"へのパッチの始め方について詳しい情報があります。疑問があれば、`core-mentorship mailing list`_ は Python "
204-
"の問題解決の過程に関するありとあらゆる疑問への答えを得ることが出来るフレンドリーな場所です。"
232+
"見つけたバグの報告だけでなく、修正パッチの提出も歓迎します。`Python "
233+
"Developer's Guide`_ には Python へのパッチの始め方について詳しい情報がありま"
234+
"す。疑問があれば、`core-mentorship mailing list`_ は Python の問題解決の過程"
235+
"に関するありとあらゆる疑問への答えを得ることが出来るフレンドリーな場所です。"

‎c-api/abstract.po

Lines changed: 19 additions & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -1,20 +1,21 @@
11
# SOME DESCRIPTIVE TITLE.
2-
# Copyright (C) 2001-2021, Python Software Foundation
2+
# Copyright (C) 2001-2022, Python Software Foundation
33
# This file is distributed under the same license as the Python package.
44
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
5-
#
5+
#
66
# Translators:
7-
# tomo, 2021
8-
#
7+
# Rafael Fontenelle <rffontenelle@gmail.com>, 2022
8+
#
99
#, fuzzy
1010
msgid ""
1111
msgstr ""
1212
"Project-Id-Version: Python 3.10\n"
1313
"Report-Msgid-Bugs-To: \n"
14-
"POT-Creation-Date: 2021-06-29 12:56+0000\n"
15-
"PO-Revision-Date: 2021-06-28 00:47+0000\n"
16-
"Last-Translator: tomo, 2021\n"
17-
"Language-Team: Japanese (https://www.transifex.com/python-doc/teams/5390/ja/)\n"
14+
"POT-Creation-Date: 2022-12-30 14:59+0000\n"
15+
"PO-Revision-Date: 2022-11-05 17:21+0000\n"
16+
"Last-Translator: Rafael Fontenelle <rffontenelle@gmail.com>, 2022\n"
17+
"Language-Team: Japanese (https://www.transifex.com/python-doc/teams/5390/"
18+
"ja/)\n"
1819
"MIME-Version: 1.0\n"
1920
"Content-Type: text/plain; charset=UTF-8\n"
2021
"Content-Transfer-Encoding: 8bit\n"
@@ -32,15 +33,18 @@ msgid ""
3233
"or all sequence types). When used on object types for which they do not "
3334
"apply, they will raise a Python exception."
3435
msgstr ""
35-
"この章で説明する関数は、オブジェクトの型に依存しないような Python オブジェクトの操作や、(数値型全て、シーケンス型全てといった) "
36-
"大まかな型のオブジェクトに対する操作を行ないます。関数を適用対象でないオブジェクトに対して使った場合、Python の例外が送出されることになります。"
36+
"この章で説明する関数は、オブジェクトの型に依存しないような Python オブジェク"
37+
"トの操作や、(数値型全て、シーケンス型全てといった) 大まかな型のオブジェクトに"
38+
"対する操作を行ないます。関数を適用対象でないオブジェクトに対して使った場合、"
39+
"Python の例外が送出されることになります。"
3740

3841
#: ../../c-api/abstract.rst:14
3942
msgid ""
4043
"It is not possible to use these functions on objects that are not properly "
41-
"initialized, such as a list object that has been created by "
42-
":c:func:`PyList_New`, but whose items have not been set to some non-\\ "
43-
"``NULL`` value yet."
44+
"initialized, such as a list object that has been created by :c:func:"
45+
"`PyList_New`, but whose items have not been set to some non-\\ ``NULL`` "
46+
"value yet."
4447
msgstr ""
45-
"これらの関数は、 :c:func:`PyList_New` で作成された後に ``NULL`` "
46-
"以外の値を設定されていないリストのような、適切に初期化されていないオブジェクトに対して使うことはできません。"
48+
"これらの関数は、 :c:func:`PyList_New` で作成された後に ``NULL`` 以外の値を設"
49+
"定されていないリストのような、適切に初期化されていないオブジェクトに対して使"
50+
"うことはできません。"

0 commit comments

Comments
 (0)