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.

Translation status

11,592 Strings 80%
Browse Translate
226,516 Words 74%
1,460,108 Characters 75%

Strings status

Strings Words Characters
11,592 226,516 1,460,108
All strings Browse Translate Zen
9,317 169,756 1,104,995
Translated strings Browse Translate Zen
2,275 56,760 355,113
Unfinished strings Browse Translate Zen
2,275 56,760 355,113
Untranslated strings Browse Translate Zen
2,275 56,760 355,113
Unfinished strings without suggestions Browse Translate Zen
245 3,575 25,719
Translated strings with dismissed checks Browse Translate Zen

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 weeks ago
Last commit in Weblate Translated using Weblate (French) 3a74598
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.fr.po
Last change Nov. 16, 2024, 10:52 p.m.
Last change made by Jean-Noël Avila
Language French
Language code fr
Text direction Left to right
Number of speakers 295,510,923
Number of plurals 2
Plural type One/other
Plurals Singular 0, 1
Plural 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, …
Plural formula n > 1
17 hours ago

String statistics

Strings percent Hosted strings Words percent Hosted words Characters percent Hosted characters
Total 11,592 226,516 1,460,108
Translated 80% 9,317 74% 169,756 75% 1,104,995
Needs editing 0% 0 0% 0 0% 0
Read-only 0% 0 0% 0 0% 0
Failing checks 0% 0 0% 0 0% 0
Strings with suggestions 0% 0 0% 0 0% 0
Untranslated strings 19% 2,275 25% 56,760 24% 355,113
Last 12 months Previous

Activity in last 12 months

5,359 changes 989 changes 16 changes 1,412 changes 0 changes 172 changes 214 changes 13,771 changes 185 changes 3,215 changes 38 changes 6 changes 356 changes 22 changes 6 changes 36 changes 167 changes 24,229 changes 775 changes 99 changes 14 changes 125 changes 0 changes 29 changes
Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct

Quick numbers

226 k
Hosted words
11,592
Hosted strings
80%
Translated
1
Contributors
and previous 30 days

Trends of last 30 days

+1%
Hosted words
+100%
+1%
Hosted strings
+100%
+1%
Translated
+80%
—
Contributors
+100%
User avatar jnavila

Translation added
[NOTE] 'git rerere' relies on the conflict markers in the file to detect the conflict. If the file already contains lines that look the same as lines with conflict markers, 'git rerere' may fail to record a conflict resolution. To work around this, the `conflict-marker-size` setting in linkgit:gitattributes[5] can be used.
[NOTE] 'git rerere' s'appuie sur les marqueurs de conflit dans le dossier pour détecter le conflit. Si le fichier contient déjà des lignes qui ressemblent aux lignes avec des marqueurs de conflit, « git rerere» peut ne pas enregistrer une résolution de conflit. Pour contourner cette limitation, on peut utiliser le réglage de la taille de la marqueur de conflit `conflict-marker-size` dans linkgit:gitattributes[5].
17 hours ago
User avatar jnavila

Translation added
you could run `git rebase master topic`, to bring yourself up to date before your topic is ready to be sent upstream. This would result in falling back to a three-way merge, and it would conflict the same way as the test merge you resolved earlier. 'git rerere' will be run by 'git rebase' to help you resolve this conflict.
vous pouvez lancer `git rebase master topic`, pour vous mettre à jour avant que votre sujet soit prêt à être envoyé en amont. Cela entraînerait un retour à une fusion à trois points et cela serait incompatible avec la fusion que vous avez résolue plus tôt. 'git rerere' sera lancé par 'git rebase' pour vous aider à résoudre ce conflit.
18 hours ago
User avatar None

Changes committed
Changes committed yesterday
User avatar jnavila

Translation added
As a convenience measure, 'git merge' automatically invokes 'git rerere' upon exiting with a failed automerge and 'git rerere' records the hand resolve when it is a new conflict, or reuses the earlier hand resolve when it is not. 'git commit' also invokes 'git rerere' when committing a merge result. What this means is that you do not have to do anything special yourself (besides enabling the rerere.enabled config variable).
Comme mesure de commodité, 'git merge' invoque automatiquement 'git rerere' à la sortie d'une autofusion ratée et 'git rerere' enregistre la résolution manuelle lorsqu'il s'agit d'un nouveau conflit, ou réutilise la résolution manuelle antérieure sinon. 'git commit' invoque également 'git rerere' lors de la validation d'un résultat de fusion. Ce que cela signifie, c'est que vous n'avez rien de spécial à faire vous-même (à moins d'avoir désactivé la variable de configuration `rerere.enabled`).
yesterday
User avatar None

Changes committed
Changes committed 6 days ago
User avatar jnavila

Translation added
$ git rebase master topic
$ git rebase master sujet
6 days ago
User avatar jnavila

Translation added
o---*---o-------o---o topic
/
o---o---o---*---o---o---o---o master
o---*---o-------o---o sujet
/
o---o---o---*---o---o---o---o master
6 days ago
User avatar jnavila

Translation added
The information 'git rerere' records is also used when running 'git rebase'. After blowing away the test merge and continuing development on the topic branch:
Les enregistrement d'information `git rerere` sont également utilisées lors de l'exécution de `git rebase`. Après avoir fait exploser la fusion de test et continué le développement sur la branche thématique :
6 days ago
User avatar jnavila

Translation added
In our example, when you do the test merge, the manual resolution is recorded, and it will be reused when you do the actual merge later with the updated master and topic branch, as long as the recorded resolution is still applicable.
Dans notre exemple, lorsque vous faites la fusion de test, la résolution manuelle est enregistrée, et elle sera réutilisée lorsque vous faites la fusion réelle plus tard avec les branches master et topic mises à jour, tant que la résolution enregistrée est toujours applicable.
6 days ago
User avatar jnavila

Translation added
Next time, after seeing the same conflicted automerge, running 'git rerere' will perform a three-way merge between the earlier conflicted automerge, the earlier manual resolution, and the current conflicted automerge. If this three-way merge resolves cleanly, the result is written out to your working tree file, so you do not have to manually resolve it. Note that 'git rerere' leaves the index file alone, so you still need to do the final sanity checks with `git diff` (or `git diff -c`) and 'git add' when you are satisfied.
La prochaine fois, après avoir vu la même autofusion conflictuelle, lancer `git rerere` effectuera une fusion de trois points entre l'autofusion antérieure en conflit, la résolution manuelle antérieure et l'autofusion en conflit actuelle. Si cette fusion à trois points se résout proprement, le résultat est écrit à votre fichier d'arbre de travail, de sorte que vous n'avez pas à le résoudre manuellement. Notez que 'git rerere' laisse le fichier index seul, donc vous devez toujours faire les vérifications de sanity finales avec `git diff` (ou `git diff -c`) et `git add` lorsque vous êtes satisfait.
6 days ago
Browse all translation changes