git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
To: "Jean-Noël AVILA" <jn.avila@free.fr>
Cc: "Alexander Shopov" <ash@kambanaria.org>,
	"Jordi Mas" <jmas@softcatala.org>,
	"Ralf Thielow" <ralf.thielow@gmail.com>,
	"Christopher Díaz" <christopher.diaz.riv@gmail.com>,
	"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>,
	git@vger.kernel.org, "Jeff King" <peff@peff.net>
Subject: Re: Translation of git manpages
Date: Tue, 08 Jan 2019 14:54:36 +0100	[thread overview]
Message-ID: <87lg3v6yqr.fsf@evledraar.gmail.com> (raw)
In-Reply-To: <1992944.NOdEsaAZKb@cayenne>


On Mon, Jan 07 2019, Jean-Noël AVILA wrote:

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

Thanks. This has come up on list many times before and it's great to
have some movement on it.

I think a way to have early exposure of these to a lot more people would
be to have these on the git-scm.com site. Jeff knows more about the
build process there.

I see the general completion of French & German is at ~10%, but maybe
there's some pages that are fully translated already? We could then have
some UI or git-scm.com that allows you to switch between languages along
with some general overview page per-language.

Are the translations contributed through
https://hosted.weblate.org/projects/git-manpages/translations/ something
that license-wise (Signed-off-by etc.) we'd eventually be able to
upstream in git.git?

It would be great to eventually have something we can build as part of
our build process, so e.g. Debian can have git-man-de similar to
manpages-de now.

  reply	other threads:[~2019-01-08 13:54 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-01-07 20:45 Translation of git manpages Jean-Noël AVILA
2019-01-08 13:54 ` Ævar Arnfjörð Bjarmason [this message]
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=87lg3v6yqr.fsf@evledraar.gmail.com \
    --to=avarab@gmail.com \
    --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=jn.avila@free.fr \
    --cc=marcopaolone@gmail.com \
    --cc=peff@peff.net \
    --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).