From: Junio C Hamano <gitster@pobox.com>
To: Jean-Noel Avila <jn.avila@free.fr>
Cc: git@vger.kernel.org
Subject: Re: [PATCH v2 1/2] l10n: Introduce framework for localizing man pages
Date: Sat, 18 Mar 2017 12:41:22 -0700 [thread overview]
Message-ID: <xmqqfuia1ifx.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20170318175353.24578-1-jn.avila@free.fr> (Jean-Noel Avila's message of "Sat, 18 Mar 2017 18:53:52 +0100")
Jean-Noel Avila <jn.avila@free.fr> writes:
> Providing git in localized version is a good step for general adoption
> of the tool. But as of now, if one needs to refer to the manual pages,
> they are still confronted to english. The aim is to provide
> documentation to users in their own language.
Please outline how the end result looks like here. Where are the
localized man pages installed? Do installers get to choose to build
and install the localization for some but not all languages and if
so how? etc.
> signed-off-by: Jean-Noel Avila <jn.avila@free.fr>
s/sign/Sign/;
> -man: man1 man5 man7
> +man: man1 man5 man7 man_l10n
Hmmm, at least in the early days of the topic, I'd prefer that "make
doc" and "make install" I need to run dozens of times a day from the
toplevel not to require po4a.
Thanks.
next prev parent reply other threads:[~2017-03-18 19:41 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 20:02 [PATCH] l10n: add framework for localizing the manpages Jean-Noel Avila
2017-03-12 20:02 ` Jean-Noel Avila
2017-03-12 20:36 ` Jean-Noël AVILA
2017-03-13 0:01 ` Junio C Hamano
2017-03-14 21:00 ` Ævar Arnfjörð Bjarmason
2017-03-14 21:13 ` Junio C Hamano
2017-03-15 8:11 ` Jean-Noël Avila
2017-03-15 9:01 ` Ævar Arnfjörð Bjarmason
2017-03-15 7:58 ` Jean-Noël Avila
2017-03-15 16:07 ` Junio C Hamano
2017-03-15 18:28 ` Stefan Beller
2017-03-18 17:53 ` [PATCH v2 1/2] l10n: Introduce framework for localizing man pages Jean-Noel Avila
2017-03-18 17:53 ` [PATCH v2 2/2] l10n: Add git-add.txt to localized " Jean-Noel Avila
2017-03-18 19:41 ` Junio C Hamano [this message]
2017-03-18 22:17 ` [PATCH v2 1/2] l10n: Introduce framework for localizing " Jean-Noël AVILA
2017-03-18 23:03 ` Junio C Hamano
2017-03-20 2:11 ` Junio C Hamano
2017-03-20 8:10 ` Jean-Noël Avila
2017-03-20 8:21 ` Jean-Noël AVILA
2017-03-20 16:50 ` Junio C Hamano
2017-03-20 21:02 ` Rework manpage localisation Jean-Noel Avila
2017-03-20 21:02 ` [PATCH v3 1/2] l10n: Introduce framework for localizing man pages Jean-Noel Avila
2017-03-21 18:09 ` Junio C Hamano
2017-03-20 21:02 ` [PATCH v3 2/2] l10n: Add git-add.txt to localized " Jean-Noel Avila
2017-03-20 22:05 ` Junio C Hamano
2017-03-22 12:01 ` Jean-Noël Avila
2017-03-22 18:02 ` Junio C Hamano
2017-03-22 18:41 ` Stefan Beller
2017-03-22 18:56 ` Junio C Hamano
2017-03-22 18:59 ` Stefan Beller
2017-03-24 14:21 ` Michael J Gruber
2017-03-25 15:40 ` Jean-Noël AVILA
2017-03-26 22:56 ` Junio C Hamano
2017-03-27 20:12 ` Jean-Noël AVILA
2017-03-27 20:29 ` Junio C Hamano
2017-03-24 15:58 ` Ævar Arnfjörð Bjarmason
2017-03-24 17:57 ` 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
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=xmqqfuia1ifx.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
/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).