From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Jean-Noël AVILA" <jn.avila@free.fr>
Cc: git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>,
Todd Zullinger <tmz@pobox.com>,
timcharper@gmail.com, "avila.jn" <avila.jn@gmail.com>
Subject: Re: Inclusion of translated git manpages into the packaging systems
Date: Mon, 10 Jun 2019 19:09:54 +0200 (CEST) [thread overview]
Message-ID: <nycvar.QRO.7.76.6.1906101906140.789@QRFXGBC-DHN364S.ybpnyqbznva> (raw)
In-Reply-To: <1979608.xhrAu3A07H@cayenne>
[-- Attachment #1: Type: text/plain, Size: 1595 bytes --]
Hi Jean-Noël,
On Sun, 9 Jun 2019, Jean-Noël AVILA wrote:
> I took on the task of creating a project for the translation of man-pages at
> https://github.com/jnavila/git-manpages-l10n
>
> Up to now, the translations have started for 3 languages:
>
> * German (2 pages)
> * Brazilian Portuguese (6 pages)
> * French (11pages)
Nice!!!
> In order to provide feedback to translators, it's time to have these
> pages included with the distributions of git. Right now the process of
> compilation of the man-pages is still a bit off-tree, because it relies
> on a recent version of po4a (v0.56) which has not yet reached most
> distros.
Maybe there is a way to skip the Makefile task when a too-old po4a is
detected, with a warning?
> I miss expertise in the process of packaging. Depending on the type of
> distribution, the route to packaging might differ (for Mac OS and
> Windows, maybe a direct inclusion, for Linux dists sister packages).
> That's why I need your help to correctly perform this integration.
Historically, Git for Windows punts on translations, excluding any
non-en-US documentation (to save on bandwidth for the installer, which did
grow from <30MB to 44MB in the last four years alone).
There were a couple of motions to change that (maybe in the form of add-on
packages/installers, maybe in the form of a "full" installer), but nothing
came of it so far.
Therefore, as far as Windows is concerned, I hate to admit that my answer
is "don't worry for now, we only include US-English documentation
anyway"... :-(
Ciao,
Dscho
next prev parent reply other threads:[~2019-06-10 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-09 15:47 Inclusion of translated git manpages into the packaging systems Jean-Noël AVILA
2019-06-10 17:09 ` Johannes Schindelin [this message]
2019-06-10 19:02 ` Jean-Noël AVILA
2019-06-10 19:15 ` Junio C Hamano
2019-06-11 20:37 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=nycvar.QRO.7.76.6.1906101906140.789@QRFXGBC-DHN364S.ybpnyqbznva \
--to=johannes.schindelin@gmx.de \
--cc=avila.jn@gmail.com \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
--cc=jrnieder@gmail.com \
--cc=timcharper@gmail.com \
--cc=tmz@pobox.com \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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).