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.

Contributing to this translation requires agreeing to its contributor agreement.
Language Translated Unfinished Unfinished words Unfinished characters Untranslated Checks Suggestions Comments
English GPL-2.0 0 0 0 0 3,581 0 2
Chinese (Simplified Han script) GPL-2.0 97% 290 7,006 51,605 0 126 0 8
Chinese (Traditional Han script) GPL-2.0 19% 9,318 221,169 1,406,363 9,051 135 0 1
Dutch GPL-2.0 14% 9,951 224,810 1,434,855 9,490 221 0 0
French GPL-2.0 80% 2,288 57,232 358,072 2,288 0 0 0
German GPL-2.0 26% 8,561 211,655 1,347,286 7,390 496 8 2
Hungarian GPL-2.0 14% 9,961 224,821 1,434,949 9,780 85 0 0
Icelandic GPL-2.0 15% 9,786 222,435 1,419,647 9,352 171 0 0
Indonesian GPL-2.0 15% 9,835 224,373 1,430,295 9,180 475 0 0
Italian GPL-2.0 14% 9,865 223,794 1,427,031 8,640 622 1 0
Japanese GPL-2.0 22% 8,950 209,267 1,328,597 8,778 71 0 2
Korean GPL-2.0 17% 9,530 219,585 1,396,150 8,912 415 0 0
Marathi GPL-2.0 14% 9,949 224,784 1,434,647 9,763 86 0 0
Norwegian Bokmål GPL-2.0 14% 9,962 224,822 1,434,976 9,748 99 0 0
Polish GPL-2.0 14% 9,889 224,626 1,433,820 9,135 494 155 0
Portuguese (Brazil) GPL-2.0 96% 409 10,391 73,132 122 122 0 0
Portuguese (Portugal) GPL-2.0 14% 9,962 224,822 1,434,976 9,744 92 0 0
Romanian GPL-2.0 16% 9,681 221,369 1,412,520 9,233 162 0 1
Russian GPL-2.0 16% 9,682 222,774 1,420,885 9,007 393 3 1
Slovak GPL-2.0 14% 9,962 224,822 1,434,976 9,839 50 0 0
Spanish GPL-2.0 31% 7,902 193,255 1,223,774 7,895 4 0 0
Spanish (Mexico) GPL-2.0 14% 9,938 224,698 1,434,196 9,282 462 1 0
Turkish GPL-2.0 15% 9,804 223,953 1,428,571 9,523 112 0 0
Ukrainian GPL-2.0 14% 9,890 223,572 1,427,167 9,757 56 0 0
Vietnamese GPL-2.0 14% 9,933 224,726 1,434,219 9,367 414 0 0
Please sign in to see the alerts.

Overview

Project website git-scm.com
Project maintainers User avatar jnavila
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.
Translation process
  • Translations can be made directly.
  • Translation suggestions can be made.
  • Any authenticated user can contribute.
  • The translation uses bilingual files.
Source code repository https://github.com/jnavila/git-manpages-l10n
Repository branch master
Last remote commit Merge pull request #118 from jnavila/update_ghactions 0c92843
User avatar jnavila authored 2 days ago
Last commit in Weblate Merge branch 'origin/master' into Weblate. ca034db
Hosted Weblate authored 2 days ago
Weblate repository https://hosted.weblate.org/git/git-manpages/translations/
File mask po/documentation.*.po
2 days ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 289,800 5,662,900 36,502,700
Source 11,592 226,516 1,460,108
Translated 29% 84,502 16% 948,139 17% 6,439,991
Needs editing 3% 10,022 1% 98,055 1% 701,573
Read-only 4% 11,592 4% 226,516 4% 1,460,108
Failing checks 3% 8,944 2% 123,547 2% 856,914
Strings with suggestions 1% 168 1% 710 1% 5,592
Untranslated strings 67% 195,276 81% 4,616,706 80% 29,361,136
Last 12 months Previous

Activity in last 12 months

126,798 changes 11,660 changes 149 changes 21,176 changes 9 changes 1,513 changes 3,891 changes 228,339 changes 396 changes 78,062 changes 370 changes 121 changes 6,672 changes 3,064 changes 2,330 changes 199 changes 822 changes 64,568 changes 6,971 changes 136 changes 261 changes 13,065 changes 937 changes 146 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

