Re: git-gui i18n status?

From: Christian Stimming <stimming@tuhh.de>
Date: Sep 16, 2007, 12:03 UTC
Message-ID: <200709161403.50780.stimming@tuhh.de>
In-Reply-To: <Pine.LNX.4.64.0709021320230.28586@racer.site>

Hi Shawn et al.,

Am Sonntag, 2. September 2007 14:20 schrieb Johannes Schindelin:

Show 14 quoted lines

> > > > Hmm.  I am not enough involved in i18n stuff to form a proper opinion
> > > > here...  Do you suggest to move the initialisation earlier?
> > >
> > > Yea, I think that's what we are going to have to do here.  If we don't
> > > setup the directory for the .msg files early enough than we cannot do
> > > translations through [mc].  Unfortunately that means we have to also
> > > break up the library initialization.
> > >
> > > I'll try to work up a patch that does this.
> >
> > This two patch series is based on my current master (gitgui-0.8.2).
> > Its also now in my pu branch.
>
> Sound both good to me.  Christian?

Thanks for including the i18n framework and existing translations into the master of git-gui. I loosely watched the progress here, but due to other commitments I cannot spend as much time on git-gui i18n as I initially thought. I'd happily update and polish the German translation, though (will send other email for that), but I probably can't follow any of the ongoing i18n cleanup work.

One question came up when seeing the i18n code really in git-gui.git: How are translators supposed to submit new or updated translations? Is git-gui-i18n.git of any use anymore? This doesn't seem so. Should updated translations just be submitted by email to git@vger? In any case, the instructions in po/README should probably be updated to explain the recommended way of submitting translation updates.

Oh, and po/git-gui.pot should probably be updated to reflect the latest string additions and changes.

Thanks a lot.

Christian