From: Junio C Hamano <gitster@pobox.com>
To: Helge Kreutzmann <debian@helgefjell.de>
Cc: "Peter Krefting" <peter@softwolves.pp.se>,
"Jean-Noël AVILA" <avila.jn@gmail.com>,
git@vger.kernel.org
Subject: Re: i18n of git man pages
Date: Wed, 08 May 2024 13:12:02 -0700 [thread overview]
Message-ID: <xmqqedacxdv1.fsf@gitster.g> (raw)
In-Reply-To: <ZjvHoykzIo34YJaT@meinfjell.helgefjelltest.de> (Helge Kreutzmann's message of "Wed, 8 May 2024 18:42:43 +0000")
Helge Kreutzmann <debian@helgefjell.de> writes:
> This mentions https://github.com/jnavila/git-manpages-l10n, so I can
> point our translator to this source.
That is a good move.
Perhaps we should make the manpage l10n project easier to discover
on our end to help volunteers.
Possible places are the "SubmittingPatches" document in our tree,
and "the Notes from the maintainer" letter that are sent out after
major releases.
Jean-Noël, how does the following look?
Thanks.
Documentation/SubmittingPatches | 7 +++++++
1 file changed, 7 insertions(+)
diff --git c/Documentation/SubmittingPatches w/Documentation/SubmittingPatches
index 384893be1c..b36b3d9919 100644
--- c/Documentation/SubmittingPatches
+++ w/Documentation/SubmittingPatches
@@ -562,6 +562,13 @@ repositories.
Patches to these parts should be based on their trees.
+- The "Git documentation translations" project, led by Jean-Noël
+ Avila, translates our documentation pages. Theire work products are
+ maintained separately from this project:
+
+ https://github.com/jnavila/git-manpages-l10n/
+
+
[[patch-flow]]
== An ideal patch flow
next prev parent reply other threads:[~2024-05-08 20:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-08 16:30 i18n of git man pages Helge Kreutzmann
2024-05-08 17:26 ` Junio C Hamano
2024-05-08 18:42 ` Helge Kreutzmann
2024-05-08 20:12 ` Junio C Hamano [this message]
2024-05-09 14:39 ` Peter Krefting
2024-05-09 16:10 ` Junio C Hamano
2024-05-10 7:39 ` Jean-Noël AVILA
2024-05-10 15:45 ` Junio C Hamano
2024-05-10 16:33 ` Jean-Noël AVILA
2024-05-09 14:56 ` Jean-Noël AVILA
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqedacxdv1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=avila.jn@gmail.com \
--cc=debian@helgefjell.de \
--cc=git@vger.kernel.org \
--cc=peter@softwolves.pp.se \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).