From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Christian Stimming <stimming@tuhh.de>, git@vger.kernel.org
Subject: Re: git-gui i18n / 0.9.x plans
Date: Tue, 31 Jul 2007 11:47:30 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0707311136540.14781@racer.site> (raw)
In-Reply-To: <20070731012804.GZ20052@spearce.org>
Hi,
On Mon, 30 Jul 2007, Shawn O. Pearce wrote:
> Regarding future development for the off-in-the-future 0.9.0 release I'd
> like to see the i18n work merge in before we do anything else major to
> git-gui.
Very good! As it happens, I pushed an update this morning.
temp-rebase-to-shawns-master is the branch which forward-ported all
patches to the current master of git-gui.git.
As I understand, Christian will find and mark all strings lacking [mc ...]
and update the .pot file. Then we'll kindly ask the good translators
(thanks everyone!) to review the changes, and after that I'll prepare some
submittable patch series (no need to have several patches per language).
> - Hunk splitting/selection
Yeah, I am personally interested in this, so time permitting I will
continue on that part. Regarding your idea from another post of yours:
IMHO selections are only meaningful if they take whole lines. But that's
almost like hunk splitting, so it should be easy to support with the code
I wrote and will have written.
Ciao,
Dscho
next prev parent reply other threads:[~2007-07-31 10:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 1:28 git-gui i18n / 0.9.x plans Shawn O. Pearce
2007-07-31 10:47 ` Johannes Schindelin [this message]
2007-08-12 20:08 ` Christian Stimming
2007-07-31 13:38 ` Jean-François Veillette
2007-07-31 14:32 ` 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=Pine.LNX.4.64.0707311136540.14781@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=spearce@spearce.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).