From: Jonathan Nieder <jrnieder@gmail.com>
To: Jiang Xin <worldhello.net@gmail.com>
Cc: "Git List" <git@vger.kernel.org>,
"Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Alexander Shopov (Александър Шопов)" <lists@kambanaria.org>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: Bulgarian translation of git
Date: Mon, 13 Feb 2012 08:00:36 -0600 [thread overview]
Message-ID: <20120213133957.GA4838@burratino> (raw)
In-Reply-To: <7vy5s7idxb.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> Jiang Xin <worldhello.net@gmail.com> writes:
>> I have a question, which version of po should be maintained? master
>> branch or maint branch.
>
> I would say for this round the git-po repository and its pot file should
> pick up whatever new translatable strings are added to 'master'.
>
> After this is merged in 1.7.10, we may want to maintain separate tracks,
> but at this moment there is no point maintaining something mergeable to
> 1.7.9.x maintenance track.
I wonder if there's a simple to ask the gettext tools to make a po
template including strings from both 'maint' and 'master'. (Hackish way
demonstrated below.)
Hopefully that would make it easier for translators to keep both
tracks well maintained at the same time. If a problem in the
translation of a string shared by 'master' and 'maint' is only noticed
while working on 'master', there would be no need to go through the
"switch branches; make the change; switch back; merge" dance.
What do you think?
Jonathan
diff --git i/Makefile w/Makefile
index 1e91b19c..5dbc6205 100644
--- i/Makefile
+++ w/Makefile
@@ -2103,7 +2103,8 @@ LOCALIZED_C := $(C_OBJ:o=c)
LOCALIZED_SH := $(SCRIPT_SH)
po/git.pot: $(LOCALIZED_C)
- $(QUIET_XGETTEXT)$(XGETTEXT) -o$@+ $(XGETTEXT_FLAGS_C) $(LOCALIZED_C)
+ cp $@ $@+
+ $(QUIET_XGETTEXT)$(XGETTEXT) -o$@+ --join-existing $(XGETTEXT_FLAGS_C) $(LOCALIZED_C)
$(QUIET_XGETTEXT)$(XGETTEXT) -o$@+ --join-existing $(XGETTEXT_FLAGS_SH) \
$(LOCALIZED_SH)
mv $@+ $@
next prev parent reply other threads:[~2012-02-13 14:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-10 12:26 Bulgarian translation of git Alexander Shopov (Александър Шопов)
2012-02-13 2:46 ` Jiang Xin
2012-02-13 3:56 ` Junio C Hamano
2012-02-13 7:12 ` Jiang Xin
2012-02-13 8:07 ` Junio C Hamano
2012-02-13 8:52 ` Jiang Xin
2012-02-13 14:00 ` Jonathan Nieder [this message]
2012-02-13 15:43 ` Jiang Xin
2012-02-13 15:56 ` Jonathan Nieder
2012-02-13 18:52 ` Junio C Hamano
2012-02-15 3:28 ` Jiang Xin
2012-02-15 18:09 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120213133957.GA4838@burratino \
--to=jrnieder@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=lists@kambanaria.org \
--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).