From: "Jean-Noël AVILA" <jn.avila@free.fr>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>,
Stefan Beller <sbeller@google.com>,
Stefan Hajnoczi <stefanha@redhat.com>
Subject: Re: What's cooking in git.git (May 2017, #03; Wed, 10)
Date: Wed, 10 May 2017 11:04:20 +0200 [thread overview]
Message-ID: <9774445.E3R3CqpI8C@cayenne> (raw)
In-Reply-To: <CACBZZX4F2TL-kZj6y=00UTEhC-4VeDLm1EYOe2_eK=hscSdJ4g@mail.gmail.com>
Le mercredi 10 mai 2017, 10:08:14 CEST Ævar Arnfjörð Bjarmason a écrit :
> > * ja/doc-l10n (2017-03-20) 3 commits
> > . SQUASH???
> > . l10n: add git-add.txt to localized man pages
> > . l10n: introduce framework for localizing man pages
> >
> > A proposal to use po4a to localize our manual pages.
> >
> > Will discard.
> > Has been stalled for too long.
>
> Jean-Noel: Need any help with this?
>
I restarted on this yesterday. The change for git will be reduced to what Junio proposed, that is embedding a repo into /Documentation, with some targets added to Makefile if the directory is present. In the doc l10n repo, a Makefile's target will copy the asciidoc source files from /Documentation into the repo, in order to create a stable base for all the po4a stuff.
This is quite slow as my Makefile-fu is very basic.
next prev parent reply other threads:[~2017-05-10 9:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-10 5:18 What's cooking in git.git (May 2017, #03; Wed, 10) Junio C Hamano
2017-05-10 8:08 ` Ævar Arnfjörð Bjarmason
2017-05-10 9:04 ` Jean-Noël AVILA [this message]
2017-05-11 1:12 ` Junio C Hamano
2017-05-11 2:50 ` Junio C Hamano
2017-05-10 8:12 ` Ævar Arnfjörð Bjarmason
2017-05-11 2:19 ` Junio C Hamano
2017-05-11 13:08 ` Johannes Schindelin
2017-05-12 5:29 ` Junio C Hamano
2017-05-11 13:09 ` Johannes Schindelin
2017-05-11 16:35 ` Lars Schneider
2017-05-11 21:31 ` Marc Branchaud
2017-05-11 23:38 ` Jeff King
2017-05-12 1:01 ` Junio C Hamano
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=9774445.E3R3CqpI8C@cayenne \
--to=jn.avila@free.fr \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sbeller@google.com \
--cc=stefanha@redhat.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.