5,662 k
Hosted words
289 k
Hosted strings
29%
Translated
4
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
+1%
Hosted strings
+100%
—
Translated
+29%
+25%
Contributors
+100%
User avatar None

Repository merged
Repository merged

Original revision: e68dc3ae4be2d93282ddbe667d8d952c93a4df7e
New revision: ca034dbfa37d90c2f266f5b82ed6e0a6adb87c8c 2 days ago
User avatar None

Changes committed
Changes committed 2 days ago
User avatar None

Repository notification received
GitHub: https://github.com/jnavila/git-manpages-l10n, master 2 days ago
User avatar None

Repository notification received
GitHub: https://github.com/jnavila/git-manpages-l10n, master 2 days ago
User avatar wujianbo

Translation changed
As a special case, you may use `A...B` as a shortcut for the merge base of `A` and `B` if there is exactly one merge base. You can leave out at most one of `A` and `B`, in which case it defaults to `HEAD`.
作为一种特殊情况，如果正好有一个合并基础，你可以使用 `A...B` 作为 `A`和 和 `B` 的合并基础的快捷方式。你最多可以省略在 `A`和 和 `B` 中默认为 `HEAD` 的一个分支。
3 days ago
User avatar wujianbo

Translation changed
You can use the `@{-N}` syntax to refer to the N-th last branch/commit checked out using "git checkout" operation. You may also specify `-` which is synonymous to `@{-1}`.
你可以使用 `@{-N}` 语法来指代使用 "git checkout "操作检查出来的第N个最后的分支或是提交。你也可以指定 `-`，它与 `@{-1}` 同义。
3 days ago
User avatar wujianbo

Translation changed
Branch to checkout; if it refers to a branch (i.e., a name that, when prepended with "refs/heads/", is a valid ref), then that branch is checked out. Otherwise, if it refers to a valid commit, your `HEAD` becomes "detached" and you are no longer on any branch (see below for details).
签出的分支；如果它指的是一个分支（即一个名字，在前面加上 "refs/heads/"时，是一个有效的 引用），那么这个分支就被签出。否则，如果它指的是一个有效的提交，你的 `HEAD` 就会"分离"，此时，你就不再在任何一个分支上了（详见下文）。
3 days ago
User avatar wujianbo

Translation changed
In the default overlay mode, `git checkout` never removes files from the index or the working tree. When specifying `--no-overlay`, files that appear in the index and working tree, but not in `<tree-ish>` are removed, to make them match `<tree-ish>` exactly.
在默认的覆盖模式下，`git checkout` 不会从索引或工作区中删除文件。 当指定 `--no-overlay` 时，出现在索引和工作区中，但不在 `<树状对象>` 中的文件会被删除，以使它们与 `<树状对象>` 完全匹配。
3 days ago
User avatar wujianbo

Translation changed
Using `--recurse-submodules` will update the content of all active submodules according to the commit recorded in the superproject. If local modifications in a submodule would be overwritten the checkout will fail unless `-f` is used. If nothing (or `--no-recurse-submodules`) is used, submodules working trees will not be updated. Just like linkgit:git-submodule[1], this will detach `HEAD` of the submodule.
使用 `--recurse-submodules` 将根据父项目的提交记录更新所有活动的子模块的内容。如果子模块中的本地修改会被覆盖，除非使用 `-f` ，则会签出将失败。如果什么都不使用（或 `--no-recurse-submodules` ），子模块的工作区将不会被更新。 就像linkgit:git-submodule[1]，这将分离子模块的 `HEAD` 。
3 days ago
User avatar wujianbo

Translation changed
Using `--recurse-submodules` will update the content of all active submodules according to the commit recorded in the superproject. If local modifications in a submodule would be overwritten the checkout will fail unless `-f` is used. If nothing (or `--no-recurse-submodules`) is used, submodules working trees will not be updated. Just like linkgit:git-submodule[1], this will detach `HEAD` of the submodule.
使用 `--recurse-submodules` 将根据父项目的提交记录更新所有活动的子模块的内容。如果子模块中的本地修改会被覆盖，除非使用 `-f` ，则会签出将失败。如果什么都不使用（或 `--no-recurse-submodules` ），子模块的工作区将不会被更新。 就像linkgit:git-submodule[1]，这将分离子模块的`HEAD`。
3 days ago
Browse all component changes