git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ralf Thielow <ralf.thielow@gmail.com>
To: Xin Jiang <worldhello.net@gmail.com>, Junio C Hamano <gitster@pobox.com>
Cc: "Trần Ngọc Quân" <vnwildman@gmail.com>,
	"Peter Krefting" <peter@softwolves.pp.se>,
	DJm00n@mail.ru, "Marco Sousa" <marcomsousa@gmail.com>,
	cwryu@debian.org, "Marco Paolone" <marcopaolone@gmail.com>,
	"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	"Jean-Noël Avila" <jn.avila@free.fr>,
	"Alex Henrie" <alexhenrie24@gmail.com>,
	"Alexander Shopov" <ash@kambanaria.org>,
	git <git@vger.kernel.org>
Subject: Update *.po with git.pot?
Date: Fri, 18 Mar 2016 21:19:57 +0100	[thread overview]
Message-ID: <CAN0XMO+8PQNXPRgROd9oVqHzTsgLo_k1yP-MLpqK5N44+1ShDQ@mail.gmail.com> (raw)

When a translation round starts for a Git release, the
git.pot file will be updated and translators msgmerge
their .po-files accordingly before translating. This results
in a huge change to the .po-file as line numbers and
stuff gets updated.

Since translations are made in one commit, this commit
is messed up with the msgmerge update so when you
look at the commit later, you'll have a hard time to find
out what the actual changes in translations were.

We could improve this by making git.pot-updates update
the *.po files as well, so further updates from translators
will only contain actual translations. I think this is what the
gitk project does. It will make the history of *.po-files much
more readable.

Ralf

             reply	other threads:[~2016-03-18 20:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-18 20:19 Ralf Thielow [this message]
2016-03-19  6:53 ` Update *.po with git.pot? Peter Krefting
2016-03-20  7:29   ` Jiang Xin

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAN0XMO+8PQNXPRgROd9oVqHzTsgLo_k1yP-MLpqK5N44+1ShDQ@mail.gmail.com \
    --to=ralf.thielow@gmail.com \
    --cc=DJm00n@mail.ru \
    --cc=alexhenrie24@gmail.com \
    --cc=ash@kambanaria.org \
    --cc=avarab@gmail.com \
    --cc=cwryu@debian.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jn.avila@free.fr \
    --cc=marcomsousa@gmail.com \
    --cc=marcopaolone@gmail.com \
    --cc=peter@softwolves.pp.se \
    --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.
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 NNTP newsgroup(s).