git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Peter Krefting" <peter@softwolves.pp.se>,
	"Jean-Noël AVILA" <avila.jn@gmail.com>
Cc: git@vger.kernel.org, Helge Kreutzmann <debian@helgefjell.de>
Subject: Re: i18n of git man pages
Date: Wed, 08 May 2024 10:26:35 -0700	[thread overview]
Message-ID: <xmqqjzk4xlis.fsf@gitster.g> (raw)
In-Reply-To: <Zjuokc2H0zI1JCVH@meinfjell.helgefjelltest.de> (Helge Kreutzmann's message of "Wed, 8 May 2024 16:30:09 +0000")

Cc'ing folks who have shown interest in translated manual pages.

cf. 
https://lore.kernel.org/git/cb74f3b-c2e9-947f-8f89-f51e79b17825@softwolves.pp.se/
https://lore.kernel.org/git/11498572.Kui42GGras@cayenne/

Thanks.

Helge Kreutzmann <debian@helgefjell.de> writes:

> Hello,
> I'm maintainer of manpages-l10n[1], a collection of translations of man
> pages for over 100 projects into many languages. 
>
> Our policy is to move translations into the upstream project where
> possible. Only where projects are not interested in maintaining the
> translations for their man pages themselves we host them[2].
>
> Recently one of our translators approached me to translate the man
> pages for git. Before adding them, I want to check with you if you are
> interested in adding translations of the man pages directly in the git
> project. 
>
> (Technically, po4a has been proven to be a good tool to maintain
> man page translations).
>
> Thanks for considering i18n your man page part.
>
> Greetings
>
>          Helge
>
>
> [1]
> https://manpages-l10n-team.pages.debian.net/manpages-l10n/index.html
>
> [2] We collected many translated man pages from the web in the past
>     and transferring them upstream is a (very) slow process.

  reply	other threads:[~2024-05-08 17:26 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 [this message]
2024-05-08 18:42   ` Helge Kreutzmann
2024-05-08 20:12     ` Junio C Hamano
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=xmqqjzk4xlis.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).