Git Manpages @ Hosted Weblate

Component	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
Translations GPL-2.0	29%	205,283	4,714,275	30,059,666	195,261	8,944	168	17

Glossary Git Manpages GPL-2.0	62%	3,737	5,127	40,981	3,601	0	18	3

Overview

Project website	git-scm.com
Project maintainers	jnavila

15 hours ago

String statistics

	Strings percent	Hosted strings	Words percent	Hosted words	Characters percent	Hosted characters
Total		299,867		5,675,093		36,660,102
Source		12,462		227,635		1,470,903
Translated	30%	90,847	16%	955,691	17%	6,559,455
Needs editing	3%	10,158	1%	98,191	1%	704,717
Read-only	5%	16,306	4%	231,440	4%	1,561,171
Failing checks	2%	8,944	2%	123,547	2%	856,914
Strings with suggestions	1%	186	1%	738	1%	5,806
Untranslated strings	66%	198,862	81%	4,621,211	80%	29,395,930

Last 12 months Previous

Activity in last 12 months


Nov	Dec	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct

Quick numbers

5,675 k

Hosted words

299 k

Hosted strings

30%

Translated

Contributors

and previous 30 days

Trends of last 30 days

+1%

Hosted words

+100%

+1%

Hosted strings

+100%

—

Translated

+30%

+40%

Contributors

+100%

Language	Translated	Unfinished	Unfinished words	Unfinished characters	Untranslated	Checks	Suggestions	Comments
English		0	0	0	0	3,581	0	3

Chinese (Simplified Han script)	96%	386	7,109	52,544	96	126	0	8

Chinese (Traditional Han script)	20%	9,458	221,367	1,407,848	9,191	135	0	1

Dutch	15%	10,136	225,066	1,436,747	9,675	221	2	0

French	79%	2,441	56,990	356,820	2,441	0	1	0

German	26%	8,739	211,902	1,349,106	7,568	496	13	2

Hungarian	15%	10,146	225,077	1,436,841	9,965	85	0	0

Icelandic	17%	9,946	222,661	1,421,348	9,512	171	0	0

Indonesian	16%	10,020	224,629	1,432,187	9,365	475	0	0

Italian	15%	10,050	224,050	1,428,923	8,824	622	1	0

Japanese	25%	8,949	209,254	1,328,516	8,777	71	0	4

Korean	19%	9,642	219,740	1,397,387	9,024	415	0	0

Marathi	15%	10,134	225,040	1,436,539	9,948	86	1	0

Norwegian Bokmål	15%	10,147	225,078	1,436,868	9,933	99	0	0

Polish	15%	10,074	224,882	1,435,712	9,320	494	156	0

Portuguese (Brazil)	96%	409	10,391	73,132	122	122	0	0

Portuguese (Portugal)	15%	10,147	225,078	1,436,868	9,929	92	0	0

Romanian	17%	9,866	221,625	1,414,412	9,418	162	1	1

Russian	18%	9,835	222,994	1,422,551	9,160	393	6	1

Slovak	15%	10,147	225,078	1,436,868	10,024	50	0	0

Spanish	33%	7,917	193,307	1,224,111	7,909	4	1	0

Spanish (Mexico)	15%	10,123	224,954	1,436,088	9,467	462	2	0

Turkish	16%	9,989	224,209	1,430,463	9,708	112	0	0

Ukrainian	15%	10,051	223,796	1,428,866	9,918	56	2	0

Vietnamese	14%	10,268	225,125	1,439,902	9,568	414	0	0

