From: "Jean-Noël AVILA" <jn.avila@free.fr>
To: Junio C Hamano <gitster@pobox.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
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: Tue, 11 Jun 2019 22:37:39 +0200 [thread overview]
Message-ID: <7802960.VzbTMjdsy5@cayenne> (raw)
In-Reply-To: <xmqqmuipmett.fsf@gitster-ct.c.googlers.com>
On Monday, 10 June 2019 21:15:58 CEST Junio C Hamano wrote:
> Jean-Noël AVILA <jn.avila@free.fr> writes:
>
> > I can provide an archive comprising the precompiled manpages so that
packagers
> > don't need to mess up with po4a.
>
> That's an interesting thing to hear---if this effort eventually
> relieves me from having to supply preformatted manpages and HTML
> docs (after all, en/C is just one more locale from your point of
> view, right?), that would be an excellent news for me ;-)
I wasn't expecting this one ;-D In fact, the translation project is different
in two points:
* Not all the sources have been copied; only sources for some manpages
* the en version is the source for translation. It's not compiled (why
bother? it's already done in the main repo).
>
> The last-mile packagers that are directly facing end-users would be
> happy to have a place (or two) that they can pull the pre-built docs
> for these locales from, and they would not particularly care where
> exactly those places are, I think.
BTW, who is using the preformatted docs? If it's useful to anybody to have
access to the compound of en + translated docs, such repo can be set up.
Please note that Johannes clearly stated that git-for-windows cannot afford
more weight, so English only manpages are still required.
prev parent reply other threads:[~2019-06-11 20:37 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
2019-06-10 19:15 ` Junio C Hamano
2019-06-11 20:37 ` 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
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=7802960.VzbTMjdsy5@cayenne \
--to=jn.avila@free.fr \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--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).