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.

Dear fellow Git translator,

I skipped the v2.45 release, sorry for that.

Now, a new release of Git is coming soon, v2.46.0. The strings are frozen, and the release candidate 0 has been tagged. It's time to update your translations.

In addition to upstream updates, this new release brings a lot a changes which are partly due to the work on the source documentation that I brought in v2.45. Namely:

Contributing to this translation requires agreeing to its contributor agreement.

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 update po files with v2.46.0 d63f0c4
User avatar jnavila authored 9 days ago
Last commit in Weblate Translated using Weblate (French) 3dd2f5d
User avatar jnavila authored yesterday
Weblate repository https://hosted.weblate.org/git/git-manpages/translations/
File mask po/documentation.*.po
Translation file Download po/documentation.es.po
Last change July 15, 2024, 10:18 p.m.
Last author None
yesterday

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 11,563 225,910 1,455,824
Translated 30% 3,472 12% 29,043 14% 207,232
Needs editing 1% 153 1% 2,575 1% 19,239
Read-only 0% 0 0% 0 0% 0
Failing checks 1% 56 1% 769 1% 6,564
Strings with suggestions 1% 2 1% 41 1% 309
Untranslated strings 68% 7,938 86% 194,292 84% 1,229,353

Quick numbers

225 k
Hosted words
11,563
Hosted strings
30%
Translated
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
+1%
Hosted strings
+100%
−1%
Translated
+31%
−100%
Contributors
+100%
User avatar None

Resource updated

The “po/documentation.es.po” file was changed. 9 days ago
User avatar None

String added in the repository

9 days ago
User avatar None

Source string changed

9 days ago
User avatar None

String added in the repository

9 days ago
User avatar None

Source string changed

9 days ago
User avatar None

String added in the repository

9 days ago
User avatar None

Source string changed

9 days ago
User avatar None

String added in the repository

9 days ago
User avatar None

Source string changed

9 days ago
User avatar None

String added in the repository

9 days ago
Browse all translation changes