From: "Jean-Noël AVILA" <jn.avila@free.fr>
To: git@vger.kernel.org
Subject: Re: [PATCH] l10n: add framework for localizing the manpages
Date: Sun, 12 Mar 2017 21:36:32 +0100 [thread overview]
Message-ID: <12214955.EmB7ja1MbS@cayenne> (raw)
In-Reply-To: <20170312200248.3610-2-jn.avila@free.fr>
This patch is only a preview and a request for comment. The tool used to
perform the localization of manpages is po4a (po for anything). This tool
digests the asciidoc source files and writes a pot file, and then merges back
the po files into translated asciidoc files, for further processing.
The choice of this workflow is driven by two concerns: manage the tracking of
the changes in the original files and provide the translators with a format of
file that they already use. Moreover, I plan to upload the po files to web
translation platforms such as transifex or weblate to take advantage of crowd
translation.
In this patch, only one manpage is generated for the git-add command in
french. po4a already supports extending to other languages, and merges all the
strings from multiple source manpages into one big pot file. In the next
version, two files will be included so that the sharing of common strings is
shown. There are some enhancement needed for better support of other output
formats.
One problem with this setup is that we don't know before hand which files will
be generated from the po files and the source files. This depends on the level
of completion of translation for each language and each target file. To
circumvent this, the makefile calls itself recursively after running po4a, so
that the generated files can be enumerated in the downstream targets.
It would be understandable that the git devel list would not like to be
spammed by the traffic generated by this new activity.If the present proposition
is accepted, I'm open to any modus operandi for submitting the changes.
Thanks for reading.
next prev parent reply other threads:[~2017-03-12 20:36 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 [this message]
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 ` [PATCH v2 1/2] l10n: Introduce framework for localizing " Junio C Hamano
2017-03-18 22:17 ` 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=12214955.EmB7ja1MbS@cayenne \
--to=jn.avila@free.fr \
--cc=git@vger.kernel.org \
/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).