Re: [PATCH 1/4] git-gui i18n: Add more words to glossary.

[Christian Stimming <stimming@tuhh.de>]

Am Montag, 8. Oktober 2007 01:39 schrieb Shawn O. Pearce:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote:
> > On Sun, 7 Oct 2007, Shawn O. Pearce wrote:
> > > If you are sending a series like that and its all po translation stuff
> > > that is unlikely to need commenting on feel free to just dump it all
> > > out as a single mbox (`git format-patch --stdout`) and attach it to the
> > > email.  Less chance of the MUA mangling the message.
> >
> > In this case, I suggest just pushing it to git-gui-i18n.git, maybe as a
> > temporary branch "for-shawn", and send a pull request.  That's the best
> > way to ensure that nothing gets mangled.
>
> Yea, that's an even better option.  :-)

All pushed to git-gui-i18n.git mob branch now.  I hope you can easily merge 
them over.

Maybe po/git-gui.pot should be updated by you on git-gui.git and (by Dscho?) 
on git-gui-i18n.git as well. 

In other news, according to http://marc.info/?l=git&m=119170887523610&w=2 
(almost last paragraph) people are already recognizing the localized 
versions, but this also means the translations have to be watched out for so 
that they will get updated as completely as possible especially before the 
next release. 
http://wiki.gnucash.org/wiki/index.php?title=String_Freeze&oldid=2022 is an 
example on how the gnucash project tried to communicate to its translators 
how the special "string freeze" period (i.e. a few weeks before the release) 
will be handled in order to get a finalized translation for the actual 
release. I don't know how formal you want to put this, but at least *some* 
period of string freeze would be very good. As for the German translation, 
I'd prefer any period length greater than 10 days in order to verify a 
complete translation...

Regards,

Christian