Skip to content

Update Japanese translation files #602

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
tkoyama010 wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Update Japanese translation files #602

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f45549c
Update Japanese translation files
tkoyama010 Jan 4, 2026
177af25
'[pre-commit.ci 🤖] Apply code format tools to PR'
pre-commit-ci[bot] Jan 4, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
131 changes: 71 additions & 60 deletions locales/ja/LC_MESSAGES/CONTRIBUTING.po
View file
Open in desktop

Large diffs are not rendered by default.

105 changes: 87 additions & 18 deletions locales/ja/LC_MESSAGES/documentation.po
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,7 +11,7 @@ msgid ""
msgstr ""
"Project-Id-Version: pyOpenSci Python Package Guide\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2025-07-12 11:17+0200\n"
"POT-Creation-Date: 2026-01-04 09:59+0900\n"
"PO-Revision-Date: 2025-04-14 18:12+0000\n"
"Last-Translator: Tetsuo Koyama <[email protected]>, 2025\n"
"Language: ja\n"
Expand Down Expand Up @@ -219,12 +219,13 @@ msgid "What is GitHub Pages?"
msgstr "GitHub Pagesとは？"

#: ../../documentation/hosting-tools/publish-documentation-online.md:25
#, fuzzy
msgid ""
"[GitHub Pages](https://docs.github.com/en/pages/getting-started-with-"
"github-pages/about-github-pages) is a free web hosting service offered by"
" GitHub. Using GitHub pages, you can build your documentation locally or "
"using a Continuous Integration setup, and then push to a branch in your "
"GitHub repository that is setup to run the GitHub Pages web build."
"github-pages/what-is-github-pages) is a free web hosting service offered "
"by GitHub. Using GitHub pages, you can build your documentation locally "
"or using a Continuous Integration setup, and then push to a branch in "
"your GitHub repository that is setup to run the GitHub Pages web build."
msgstr ""
"[GitHub Pages](https://docs.github.com/en/pages/getting-started-with-"
"github-pages/about-github-pages) は GitHub が提供する無料のウェブホスティングサービスです。 GitHub"
Expand Down Expand Up @@ -1639,10 +1640,11 @@ msgid "Use open permissive licenses when possible"
msgstr "可能な限りオープンパーミッシブライセンスを使用する"

#: ../../documentation/repository-files/license-files.md:46
#, fuzzy
msgid ""
"We generally suggest that you use a permissive, license that is [Open "
"Software Initiative (OSI) approved](https://opensource.org/licenses/). If"
" you are [submitting your package to pyOpenSci for peer "
"Software Initiative (OSI) approved](https://opensource.org/license). If "
"you are [submitting your package to pyOpenSci for peer "
"review](https://www.pyopensci.org/about-peer-review/index.html), then we "
"require an OSI approved license."
msgstr ""
Expand Down Expand Up @@ -1900,22 +1902,85 @@ msgid "What about software citation?"
msgstr "ソフトウェアの引用についてはどうだろうか？"

#: ../../documentation/repository-files/license-files.md:133
#, fuzzy
msgid ""
"While many permissive licenses do not require citation we STRONG "
"encourage that you cite all software that you use in papers, blogs and "
"While many permissive licenses do not require citation, we strongly "
"encourage that you cite all software that you use in papers, blogs, and "
"other publications. You tell your users how to cite your package by using"
" a [citation.cff file](https://docs.github.com/en/repositories/managing-"
"your-repositorys-settings-and-features/customizing-your-repository/about-"
"citation-files). We will cover this topic when we talk about creating "
"DOI's for your package using Zenodo."
"citation-files)."
msgstr ""
"多くの寛容なライセンスは引用を必要としませんが、わたしたちは、あなたが論文やブログ、その他の出版物で使用するすべてのソフトウェアを引用することを強く推奨します。"
" あなたは、 [citation.cff ファイル](https://docs.github.com/en/repositories"
"/managing-your-repositorys-settings-and-features/customizing-your-"
"repository/about-citation-files) を使うことで、あなたのパッケージの引用方法をユーザに伝えることができます。 "
"このトピックについては、Zenodoを使ってパッケージのDOIを作成する際に説明します。"

#: ../../documentation/repository-files/license-files.md:135
msgid "Citation.cff files: Making your software citable"
msgstr ""

