git-gui translators - please update translations if necessary

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.

Thanks.

"Shawn O. Pearce" <spearce@spearce.org> writes:

Thanks.

There have been a handful gitweb patches on the list recently (I think they were all post -rc0 feature enhancements, but I may be mistaken). I'm wondering what their status are. Does any of them matter in the current cycle?

By the way, I've privately pinged Paul for gitk status.

On Sat, Aug 02, 2008 at 02:28:27PM -0700, Junio C Hamano wrote:

I think these are all feature enhancements and I'd rather wait with them for 1.6.1 (and I'm preparing to dump quite a few my gitweb patches afer 1.6.0 is out as well ;).

"Shawn O. Pearce" <spearce@spearce.org> writes:

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?

Junio C Hamano <gitster@pobox.com> wrote:

Oh. Its updated now, but msgmerge on my system is busted and won't update the po files themselves. *sigh*

"Shawn O. Pearce" <spearce@spearce.org> writes:

I think that's Ok.  msgmerge and edit are in the translators' bailiwick.

Shawn O. Pearce:

In that case I would recommend submitting the translation to translationsproject.org, which helps both you and us translators in handling all the uninteresting tool-bashing itself. Submit an updated POT file when strings are frozen, and download all the updated translations before releasing.

Peter Krefting <peter@softwolves.pp.se> wrote:

This has come up before on the mailing list. We talked about moving to translationsproject.org but decided against it at that time as the current pool of translators for Git felt the dictionary involved was too technical (and too Git specific) for the run-of-the-mill translators who work through translationsproject.org. At least some knowledge of Git is required to get a good translation, and we cannot except all translators to have that.

So translation work is still here, on this mailing list.

Shawn O. Pearce:

The problem is then that it might drown in the noise. And of course the problem with having to do all the boring tool-bashing yourself :-)