From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: git-gui translators - please update translations if necessary
Date: Sat, 02 Aug 2008 14:41:39 -0700 [thread overview]
Message-ID: <7vod4bccx8.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080802211714.GG24723@spearce.org> (Shawn O. Pearce's message of "Sat, 2 Aug 2008 14:17:14 -0700")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> We're getting ready for the git 1.6 release in the not-too-distant
> future, and that will ship with gitgui-0.11.
>
> The current tip of my master branch builds as follows. There have
> not been many changes in the interface so I don't think there is
> much (if any) translation work for this release.
>
> MSGFMT po/de.msg 402 translated.
> MSGFMT po/fr.msg 391 translated.
> MSGFMT po/hu.msg 391 translated.
> MSGFMT po/it.msg 390 translated, 1 untranslated.
> MSGFMT po/ja.msg 391 translated.
> MSGFMT po/ru.msg 387 translated, 4 untranslated.
> MSGFMT po/sv.msg 391 translated.
> MSGFMT po/zh_cn.msg 367 translated, 7 fuzzy, 17 untranslated.
Hmm, I am confused.
Grepping po/*.po and po/git-gui.pot for POT-Creation-Date reveals that
po/de.msg is much more recent than po/git-gui.pot and all others are
translating the same POT.
Perhaps you wanted to update git-gui.pot first before sending this request
out?
next prev parent reply other threads:[~2008-08-02 21:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-02 21:17 git-gui translators - please update translations if necessary Shawn O. Pearce
2008-08-02 21:28 ` gitweb status for 1.6.0? Junio C Hamano
2008-08-03 12:00 ` Petr Baudis
2008-08-02 21:41 ` Junio C Hamano [this message]
2008-08-02 21:49 ` git-gui translators - please update translations if necessary Shawn O. Pearce
2008-08-02 21:51 ` Junio C Hamano
2008-08-04 11:17 ` Peter Krefting
2008-08-04 14:50 ` Shawn O. Pearce
2008-08-04 18:22 ` Peter Krefting
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=7vod4bccx8.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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.
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).