git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Shawn O. Pearce" <spearce@spearce.org>
To: Christian Stimming <stimming@tuhh.de>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>, git@vger.kernel.org
Subject: Re: [PATCH 1/4] git-gui i18n: Add more words to glossary.
Date: Wed, 10 Oct 2007 02:03:28 -0400	[thread overview]
Message-ID: <20071010060328.GO2137@spearce.org> (raw)
In-Reply-To: <200710082143.13750.stimming@tuhh.de>

Christian Stimming <stimming@tuhh.de> wrote:
> All pushed to git-gui-i18n.git mob branch now.  I hope you can easily merge 
> them over.

I basically had to cherry-pick your 4 patches out of the mob branch
from the i18n fork.  The issue is the mob branch is based on an old
lineage that Dscho hand picked patches out of and squashed when he
created the initial i18n series for me to merge.

The i18n fork as it currently stands is pretty far away from my
own tree; it probably should be reset to my tree in the near future.
 
> Maybe po/git-gui.pot should be updated by you on git-gui.git and (by Dscho?) 
> on git-gui-i18n.git as well. 

Yea, I'll run it before I push out my newest master tonight.
 
> 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...

I agree on the need for the string freeze period and will plan
to include a 14+ day window near the end of the 0.9.0 release to
update the translations.  I want to get the major functionality
written and then we can work on debugging/testing/translation.

Schedule wise I'm probably looking at middle of next month or the
month after (so Nov 15th-ish or Dec 15th-ish) for the 0.9.0 string
freeze period starting.  That means there is a good chance we won't
be seeing 0.9.0 final in 2007; probably it will be in early 2008.

-- 
Shawn.

  reply	other threads:[~2007-10-10  6:03 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-05 20:39 [PATCH 1/4] git-gui i18n: Add more words to glossary Christian Stimming
2007-10-05 20:39 ` [PATCH 2/4] git-gui i18n: Update German glossary according to mailing list discussion Christian Stimming
2007-10-05 20:40   ` [PATCH 3/4] git-gui i18n: Incorporate glossary changes into existing German translation Christian Stimming
2007-10-05 20:41     ` [PATCH 4/4] git-gui i18n: Update German translation, including latest glossary changes Christian Stimming
2007-10-07 18:05 ` [PATCH 1/4] git-gui i18n: Add more words to glossary Shawn O. Pearce
2007-10-07 20:42   ` Christian Stimming
2007-10-07 23:12     ` Shawn O. Pearce
2007-10-07 23:31       ` Johannes Schindelin
2007-10-07 23:39         ` Shawn O. Pearce
2007-10-08 19:43           ` Christian Stimming
2007-10-10  6:03             ` Shawn O. Pearce [this message]
2007-10-10 16:01               ` Johannes Schindelin
2007-10-20 13:30               ` [PATCH 1/2] git-gui: Add more terms " Christian Stimming
2007-10-20 13:31                 ` [PATCH 2/2] git-gui: Update German translation Christian Stimming

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=20071010060328.GO2137@spearce.org \
    --to=spearce@spearce.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=stimming@tuhh.de \
    /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).