jnavila Translation added Git Manpages Translations French	English [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. French 416 characters edited Current translation Translated [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]. 15 hours ago
jnavila Translation added Git Manpages Translations French	English 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. French 336 characters edited Current translation Translated 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. 15 hours ago
None Changes committed Git Manpages Translations French	Changes committed yesterday
jnavila Translation added Git Manpages Translations French	English 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). French 497 characters edited Current translation Translated 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
None Changes committed Git Manpages Translations French	Changes committed 6 days ago
jnavila Translation added Git Manpages Translations French	English $ git rebase master topic French 27 characters edited Current translation Translated $ git rebase master sujet 6 days ago
jnavila Translation added Git Manpages Translations French	English o------o-------o---o topic / o---o---o------o---o---o---o master French 100 characters edited Current translation Translated o------o-------o---o sujet / o---o---o------o---o---o---o master 6 days ago
jnavila Translation added Git Manpages Translations French	English 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: French 208 characters edited Current translation Translated 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
jnavila Translation added Git Manpages Translations French	English 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. French 277 characters edited Current translation Translated 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
jnavila Translation added Git Manpages Translations French	English 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. French 603 characters edited Current translation Translated 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 project changes

jnavila Announcement posted Git Manpages	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: Starting to standardize the markup for placeholders and constant strings. The work was done in order to better uniformize the look of the man pages and update them to the style applied for other applications. verbatim strings, i.e. strings that are constant and must not be translated are marked up as verbatim with backticks (or double + signs when they are stuck with other letters): `clone.filterSubmodules` , `++--filter=++1` placeholders are emphasized with underscores :`_<pathspec>_`. They are meant to be variable names, and translated. The formatting has already been applied to git-init and git-clone. So that makes a lot of small markup changes. More updated pages are coming. As some of may have noticed, I added a script in order to mark as keywords the verbatim string in Weblate. This way, the formatting errors are caught up early. There are still some edge cases that create false positive. Please let me know when you meet some. The update window will close on Sun, 28 Jul 2024. If you have any questions, please get in touch with me. Thanks, Jean-Noël Avila 4 months ago
jnavila Announcement posted Git Manpages	Dear fellow Git translator, A new release of Git is coming soon, v2.44.0. The strings are frozen now, and the release candidate 0 has been tagged. It's time to update your translations. The update window will close on Sun, 18 Feb 2024. This time, I will run an automated script to check the po files for errors and warnings and push an annotated version of the translation files. The translations that are not conforming to the script will be marked as "fuzzy" and a translator comment will be added to them. On Weblate, the string will be marked "needs review" and the error messages will be displayed in the small black box above the original string. I will push the updated po files to the source repository and to the Weblate repository. Then, a second publishing will be done to the source repository one week later, on Sun, 25 Feb 2024. If you want to check your po file before that, you can run the script yourself. You can find the script in the source repository under `scripts/check_po`. You can run it like this: `$ scripts/check-po po/documentation.fr.po` If you have any questions, please get in touch with me. Thanks, Jean-Noël Avila 9 months ago
jnavila Announcement posted Git Manpages Translations	Hi, Git v2.43.0-rc0 has been released, opening the merge window for a new version of the man pages. This time there are 360 updated segments that need to be translated since last release. The update window closes on Sun, 19 Nov 2023. Best regards, Jean-Noël a year ago
jnavila Announcement posted Git Manpages Translations	Hi everyone, Git v2.42.0-rc0 has just been tagged, opening the release window to the upcoming v2.42.0. There are 175 modified or new strings. Some changes may occur during the release window which will close on August 20th 2023. Happy translating! JN a year ago
jnavila Announcement posted Git Manpages Translations	Hi, Git v2.41.0-rc0 has been released, and it's time to start new round of git manpage l10n. This time, there are 54 new strings, which is quite small and should allow to make some advance in the languages that are not totally translated yet. As usual, note that the update window will close on Wed, 31 May 2023, at which time the changes will be merged back and the manpages published. JN a year ago
jnavila Announcement posted Git Manpages	Git v2.40.0-rc0 has been tagged. Be ready for a new round of translations with 104 entries changed or added. The fusion window will close on Sun, 12 Mar 2023, at which point the changes will be merged and pushed to git-scm.com. Happy translating! Jean-Noël a year ago
jnavila Announcement posted Git Manpages	Hi, The release cycle for v2.39 has started. The translation of documentation has been updated. For the languages which have a translation in the master git repo, these translations were used to pre-translate the documentation. This process will repeat from now on, as a special attention has been put on making the documentation embedded in git match the manpages. The window of translation will close on Sun, Dec 11, 2022. JN a year ago
jnavila Announcement posted Git Manpages Translations	Hello everyone, The sprint for tagging Git v2.38.0 has just started and the po files have been accordingly. Please translate, until the end of the release window, on Sun, Oct 02, 2022. Jean-Noël 2 years ago
jnavila Announcement posted Git Manpages Translations	Hi fellow translators, Git v2.37.0 is reaching the release candidate phase, and there are 36 strings to update. As usual, I will close the merge window when the final tag is set. Jean-Noël 2 years ago
jnavila Announcement posted Git Manpages Translations	Hi everyone, Git v2.36.0 rc 1 has been tagged, leading the upcoming release of v2.36.0. The strings for the manpages were updated with 162 segments to check/translate. As usual, I'll close the merge window and publish the manpages when the final version is released. Jean-Noël 2 years ago

