From: "Jean-Noël AVILA" <jn.avila@free.fr>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org, Jonathan Nieder <jrnieder@gmail.com>,
Todd Zullinger <tmz@pobox.com>,
timcharper@gmail.com
Subject: Re: Inclusion of translated git manpages into the packaging systems
Date: Mon, 10 Jun 2019 21:02:17 +0200 [thread overview]
Message-ID: <1835964.yutTd2aTbA@cayenne> (raw)
In-Reply-To: <nycvar.QRO.7.76.6.1906101906140.789@QRFXGBC-DHN364S.ybpnyqbznva>
On Monday, 10 June 2019 19:09:54 CEST Johannes Schindelin wrote:
> 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?
The project is provided with a script that downloads the correct version of
po4a from the root repo (this is needed for ci).
I can provide an archive comprising the precompiled manpages so that packagers
don't need to mess up with po4a.
>
> > 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).
It might not be the correct argument for now, but a tgz of the manpages
presently weights 230kB.
>
> 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.
If there's any chance to get this move alive, who should I refer to?
Otherwise, where can an additional package be built?
>
> 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 19:02 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
2019-06-10 19:02 ` Jean-Noël AVILA [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1835964.yutTd2aTbA@cayenne \
--to=jn.avila@free.fr \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.