Welcome to the Git manpages translation project

This project is not about translating Git itself. Unfortunately, Git does not use Weblate and relies on direct use of po files and Git. If you are up to the task, please refer to the specific instructions.

Helpful Tips

Anyway, Git is a version control system (VCS in short) and this kind of software expects users to understand some dedicated concepts. More generally, translating a tool requires at least a minimum of knowledge of its purpose and use. Git is no exception, and its manpages are full of its specifics.

Here are a few helpful advices in order to help you work through this translation.

Know a little more about Git

As said earlier, knowing the base of Git is necessary in order to prevent mistranslations. Even if you are not going to be an expert at Git (you could, given the content of the manpages), you can try to install it and make a basic use of it. To get you started, please refer to the introductory chapters of the Progit book, at least the first three chapters.

Set up a glossary of the key concepts

When translating a software where some words have been chosen to hold some key concepts, it is often necessary to maintain a list of the selected translation of these words, that convey the concept correctly and are used in every place the original word is used.

Git provides a glossary with definitions and Weblate has a glossary feature where a reminder is shown when a glossary term appears in the original string. This is an excellent way to enhance the quality of the translation, while helping translators share the same vocabulary.

Translate placeholders in command lines

When some template command lines contain <terms-in-brackets>, it is helpful for the reader that these terms are translated in their language and used repeatedly (use the glossary for that).

Translate in order

If you don't specify an order on Weblate, the source segments are presented in the order priority, which places in first the content of most used git commands. The corresponding manpages are more susceptible to be read by beginners. So your work has the biggest impact right when starting.

Get in touch the maintainer

In case you need to contact the maintainer for e.g. an issue in a source string or an issue with the translated manpages, the project is hosted on GitHub where issues can be opened.

Contribution to this translation requires you to agree with a contributor agreement.
Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English This language is used for source strings. GPL-2.0 0 0 0 0 5,008 0 2
Chinese (Simplified) GPL-2.0 24% 8,157 179,839 1,150,588 6,134 1,959 1,375 6
Chinese (Traditional) GPL-2.0 14% 9,314 208,658 1,330,734 9,191 13 0 1
Dutch GPL-2.0 13% 9,350 209,314 1,334,889 9,101 29 0 0
French GPL-2.0 65% 3,766 90,886 577,767 3,766 0 0 0
German GPL-2.0 29% 7,594 184,044 1,171,738 7,114 158 11 6
Hungarian GPL-2.0 13% 9,363 209,328 1,335,001 9,282 9 0 0
Icelandic GPL-2.0 16% 9,048 202,870 1,293,567 8,994 14 0 0
Indonesian GPL-2.0 14% 9,259 208,905 1,330,279 9,179 39 0 0
Italian GPL-2.0 13% 9,337 209,026 1,333,028 8,366 720 2 0
Japanese GPL-2.0 20% 8,624 197,380 1,254,367 8,624 0 0 2
Korean GPL-2.0 13% 9,350 209,265 1,334,446 9,283 7 0 0
Marathi GPL-2.0 13% 9,351 209,291 1,334,699 9,279 8 0 0
Norwegian Bokmål GPL-2.0 13% 9,364 209,329 1,335,028 9,252 11 0 0
Polish GPL-2.0 14% 9,292 208,980 1,333,010 9,137 80 164 0
Portuguese (Brazil) GPL-2.0 0 0 0 0 0 0 0
Portuguese (Portugal) GPL-2.0 13% 9,364 209,329 1,335,028 9,244 14 0 0
Romanian GPL-2.0 17% 8,907 200,419 1,278,168 8,875 38 0 1
Russian GPL-2.0 16% 9,055 206,124 1,314,355 8,663 194 2 2
Slovak GPL-2.0 13% 9,364 209,329 1,335,028 9,342 0 0 0
Spanish GPL-2.0 17% 8,974 207,104 1,319,148 8,688 124 0 0
Spanish (Mexico) GPL-2.0 13% 9,336 208,917 1,332,662 8,823 269 1 0
Turkish GPL-2.0 15% 9,182 208,172 1,326,749 9,162 0 0 0
Ukrainian GPL-2.0 13% 9,348 209,299 1,334,790 9,332 1 0 0
Please sign in to see the alerts.

Overview

Project website git-scm.com
Project maintainers User avatar jnavila
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Translation license GNU General Public License v2.0 only
Contributor agreement

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

a. The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or

b. The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or

c. The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.

d. I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
Source code repository https://github.com/jnavila/git-manpages-l10n
Repository branch master
Last remote commit update priorities in translated files 6780a46
User avatar jnavila authored 3 weeks ago
Last commit in Weblate Translated using Weblate (Japanese) 6fce701
User avatar yajamon authored 10 hours ago
Weblate repository https://hosted.weblate.org/git/git-manpages/translations/
File mask po/documentation.*.po

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 260,136 5,060,760 32,574,624
Source 10,839 210,865 1,357,276
Translated 25% 65,437 13% 664,952 13% 4,549,555
Needs editing 2% 5,868 1% 49,200 1% 363,227
Read-only 4% 10,839 4% 210,865 4% 1,357,276
Failing checks 3% 8,695 2% 144,874 2% 954,702
Strings with suggestions 1% 1,555 1% 8,949 1% 71,142
Untranslated strings 72% 188,831 85% 4,346,608 84% 27,661,842
Last 12 months Previous

