Re: [PATCH v2 1/2] l10n: Introduce framework for localizing man pages

From: Junio C Hamano <gitster@pobox.com>
Date: Mar 18, 2017, 23:03 UTC
Message-ID: <xmqq37ea192h.fsf@gitster.mtv.corp.google.com>
In-Reply-To: <xmqqfuia1ifx.fsf@gitster.mtv.corp.google.com>

Junio C Hamano <gitster@pobox.com> writes:

Show 24 quoted lines

> 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.

Travis seems to have failed. Perhaps something like this is needed, at least?

 .travis.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.travis.yml b/.travis.yml
index 591cc57b80..719e5cdb00 100644
--- a/.travis.yml
+++ b/.travis.yml
@@ -20,6 +20,7 @@ addons:
     - language-pack-is
     - git-svn
     - apache2
+    - po4a
 
 env:
   global: