From: "Jean-Noël AVILA" <avila.jn@gmail.com>
To: Helge Kreutzmann <debian@helgefjell.de>, git@vger.kernel.org
Subject: Re: i18n of git man pages
Date: Thu, 09 May 2024 16:56:18 +0200 [thread overview]
Message-ID: <8450777.T7Z3S40VBb@cayenne> (raw)
In-Reply-To: <Zjuokc2H0zI1JCVH@meinfjell.helgefjelltest.de>
On Wednesday, 8 May 2024 18:30:09 CEST Helge Kreutzmann wrote:
> 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.
>
Hello,
I took in charge to provide translation of the man pages of git. The projects
lives on https://github.com/jnavila/git-manpages-l10n
As explained in the README file, the strategy has been to translate the sources
asciidoc files, instead of managing the resulting man pages. Translating the
source files of the man pages is needed in order to publish them on git-
scm.com (single source principle), as well as because the sources files use
asciidoc features such as dedicated macros, conditionals and includes. In
order to lower the difficulty for translators, the repo is coupled with the
online translation tool weblate[1] .
Right now, I'm using a slightly modified version of po4a for asciidoc (merge
request pending). This translation gave also way to some improvements of
asciidoc support for po4a. That's a two way development.
The project was submitted for inclusion in Debian, but lacking more support,
the process was never achieved. I would be delighted to have the git-manpages
included in the main distros. For Windows, the inclusion in the main package
was rejected as it would make it even fatter.
Jean-Noël
[1] https://hosted.weblate.org/projects/git-manpages/
prev parent reply other threads:[~2024-05-09 15:04 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
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 [this message]
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=8450777.T7Z3S40VBb@cayenne \
--to=avila.jn@gmail.com \
--cc=debian@helgefjell.de \
--cc=git@vger.kernel.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).