Browse all project changes

Search

Advanced query builder

Query examples

Review strings changed by other users	`changed:>="1 month ago" AND NOT changed_by:anonymous`	Add
Translated strings	`state:>=translated`	Add
Strings with comments	`has:comment`	Add
Strings with any failing checks	`has:check`	Add
Strings with suggestions from others	`has:suggestion AND NOT suggestion_author:anonymous`	Add
Approved strings with suggestions	`state:approved AND has:suggestion`	Add
All untranslated strings added the past month	`added:>="1 month ago" AND state:<=needs-editing`	Add
Strings changed in the past two weeks	`changed:>="2 weeks ago"`	Add
Translated strings in a certain language	`is:translated AND language:en`	Add

Shortcut	Action
`?`	Open available keyboard shortcuts.
`Alt` + `Home`	Navigate to the first translation in the current search.
`Alt` + `End`	Navigate to the last translation in the current search.
`Alt` + `PageUp` or `Ctrl` + `↑` or `Alt` + `↑` or `Cmd` + `↑` or	Navigate to the last translation in the current search.
`Alt` + `PageDown` or `Ctrl` + `↓` or `Alt` + `↓` or `Cmd` + `↓` or	Navigate to the next translation in the current search.
`Ctrl` + `Enter` or `Cmd` + `Enter`	Submit current form; this works the same as pressing Save and continue while editing translation.
`Ctrl` + `Shift` + `Enter` or `Cmd` + `Shift` +`Enter`	Unmark translation as Needing edit and submit it.
`Alt` + `Enter` or `Option` + `Enter`	Submit the string as a suggestion; this works the same as pressing Suggest while editing translation.
`Ctrl` + `E` or `Cmd` + `E`	Focus on translation editor.
`Ctrl` + `U` or `Cmd` + `U`	Focus on comment editor.
`Ctrl` + `M` or `Cmd` + `M`	Shows Automatic suggestions tab.
`Ctrl` + `1` to `Ctrl` + `9` or `Cmd` + `1` to `Cmd` + `9`	Copies placeable of a given number from source string.
`Ctrl` + `M` followed by `1` to `9` or `Cmd` + `M` followed by `1` to `9`	Copy the machine translation of a given number to current translation.
`Ctrl` + `I` followed by `1` to `9` or `Cmd` + `I` followed by `1` to `9`	Ignore one item in the list of failing checks.
`Ctrl` + `J` or `Cmd` + `J`	Shows the Nearby strings tab.
`Ctrl` + `S` or `Cmd` + `S`	Focus on search field.
`Ctrl` + `O` or `Cmd` + `O`	Copy the source string.
`Ctrl` + `Y` or `Cmd` + `Y`	Toggle the Needs editing checkbox.
`→`	Browse the next translation string.
`←`	Browse the previous translation string.