From: "Jean-Noël AVILA" <jn.avila@free.fr>
To: "Alexander Shopov" <ash@kambanaria.org>,
"Jordi Mas" <jmas@softcatala.org>,
"Ralf Thielow" <ralf.thielow@gmail.com>,
"Christopher Díaz" <christopher.diaz.riv@gmail.com>,
"Jean-Noël Avila" <jn.avila@free.fr>,
"Marco Paolone" <marcopaolone@gmail.com>,
"Gwan-gyeong Mun" <elongbug@gmail.com>,
"Vasco Almeida" <vascomalmeida@sapo.pt>,
"Dimitriy Ryazantcev" <DJm00n@mail.ru>,
"Peter Krefting" <peter@softwolves.pp.se>,
"Trần Ngọc Quân" <vnwildman@gmail.com>,
"Alessandro Menti" <alessandro.menti@hotmail.it>,
"Jiang Xin" <worldhello.net@gmail.com>
Cc: git@vger.kernel.org
Subject: Translation of git manpages
Date: Mon, 07 Jan 2019 21:45:12 +0100 [thread overview]
Message-ID: <1992944.NOdEsaAZKb@cayenne> (raw)
Dear fellow translators,
I'm trying to put up a longstanding project of providing translated manual
pages for Git. After several experiments, the best choice seemed to be the use
of po4a[1] to convert the asciidoc[2] sources of git manpages into po files
that could be processed the same way we are already doing for the translation
of Git itself.
The text is segmented into paragraphs and structural units (titles, list
items...) and when translated, they are reinjected into the original text
structure. Only inline asciidoc formatting marks are passed in segments.
The translation takes place in a dedicated repository[3] . It simpler to not
meddle in git main workflow while adjusting the translation workflow. If
everybody is satisfied with it, we can maybe migrate the repo under git
organization. Now, this repo is standalone with respect to translation content
source, but a patch has been submitted so that the translated manpages can be
generated and installed from the main git project[4]. Symmetrically, there's a
script in the project to pull the manpages source files from the main git repo.
The repository is connected to Weblate[5] if you have collaborators who don't
know how to process po files and prefer translating in the browser.
The repository is also open to pull-request on the tooling. Let me know if you
have issues. In any case, the translation work can be reused for any other
arrangements.
There is already a kernel of translation in French, from my experiments and a
previous effort of German translation[6] was gettextized. If you have such
archives for other languages, I'd be happy to integrate them, even if they are
not up to date.
--
Jean-Noël
[1]: https://po4a.org/
[2]: http://asciidoc.org/
[3]: https://github.com/jnavila/git-manpages-l10n
[4]: https://public-inbox.org/git/20190104165406.22358-1-jn.avila@free.fr/
[5]: https://hosted.weblate.org/projects/git-manpages/translations/
[6]: https://repo.or.cz/w/gitman-de.git
next reply other threads:[~2019-01-07 20:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-07 20:45 Jean-Noël AVILA [this message]
2019-01-08 13:54 ` Translation of git manpages Ævar Arnfjörð Bjarmason
2019-01-09 10:32 ` Jeff King
2019-01-09 11:24 ` Jean-Noël Avila
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=1992944.NOdEsaAZKb@cayenne \
--to=jn.avila@free.fr \
--cc=DJm00n@mail.ru \
--cc=alessandro.menti@hotmail.it \
--cc=ash@kambanaria.org \
--cc=christopher.diaz.riv@gmail.com \
--cc=elongbug@gmail.com \
--cc=git@vger.kernel.org \
--cc=jmas@softcatala.org \
--cc=marcopaolone@gmail.com \
--cc=peter@softwolves.pp.se \
--cc=ralf.thielow@gmail.com \
--cc=vascomalmeida@sapo.pt \
--cc=vnwildman@gmail.com \
--cc=worldhello.net@gmail.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).