jnavila/git-manpages-l10n

Translation of git manpages

git-manpages-l10n's Issues

Pretranslate with strings from git

Some parts of git inline help are very close to the documentation strings. This task could be applied to all available languages in git and could help kickstart translations in other languages.

ellipsis errors on weblate

does it make sense to fix ellipsis errors given on weblate ?
weblate

Request for clarification: Ambiguous sections in documentation

Hello,

I am confused by the description of the --namespace option on this page.

In the SYNOPSIS section, the --namespace option is followed by <name>, but in the OPTIONS section, the --namespace option is followed by <path>. Is there anything wrong with this?"

Grammar updates needed?

While trying to better understand git update-index I found this line The way git update-index handles files it is told about can be modified using the various options: It doesn't read correctly, but I'm no expert to fix it. Thanks!

https://github.com/jnavila/git-manpages-
l10n/blob/a281eebe993f24150e3393638c08fc43cdd9d792/en/git-update-index.txt#L39

dosen't exist korean version

dosen't exist korean version

How can I use those translations?

What should I do to see these translations instead of the manuals I see on the default git command line?

Licensing

We might have a bit of a licensing issue on our hands.

I've stumbled accross this section in LICENSE.txt:

While most of this project is under the GPL (see COPYING), the xdiff/
library and some libc code from compat/ are licensed under the
GNU LGPL, version 2.1 or (at your option) any later version and some
other files are under other licenses. Check the individual files to
be sure.

We have no file COPYING, no folders xdiff/ and compat/ and use neither code from xdiff nor libc AFAIK.

While github and weblate have pulled from LICENSE.txt that it contains LGPL-2.1, the po files for de, es_MX, fr and ru say:

This file is distributed under the same license as the Git package.

The other languages say the same thing, but for "the PACKAGE package".

As LICENSE.txt indicates most of Git is under the GPL v2. From my understanding that includes the Documentation. You can probably see where this is going.

The proper license file to copy from Git would have probably been COPYING instead of LGPL-2.1. I'm not sure if we need to contact the contributors about relicensing their contributions. According to the FSF translations are derived works, so I think we're legally required to relicense under GPLv2.

They also say in their Quick Guide to GPLv3

Under GPLv2, if you violated the license in any way, your rights were automatically and permanently lost. The only way to get them back was to petition the copyright holder.

I'm not sure if we are in that situation yet. But talking to Junio about this whole situation might not hurt. We should probably clear this up sooner, rather than later.

الالبد

Missing file

Hello,
I found some mistakes when translating the document:

• Tins page only have English version,and the others are show :"Warning | Missing **/glossary-content.txt See original version for this content."
• This page, I can't find the source file in the Weblate platform.

Missing content

Near the end of this page for the Brazilian Portuguese translation, it display a few missing content errors.

man 7 gitglossary is missing

The repository doesn't include the gitglossary(7) man page. It would be nice to have it because IMHO it is quite crucial to establish basic glossary as early as possible during translation and having the page would help this task a lot.

Missing includes in ES

In en/git.txt by lines 339 and 348 there are the following includes:

• include::cmds-userinterfaces.txt[]
• include::cmds-developerinterfaces.txt[]

So in ES there are warnings about missing:

• es/cmds-userinterfaces.txt
• es/cmds-developerinterfaces.txt

Language style question

This question only concerns the German translations, so I am formulating it here in German in order to be better understood.

@rimrul
Eine grundsätzliche Frage zum Sprachstil in den Übersetzungen der Git-Manpages.
In den mir bekannten Übersetzungen von Manpages (z.B. apt(8) und dpkg-buildpackage(1) aus der Debian Distribution) werden die erklärenden Texte zu einem Befehl oder einer Option in der 3. Person Singular verfasst. Dabei ist der Text so formuliert als, ob er das Ergebnis des Befehl-Aufrufs sei.
Hier, in einigen vorhandenen Übersetzungen, wird der Text dagegen wie eine Aufforderung formuliert den Befehl auszuführen.

Beispiel:

(Source) 		git-clone - Clone a repository into a new directory
(1.Übersetzung) 	git-clone - Klone ein Projektarchiv (repository) in ein neues Verzeichnis
(mein Vorschlag)	git-clone – Klont ein Repository (Projektarchiv) in ein neues Verzeichnis

Ich denke, dass meine Version sich näher an den Übersetzungen der übrigen Manpages orientiert.
Wie soll zukünftig verfahren werden?

Contributing to translation

@jnavila
Following my promise during our conversation on progit2 last October, I would like to contribute to the German translation of the "git-manpages".
I used Weblate a few days ago to translate a few strings and also corrected some typos.
So far I do not really understand the workflow here.
However, my changes don't appear on https://git-scm.com/docs.
Is there another site where I can check the output?

A second problem, even more serious to me, is that the order of the strings to be translated is completely confusingly composed coming from various files.
In order to be able to consider the context, when translating, I usually prefer to proceed file by file.
Is there a setting at Weblate that enables something similar or is there another way to contribute here?

Add Vietnamese support

Hi. I can help with Vietnamese translation. Can you please add it to weblate? Thanks.

Danh

Prioritize strings to translate in Weblate

WeblateOrg/weblate#2940 asked for a way to prioritize po entries in order to help translators begin by mostly viewed strings. The ability to input priority was added in weblate via WeblateOrg/weblate@d13805f.

The idea here is to set priorities down to 100 (normal priority) depending on https://git-scm.com/docs/ starting with:

Section	score
Getting and Creating Projects	300
Basic snapshotting	280
Inspection and Comparison	260
Branching and Merging	240
Sharing and Updating Projects	220

who is the team leader of zh_HANS_CN?

who is the team leader of zh_HANS_CN?

Source string problem: slightly broken placeholder

Hello.

I found a slightly broken placeholder in the source string.

git-manpages-l10n/en/git-clone.txt

Line 314 in c1cb222

--ref-format=<ref-format::

A problem with bundle exec make all

Hello, I've got a problem with bundle exec make all
When I try to use it, there Is an error

/Documents/Repositories/git-manpages-l10n$ bundle exec make all
PERL5LIB=./po4a/lib po4a/po4a -v po4a.conf
POT file po/documentation.pot already up to date.
Error: failed to execute 'msgmerge
/home/alexey/Documents/Repositories/git-manpages-l10n/po/documentation.de.po
/home/alexey/Documents/Repositories/git-manpages-l10n/po/documentation.pot
--previous --backup=none --update': No such file or directory.
make: *** [Makefile:22: po4a-stamp] Error 2

Could you tell me what I did wrong?

Another question is why don't we use a docker image with ruby and pearl dependencies, or at least some script to set up all necessary dependencies without any container? I think it will be much easier for new contributors to start translating the documents and don't waste time trying to make the "bundle exec make all" work.

I've got some free time next month and I would like to contribute a lot to the Russian translation.

Thank you.