From: Junio C Hamano <gitster@pobox.com>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: Re: git-gui translators: gitgui-0.10.0 coming soon
Date: Wed, 12 Mar 2008 22:36:05 -0700 [thread overview]
Message-ID: <7v4pbb18ze.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080313052713.GU8410@spearce.org> (Shawn O. Pearce's message of "Thu, 13 Mar 2008 01:27:13 -0400")
"Shawn O. Pearce" <spearce@spearce.org> writes:
> I'm nearing the point where I want to cut a 0.10.0 tag, as Junio
> is looking to do 1.5.5-rc0/1 in the near future.
>
> I've been busy on jgit/egit lately, and day-job, so I haven't
> done any major feature development on git-gui in a few weeks.
> Its basically in feature freeze at this point.
>
> If you get a chance, please review your translations and send a
> patch if there are any updates.
>
> Current status of my master branch:
>
> MSGFMT po/de.msg 386 translated.
> MSGFMT po/fr.msg 371 translated.
> MSGFMT po/hu.msg 371 translated.
> MSGFMT po/it.msg 390 translated, 1 untranslated.
> MSGFMT po/ja.msg 371 translated.
> MSGFMT po/ru.msg 367 translated, 4 untranslated.
> MSGFMT po/sv.msg 371 translated.
> MSGFMT po/zh_cn.msg 368 translated, 2 fuzzy, 1 untranslated.
Just curious. Why do these languages have different totall number of
messages?
next prev parent reply other threads:[~2008-03-13 5:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 5:27 git-gui translators: gitgui-0.10.0 coming soon Shawn O. Pearce
2008-03-13 5:36 ` Junio C Hamano [this message]
2008-03-13 5:42 ` Shawn O. Pearce
2008-03-13 13:25 ` Miklos Vajna
2008-03-14 6:27 ` Peter Karlsson
2008-03-14 6:38 ` Shawn O. Pearce
2008-03-14 8:38 ` Peter Karlsson
2008-03-15 3:31 ` Shawn O. Pearce
2008-03-14 16:38 ` Miklos Vajna
2008-03-14 20:59 ` [PATCH] git-gui: remove spurious "fuzzy" attributes in po/it.po Michele Ballabio
2008-03-15 5:00 ` Shawn O. Pearce
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=7v4pbb18ze.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).