From 16a1689ddb2e3e2734b8f5b63b4a15fe0849531e Mon Sep 17 00:00:00 2001 From: Tetsuo Koyama Date: Tue, 25 Aug 2026 07:48:06 +0900 Subject: [PATCH] docs: update Japanese translations for po files - CONTRIBUTING.po: +2 new strings - TRANSLATING.po: +22, -13 strings - maintain-automate.po: +29 new strings - package-structure-code.po: +55, -3 strings --- locales/ja/LC_MESSAGES/CONTRIBUTING.po | 163 +++--- locales/ja/LC_MESSAGES/TRANSLATING.po | 365 +++++++----- locales/ja/LC_MESSAGES/maintain-automate.po | 203 ++++++- .../ja/LC_MESSAGES/package-structure-code.po | 520 +++++++++++++++--- 4 files changed, 948 insertions(+), 303 deletions(-) diff --git a/locales/ja/LC_MESSAGES/CONTRIBUTING.po b/locales/ja/LC_MESSAGES/CONTRIBUTING.po index 2dc634003..2118c8d50 100644 --- a/locales/ja/LC_MESSAGES/CONTRIBUTING.po +++ b/locales/ja/LC_MESSAGES/CONTRIBUTING.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-01-04 09:59+0900\n" +"POT-Creation-Date: 2026-08-25 07:47+0900\n" "PO-Revision-Date: 2025-04-14 18:12+0000\n" "Last-Translator: Tetsuo Koyama , 2025\n" "Language: ja\n" @@ -21,7 +21,7 @@ msgstr "" "MIME-Version: 1.0\n" "Content-Type: text/plain; charset=utf-8\n" "Content-Transfer-Encoding: 8bit\n" -"Generated-By: Babel 2.17.0\n" +"Generated-By: Babel 2.18.0\n" #: ../../CONTRIBUTING.md:4 msgid "Contributing to the Python Packaging Guide" @@ -352,38 +352,52 @@ msgid "" msgstr "開発依存関係をインストールするには、ターミナルで以下のコマンドを実行します:" #: ../../CONTRIBUTING.md:156 +msgid "" +"The quotes around `'.[dev]'` matter if you use zsh, the default shell on " +"macOS. Without them, zsh treats the square brackets as a filename pattern" +" and fails with `no matches found`." +msgstr "" + +#: ../../CONTRIBUTING.md:158 +msgid "" +"On Windows they are harmless in PowerShell, but if you use the older " +"`cmd.exe` prompt you need to remove them and run `python -m pip install " +"-e .[dev]` instead, because `cmd.exe` does not strip single quotes." +msgstr "" + +#: ../../CONTRIBUTING.md:160 msgid "Commit your changes" msgstr "変更をコミットする" -#: ../../CONTRIBUTING.md:158 +#: ../../CONTRIBUTING.md:162 msgid "" "After making your changes, you need to commit them to your local " "repository. To do this, run the following commands in your terminal:" msgstr "変更を加えたら、ローカルリポジトリにコミットする必要があります。 これを行うには、ターミナルで以下のコマンドを実行します:" -#: ../../CONTRIBUTING.md:160 +#: ../../CONTRIBUTING.md:164 msgid "To see the changes you made:" msgstr "変更を確認するには:" -#: ../../CONTRIBUTING.md:164 +#: ../../CONTRIBUTING.md:168 msgid "To add the changes to the staging area:" msgstr "変更をステージングエリアに追加するには:" -#: ../../CONTRIBUTING.md:168 +#: ../../CONTRIBUTING.md:172 msgid "To commit the changes:" msgstr "変更をコミットするには:" -#: ../../CONTRIBUTING.md:172 +#: ../../CONTRIBUTING.md:176 msgid "" "Replace `\"Your commit message here\"` with a clear and concise message " "that describes the changes you made." msgstr "`\"Your commit message here\"` を、あなたが行った変更を説明する明確で簡潔なメッセージに置き換えてください。" -#: ../../CONTRIBUTING.md:174 +#: ../../CONTRIBUTING.md:178 msgid "How to build the guide locally" msgstr "ローカルでのガイドのビルド方法" -#: ../../CONTRIBUTING.md:176 +#: ../../CONTRIBUTING.md:180 msgid "" "To build the guide locally, you can use the `nox` command. This will run " "the default `nox` session, which builds the guide and opens it in your " @@ -392,13 +406,13 @@ msgstr "" "ガイドをローカルにビルドするには、`nox`コマンドを使うことができます。これはデフォルトの `nox` " "セッションを実行し、ガイドをビルドしてブラウザで開きます。" -#: ../../CONTRIBUTING.md:178 +#: ../../CONTRIBUTING.md:182 msgid "" "To see the different sessions available, you can run the following " "command in your terminal:" msgstr "利用可能なさまざまなセッションを確認するには、ターミナルで次のコマンドを実行します:" -#: ../../CONTRIBUTING.md:183 +#: ../../CONTRIBUTING.md:187 msgid "" "There are different sessions in nox related to building the docs: `docs`," " `docs-test`, `docs-live`. You can run them by specifying the session " @@ -407,59 +421,59 @@ msgstr "" "noxには、ドキュメントの作成に関連するさまざまなセッションがあります: `docs`, `docs-test`, `docs-live` 。 " "`nox` コマンドの後にセッション名を指定して実行することができます。" -#: ../../CONTRIBUTING.md:185 +#: ../../CONTRIBUTING.md:189 msgid "`docs`: this session builds the guide and opens it in your browser." msgstr "`docs`: このセッションでガイドを作成し、ブラウザで開きます。" -#: ../../CONTRIBUTING.md:189 +#: ../../CONTRIBUTING.md:193 msgid "" "To see the guide built locally, open the file `_build/html/index.html` in" " your browser." msgstr "ローカルに構築されたガイドを見るには、ブラウザで `_build/html/index.html` ファイルを開いてください。" -#: ../../CONTRIBUTING.md:191 +#: ../../CONTRIBUTING.md:195 msgid "`docs-linkcheck`: this session checks that links in documentation work" msgstr "`docs-linkcheck`: このセッションでドキュメント内のリンクが正常に機能するか確認します。" -#: ../../CONTRIBUTING.md:195 +#: ../../CONTRIBUTING.md:199 msgid "" "If the tests fail, you will see logs in the terminal and in " "`_build/linkcheck_output/output.txt`." msgstr "テストが失敗した場合はターミナル及び`_build/linkcheck_output/output.txt`.にログが表示されます" -#: ../../CONTRIBUTING.md:197 +#: ../../CONTRIBUTING.md:201 msgid "`docs-test`: this session runs the tests for the guide." msgstr "`docs-test`: このセッションでは、ガイドのテストを実行します。" -#: ../../CONTRIBUTING.md:201 +#: ../../CONTRIBUTING.md:205 msgid "" "If the tests fail, you will see an error message in your terminal. You " "need to fix the errors before submitting your pull request." msgstr "テストが失敗すると、ターミナルにエラーメッセージが表示されます。 プルリクエストを提出する前にエラーを修正する必要があります。" -#: ../../CONTRIBUTING.md:203 +#: ../../CONTRIBUTING.md:207 msgid "" "`docs-live`: this session builds the guide and opens it in your browser " "with live reloading." msgstr "`docs-live`: このセッションでガイドを作成し、ライブリローディングしてブラウザで開きます。" -#: ../../CONTRIBUTING.md:207 +#: ../../CONTRIBUTING.md:211 msgid "" "open the local version of the guide in your browser at ``localhost`` " "shown in the terminal." msgstr "ターミナルに表示されている ``localhost`` のブラウザでローカル版のガイドを開いてください。" -#: ../../CONTRIBUTING.md:209 +#: ../../CONTRIBUTING.md:213 msgid "Before you submit your pull request" msgstr "プルリクエストを提出する前に" -#: ../../CONTRIBUTING.md:211 +#: ../../CONTRIBUTING.md:215 msgid "" "Before submitting your pull request, make sure to run the tests and check" " the formatting of your code." msgstr "プルリクエストを提出する前に、必ずテストを実行し、コードのフォーマットをチェックしてください。" -#: ../../CONTRIBUTING.md:216 +#: ../../CONTRIBUTING.md:220 msgid "" "If the tests fail, you will see an error message in your terminal. You " "need to fix the errors before submitting your pull request. Also make " @@ -469,62 +483,62 @@ msgstr "" "テストに失敗すると、ターミナルにエラーメッセージが表示されます。 プルリクエストを提出する前にエラーを修正する必要があります。 " "また、ドキュメントをローカルでビルドし、変更が正しく見えるかどうかをチェックすることで、ドキュメントのフォーマットを確認してください。" -#: ../../CONTRIBUTING.md:220 +#: ../../CONTRIBUTING.md:224 msgid "Submitting a pull request with your contribution" msgstr "あなたの貢献のプルリクエストを投稿する" -#: ../../CONTRIBUTING.md:222 +#: ../../CONTRIBUTING.md:226 msgid "How to make a pull request" msgstr "プルリクエストの作り方" -#: ../../CONTRIBUTING.md:224 +#: ../../CONTRIBUTING.md:228 msgid "" "To open a pull request on GitHub, navigate to the main page of your " "forked repository and click on the \"Pull requests\" tab." msgstr "GitHubでプルリクエストを開くには、フォークしたリポジトリのメインページに移動し、 \"Pull requests\" タブをクリックします。" -#: ../../CONTRIBUTING.md:226 +#: ../../CONTRIBUTING.md:230 msgid "Pull requests tab in GitHub" msgstr "GitHubのPull requestsタブ" -#: ../../CONTRIBUTING.md:232 +#: ../../CONTRIBUTING.md:236 msgid "" "An image showing how to navigate to the pull requests tab in GitHub. The " "pull requests tab is highlighted with a red rectangle." msgstr "GitHubのプルリクエストタブへの移動方法を示す画像です。プルリクエストタブは赤い四角で強調表示されます。" -#: ../../CONTRIBUTING.md:235 +#: ../../CONTRIBUTING.md:239 msgid "Click on the \"New pull request\" button." msgstr "\"New pull request\" ボタンをクリックします。" -#: ../../CONTRIBUTING.md:237 +#: ../../CONTRIBUTING.md:241 msgid "New pull request button in GitHub" msgstr "GitHubの新しいプルリクエストボタン" -#: ../../CONTRIBUTING.md:243 +#: ../../CONTRIBUTING.md:247 msgid "" "An image showing how to create a new pull request in GitHub. The new pull" " request button is highlighted with a red rectangle." msgstr "GitHubで新しいプルリクエストを作成する方法を示す画像です。 新しいプルリクエストボタンは赤い四角で強調表示されます。" -#: ../../CONTRIBUTING.md:246 +#: ../../CONTRIBUTING.md:250 msgid "" "Write a clear and concise title and description for your pull request. " "Make sure to describe the changes you made and why they are necessary." msgstr "プルリクエストのタイトルと説明を明確かつ簡潔に書きましょう。変更した内容と、それが必要な理由を必ず説明してください。" -#: ../../CONTRIBUTING.md:248 +#: ../../CONTRIBUTING.md:252 msgid "What happens when you submit a pull request (CI/CD)" msgstr "プルリクエストを提出するとどうなるか(CI/CD)" -#: ../../CONTRIBUTING.md:250 +#: ../../CONTRIBUTING.md:254 msgid "" "Once you submit a pull request, a series of checks will be run to ensure " "that your changes do not introduce any bugs or errors. These checks " "include:" msgstr "あなたがプルリクエストを提出すると、あなたの変更がバグやエラーを引き起こさないように、一連のチェックが実行されます。これらのチェックには以下が含まれます:" -#: ../../CONTRIBUTING.md:252 +#: ../../CONTRIBUTING.md:256 msgid "" "**Code formatting and styles**: checks that your code is formatted " "correctly, by `pre-commit.ci - pr check`." @@ -532,21 +546,21 @@ msgstr "" "**コードのフォーマットとスタイル**: は、あなたのコードが `pre-commit.ci - pr check` " "によって正しくフォーマットされているかをチェックします。" -#: ../../CONTRIBUTING.md:253 +#: ../../CONTRIBUTING.md:257 msgid "" "**docs build**: checks that the documentation builds correctly, using " "`circleci`." msgstr "**ドキュメントビルド**: は、 `circleci` を使用して、ドキュメントが正しくビルドされることをチェックします。" -#: ../../CONTRIBUTING.md:255 +#: ../../CONTRIBUTING.md:259 msgid "You will see the status of these checks in your pull request." msgstr "プルリクエストには、これらのチェックのステータスが表示されます。" -#: ../../CONTRIBUTING.md:257 +#: ../../CONTRIBUTING.md:261 msgid "Pull request checks in GitHub" msgstr "GitHubでのプルリクエストチェック" -#: ../../CONTRIBUTING.md:263 +#: ../../CONTRIBUTING.md:267 msgid "" "An image showing the status of the checks in a pull request in GitHub. " "The checks are displayed in a table with a status icon next to each " @@ -555,17 +569,17 @@ msgstr "" "GitHubのプルリクエストのチェック状況を示す画像です。チェックは表で表示され、各チェックの横にステータスアイコンが表示されます。 " "チェックは赤い四角で強調表示されます。" -#: ../../CONTRIBUTING.md:265 +#: ../../CONTRIBUTING.md:269 msgid "" "If any of these checks fail, you will see an error message in your pull " "request. You need to fix the errors before your changes can be merged." msgstr "これらのチェックのいずれかが失敗した場合、プルリクエストにエラーメッセージが表示されます。変更をマージする前に、エラーを修正する必要があります。" -#: ../../CONTRIBUTING.md:267 +#: ../../CONTRIBUTING.md:271 msgid "Pull request checks failed in GitHub" msgstr "GitHubでのプルリクエストチェックに失敗" -#: ../../CONTRIBUTING.md:273 +#: ../../CONTRIBUTING.md:277 msgid "" "An image showing the status of the checks in a pull request in GitHub. " "The checks are displayed in a table with a status icon next to each " @@ -575,62 +589,62 @@ msgstr "" "GitHubのプルリクエストのチェック状況を示す画像です。チェックは表で表示され、各チェックの横にステータスアイコンが表示されます。 " "失敗と詳細リンクのチェックは赤い四角で強調表示されます。" -#: ../../CONTRIBUTING.md:276 +#: ../../CONTRIBUTING.md:280 msgid "" "To get more information about the errors, you can click on the " "\"Details\" link next to the failed check." msgstr "エラーに関する詳細情報を得るには、失敗したチェックの隣にある \"Details\" リンクをクリックすることができます。" -#: ../../CONTRIBUTING.md:278 +#: ../../CONTRIBUTING.md:282 msgid "What to expect from the review process" msgstr "レビュープロセスに期待すること" -#: ../../CONTRIBUTING.md:280 +#: ../../CONTRIBUTING.md:284 msgid "" "Once you submit a pull request, a maintainer of the repository will " "review your changes and provide feedback. The review process may involve:" msgstr "プルリクエストを提出すると、リポジトリのメンテナがあなたの変更を確認し、フィードバックを提供します。審査プロセスには以下が含まれます:" -#: ../../CONTRIBUTING.md:282 +#: ../../CONTRIBUTING.md:286 msgid "" "**Comments**: the reviewer may leave comments on your pull request to ask" " questions or provide feedback." msgstr "**Comments**: レビュアーはあなたのプルリクエストにコメントを残し、質問やフィードバックをすることができます。" -#: ../../CONTRIBUTING.md:283 +#: ../../CONTRIBUTING.md:287 msgid "" "**Suggestions**: the reviewer may suggest changes to your code or " "documentation." msgstr "**Suggestions**: レビューワーは、あなたのコードや文書の変更を提案するかもしれません。" -#: ../../CONTRIBUTING.md:284 +#: ../../CONTRIBUTING.md:288 msgid "" "**Approvals**: once the reviewer is satisfied with your changes, they " "will approve the pull request." msgstr "**Approvals**: レビュアーがあなたの変更に満足したら、プルリクエストを承認します。" -#: ../../CONTRIBUTING.md:286 +#: ../../CONTRIBUTING.md:290 msgid "" "You can make changes to your pull request by pushing new commits to the " "branch. The pull request will be updated automatically with your new " "changes." msgstr "新しいコミットをブランチにプッシュすることで、プルリクエストに変更を加えることができます。プルリクエストはあなたの新しい変更で自動的に更新されます。" -#: ../../CONTRIBUTING.md:288 +#: ../../CONTRIBUTING.md:292 msgid "" "Once your pull request is approved, it will be merged into the main " "branch and your changes will be included in the guide." msgstr "あなたのプルリクエストが承認されると、メインブランチにマージされ、あなたの変更がガイドに含まれます。" -#: ../../CONTRIBUTING.md:290 +#: ../../CONTRIBUTING.md:294 msgid "Additional help" msgstr "追加ヘルプ" -#: ../../CONTRIBUTING.md:292 +#: ../../CONTRIBUTING.md:296 msgid "How to get help" msgstr "助けを求めるには" -#: ../../CONTRIBUTING.md:294 +#: ../../CONTRIBUTING.md:298 msgid "" "*__TODO__: This section should describe the options for finding more help" " in case beginner contributors need more help (e.g., create an issue, " @@ -639,25 +653,25 @@ msgstr "" "*__TODO__: このセクションには、初心者の投稿者がさらに助けを必要とする場合に備えて、より多くの助けを見つけるためのオプション " "(イシューの作成、フォーラムへの投稿など) を記述してください。*" -#: ../../CONTRIBUTING.md:296 +#: ../../CONTRIBUTING.md:300 msgid "Additional resources" msgstr "その他のリソース" -#: ../../CONTRIBUTING.md:298 +#: ../../CONTRIBUTING.md:302 msgid "" "*__TODO__: It should also include links to beginner documentation, like " "the GitHub docs.*" msgstr "*__TODO__: また、GitHubのドキュメントのような初心者向けのドキュメントへのリンクも含める必要があります。*" -#: ../../CONTRIBUTING.md:300 +#: ../../CONTRIBUTING.md:304 msgid "Annex" msgstr "書き添える" -#: ../../CONTRIBUTING.md:302 +#: ../../CONTRIBUTING.md:306 msgid "Code examples" msgstr "コード例" -#: ../../CONTRIBUTING.md:304 +#: ../../CONTRIBUTING.md:308 msgid "" "This guide uses the [literalinclude Sphinx directive](https://www.sphinx-" "doc.org/en/master/usage/restructuredtext/directives.html#directive-" @@ -669,11 +683,11 @@ msgstr "" "literalinclude) を使用して、コードと散文を分けています。 ドキュメントで使用するコードは `examples/` " "フォルダにあります。" -#: ../../CONTRIBUTING.md:308 +#: ../../CONTRIBUTING.md:312 msgid "Referencing code in documentation" msgstr "ドキュメントでコードを参照する" -#: ../../CONTRIBUTING.md:310 +#: ../../CONTRIBUTING.md:314 msgid "" "If an example is present elsewhere in the documentation that you want to " "use, you can copy the `literalinclude` directive verbatim and the " @@ -682,7 +696,7 @@ msgstr "" "使用したい例がドキュメントの他の場所にある場合、 `literalinclude` " "ディレクティブをそのままコピーすれば、例は同期されたままになります。" -#: ../../CONTRIBUTING.md:313 +#: ../../CONTRIBUTING.md:317 msgid "" "If you already see code in the examples folder that you can use for new " "documentation, a new `literalinclude` can be made to extract it into the " @@ -696,7 +710,7 @@ msgstr "" "に必要なのはコードへの相対パスだけですが、ほとんどの場合 `:language:` と `:lines:` も指定する必要があります。 " "前者はコード例をより美しくし、後者は将来的なコードの変更からサンプルを守ることができます。" -#: ../../CONTRIBUTING.md:318 +#: ../../CONTRIBUTING.md:322 msgid "" "**Pro tip**: As an alternative to `:lines:` there are also the `:start-" "after:`, `:start-at:`, `:end-before:`, and `:end-at:` options. And if the" @@ -707,7 +721,7 @@ msgstr "" "before:`, `:end-at:` オプションもあります。 また、サンプルコードがPythonの場合、 `:pyobject:` " "を使用すると、コードのリファクタリングがあっても同じドキュメント内容を維持することができます。" -#: ../../CONTRIBUTING.md:322 +#: ../../CONTRIBUTING.md:326 msgid "" "If you need example code that doesn't yet exist in `examples/` see " "[creating code for documentation](#creating-code-for-documentation)." @@ -715,11 +729,11 @@ msgstr "" "`examples/` にまだ存在しないサンプルコードが必要な場合は、 [ドキュメント用のコードを作成する](#creating-code-" "for-documentation) を参照してください。" -#: ../../CONTRIBUTING.md:325 +#: ../../CONTRIBUTING.md:329 msgid "Creating code for documentation" msgstr "ドキュメント用コードの作成" -#: ../../CONTRIBUTING.md:327 +#: ../../CONTRIBUTING.md:331 msgid "" "Whenever you come across a place that could benefit from a code block, " "instead of writing it in-line with a code fence (`` ``` `` blocked text) " @@ -731,7 +745,7 @@ msgstr "" "ブロックテキスト)と一緒にインラインで書く代わりに、独自の形式でファイルとして書くことができます。 あなたの例はすでに存在しているかもしれません;" " [ドキュメントのコードを参照する](#referencing-code-in-documentation) を参照してください。" -#: ../../CONTRIBUTING.md:331 +#: ../../CONTRIBUTING.md:335 msgid "" "If you want to add a new example that doesn't fit into any of the " "existing example files, you can create a new file and reference it in a " @@ -744,7 +758,7 @@ msgstr "" "もしそのファイルが既存のサンプルプロジェクトの中にあるのが理にかなっているのであれば、そこに追加してください。そうでなければ、 " "`examples` ディレクトリに新しいフォルダを作成してください。" -#: ../../CONTRIBUTING.md:335 +#: ../../CONTRIBUTING.md:339 msgid "" "If an existing example is incomplete or a new example makes sense to be " "added to an existing file, go ahead and add it, but take care to not " @@ -756,14 +770,14 @@ msgstr "" "可能な限り、例を書き直すのではなく、拡張してください。 " "例えば、ファイルの最後に新しい関数を追加したり、クラス内の既存のメソッドの後に新しいメソッドを追加したりします。" -#: ../../CONTRIBUTING.md:339 +#: ../../CONTRIBUTING.md:343 msgid "" "Example code is checked for correctness, so adding a new example may " "require adding additional tests for coverage, and will require fixing any" " failing tests." msgstr "例題のコードは正しさをチェックされるので、新しい例題を追加するには、カバレッジのためのテストを追加する必要があるかもしれないし、失敗したテストを修正する必要があるかもしれません。" -#: ../../CONTRIBUTING.md:342 +#: ../../CONTRIBUTING.md:346 msgid "" "***⚠️ WARNING***: great care should be taken when modifying existing " "example code, especially any modification beyond appending to the end of " @@ -778,19 +792,19 @@ msgstr "" "これにより、ガイド内のサンプルはより一貫したものになりますが、ある特定のユースケースのためにサンプルを修正する場合、アクションが遠のく可能性があります。" " もし既存のサンプルを修正することに気づいたら、このコマンドを実行し、新しいビルドでそれらのページをチェックしてみてください。" -#: ../../CONTRIBUTING.md:350 +#: ../../CONTRIBUTING.md:354 msgid "Example:" msgstr "例:" -#: ../../CONTRIBUTING.md:352 +#: ../../CONTRIBUTING.md:356 msgid "Instead of writing example code in markdown like this" msgstr "このようにマークダウンでサンプルコードを書くのではなく" -#: ../../CONTRIBUTING.md:363 +#: ../../CONTRIBUTING.md:367 msgid "The python can be extracted into a `.py` file" msgstr "python は `.py` ファイルに展開することができます。" -#: ../../CONTRIBUTING.md:377 +#: ../../CONTRIBUTING.md:381 msgid "" "As another example, if you only need to show part of a `pyproject.toml`, " "we already have complete project definitions, you need only to find the " @@ -799,10 +813,11 @@ msgstr "" "別の例として、 `pyproject.toml` " "の一部だけを表示する必要がある場合、我々はすでに完全なプロジェクト定義を持っているので、関連する部分を見つけるだけでよいです。" -#: ../../CONTRIBUTING.md:380 +#: ../../CONTRIBUTING.md:384 msgid "Instead of writing this" msgstr "こう書く代わりに" -#: ../../CONTRIBUTING.md:391 +#: ../../CONTRIBUTING.md:395 msgid "an example could be extracted from an existing toml file" msgstr "例は、既存のtomlファイルから抽出することができます" + diff --git a/locales/ja/LC_MESSAGES/TRANSLATING.po b/locales/ja/LC_MESSAGES/TRANSLATING.po index 736ac16de..a2a279613 100644 --- a/locales/ja/LC_MESSAGES/TRANSLATING.po +++ b/locales/ja/LC_MESSAGES/TRANSLATING.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-05-22 12:19-0700\n" +"POT-Creation-Date: 2026-08-25 07:47+0900\n" "PO-Revision-Date: 2025-04-14 18:12+0000\n" "Last-Translator: Tetsuo Koyama , 2025\n" "Language: ja\n" @@ -45,10 +45,17 @@ msgid "Translation Status" msgstr "翻訳ステータス" #: ../../TRANSLATING.md:16 +msgid "" +"The translation status graph updates every time the book is build with " +"translations. You can see the status of the translations by going to " +"[this link](https://www.pyopensci.org/python-package-guide/TRANSLATING)" +msgstr "" + +#: ../../TRANSLATING.md:18 msgid "Overview of the Translation Process" msgstr "翻訳プロセスの概要" -#: ../../TRANSLATING.md:18 +#: ../../TRANSLATING.md:20 msgid "" "The process of adapting software to different languages is called " "internationalization, or i18n for short. Internationalization makes sure " @@ -58,50 +65,50 @@ msgstr "" "ソフトウェアを異なる言語に適応させるプロセスは国際化、略してi18nと呼ばれます。 " "国際化はソースコード、私たちの場合はガイドのオリジナルの英語のソースファイルを修正することなく翻訳が行われるようにします。" -#: ../../TRANSLATING.md:20 +#: ../../TRANSLATING.md:22 msgid "" "Sphinx, the documentation engine we use to build the Python Package " "Guide, has built-in support for internationalization, so the workflow is " "very straightforward." msgstr "Pythonパッケージガイドをビルドするために使っているドキュメントエンジンであるSphinxは、国際化をビルトインでサポートしているので、ワークフローはとても簡単です。" -#: ../../TRANSLATING.md:22 +#: ../../TRANSLATING.md:24 msgid "" "The process of actually translating the guide into different languages is" " called localization, or l10n for short. This is the step you will be " "helping with your contribution." msgstr "ガイドを実際に異なる言語に翻訳するプロセスをローカリゼーション、略してl10nと呼びます。 あなたが貢献するのはこのステップです。" -#: ../../TRANSLATING.md:24 +#: ../../TRANSLATING.md:26 msgid "Here is a quick overview of how the translation process works:" msgstr "ここでは、翻訳プロセスの概要を簡単に説明します:" -#: ../../TRANSLATING.md:26 +#: ../../TRANSLATING.md:28 msgid "" "The guide is originally written in English and stored in a set of " "MarkDown files." msgstr "このガイドはもともと英語で書かれており、MarkDownのファイル群に保存されています。" -#: ../../TRANSLATING.md:27 +#: ../../TRANSLATING.md:29 msgid "" "The source files are processed by Sphinx to generate a set of translation" " files stored in a folder for each target language." msgstr "ソースファイルはSphinxによって処理され、各ターゲット言語のフォルダに格納された翻訳ファイルのセットを生成します。" -#: ../../TRANSLATING.md:28 +#: ../../TRANSLATING.md:30 msgid "" "Contributors (like you!) translate these files into the different " "languages." msgstr "（あなたのような!）貢献者は、これらのファイルをさまざまな言語に翻訳します。" -#: ../../TRANSLATING.md:29 +#: ../../TRANSLATING.md:31 msgid "" "When the guide is built, Sphinx creates a version of the guide in the " "original language (English) and the translated versions for the languages" " defined in the configuration." msgstr "ガイドがビルドされると、Sphinxはオリジナルの言語(英語)と、設定で定義された言語の翻訳版のガイドを作成します。" -#: ../../TRANSLATING.md:32 +#: ../../TRANSLATING.md:34 msgid "" "You don't need to understand the technical details to contribute, but if " "you are interested in learning how Sphinx handles internationalization " @@ -112,47 +119,102 @@ msgstr "" "[ここ](https://www.sphinx-doc.org/en/master/usage/advanced/intl.html) " "に詳しい情報があります。" -#: ../../TRANSLATING.md:35 -msgid "Setting up Your Local Environment" -msgstr "ローカル環境の設定" - #: ../../TRANSLATING.md:37 -msgid "Before you start, you will need to set up your local work environment." -msgstr "作業を始める前に、ローカルの作業環境を設定する必要があります。" +#, fuzzy +msgid "Two Ways to Contribute a Translation" +msgstr "翻訳作業" #: ../../TRANSLATING.md:39 msgid "" -"First, fork the guide repository into your personal GitHub account and " -"clone the forked repository to your local computer." -msgstr "まず、ガイドリポジトリを個人のGitHubアカウントにフォークし、フォークしたリポジトリをローカルコンピューターにクローンします。" +"There are two ways to contribute a translation, and the first one does " +"not require you to install anything on your computer." +msgstr "" #: ../../TRANSLATING.md:41 msgid "" -"To create a virtual environment and install the development dependencies " -"for the guide, run the following commands:" -msgstr "仮想環境を作成し、ガイドの開発依存関係をインストールするには、以下のコマンドを実行します:" +"**From the GitHub website.** Translation files are plain text, so you can" +" edit them right in your browser. Fork the repository, edit a `.po` file " +"in your fork, and open a pull request. This is the best place to start if" +" this is your first open source contribution. The contributing guide " +"walks through the browser workflow in [Contributing via the GitHub " +"website](CONTRIBUTING.md#contributing-via-the-github-website). Once you " +"have a fork, you can skip ahead to [Editing the Translation Files" +"](#editing-the-translation-files)." +msgstr "" + +#: ../../TRANSLATING.md:43 +msgid "" +"**From a local copy on your computer.** This takes more setup, but it " +"lets you check how much of a file is translated with `sphinx-intl stat` " +"and preview the translated guide in your browser before you open a pull " +"request. Choose this if you plan to translate a lot of strings or want to" +" see your work in context." +msgstr "" + +#: ../../TRANSLATING.md:45 +msgid "Setting up Your Local Environment" +msgstr "ローカル環境の設定" + +#: ../../TRANSLATING.md:47 +msgid "You only need this if you chose the second approach above." +msgstr "" -#: ../../TRANSLATING.md:50 +#: ../../TRANSLATING.md:49 msgid "" -"TODO: This section needs more work or to be replaced with a reference to " -"the CONTRIBUTING guide." -msgstr "TODO: このセクションは、より多くの作業が必要か、CONTRIBUTINGガイドへの参照に置き換える必要があります。" +"Setting up to translate is no different from setting up to contribute " +"anything else to the guide, so rather than repeat the steps here, follow " +"these sections of the contributing guide in order:" +msgstr "" + +#: ../../TRANSLATING.md:51 +msgid "[Forking the repository](CONTRIBUTING.md#forking-the-repository)" +msgstr "" #: ../../TRANSLATING.md:52 +msgid "" +"[Clone your forked repository](CONTRIBUTING.md#clone-your-forked-" +"repository)" +msgstr "" + +#: ../../TRANSLATING.md:53 +msgid "[Create a new branch](CONTRIBUTING.md#create-a-new-branch)" +msgstr "" + +#: ../../TRANSLATING.md:54 +msgid "" +"[Create a virtual environment](CONTRIBUTING.md#create-a-virtual-" +"environment), which gives the commands for both Windows and macOS/Linux" +msgstr "" + +#: ../../TRANSLATING.md:55 +msgid "" +"[Install the development dependencies](CONTRIBUTING.md#install-the-" +"development-dependencies)" +msgstr "" + +#: ../../TRANSLATING.md:58 +msgid "" +"Installing the development dependencies is what makes `sphinx-intl` and " +"`nox` available in your environment. Both are used later in this guide: " +"`sphinx-intl` reports how much of each file has been translated, and " +"`nox` builds the guide so you can preview your work." +msgstr "" + +#: ../../TRANSLATING.md:61 msgid "Starting a New Language Translation" msgstr "新しい言語の翻訳を始める" -#: ../../TRANSLATING.md:54 +#: ../../TRANSLATING.md:63 msgid "" "If you plan to work on an existing translation, you can skip this step " "and go directly to the next section." msgstr "既存の翻訳に手を加える場合は、このステップを飛ばして直接次のセクションに進んでください。" -#: ../../TRANSLATING.md:56 ../../TRANSLATING.md:222 +#: ../../TRANSLATING.md:65 ../../TRANSLATING.md:231 msgid "Important" msgstr "重要" -#: ../../TRANSLATING.md:57 +#: ../../TRANSLATING.md:66 msgid "" "If you would like to start the translation of the guide into a new " "language, start by [creating an issue](https://github.com/pyOpenSci" @@ -161,28 +223,30 @@ msgstr "" "新しい言語へのガイドの翻訳を開始したい場合は、リポジトリに [issueを作成する](https://github.com/pyOpenSci" "/python-package-guide/issues) ことから始めてください。" -#: ../../TRANSLATING.md:60 +#: ../../TRANSLATING.md:69 #, fuzzy msgid "" "To generate the translation files for a new language, add the language to" -" the `LANGUAGES` list in the `conf.py` configuration file. " +" the `languages` list in the `conf.py` configuration file. " "[Nox](https://nox.thea.codes/en/stable/index.html) is the tool we use to " -"manage the building of the guide and its translations." +"manage the building of the guide and its translations, and it reads this " +"list from `conf.py`." msgstr "" "新しい言語の翻訳ファイルを生成するには、 `noxfile.py` 設定ファイルの `LANGUAGES` リストにその言語を追加します。 " "[Nox](https://nox.thea.codes/en/stable/index.html) " "はガイドとその翻訳のビルドを管理するために使うツールです。" -#: ../../TRANSLATING.md:62 +#: ../../TRANSLATING.md:71 +#, fuzzy msgid "" -"Inside `noxfile.py`, find the `LANGUAGES` list and add the corresponding " +"Inside `conf.py`, find the `languages` list and add the corresponding " "two-letter code. For example, if you want to start the translation of the" " guide into French, you would add `'fr'`:" msgstr "" "`noxfile.py` の中で `LANGUAGES` リストを見つけて、対応する2文字のコードを追加します。 " "例えば、フランス語への翻訳を開始したい場合は `'fr'` を追加します:" -#: ../../TRANSLATING.md:73 +#: ../../TRANSLATING.md:80 msgid "" "You can find a list of the two-letter Sphinx language option " "[here](https://www.sphinx-doc.org/en/master/usage/configuration.html" @@ -191,11 +255,11 @@ msgstr "" "[ここで](https://www.sphinx-doc.org/en/master/usage/configuration.html" "#confval-language) 、2文字のSphinx言語オプションのリストを見つけることができます。" -#: ../../TRANSLATING.md:76 +#: ../../TRANSLATING.md:83 msgid "Preparing the Translation Files" msgstr "翻訳ファイルの準備" -#: ../../TRANSLATING.md:78 +#: ../../TRANSLATING.md:85 msgid "" "The translation files contain the original English text and a space for " "you to enter the translated text. Before starting to translate, you need " @@ -205,29 +269,30 @@ msgstr "" "翻訳ファイルには、英語の原文と翻訳文を入力するスペースが含まれています。 " "翻訳を始める前に、翻訳ファイルがガイドの最新の変更に対応していることを確認する必要があります。" -#: ../../TRANSLATING.md:80 +#: ../../TRANSLATING.md:87 msgid "" "You can do this by running the following command, replacing LANG by the " "language code you plan to work on (e.g., `es` for Spanish):" msgstr "以下のコマンドを実行し、LANGを作業する予定の言語コードに置き換えてください (例えばスペイン語は `es`):" -#: ../../TRANSLATING.md:86 +#: ../../TRANSLATING.md:93 msgid "" "This command will create the translation files if they don't exist yet, " "or update them with the latest changes if they already exist." msgstr "このコマンドは、翻訳ファイルがまだ存在しない場合は作成し、すでに存在する場合は最新の変更内容で更新します。" -#: ../../TRANSLATING.md:88 +#: ../../TRANSLATING.md:95 +#, fuzzy msgid "" "The translation files are text files with the `.po` extension stored in " -"the `./locales`, in folders corresponding to each language. For example, " -"the translation files for Spanish are stored in the " -"`locale/es/LC_MESSAGES` directory." +"`./locales`, in folders corresponding to each language. For example, the " +"translation files for Spanish are stored in the `locales/es/LC_MESSAGES` " +"directory." msgstr "" "翻訳ファイルは拡張子が `.po` のテキストファイルで、各言語に対応するフォルダ `./locales` に格納されています。 " "例えば、スペイン語の翻訳ファイルは `locale/es/LC_MESSAGES` ディレクトリに格納されています。" -#: ../../TRANSLATING.md:90 +#: ../../TRANSLATING.md:97 msgid "" "Because the translation files map the original English text to translated" " text, they are sometimes referred to as \"catalog\" files or \"portable " @@ -236,7 +301,7 @@ msgstr "" "翻訳ファイルは、元の英文テキストと翻訳テキストを対応付けるため、 \"catalog\" ファイルや \"portable object\" " "ファイルと呼ばれることもあります。" -#: ../../TRANSLATING.md:93 +#: ../../TRANSLATING.md:100 msgid "" "You don't need to know all the details about the PO format in order to " "translate. If you are interested in learning more, you can find " @@ -248,26 +313,27 @@ msgstr "" "documentation](https://www.gnu.org/software/gettext/manual/html_node/PO-" "Files.html) に詳細があります。" -#: ../../TRANSLATING.md:96 +#: ../../TRANSLATING.md:103 msgid "Working on a Translation" msgstr "翻訳作業" -#: ../../TRANSLATING.md:98 +#: ../../TRANSLATING.md:105 +#, fuzzy msgid "" "In order to start translating, go to the folder inside `./locales` " "corresponding to the target language you want to translate to (for " -"example, `./locale/es/LC_MESSAGES/` for the Spanish translation)." +"example, `./locales/es/LC_MESSAGES/` for the Spanish translation)." msgstr "" "翻訳を開始するには、翻訳したいターゲット言語に対応する `./locales` 内のフォルダに移動します（例えば、スペイン語翻訳なら " "`./locale/es/LC_MESSAGES/` です）。" -#: ../../TRANSLATING.md:100 +#: ../../TRANSLATING.md:107 msgid "" "In this folder you will find a set of `.po` files, corresponding to the " "different sections of the guide:" msgstr "このフォルダには、ガイドの各セクションに対応する `.po` ファイルのセットがあります：" -#: ../../TRANSLATING.md:116 +#: ../../TRANSLATING.md:125 msgid "" "You may also see some `.mo` files in the same folder. These are compiled " "versions of the `.po` files create by Sphinx during the build process, " @@ -279,7 +345,7 @@ msgstr "" "ファイルをコンパイルしたもので、翻訳されたバージョンのガイドを生成するために使用されます。 " "これらは中間的なファイルで、直接編集したり、リポジトリに保存したりするものではありません。" -#: ../../TRANSLATING.md:119 +#: ../../TRANSLATING.md:128 msgid "" "If you are working on a new translation, choose one of the `.po` files to" " start with. If you are working on an existing translation, you can start" @@ -288,7 +354,7 @@ msgstr "" "新しい翻訳をする場合は、`.po` ファイルを1つ選んで始めます。 既存の翻訳をする場合は、最も作業が必要な `.po` " "ファイルから始めることができます。" -#: ../../TRANSLATING.md:121 +#: ../../TRANSLATING.md:130 msgid "" "To see how much of each file has been translated, use the `sphinx-intl " "stat`. You will be able to see the number of translated, fuzzy, and " @@ -297,33 +363,33 @@ msgstr "" "各ファイルがどれくらい翻訳されたかを見るには、 `sphinx-intl stat` を使ってください。 それぞれの `.po` " "ファイルに含まれる、翻訳された文字列、あいまいな文字列、未翻訳の文字列の数を見ることができます。" -#: ../../TRANSLATING.md:123 +#: ../../TRANSLATING.md:132 msgid "" "For example, to see the statistics for the Spanish translation, you would" " run:" msgstr "例えば、スペイン語翻訳の統計を見るには、次のように実行します:" -#: ../../TRANSLATING.md:137 +#: ../../TRANSLATING.md:146 msgid "What do these categories mean:" msgstr "これらのカテゴリーは何を意味するのか:" -#: ../../TRANSLATING.md:139 +#: ../../TRANSLATING.md:148 msgid "" "Translated strings are strings that have been translated into the target " "language." msgstr "Translated stringsは、ターゲット言語に翻訳された文字列です。" -#: ../../TRANSLATING.md:140 +#: ../../TRANSLATING.md:149 msgid "" "Fuzzy strings are strings that have been translated but need to be " "reviewed because the original English string in the guide changed." msgstr "Fuzzy stringsとは、翻訳されたものの、ガイドの元の英語の文字列が変更されたため、見直しが必要な文字列のことです。" -#: ../../TRANSLATING.md:141 +#: ../../TRANSLATING.md:150 msgid "Untranslated strings are strings that have not been translated yet." msgstr "Untranslated stringsは、まだ翻訳されていない文字列です。" -#: ../../TRANSLATING.md:144 +#: ../../TRANSLATING.md:153 msgid "" "When Sphinx is building the guide in another language, it will look into " "the corresponding folder in `./locales/` for translated strings. If the " @@ -335,11 +401,11 @@ msgstr "" "もし翻訳が利用可能であれば、Sphinxは英語のテキストをターゲット言語の同等のテキストに置き換えます。 " "もし翻訳が利用できない場合、Sphinxはオリジナルの英語の文字列を使用します。" -#: ../../TRANSLATING.md:147 +#: ../../TRANSLATING.md:156 msgid "Editing the Translation Files" msgstr "翻訳ファイルの編集" -#: ../../TRANSLATING.md:149 +#: ../../TRANSLATING.md:158 msgid "" "You can use any text editor to edit the `.po` file. But if you prefer, " "there are also tools like [Poedit](https://poedit.net/) that provide a " @@ -348,7 +414,7 @@ msgstr "" ".po`ファイルの編集にはどんなテキストエディタでも使えます。 しかし、お好みであれば、 " "[Poedit](https://poedit.net/) のようなグラフィックなインターフェースを提供するツールもあります。" -#: ../../TRANSLATING.md:151 +#: ../../TRANSLATING.md:160 msgid "" "Depending on your editor of choice, you may be able to install a plugin " "or extension that can provide syntax highlighting and other features for " @@ -361,13 +427,13 @@ msgstr "" "[gettext](https://marketplace.visualstudio.com/items?itemName=mrorz" ".language-gettext) エクステンションのようなものです。" -#: ../../TRANSLATING.md:153 +#: ../../TRANSLATING.md:162 msgid "" "When you open a `.po` file, you will see a series of entries that look " "like this:" msgstr ".po`ファイルを開くと、次のようなエントリーが並んでいます:" -#: ../../TRANSLATING.md:163 +#: ../../TRANSLATING.md:172 msgid "" "The first line of an entry starts with `#:` and is a reference to the " "original source file and line number from which the text was extracted. " @@ -377,7 +443,7 @@ msgstr "" "エントリーの最初の行は `#:` で始まり、テキストが抽出された元のソースファイルと行番号への参照となります。 " "この情報は、ガイド内のテキストの文脈を見つけるのに便利です。" -#: ../../TRANSLATING.md:165 +#: ../../TRANSLATING.md:174 msgid "" "The `msgid` field contains the original English text that needs to be " "translated. The `msgstr` field is where you will enter the translated " @@ -387,7 +453,7 @@ msgstr "" "`msgid` フィールドには翻訳が必要な元の英語のテキストを入力します。 `msgstr` フィールドには翻訳されたテキストを入力します。 " "このフィールドには他の人がすでに翻訳したテキストが入るかもしれません。" -#: ../../TRANSLATING.md:175 +#: ../../TRANSLATING.md:184 msgid "" "Sometimes the original English text may be too long for a single line, " "and it may be split into multiple lines. In this case, you can keep the " @@ -398,21 +464,21 @@ msgstr "" "英語の原文が1行では長すぎて、複数行に分かれている場合があります。 このような場合、翻訳されたテキストでも同じ構造を保つことができます。 " "以下の例の `msgid` フィールドと `msgstr` フィールドの両方が空文字列で始まっていることに注意してください。" -#: ../../TRANSLATING.md:191 +#: ../../TRANSLATING.md:200 msgid "" "The English text will sometimes contain Markdown formatting, such as bold" " or italic text. You should keep the formatting in the translated text, " "making sure to translate the text inside the formatting tags." msgstr "英語のテキストには、太字や斜体などのMarkdown書式が含まれていることがあります。翻訳されたテキストで書式を維持する必要があります、フォーマットタグの中のテキストを翻訳してください。" -#: ../../TRANSLATING.md:193 +#: ../../TRANSLATING.md:202 msgid "" "The English text may also contain links to other sections of the guide or" " external resources. You should keep the links in the translated text, " "making sure to update the link text when appropriate." msgstr "英文テキストには、ガイドの他のセクションや外部リソースへのリンクが含まれている場合があります。リンクは翻訳されたテキストの中に残してください、必要に応じてリンクテキストを更新してください。" -#: ../../TRANSLATING.md:201 +#: ../../TRANSLATING.md:210 msgid "" "An entry may be marked as `fuzzy`, which means that the original English " "text has changed since the translation was made, and the translation may " @@ -423,13 +489,13 @@ msgstr "" "と表示されることがありますが、これは原文の英文が翻訳後に変更され、翻訳を修正する必要があることを意味します。このような場合、エントリーに `#,`" " で始まる行が追加されます:" -#: ../../TRANSLATING.md:218 +#: ../../TRANSLATING.md:227 msgid "" "You can review the translation and make any necessary changes, removing " "the `fuzzy` tag once you are satisfied with the translation." msgstr "翻訳を確認して必要な変更を加え、翻訳に満足したら `fuzzy` タグを削除することができます。" -#: ../../TRANSLATING.md:220 +#: ../../TRANSLATING.md:229 msgid "" "You can also add comments to the translation file, by adding lines that " "start with a `#` character to the entry. This can be helpful to add " @@ -437,7 +503,7 @@ msgid "" " this might be only necessary in special circumstances." msgstr "文字で始まる行をエントリに追加することで、翻訳ファイルにコメントを追加することもできます。これは、他の翻訳者やレビュアーが翻訳を見るために文脈を追加するのに役立ちます、しかし、これは特別な状況でのみ必要かもしれません。" -#: ../../TRANSLATING.md:223 +#: ../../TRANSLATING.md:232 msgid "" "When working on a translation, you **should not** modify the original " "English text in the `msgid` field. If you see a typo or an error in the " @@ -448,11 +514,11 @@ msgstr "" "翻訳作業をするときは、 `msgid` フィールドの元の英文を修正 **しないで** ください。 " "もし原文に誤字や脱字があった場合は、原文のソースファイル（エントリーの1行目から探してください）を修正し、別途プルリクエストを提出してください。" -#: ../../TRANSLATING.md:226 +#: ../../TRANSLATING.md:235 msgid "Building the Translated Documentation" msgstr "翻訳されたドキュメントの構築" -#: ../../TRANSLATING.md:228 +#: ../../TRANSLATING.md:237 msgid "" "Once you finished translating or when you want to check the translation " "in context, you can build the guide locally on your computer, using the " @@ -462,17 +528,18 @@ msgstr "" "翻訳が終わったら、あるいは文脈の中で翻訳をチェックしたい場合は、次のコマンドを使用して、ガイドをコンピュータにローカルに構築することができます、 " "LANGを適切な言語コードに置き換えます (例: スペイン語なら `es` )。" -#: ../../TRANSLATING.md:234 +#: ../../TRANSLATING.md:243 +#, fuzzy msgid "" -"This command will build all the translated versions of the guide defined " -"in the `LANGUAGES` list in `noxfile.py`. These translations will be " -"stored in the `_build/html`, in folders named after the language code " -"(e.g., `es`, `fr`, etc.)." +"This command builds a single translated version of the guide: the one for" +" LANG. The result is stored in `_build/html`, in a folder named after the" +" language code (e.g., `es`). If you want to build every language at once " +"instead, use `nox -s build-all-languages`." msgstr "" "このコマンドは `noxfile.py` の `LANGUAGES` リストで定義されたガイドの全ての翻訳版をビルドします。 これらの翻訳版は " "`_build/html` に、言語コードにちなんだ名前(例えば `es`、`fr` など)のフォルダに保存されます。" -#: ../../TRANSLATING.md:236 +#: ../../TRANSLATING.md:245 msgid "" "To view the translated version of the guide in your browser, open the " "corresponding `index.html` file. For example, to view the Spanish " @@ -481,7 +548,7 @@ msgstr "" "ブラウザで翻訳版のガイドを見るには、対応する `index.html` ファイルを開いてください。 例えば、スペイン語の翻訳版を見るには、 " "`_build/html/es/index.html` を開きます。" -#: ../../TRANSLATING.md:238 +#: ../../TRANSLATING.md:247 msgid "" "You can also build a live version of the guide that updates automatically" " as you make changes to the translation files. To do this, use the `nox " @@ -493,7 +560,7 @@ msgstr "" "live-lang` コマンドを使用します。 この場合、ビルドしたい言語を指定する必要があることに注意してください。 " "例えば、スペイン語翻訳に取り組んでいる場合、次のように実行します:" -#: ../../TRANSLATING.md:244 +#: ../../TRANSLATING.md:253 msgid "" "Note the `--` before the language code, it indicates that the following " "arguments should be passed into the nox session and not be interpreted " @@ -503,7 +570,7 @@ msgstr "" "言語コードの前の `--` に注意してください。これは次の引数がnoxセッションに渡され、noxによって直接解釈されないことを示します。 もし " "`--` を忘れると、noxは代わりに 'es' という名前のセッションを探し、それが存在しないとエラーを発生させます。" -#: ../../TRANSLATING.md:246 +#: ../../TRANSLATING.md:255 msgid "" "This command will use `sphinx-autobuild` to launch a local web server " "where you can access the translated version of the guide. You can open " @@ -513,17 +580,17 @@ msgstr "" "を使って、ローカルのWebサーバーを起動し、そこでガイドの翻訳版にアクセスすることができます。 ブラウザで " "`http://localhost:8000` に移動して、ガイドを開くことができます。" -#: ../../TRANSLATING.md:248 +#: ../../TRANSLATING.md:257 msgid "" "This is a great way to see how the translated version of the guide looks " "as you make changes to the translation files." msgstr "これは、翻訳ファイルに変更を加えながら、翻訳版のガイドがどのように見えるかを確認するのに最適な方法です。" -#: ../../TRANSLATING.md:250 +#: ../../TRANSLATING.md:259 msgid "Submitting a PR for Your Contribution" msgstr "貢献PRの提出" -#: ../../TRANSLATING.md:252 +#: ../../TRANSLATING.md:261 msgid "" "Once you are finished translating and before you submit a pull request " "(PR) for your translation, you need to make sure that the translated " @@ -531,23 +598,23 @@ msgid "" "correctly in the browser." msgstr "翻訳が終わり、翻訳のプルリクエスト（PR）を提出する前に、翻訳されたバージョンのガイドがエラーや警告なしにビルドされ、ブラウザで正しく表示されることを確認する必要があります。" -#: ../../TRANSLATING.md:254 +#: ../../TRANSLATING.md:263 msgid "You can follow these steps:" msgstr "以下の手順に従ってください:" -#: ../../TRANSLATING.md:256 +#: ../../TRANSLATING.md:265 msgid "" "Build the translations of the guide with same parameters that will be " "used during the release:" msgstr "リリース時に使用されるのと同じパラメータでガイドの翻訳をビルドします:" -#: ../../TRANSLATING.md:262 +#: ../../TRANSLATING.md:271 msgid "" "Make sure there are no warnings or errors in the output. If there are, " "you will need to fix them before submitting the PR." msgstr "出力に警告やエラーがないことを確認してください。 もしあれば、PRを提出する前に修正する必要があります。" -#: ../../TRANSLATING.md:263 +#: ../../TRANSLATING.md:272 msgid "" "Make sure the translated version of the guide looks good in the browser " "by opening the `_build/html//index.html` file, where `` is " @@ -556,18 +623,18 @@ msgstr "" "`_build/html//index.html` " "ファイルを開いて、翻訳版のガイドがブラウザでうまく表示されることを確認してください。 `` は作業中の言語です。" -#: ../../TRANSLATING.md:265 +#: ../../TRANSLATING.md:274 msgid "If everything looks good, you can submit a PR with your changes." msgstr "問題がなければ、変更内容をPRとして提出することができます。" -#: ../../TRANSLATING.md:268 +#: ../../TRANSLATING.md:277 msgid "" "When you submit a PR for a translation, you should only include changes " "to one language. If you worked in multiple languages, please submit a " "separate PR for each language." msgstr "翻訳のPRを提出する際は、1つの言語に対する変更のみを記載してください。 複数の言語で翻訳した場合は、言語ごとにPRを提出してください。" -#: ../../TRANSLATING.md:271 +#: ../../TRANSLATING.md:280 msgid "" "Translations PRs will be tagged with a label indicating the language to " "make them easier to identify and review. For example, contributions to " @@ -576,11 +643,11 @@ msgstr "" "翻訳PRには、識別とレビューを容易にするため、言語を示すラベルが付けられます。 例えば、スペイン語翻訳への貢献には 'lang-es' " "というタグが付けられます。" -#: ../../TRANSLATING.md:273 +#: ../../TRANSLATING.md:282 msgid "TODO: This tagging could be automated with a GitHub Actions." msgstr "TODO: このタグ付けは、GitHub Actionsで自動化できるかもしれません。" -#: ../../TRANSLATING.md:275 +#: ../../TRANSLATING.md:284 msgid "" "When you submit the PR, make sure to include a short description of the " "changes you made and any context that might be helpful for the reviewer " @@ -588,17 +655,17 @@ msgid "" "typos, etc.)" msgstr "PRを提出する際には、あなたが行った変更についての簡単な説明と、レビュアーにとって参考になりそうな文脈（新しい文字列を翻訳した、あいまいなエントリーを見直した、誤字脱字を修正した、など）を必ず含めてください。" -#: ../../TRANSLATING.md:277 +#: ../../TRANSLATING.md:286 msgid "The Review Process" msgstr "レビュープロセス" -#: ../../TRANSLATING.md:279 +#: ../../TRANSLATING.md:288 msgid "" "The review process for a translation contribution is similar to the " "review process for any other contribution to the guide." msgstr "翻訳貢献のレビュープロセスは、ガイドへの他のレビューのレビュープロセスと同様です。" -#: ../../TRANSLATING.md:281 +#: ../../TRANSLATING.md:290 msgid "" "TODO: This section needs more work, depending on the review workflow we " "decide to adopt. Other projects usually assign a coordinator/editor for " @@ -608,7 +675,7 @@ msgstr "" "TODO: このセクションは、私たちが採用するレビューのワークフローによって、もっと作業が必要です。 " "他のプロジェクトでは、通常、言語ごとにコーディネーター/編集者を割り当て、その人が翻訳投稿のレビューとマージに責任を持ちます。" -#: ../../TRANSLATING.md:283 +#: ../../TRANSLATING.md:292 msgid "" "Each language has an assigned editor who is responsible for reviewing and" " merging translation contributions. The editor will review the changes to" @@ -618,7 +685,7 @@ msgstr "" "各言語には担当エディターがおり、翻訳投稿の確認と統合を担当します。 " "エディターは、変更が正確で、ガイドのスタイルやトーンと一致していることを確認します。" -#: ../../TRANSLATING.md:285 +#: ../../TRANSLATING.md:294 msgid "" "Sometimes the editor may ask for clarification or suggest changes to " "improve the translation. If this happens, you can make the requested " @@ -628,36 +695,37 @@ msgstr "" "エディターが翻訳を改善するために説明を求めたり、変更を提案したりすることがあります。 " "このような場合は、要求された変更を行い、元のPRを投稿したブランチにプッシュしてください。" -#: ../../TRANSLATING.md:287 +#: ../../TRANSLATING.md:296 msgid "" "When the editor is satisfied with the translation, they will merge the " "PR. The translated version of the guide will be available on the " "pyOpenSci website once the language is released." msgstr "エディターが翻訳に満足したら、PRをマージします。ガイドの翻訳版は言語がリリースされ次第、pyOpenSciのウェブサイトから入手できます。" -#: ../../TRANSLATING.md:289 +#: ../../TRANSLATING.md:298 msgid "The Release Process" msgstr "リリースのプロセス" -#: ../../TRANSLATING.md:291 +#: ../../TRANSLATING.md:300 +#, fuzzy msgid "" "If a language is ready to go live, the maintainers will add the language " -"code to the `RELEASE_LANGUAGES` list in the `noxfile.py` configuration " -"file." +"code to the `release_languages` list in the `conf.py` configuration file." msgstr "" "言語がライブにする準備ができたら、メンテナは `noxfile.py` 設定ファイルの `RELEASE_LANGUAGES` " "リストに言語コードを追加します。" -#: ../../TRANSLATING.md:293 +#: ../../TRANSLATING.md:302 +#, fuzzy msgid "" "When the guide is built for release in CI, Sphinx will also generate the " "translated versions of the guide for the languages in the " -"`RELEASE_LANGUAGES` list." +"`release_languages` list." msgstr "" "ガイドがCIでリリースするためにビルドされると、Sphinxは `RELEASE_LANGUAGES` " "リストにある言語の翻訳版のガイドも生成します。" -#: ../../TRANSLATING.md:295 +#: ../../TRANSLATING.md:304 #, fuzzy msgid "" "Translations are released in the same way as the English version of the " @@ -670,15 +738,15 @@ msgstr "" "[https://www.pyopensci.org/python-package-" "guide/es/](https://www.pyopensci.org/python-package-guide/es/) にあります。" -#: ../../TRANSLATING.md:297 +#: ../../TRANSLATING.md:306 msgid "Frequently Asked Questions (FAQ)" msgstr "よくある質問(FAQ)" -#: ../../TRANSLATING.md:299 +#: ../../TRANSLATING.md:308 msgid "How do I know which strings need to be translated?" msgstr "どの文字列を翻訳する必要があるか、どうすればわかりますか？" -#: ../../TRANSLATING.md:301 +#: ../../TRANSLATING.md:310 msgid "" "When you run the `sphinx-intl stat` command, you will see a list of `.po`" " files with the number of translated, fuzzy, and untranslated strings. " @@ -687,29 +755,30 @@ msgstr "" "`sphinx-intl stat` コマンドを実行すると、翻訳された文字列、あいまいな文字列、未翻訳の文字列を含む `.po` " "ファイルのリストが表示されます。 未翻訳の文字列が最も多いファイルから、作業を始めることができます。" -#: ../../TRANSLATING.md:303 +#: ../../TRANSLATING.md:312 msgid "What happens when a string has changed in the original English text?" msgstr "英語の原文で文字列が変更された場合はどうなりますか？" -#: ../../TRANSLATING.md:305 +#: ../../TRANSLATING.md:314 +#, fuzzy msgid "" "If a string has changed in the original English version, it will be " "marked as `fuzzy` in the translation file the next time it is updated " -"(`update-language`, `update-all-languages`, or `update-all-release-" -"languages`). Contributors working on the translation can then review the " -"fuzzy entries and make the necessary changes to ensure it is accurate, " -"before removing the `fuzzy` tag." +"(`update-language` or `update-release-languages`). Contributors working " +"on the translation can then review the fuzzy entries and make the " +"necessary changes to ensure it is accurate, before removing the `fuzzy` " +"tag." msgstr "" "オリジナルの英語版で文字列が変更された場合、次に翻訳ファイルが更新されるとき (`update-language`, `update-all-" "languages`, または `update-all-release-languages`) に `fuzzy` としてマークされます。 " "翻訳に携わっているコントリビューターは、 `fuzzy` " "タグを削除する前に、あいまいなエントリを確認し、正確であることを確認するために必要な変更を行うことができます。" -#: ../../TRANSLATING.md:307 +#: ../../TRANSLATING.md:316 msgid "How do I handle links in the translated text?" msgstr "翻訳されたテキスト内のリンクはどのように扱えばいいですか？" -#: ../../TRANSLATING.md:309 +#: ../../TRANSLATING.md:318 msgid "" "You should keep the links in the translated text, but make sure to update" " the link text if necessary. For example, if the original English text " @@ -721,11 +790,11 @@ msgstr "" "Python package?](/tutorials/intro)` へのリンクがある場合、翻訳文のリンクはそのままにして、リンクテキストを " "`[Pythonパッケージとは何ですか](/tutorials/intro)` に更新してください。" -#: ../../TRANSLATING.md:311 +#: ../../TRANSLATING.md:320 msgid "How do I handle formatting in the translated text?" msgstr "翻訳されたテキストの書式設定はどうすればよいですか？" -#: ../../TRANSLATING.md:313 +#: ../../TRANSLATING.md:322 msgid "" "You should keep the formatting in the translated text, but make sure to " "translate the text inside the formatting tags as well. For example, if " @@ -737,11 +806,11 @@ msgstr "" "special cases:**` の場合、翻訳されたテキストでは太字の書式を維持しますが、書式タグ内のテキストを `**特殊ケーステスト:**`" " に更新する必要があります。" -#: ../../TRANSLATING.md:315 +#: ../../TRANSLATING.md:324 msgid "How do I handle strings that are too long for a single line?" msgstr "1行では長すぎる文字列はどう扱えばいいですか？" -#: ../../TRANSLATING.md:317 +#: ../../TRANSLATING.md:326 msgid "" "If the original English text is too long for a single line, it may be " "split into multiple lines. Multiline strings in the `.po` file are " @@ -751,11 +820,11 @@ msgstr "" "元の英文が長すぎて1行に収まらない場合は、複数行に分けることができます。 `.po` ファイル内の複数行の文字列は `msgid` と " "`msgstr` フィールドに空の文字列を入れ、その後に次の行のテキストの続きを入れることで示されます。 例えば:" -#: ../../TRANSLATING.md:330 +#: ../../TRANSLATING.md:339 msgid "How do I translate images?" msgstr "画像を翻訳するにはどうすればよいですか？" -#: ../../TRANSLATING.md:332 +#: ../../TRANSLATING.md:341 msgid "" "You should not translate images in the guide. Producing translated " "versions of images is a complex process that requires additional tools " @@ -767,20 +836,20 @@ msgstr "" "画像の翻訳版を作成するのは、追加のツールやリソースを必要とする複雑なプロセスであり、翻訳された画像がオリジナルの画像と一緒に作成されない限り、通常は行われません。" " 多くの場合、画像の周りのテキストは、必要な翻訳を含むように修正されます。" -#: ../../TRANSLATING.md:334 +#: ../../TRANSLATING.md:343 msgid "" "In some special cases, an image might be critical to the understanding of" " the content. In those cases, the translations will be handled by the " "maintainers and editors outside this workflow." msgstr "特殊なケースでは、画像がコンテンツの理解に不可欠な場合があります。 そのような場合、翻訳はこのワークフロー外のメンテナやエディタが担当します。" -#: ../../TRANSLATING.md:336 +#: ../../TRANSLATING.md:345 msgid "" "I am interested in translating the guide into a language that is not " "listed. How can I get started?" msgstr "ガイドに掲載されていない言語への翻訳に興味があります。 どうすれば始められますか？" -#: ../../TRANSLATING.md:338 +#: ../../TRANSLATING.md:347 msgid "" "If you want to start a new translation of the guide into a language that " "is not listed, you should [create an issue](https://github.com/pyOpenSci" @@ -794,35 +863,36 @@ msgstr "" "して、あなたがその翻訳に取り組むつもりであることをメンテナに知らせてください。 " "こうすることで、作業の重複を避け、あなたが作業を終えたときにメンテナがあなたの貢献をレビューできるようになります。" -#: ../../TRANSLATING.md:340 +#: ../../TRANSLATING.md:349 msgid "How do I know when a translation is ready to be released?" msgstr "翻訳がいつリリースできるか、どうすればわかりますか？" -#: ../../TRANSLATING.md:342 +#: ../../TRANSLATING.md:351 +#, fuzzy msgid "" "When a translation is ready to be included in the next release of the " "guide, the maintainers will add the language code to the " -"`RELEASE_LANGUAGES` list in the `noxfile.py` configuration file. This " -"will trigger the build of the translation during the release process, and" -" the translated version of the guide will be available on the pyOpenSci " +"`release_languages` list in the `conf.py` configuration file. This will " +"trigger the build of the translation during the release process, and the " +"translated version of the guide will be available on the pyOpenSci " "website." msgstr "" "ガイドの次のリリースに翻訳を含める準備ができたら、メンテナは `noxfile.py` 設定ファイルの `RELEASE_LANGUAGES` " "リストに言語コードを追加します。 " "これにより、リリースプロセス中に翻訳のビルドが開始され、翻訳されたバージョンのガイドがpyOpenSciのウェブサイトで利用できるようになります。" -#: ../../TRANSLATING.md:344 +#: ../../TRANSLATING.md:353 msgid "" "TODO: There are many approaches here, some projects release a translation" " as soon as some strings are translated, others wait until a certain " "percentage of the content is translated." msgstr "TODO：ここにはさまざまなアプローチがあります。あるプロジェクトでは、いくつかの文字列が翻訳されるとすぐに翻訳をリリースしますし、ある一定の割合のコンテンツが翻訳されるまで待つプロジェクトもあります。" -#: ../../TRANSLATING.md:346 +#: ../../TRANSLATING.md:355 msgid "How can I get help with my translation?" msgstr "翻訳を手伝ってもらうにはどうすればよいですか？" -#: ../../TRANSLATING.md:348 +#: ../../TRANSLATING.md:357 msgid "" "If you have any questions or need help with your translation, you can " "create an [issue](https://github.com/pyOpenSci/python-package-" @@ -833,7 +903,7 @@ msgstr "" "/python-package-guide) に [issue](https://github.com/pyOpenSci/python-" "package-guide/issues) を作成してください。" -#: ../../TRANSLATING.md:350 +#: ../../TRANSLATING.md:359 msgid "" "You can also ask in the PyOpenSci Discord server ([click " "here](https://discord.gg/NQtTTqtv) to join), you will find a general " @@ -845,3 +915,26 @@ msgstr "" "、私たちのワークフロー、プロセス、ツールに関する一般的な質問用のチャンネル (translation-general) " "と、私たちが取り組んでいる各言語のチャンネル (spanish-translation、japanese-translationなど) " "があります。" + +#~ msgid "Before you start, you will need to set up your local work environment." +#~ msgstr "作業を始める前に、ローカルの作業環境を設定する必要があります。" + +#~ msgid "" +#~ "First, fork the guide repository into" +#~ " your personal GitHub account and " +#~ "clone the forked repository to your " +#~ "local computer." +#~ msgstr "まず、ガイドリポジトリを個人のGitHubアカウントにフォークし、フォークしたリポジトリをローカルコンピューターにクローンします。" + +#~ msgid "" +#~ "To create a virtual environment and " +#~ "install the development dependencies for " +#~ "the guide, run the following commands:" +#~ msgstr "仮想環境を作成し、ガイドの開発依存関係をインストールするには、以下のコマンドを実行します:" + +#~ msgid "" +#~ "TODO: This section needs more work " +#~ "or to be replaced with a reference" +#~ " to the CONTRIBUTING guide." +#~ msgstr "TODO: このセクションは、より多くの作業が必要か、CONTRIBUTINGガイドへの参照に置き換える必要があります。" + diff --git a/locales/ja/LC_MESSAGES/maintain-automate.po b/locales/ja/LC_MESSAGES/maintain-automate.po index a9968dfdb..f82b01bf2 100644 --- a/locales/ja/LC_MESSAGES/maintain-automate.po +++ b/locales/ja/LC_MESSAGES/maintain-automate.po @@ -9,7 +9,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide \n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-05-18 12:56-0700\n" +"POT-Creation-Date: 2026-08-25 07:47+0900\n" "PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n" "Last-Translator: FULL NAME \n" "Language: ja\n" @@ -226,6 +226,186 @@ msgid "" "documentation and docstrings!" msgstr "" +#: ../../maintain-automate/dev-installs.md:1 +msgid "Installing your own code" +msgstr "" + +#: ../../maintain-automate/dev-installs.md:3 +msgid "" +"You have a conda environment. It works. Maybe it has packages that were " +"hard to install, like GDAL, HDF5, or other compiled scientific " +"dependencies." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:5 +msgid "" +"You also have code that you are writing locally. Maybe it started as a " +"script, or maybe it is already organized as a Python package. You want to" +" use that code inside the same environment with GDAL, HDF5, and the other" +" tools you already installed." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:7 +msgid "" +"The instructions to install your code into a conda environment is to " +"first activate your conda environment `conda activate your_env_name` and " +"then run this: `python -m pip install -e . --no-deps`. You may also see " +"this written as `pip install -e .`. See [The Full Command](the-full-" +"command) section below for more info as to the details of this command." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:9 +msgid "" +"If this is the first time you're seeing pip install commands, you may not" +" be totally sure what is going on here. Conda created the environment, " +"why am I using `pip` to install things now? You may have heard guidance " +"to generally try and avoid mixing conda and pip? You may already be " +"mixing conda and pip and things are totally fine. You may also not care " +"at all because `pip install -e .` seems to work fine and you can get back" +" to what you're actually trying to do. (If that last one is you, you're " +"also probably not reading this page). In any event, all of these " +"situations are perfectly understandable and totally okay for you to be " +"going through." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:11 +msgid "" +"So... why pip? The short answer is that conda and pip are doing different" +" jobs here." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:13 +msgid "" +"The slightly longer, mostly apologetic, answer is this is just sort of " +"the current ergonomics of how python packaging works and, honestly? Most " +"of us have turned this confusing pain point into muscle memory. But not " +"you. You're new here. And you're like... wat? And you're totally " +"justified to feel this way." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:15 +msgid "" +"So, what is happening here? `conda` manages the environment: the Python " +"runtime, compiled libraries, command line tools, and the packages your " +"project depends on. This is stuff that you've already been doing and " +"you're comfortable with (or at least familiar with). `pip` is doing one " +"Python-packaging-specific job: installing your local package into the " +"active environment." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:17 +msgid "" +"In editable mode, the `-e` flag, `pip` connects the active environment to" +" the source files you are editing. And... why exactly is that useful?" +msgstr "" + +#: ../../maintain-automate/dev-installs.md:19 +msgid "It's useful because it gives you a pretty quick development loop:" +msgstr "" + +#: ../../maintain-automate/dev-installs.md:21 +msgid "Edit your code in your editor." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:22 +msgid "Run it from a terminal, test suite, or Jupyter notebook." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:23 +msgid "Edit the code again." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:24 +msgid "Run it again without reinstalling your package." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:26 +msgid "" +"So the goal is not to switch from conda to pip. The goal is to keep using" +" your conda environment while making your local package importable inside" +" that environment." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:28 +msgid "Should I use pip for everything now?" +msgstr "" + +#: ../../maintain-automate/dev-installs.md:30 +msgid "Probably not?" +msgstr "" + +#: ../../maintain-automate/dev-installs.md:32 +msgid "" +"If conda is already working well for your project, keep using conda to " +"manage the environment. Use pip only for this one task: installing your " +"local package in editable mode." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:34 +msgid "" +"If you are curious about other tools like uv, pixi, Hatch, or pip-only " +"workflows, see [Environment Managers](environment-managers.md). Those " +"tools can be great choices. But you do not need to switch tools just to " +"develop your local package inside a conda environment." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:36 +msgid "" +"As a final note, people in the conda ecosystem are actively working on " +"better conda/pip interoperability. In the future, this workflow may " +"become less awkward. For now, `python -m pip install -e . --no-deps` is " +"the standard bridge." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:39 +msgid "The full command" +msgstr "" + +#: ../../maintain-automate/dev-installs.md:41 +msgid "" +"`python -m pip install -e . --no-deps` is a mouthful. I know it. You know" +" it. Why do we do these things?" +msgstr "" + +#: ../../maintain-automate/dev-installs.md:43 +msgid "The simplest version of this is:" +msgstr "" + +#: ../../maintain-automate/dev-installs.md:48 +msgid "But we recommend the longer version in conda environments for two reasons." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:50 +msgid "" +"The `python -m pip` part ensures that you're using pip from the active " +"conda environment. Sometimes this results in `pip not found`, which is " +"actually a good error to get because it means you prevented an annoying-" +"to-debug failure mode. If this happens just `conda install pip` and try " +"again. So, why? Sometimes `pip` from a different python environment can " +"be on your PATH which means that you'll accidentally install your code " +"into an unrelated python environment. This can be confusing to debug. " +"This has happened to most (all?) of us. It usually hits when you're least" +" prepared to debug and fix it. So we recommend the `python -m` in front " +"to prevent this from happening. But it does add to the length of the " +"command." +msgstr "" + +#: ../../maintain-automate/dev-installs.md:52 +msgid "" +"The `--no-deps` flag tells pip not to install your package's " +"dependencies, if you have any listed in your project. If you do have them" +" listed, probably in your `pyproject.toml` file, then `pip install -e .` " +"will try to install the dependencies that are listed in that file. In a " +"conda environment, that can range from \"mostly fine\" to \"now my " +"environment is broken and I am not sure how to recover.\"" +msgstr "" + +#: ../../maintain-automate/dev-installs.md:54 +msgid "" +"With `--no-deps`, pip installs only your local package. You remain " +"responsible for managing the environment dependencies with conda." +msgstr "" + #: ../../maintain-automate/environment-managers.md:2 msgid "Environment Managers for Python Packaging" msgstr "" @@ -599,7 +779,7 @@ msgid "Conda and mamba also function as environment managers - see below!" msgstr "" #: ../../maintain-automate/environment-managers.md:112 -#: ../../maintain-automate/index.md:46 +#: ../../maintain-automate/index.md:51 msgid "Environment Managers" msgstr "" @@ -750,15 +930,19 @@ msgid "" " your team gets identical environments." msgstr "" -#: ../../maintain-automate/index.md:46 +#: ../../maintain-automate/index.md:51 msgid "What is CI?" msgstr "" -#: ../../maintain-automate/index.md:46 +#: ../../maintain-automate/index.md:51 msgid "Task runners" msgstr "" -#: ../../maintain-automate/index.md:46 +#: ../../maintain-automate/index.md:51 +msgid "Development installs with conda" +msgstr "" + +#: ../../maintain-automate/index.md:51 msgid "Maintain & Automate" msgstr "" @@ -831,6 +1015,14 @@ msgid "" "contributors." msgstr "" +#: ../../maintain-automate/index.md:46 +msgid "" +"[**Development installs in conda environments**](dev-installs) help you " +"connect conda-based scientific development environments with local Python" +" package development. This is especially useful when your package depends" +" on compiled or system-level dependencies that conda manages well." +msgstr "" + #: ../../maintain-automate/task-runners.md:2 msgid "Task Runners for Python Packaging" msgstr "" @@ -1613,3 +1805,4 @@ msgid "" "This guide is excellent if you plan to use nox as your task runner as it " "has lots of examples that you can follow." msgstr "" + diff --git a/locales/ja/LC_MESSAGES/package-structure-code.po b/locales/ja/LC_MESSAGES/package-structure-code.po index 79f923f20..779b9f454 100644 --- a/locales/ja/LC_MESSAGES/package-structure-code.po +++ b/locales/ja/LC_MESSAGES/package-structure-code.po @@ -11,7 +11,7 @@ msgid "" msgstr "" "Project-Id-Version: pyOpenSci Python Package Guide\n" "Report-Msgid-Bugs-To: \n" -"POT-Creation-Date: 2026-05-22 12:19-0700\n" +"POT-Creation-Date: 2026-08-25 07:47+0900\n" "PO-Revision-Date: 2025-04-14 18:12+0000\n" "Last-Translator: Tetsuo Koyama , 2025\n" "Language: ja\n" @@ -1015,7 +1015,7 @@ msgstr "" msgid "" "**Feature Dependencies:** These are dependencies that are required if a " "user wants to access additional functionality (that is not core) to your " -"package. Store these in the `[project.optional-dependencies]` table of " +"package. Store these in the `[project.optional-dependencies]` table or " "your pyproject.toml file." msgstr "" @@ -1024,8 +1024,8 @@ msgid "" "**Development Dependencies:** These dependencies are required if someone " "wants to develop or work on your package. These include instance linters," " testing tools like pytest and mypy are examples of development " -"dependencies. Store these in the `[dependency-groups]` table of " -"your pyproject.toml file." +"dependencies. Store these in the `[dependency-groups]` table of your " +"pyproject.toml file." msgstr "" #: ../../package-structure-code/declare-dependencies.md:64 @@ -1070,7 +1070,7 @@ msgstr "必要な依存関係をpyproject.tomlファイルに追加" #: ../../package-structure-code/declare-dependencies.md:102 #: ../../package-structure-code/declare-dependencies.md:162 -#: ../../package-structure-code/declare-dependencies.md:223 +#: ../../package-structure-code/declare-dependencies.md:222 #, fuzzy msgid "You can use uv to add dependencies to your pyproject.toml file:" msgstr "pyproject.tomlファイルに依存関係を追加" @@ -1117,8 +1117,9 @@ msgid "" "users as needed. Optional dependencies add specific features to your " "package that not all users need. For example, if your package has an " "optional interactive plotting feature that uses Bokeh, you would list " -"Bokeh under `[project.optional-dependencies]`. Users who want interactive plotting " -"will install it. Users who don't need plotting don't have to install it." +"Bokeh under `[project.optional-dependencies]`. Users who want interactive" +" plotting will install it. Users who don't need plotting don't have to " +"install it." msgstr "" #: ../../package-structure-code/declare-dependencies.md:144 @@ -1135,7 +1136,7 @@ msgstr "" #: ../../package-structure-code/declare-dependencies.md #, fuzzy -msgid "How to add optional dependencies using UV" +msgid "How to Add optional dependencies using UV" msgstr "オプションの依存関係" #: ../../package-structure-code/declare-dependencies.md:164 @@ -1186,7 +1187,7 @@ msgstr "" #: ../../package-structure-code/declare-dependencies.md:196 #, fuzzy -msgid "New: PEP 735 development dependency groups" +msgid "New: PEP 735 dependency groups" msgstr "オプションの依存グループを作成する" #: ../../package-structure-code/declare-dependencies.md:199 @@ -1197,19 +1198,19 @@ msgid "" " be installed into a user's environment." msgstr "" -#: ../../package-structure-code/declare-dependencies.md:204 +#: ../../package-structure-code/declare-dependencies.md:203 #, fuzzy msgid "How to declare dependency groups" msgstr "依存関係はどのように宣言するのか？" -#: ../../package-structure-code/declare-dependencies.md:206 +#: ../../package-structure-code/declare-dependencies.md:205 #, fuzzy msgid "" "You declare development dependencies in your **pyproject.toml** file " "within a `[dependency-groups]` table." msgstr "**pyproject.toml** ファイルでオプションの依存関係を宣言します:" -#: ../../package-structure-code/declare-dependencies.md:209 +#: ../../package-structure-code/declare-dependencies.md:208 msgid "" "Similar to optional-dependencies, you can create separate subgroups or " "arrays with names using the syntax: `group-name = [\"dep1\", \"dep2\"]`" @@ -1219,37 +1220,37 @@ msgstr "" msgid "How to Add [dependency-groups] using UV" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:225 +#: ../../package-structure-code/declare-dependencies.md:224 msgid "**Add a development dependency group:**" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:232 +#: ../../package-structure-code/declare-dependencies.md:231 #, fuzzy msgid "Will add the following to your pyproject.toml file:" msgstr "pyproject.tomlファイルに依存関係を追加" -#: ../../package-structure-code/declare-dependencies.md:245 -#: ../../package-structure-code/declare-dependencies.md:251 -#: ../../package-structure-code/declare-dependencies.md:295 -#: ../../package-structure-code/declare-dependencies.md:414 -#: ../../package-structure-code/declare-dependencies.md:496 +#: ../../package-structure-code/declare-dependencies.md:244 +#: ../../package-structure-code/declare-dependencies.md:250 +#: ../../package-structure-code/declare-dependencies.md:294 +#: ../../package-structure-code/declare-dependencies.md:434 +#: ../../package-structure-code/declare-dependencies.md:516 #: ../../package-structure-code/pyproject-toml-python-package-metadata.md:14 msgid "Todo" msgstr "Todo" -#: ../../package-structure-code/declare-dependencies.md:246 +#: ../../package-structure-code/declare-dependencies.md:245 msgid "" "i'll pick back up here tomorrow - this section is all about how things " "install and what \"ships\" with your package vs what just gets installed " "via commands (ie development)" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:249 +#: ../../package-structure-code/declare-dependencies.md:248 #, fuzzy msgid "Understanding required vs. optional dependencies" msgstr "オプションと必須の依存関係を理解する" -#: ../../package-structure-code/declare-dependencies.md:252 +#: ../../package-structure-code/declare-dependencies.md:251 msgid "" "The purpose of this section is to help users understand how dependencies " "relate to what is installed in their environment. We have two graphics on" @@ -1260,14 +1261,14 @@ msgid "" " were using optional dependencies for dev groups." msgstr "" -#: ../../package-structure-code/declare-dependencies.md:254 +#: ../../package-structure-code/declare-dependencies.md:253 msgid "" "The graphic below is two circles representing optional vs regular / " "required deps - created before development groups existed... there is " "another graphi that shows what gets installed into a uses envt." msgstr "" -#: ../../package-structure-code/declare-dependencies.md:258 +#: ../../package-structure-code/declare-dependencies.md:257 msgid "" "Diagram showing two main groups of Python package dependencies: required " "and optional. Required dependencies include core packages needed to use " @@ -1276,18 +1277,18 @@ msgid "" "functionality." msgstr "" -#: ../../package-structure-code/declare-dependencies.md:260 +#: ../../package-structure-code/declare-dependencies.md:259 msgid "" "Python package dependencies fall into two categories: **required** " "dependencies that users need to run your package, and **optional** " "dependencies for development work or additional features." msgstr "" -#: ../../package-structure-code/declare-dependencies.md:265 +#: ../../package-structure-code/declare-dependencies.md:264 msgid "Additional dependency resources" msgstr "その他の依存リソース" -#: ../../package-structure-code/declare-dependencies.md:267 +#: ../../package-structure-code/declare-dependencies.md:266 msgid "" "[Learn more: View PyPA's overview of declaring optional " "dependencies](https://packaging.python.org/en/latest/specifications" @@ -1297,7 +1298,7 @@ msgstr "" "PyPAのオプション依存関係の宣言の概要を見る](https://packaging.python.org/en/latest/specifications" "/declaring-project-metadata/#dependencies-optional-dependencies)" -#: ../../package-structure-code/declare-dependencies.md:268 +#: ../../package-structure-code/declare-dependencies.md:267 msgid "" "[Dependency " "specifiers](https://packaging.python.org/en/latest/specifications" @@ -1307,18 +1308,18 @@ msgstr "" "specifiers](https://packaging.python.org/en/latest/specifications" "/dependency-specifiers/)" -#: ../../package-structure-code/declare-dependencies.md:272 +#: ../../package-structure-code/declare-dependencies.md:271 msgid "Install dependency groups" msgstr "依存グループをインストールする" -#: ../../package-structure-code/declare-dependencies.md:274 +#: ../../package-structure-code/declare-dependencies.md:273 msgid "" "When someone installs your package, only core dependencies are installed " "by default. To install optional dependencies, you need to specify which " "groups to include when installing the package." msgstr "" -#: ../../package-structure-code/declare-dependencies.md:280 +#: ../../package-structure-code/declare-dependencies.md:279 #, fuzzy msgid "" "Diagram showing a Venn diagram with three sections representing " @@ -1336,7 +1337,7 @@ msgstr "" " python -m pip install youPackage[tests] とあります。これにより、パッケージ依存関係 - your-" "package、seaborn、numpy とテスト依存関係 pytest、pytest-cov の両方を含む環境が構築されます。" -#: ../../package-structure-code/declare-dependencies.md:282 +#: ../../package-structure-code/declare-dependencies.md:281 #, fuzzy msgid "" "When a user installs your package using `pip install your-package`, only " @@ -1351,11 +1352,11 @@ msgstr "" "はあなたのパッケージとそのコア依存パッケージの両方をインストールし、さらに `[project.optional-dependencies]` " "テーブルの tests 配列にリストされている依存パッケージをインストールします。" -#: ../../package-structure-code/declare-dependencies.md:289 +#: ../../package-structure-code/declare-dependencies.md:288 msgid "Using uv or pip for installation" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:291 +#: ../../package-structure-code/declare-dependencies.md:290 msgid "" "UV streamlines this process, allowing you to sync a venv in your project " "directory with both an editable install of your package and its " @@ -1363,13 +1364,14 @@ msgid "" " into the environment of your choice." msgstr "" -#: ../../package-structure-code/declare-dependencies.md:296 +#: ../../package-structure-code/declare-dependencies.md:295 msgid "" "We shouldn't show UV pip install, so how do you add optional feature deps" " with UV??" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:299 +#: ../../package-structure-code/declare-dependencies.md:298 +#: ../../package-structure-code/declare-dependencies.md:361 #, fuzzy msgid "**Install dependency groups:**" msgstr "依存グループをインストールする" @@ -1378,22 +1380,41 @@ msgstr "依存グループをインストールする" msgid "Use UV" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:305 +#: ../../package-structure-code/declare-dependencies.md:304 msgid "You can use uv sync to sync dependency groups in your uv-managed venv" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:313 -#: ../../package-structure-code/declare-dependencies.md:334 +#: ../../package-structure-code/declare-dependencies.md:312 +msgid "" +"use ``--active`` with ``uv sync`` to prefer the currently active virtual " +"environment over the project's own managed environment:" +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md:319 +#: ../../package-structure-code/declare-dependencies.md:354 #, fuzzy msgid "**Install optional dependencies:**" msgstr "オプションの依存関係" -#: ../../package-structure-code/declare-dependencies.md:321 +#: ../../package-structure-code/declare-dependencies.md:328 +msgid "" +"Use the `--active` flag with `uv run` to prefer the currently active " +"virtual environment over the project's own managed environment:" +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md:336 +msgid "" +"This is useful when you have activated a virtual environment and want `uv" +" run` to use it instead of automatically creating or selecting the " +"project's environment." +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md:341 #, fuzzy msgid "**Install everything (package + all dependencies):**" msgstr "Pythonパッケージの依存関係" -#: ../../package-structure-code/declare-dependencies.md:327 +#: ../../package-structure-code/declare-dependencies.md:347 msgid "" "`uv sync` is the recommended command for development workflows. It " "manages your virtual environment and keeps your lockfile up to date. Use " @@ -1404,12 +1425,7 @@ msgstr "" msgid "Use pip (version >=25.1)" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:341 -#, fuzzy -msgid "**Install dependency groups:**" -msgstr "依存グループをインストールする" - -#: ../../package-structure-code/declare-dependencies.md:348 +#: ../../package-structure-code/declare-dependencies.md:368 #, fuzzy msgid "" "Always call pip using `python -m pip` to ensure you're using the pip from" @@ -1420,81 +1436,81 @@ msgstr "" "Python 環境のものであることが保証されます。インストールの衝突を避けるために、 `pip` " "を呼び出すときは常にこの方法を使うことを強く推奨します。" -#: ../../package-structure-code/declare-dependencies.md:352 +#: ../../package-structure-code/declare-dependencies.md:372 msgid "" "**Note:** Some shells (like zsh on Mac) require quotes around brackets to" " run successfully:" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:354 +#: ../../package-structure-code/declare-dependencies.md:374 msgid "`python -m pip install \".[tests]\"`" msgstr "`python -m pip install \".[tests]\"`" -#: ../../package-structure-code/declare-dependencies.md:360 +#: ../../package-structure-code/declare-dependencies.md:380 #, fuzzy msgid "Combining dependency groups" msgstr "依存グループをインストールする" -#: ../../package-structure-code/declare-dependencies.md:362 +#: ../../package-structure-code/declare-dependencies.md:382 msgid "You can also create combined groups that reference other groups:" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:371 +#: ../../package-structure-code/declare-dependencies.md:391 msgid "Then install everything with pip install or uv sync as needed:" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:380 +#: ../../package-structure-code/declare-dependencies.md:400 #, fuzzy msgid "" "When you install optional dependencies, pip and uv install your package " "and its core dependencies automatically." msgstr "`pip` はあなたのパッケージとそのコアの依存関係もインストールします。" -#: ../../package-structure-code/declare-dependencies.md:384 +#: ../../package-structure-code/declare-dependencies.md:404 #, fuzzy msgid "Version specifiers for dependencies" msgstr "依存関係のセットを組み合わせる" -#: ../../package-structure-code/declare-dependencies.md:386 +#: ../../package-structure-code/declare-dependencies.md:406 msgid "" "Version specifiers control which versions of a dependency work with your " "package. Use them to specify minimum versions, exclude buggy releases, or" " set version ranges." msgstr "" -#: ../../package-structure-code/declare-dependencies.md:390 +#: ../../package-structure-code/declare-dependencies.md:410 msgid "Common operators" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:392 +#: ../../package-structure-code/declare-dependencies.md:412 msgid "" "**`>=`** Minimum version set: `numpy>=1.20` (This is the most common " "approach and is recommended)" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:393 +#: ../../package-structure-code/declare-dependencies.md:413 msgid "" "**`==`** Exact version: `requests==2.28.0` (Avoid pinning dependencies " "like this unless necessary)" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:394 +#: ../../package-structure-code/declare-dependencies.md:414 msgid "" "**`~=`** Compatible release: `django~=4.2.0` (Allows patches: " ">=4.2.0,<4.3.0)" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:395 +#: ../../package-structure-code/declare-dependencies.md:415 msgid "**`<` or `>`** - Upper/lower bounds: `pandas>=1.0,<3.0`" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:396 +#: ../../package-structure-code/declare-dependencies.md:416 msgid "" "**`!=`** Exclude version: `scipy>=1.7,!=1.8.0` (Rare but allows you to " "skip a buggy release version)" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:399 +#: ../../package-structure-code/declare-dependencies.md:419 msgid "" "**Best practice:** Use `>=` to specify your minimum tested version and " "avoid upper bounds unless you know at what version that dependency is no " @@ -1503,11 +1519,11 @@ msgid "" " dependency conflicts." msgstr "" -#: ../../package-structure-code/declare-dependencies.md:415 +#: ../../package-structure-code/declare-dependencies.md:435 msgid "Using conda and Pixi" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:419 +#: ../../package-structure-code/declare-dependencies.md:439 #, fuzzy msgid "" "The `pyproject.toml` file works great for pure-Python packages. However, " @@ -1519,23 +1535,23 @@ msgstr "" "いくつかのパッケージ、特に科学的なPythonエコシステムでは、Pythonで書かれていない依存関係を必要とします。 " "Condaは、PythonとPython以外の言語の両方で書かれたコードを持つツールの配布をサポートするために作られました。" -#: ../../package-structure-code/declare-dependencies.md:424 +#: ../../package-structure-code/declare-dependencies.md:444 #, fuzzy msgid "**For conda users:**" msgstr "condaユーザーへのメモ" -#: ../../package-structure-code/declare-dependencies.md:426 +#: ../../package-structure-code/declare-dependencies.md:446 msgid "" "You can maintain an `environment.yml` file to help users and contributors" " set up conda environments. This is especially useful for packages with " "system-level dependencies like GDAL." msgstr "" -#: ../../package-structure-code/declare-dependencies.md:430 +#: ../../package-structure-code/declare-dependencies.md:450 msgid "**Consider Pixi for conda package focused workflows:**" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:432 +#: ../../package-structure-code/declare-dependencies.md:452 msgid "" "[Pixi](https://pixi.sh) is a modern package manager built on top of both " "the conda and Python package ecosystems. Pixi is able to treat conda and " @@ -1553,11 +1569,11 @@ msgid "" "workspace with" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:450 +#: ../../package-structure-code/declare-dependencies.md:470 msgid "A note for conda users" msgstr "condaユーザーへのメモ" -#: ../../package-structure-code/declare-dependencies.md:453 +#: ../../package-structure-code/declare-dependencies.md:473 msgid "" "If you use a conda environment for development and install your package " "with `python -m pip install -e .` dependencies will be installed from " @@ -1566,28 +1582,28 @@ msgid "" "dependencies." msgstr "" -#: ../../package-structure-code/declare-dependencies.md:458 +#: ../../package-structure-code/declare-dependencies.md:478 #, fuzzy msgid "To avoid this, install your package without dependencies:" msgstr "`pip` はあなたのパッケージとそのコアの依存関係もインストールします。" -#: ../../package-structure-code/declare-dependencies.md:464 +#: ../../package-structure-code/declare-dependencies.md:484 #, fuzzy msgid "Then install dependencies through your conda `environment.yml` file." msgstr "pyproject.tomlファイルに依存関係を追加" -#: ../../package-structure-code/declare-dependencies.md:467 +#: ../../package-structure-code/declare-dependencies.md:487 msgid "Dependencies in Read the Docs" msgstr "Read the Docs の依存関係" -#: ../../package-structure-code/declare-dependencies.md:469 +#: ../../package-structure-code/declare-dependencies.md:489 #, fuzzy msgid "" "Once you've specified dependencies in your `pyproject.toml`, you can use " "them in other workflows like building documentation on Read the Docs." msgstr "プロジェクトで依存関係を指定できたので、Read the Docsへのパブリッシュなど、他のワークフローをサポートするためにそれらを使用できます。" -#: ../../package-structure-code/declare-dependencies.md:472 +#: ../../package-structure-code/declare-dependencies.md:492 #, fuzzy msgid "" "[Read the Docs](https://readthedocs.org) is a documentation platform that" @@ -1598,16 +1614,16 @@ msgstr "" "[Read the Docs](https://readthedocs.org) " "は、継続的インテグレーション/継続的デプロイメントサービスを備えたドキュメントプラットフォームで、あなたのドキュメントを自動的にビルドして公開します。" -#: ../../package-structure-code/declare-dependencies.md:477 +#: ../../package-structure-code/declare-dependencies.md:497 msgid "Here's an example that installs your `docs` optional dependencies:" msgstr "" -#: ../../package-structure-code/declare-dependencies.md:488 +#: ../../package-structure-code/declare-dependencies.md:508 #, fuzzy msgid "Learn more about Read the Docs" msgstr "flitについてもっと知る" -#: ../../package-structure-code/declare-dependencies.md:491 +#: ../../package-structure-code/declare-dependencies.md:511 #, fuzzy msgid "" "[Creating a readthedocs.yaml file](https://docs.readthedocs.io/en/stable" @@ -1617,7 +1633,7 @@ msgstr "" "ファイルの作成方法についてはこちらをご覧ください。](https://docs.readthedocs.io/en/stable/config-" "file/index.html)" -#: ../../package-structure-code/declare-dependencies.md:492 +#: ../../package-structure-code/declare-dependencies.md:512 #, fuzzy msgid "" "[Using uv with Read the Docs](https://docs.readthedocs.io/en/stable" @@ -1627,7 +1643,7 @@ msgstr "" "ファイルの作成方法についてはこちらをご覧ください。](https://docs.readthedocs.io/en/stable/config-" "file/index.html)" -#: ../../package-structure-code/declare-dependencies.md:493 +#: ../../package-structure-code/declare-dependencies.md:513 #, fuzzy msgid "" "[Using Poetry with Read the Docs](https://docs.readthedocs.io/en/stable" @@ -1637,7 +1653,7 @@ msgstr "" "[こちらで詳しく説明されています。](https://docs.readthedocs.io/en/stable/build-" "customization.html#install-dependencies-with-poetry)" -#: ../../package-structure-code/declare-dependencies.md:498 +#: ../../package-structure-code/declare-dependencies.md:518 #, fuzzy msgid "" "Keep this comment - `pandas 3.X.X`)" +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md:691 +#, fuzzy +msgid "new transitive dependencies (i.e. not part of your `pyproject.toml`)" +msgstr "pyproject.tomlファイルに依存関係を追加" + +#: ../../package-structure-code/declare-dependencies.md:694 +msgid "" +"A lock file captures one environment for CI testing, not the full " +"compatibility range declared in `pyproject.toml`. Projects that use lock " +"files may want to have CI test other environments such as" +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md:698 +msgid "" +"the latest packages consistent with your `pyproject.toml`, subject to " +"dependency cooldowns. This lets you know if a dependency update breaks " +"your package." +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md:701 +msgid "" +"older supported versions of Python to let you know if a recent change to " +"your package no longer works with an older Python release." +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md +msgid "What about `requirements.txt`" +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md:712 +msgid "" +"Older approaches to locking used `pip freeze` to generate a " +"`requirements.txt` that got used as a lock file. These are minimal lock " +"files that pin a specific version for the system on which the command was" +" run. They might look like" +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md:722 +msgid "" +"However, this minimal level of specificity has several downsides making " +"lock files the preferred format:" +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md:724 +msgid "" +"The versions satisfying `pyproject.toml` may differ between your Windows " +"laptop and the Linux server your CI runs on. A single lock file contains " +"the information needed to build platform specific and Python version " +"specific environments. In contrast, a separate `requirements.txt` files " +"is needed to store this information (e.g. `requirements.ci.txt`, " +"`requirements.py313-macos.txt`)" +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md:730 +msgid "" +"Packages can get updated without a version update for both legitimate and" +" malicious reasons. Lock files include package hashes to catch this. A " +"[hash](https://en.wikipedia.org/wiki/Hash_function) is a unique signature" +" computed from the code and any change to the code will cause the release" +" to have a different hash even if is given the same release version " +"number." +msgstr "" + +#: ../../package-structure-code/declare-dependencies.md:736 +msgid "" +"Other metadata determined during resolution of `pyproject.toml` (e.g. " +"which dependencies are transitive, where the packages were downloaded " +"from, etc.) that can help speed up future installs is lost." +msgstr "" + #: ../../package-structure-code/intro.md:163 msgid "Intro" msgstr "イントロ" @@ -6451,13 +6784,13 @@ msgstr "" #~ "the `project` table of your " #~ "`pyproject.toml` file. If they are " #~ "optional, they will be listed in " -#~ "the `[project.optional-dependencies]` table of your" -#~ " `pyproject.toml`." +#~ "the `[project.optional-dependencies]` table of" +#~ " your `pyproject.toml`." #~ msgstr "" #~ "依存関係はオプションか必須であると考えることができます。 必須であれば、 `pyproject` " #~ "テーブルの `dependencies` キーにリストされます。 オプションの場合は、 " -#~ "`pyproject.toml` の `[project.optional-dependencies]` " -#~ "テーブルにリストされます。" +#~ "`pyproject.toml` の `[project.optional-dependencies]`" +#~ " テーブルにリストされます。" #~ msgid "You will learn about both below." #~ msgstr "両者については後述します。" @@ -7506,3 +7839,14 @@ msgstr "" #~ " src/package directory (see example below)." #~ " ```bash src/ package/ tests/ docs/" #~ msgstr "" + +#~ msgid "" +#~ "**Feature Dependencies:** These are " +#~ "dependencies that are required if a " +#~ "user wants to access additional " +#~ "functionality (that is not core) to " +#~ "your package. Store these in the " +#~ "`[project.optional-dependencies]` table of " +#~ "your pyproject.toml file." +#~ msgstr "" +