Activity in last 12 months

6,770 changes 2,034 changes 5,574 changes 116 changes 1,013 changes 511 changes 539 changes 290 changes 130 changes 203 changes 1,469 changes 324 changes 4,864 changes 1,129 changes 926 changes 239 changes 90 changes 1,032 changes 936 changes 75 changes 638 changes 48 changes 271 changes 21,924 changes
May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr

Quick numbers

5,060 k
Hosted words
260 k
Hosted strings
25%
Translated
6
Contributors
and previous 30 days

Trends of last 30 days

—
Hosted words
+1%
—
Hosted strings
+1%
+1%
Translated
—
+16%
Contributors
+60%
User avatar yajamon

New translation

Git Manpages / Translations — Japanese

During the normal execution of several Git commands, call-outs are made to optional scripts that allow a developer to add functionality or checking. Typically, the hooks allow for a command to be pre-verified and potentially aborted, and allow for a post-notification after the operation is done. The hook scripts are found in the `$GIT_DIR/hooks/` directory, and are enabled by simply removing the `.sample` suffix from the filename. In earlier versions of Git you had to make them executable.
Gitコマンドの通常の実行中に、開発者が機能やチェックを追加するためのオプションのスクリプトを呼び出すことができます。典型的には、フックはコマンドの事前検証をして中止を可能にし、操作の終了後に事後通知を可能にします。フックスクリプトは `$GIT_DIR/hooks/` ディレクトリにあり、ファイル名から `.sample` というサフィックスを取り除くだけで有効になります。以前のバージョンのGitでは、それらを実行可能にする必要がありました。
6 hours ago
User avatar yajamon

New translation

Git Manpages / Translations — Japanese

[[def_hook]]hook
[[def_hook]]フック (hook)
6 hours ago
User avatar yajamon

New translation

Git Manpages / Translations — Japanese

[[def_head_ref]]head ref
[[def_head_ref]]ヘッド参照 (head ref)
6 hours ago
User avatar yajamon

New translation

Git Manpages / Translations — Japanese

The current <<def_branch,branch>>. In more detail: Your <<def_working_tree, working tree>> is normally derived from the state of the tree referred to by HEAD. HEAD is a reference to one of the <<def_head,heads>> in your repository, except when using a <<def_detached_HEAD,detached HEAD>>, in which case it directly references an arbitrary commit.
現在の <<def_branch,branch>>。 詳細: <<def_working_tree,ワーキングツリー>> は通常、HEADによって参照されるツリーの状態から派生します。 HEADはリポジトリ内の <<def_head,ヘッド>> の1つを参照するものですが、 << def_detached_HEAD,分離したHEAD>> を使用する場合は、任意のコミットを直接参照します。
6 hours ago
User avatar yajamon

New translation

Git Manpages / Translations — Japanese

[[def_HEAD]]HEAD
[[def_HEAD]]HEAD
6 hours ago
User avatar yajamon

New translation

Git Manpages / Translations — Japanese

A <<def_ref,named reference>> to the <<def_commit,commit>> at the tip of a <<def_branch,branch>>. Heads are stored in a file in `$GIT_DIR/refs/heads/` directory, except when using packed refs. (See linkgit:git-pack-refs[1].)
<<def_ref,名前付き参照>> の先端にある <<def_commit,コミット>> のことです。 ヘッダは、固めた参照を使うとき以外は、 `$GIT_DIR/refs/heads/` ディレクトリにあるファイルに格納されます。(linkgit:git-pack-refs[1] を参照してください。)
6 hours ago
User avatar yajamon

New translation

Git Manpages / Translations — Japanese

[[def_head]]head
[[def_head]]ヘッド (head)
6 hours ago
User avatar yajamon

New translation

Git Manpages / Translations — Japanese

In Git's context, synonym for <<def_object_name,object name>>.
Git の文脈では、 <<def_object_name,オブジェクト名>> の同義語です。
6 hours ago
User avatar yajamon

New translation

Git Manpages / Translations — Japanese

[[def_hash]]hash
[[def_hash]]ハッシュ (hash)
7 hours ago
User avatar yajamon

New translation

Git Manpages / Translations — Japanese

Note that the grafts mechanism is outdated and can lead to problems transferring objects between repositories; see linkgit:git-replace[1] for a more flexible and robust system to do the same thing.
移植 の仕組みは時代遅れで、リポジトリ間でオブジェクトを転送する際に問題になる場合があることに注意してください。同じことを行うためのより柔軟で堅牢なシステムについては linkgit:git-replace[1] をご覧ください。
9 hours ago
Browse all component changes