#: ../../documentation/repository-files/license-files.md:137
msgid ""
"A `CITATION.cff` file is a machine-readable file that provides citation "
"information for your software package. The \"cff\" stands for \"Citation "
"File Format,\" which is a standardized format for software citation "
"metadata."
msgstr ""

#: ../../documentation/repository-files/license-files.md:139
msgid "What citation.cff files add to your repository"
msgstr ""

#: ../../documentation/repository-files/license-files.md:141
msgid ""
"When you add a `CITATION.cff` file to your repository, GitHub "
"automatically detects it and displays a \"Cite this repository\" button. "
"This makes it easy for users to properly cite your software. The file "
"contains standardized citation information that tools and services can "
"automatically read and use. GitHub will generate both APA and BibTeX "
"citation formats for users."
msgstr ""

#: ../../documentation/repository-files/license-files.md:143
msgid "How dates are tracked in citation.cff files"
msgstr ""

#: ../../documentation/repository-files/license-files.md:145
msgid ""
"The citation file tracks important dates for your software. The `date-"
"released` field shows when the current version was released. The `date-"
"published` field shows when the software was first made available. You "
"also include a `version` field with the specific version number."
msgstr ""

#: ../../documentation/repository-files/license-files.md:147
msgid ""
"You should update these dates with each new release so people cite the "
"correct version of your software."
msgstr ""

#: ../../documentation/repository-files/license-files.md:149
msgid "Integration with Zenodo"
msgstr ""

#: ../../documentation/repository-files/license-files.md:151
msgid ""
"Citation.cff files work well with Zenodo, which is a popular place to "
"store research software and get DOIs. When you create a Zenodo release, "
"it can automatically pull information from your citation file. This keeps"
" your citation information the same between GitHub and Zenodo. You can "
"also include your Zenodo DOI in the citation file. Each time you make a "
"new GitHub release, it can create a new Zenodo version with updated "
"citation information."
msgstr ""

#: ../../documentation/repository-files/license-files.md:154
msgid "Here's a basic example of what a `CITATION.cff` file might look like:"
msgstr ""

#: ../../documentation/repository-files/license-files.md:170
msgid "References"
msgstr "参考文献"

Expand Down Expand Up @@ -2076,12 +2141,13 @@ msgid "PyPI version shields.io"
msgstr "PyPIバージョン shields.io"

#: ../../documentation/repository-files/readme-file-best-practices.md:78
#, fuzzy
msgid ""
"Status of tests (pass or fail) - Example: [![CI Build](https://github.com"
"/pandera-"
"dev/pandera/workflows/CI%20Tests/badge.svg?branch=main)](https://github.com"
"/pandera-"
"dev/pandera/actions?query=workflow%3A%22CI+Tests%22+branch%3Amain)"
"/unionai-"
"oss/pandera/workflows/CI%20Tests/badge.svg?branch=main)](https://github.com"
"/unionai-"
"oss/pandera/actions?query=workflow%3A%22CI+Tests%22+branch%3Amain)"
msgstr ""
"テストのステータス(合格または不合格) - 例: [![CI Build](https://github.com/pandera-"
"dev/pandera/workflows/CI%20Tests/badge.svg?branch=main)](https://github.com"
Expand Down Expand Up @@ -2118,15 +2184,18 @@ msgid "DOI"
msgstr "DOI"

#: ../../documentation/repository-files/readme-file-best-practices.md:85
#, fuzzy
msgid ""
"Once you package is accepted to pyOpenSci, we will provide you with a "
"badge to add to your repository that shows that it has been reviewed. "
"[![pyOpenSci](https://pyopensci.org/badges/peer-"
"reviewed.svg)](https://github.com/pyOpenSci/software-submission/issues/12)"
"[![pyOpenSci](https://www.pyopensci.org/badges/peer-"
"reviewed.svg)](https://github.com/pyOpenSci/software-"
"submission/issues/12)"
msgstr ""
"あなたのパッケージがpyOpenSciに受理されると、あなたのリポジトリにレビュー済みであることを示すバッジを提供します。 "
"[![pyOpenSci](https://pyopensci.org/badges/peer-"
"reviewed.svg)](https://github.com/pyOpenSci/software-submission/issues/12)"
"reviewed.svg)](https://github.com/pyOpenSci/software-"
"submission/issues/12)"

#: ../../documentation/repository-files/readme-file-best-practices.md:85
msgid "pyOpenSci"
Expand Down
Loading
Loading