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.
Strings Words Characters | |||
---|---|---|---|
11,693 227,113 1,464,291 |
|
All strings | Browse Translate Zen |
11,693 227,113 1,464,291 |
|
Read-only strings | Browse Translate Zen |
3,636 78,323 509,271 |
|
Strings with any failing checks | Browse Translate Zen |
1 1 27 |
|
Translated strings with dismissed checks | Browse Translate Zen |
32 1,112 6,816 |
|
Failing check: Unpluralised | Browse Translate Zen |
322 8,521 63,962 |
|
Failing check: Ellipsis | Browse Translate Zen |
1,331 16,128 121,739 |
|
Failing check: Multiple failing checks | Browse Translate Zen |
2,271 60,001 375,931 |
|
Failing check: Long untranslated | Browse Translate Zen |
41 1,434 9,090 |
|
Strings with comments | Browse Translate Zen |
11,693 227,113 1,464,291 |
|
Strings without a label | Browse Translate Zen |
Overview
Project website | git-scm.com | |
---|---|---|
Project maintainers | 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 |
|
|
Source code repository |
https://github.com/jnavila/git-manpages-l10n
|
|
Repository branch | master | |
Last remote commit |
Translated using Weblate (Russian)
79dfec5
Fat-Zer authored 5 days ago |
|
Last commit in Weblate |
Translated using Weblate (Russian)
14ef035
Fat-Zer authored 12 hours ago |
|
Weblate repository |
https://hosted.weblate.org/git/git-manpages/translations/
|
|
File mask |
po/documentation.*.po
|
|
Translation file |
Download
po/documentation.pot
|
|
Last change | Jan. 17, 2025, 3:04 a.m. | |
Last change made by | Golubev Alexander | |
Language | English | |
Language code | en | |
Text direction | Left to right | |
Number of speakers | 1,728,900,209 | |
Number of plurals | 2 | |
Plural type | One/other | |
Plurals | Singular | 1 | Plural | 0, 2, 3, 4, 5, 6, 7, 8, 9, 10, … |
Plural formula |
n != 1
|
String statistics
Strings percent | Hosted strings | Words percent | Hosted words | Characters percent | Hosted characters | |
---|---|---|---|---|---|---|
Total | 11,693 | 227,113 | 1,464,291 | |||
Translated | 100% | 11,693 | 100% | 227,113 | 100% | 1,464,291 |
Needs editing | 0% | 0 | 0% | 0 | 0% | 0 |
Read-only | 100% | 11,693 | 100% | 227,113 | 100% | 1,464,291 |
Failing checks | 31% | 3,636 | 34% | 78,323 | 34% | 509,271 |
Strings with suggestions | 0% | 0 | 0% | 0 | 0% | 0 |
Untranslated strings | 0% | 0 | 0% | 0 | 0% | 0 |
Quick numbers
Trends of last 30 days
Fat-Zer
Comment added |
|
Fat-Zer
Comment added |
in the neighboring string for man git-log |
Fat-Zer
Comment added |
Note: May be they should be wrapped in back-ticks rather than quotes. 2 days ago |
Fat-Zer
Comment added |
Any idea what it actually does? I don't see any changes in the output with |
Fat-Zer
Comment removed |
Same as previous one, should probably be:
5 days ago
|
Fat-Zer
Comment removed |
I was wrong about my assessments that the example was incorrect; I'm removing my comments 5 days ago |
Fat-Zer
Comment added |
I was wrong about my assessments that the example was incorrect; I'm removing my comments 5 days ago |
Fat-Zer
Comment removed |
I was wrong about my assessments that the example was incorrect; I'm removing my comments 5 days ago |
Fat-Zer
Comment removed |
Shouldn't this one be:
?? Notice remove of |
Fat-Zer
Comment added |
I was wrong about my assessments that the example was incorrect; I'm removing my comments 5 days ago |
11,693 | File in original format as translated in the repository | gettext PO file | |||||||
---|---|---|---|---|---|---|---|---|---|
11,693 | All strings, converted files enriched with comments; suitable for offline translation | CSV | gettext MO | gettext PO | TBX | TMX | XLIFF 1.1 with gettext extensions | XLIFF 1.1 | XLSX |
diff-tree here seems to refer to
yesterdaygit diff-tree
and probably should be marked with some formatting. back-ticks?