git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: Christian Stimming <stimming@tuhh.de>,
	Junio C Hamano <gitster@pobox.com>,
	git@vger.kernel.org
Subject: Re: git-gui i18n status?
Date: Mon, 17 Sep 2007 10:04:06 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0709171002510.28586@racer.site> (raw)
In-Reply-To: <20070917032042.GF3099@spearce.org>

Hi,

On Sun, 16 Sep 2007, Shawn O. Pearce wrote:

> Christian Stimming <stimming@tuhh.de> wrote:
>
> > 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.
> 
> I was sort of hoping Dscho would be able to answer that.  ;-)

Heh.  Yeah, sorry...  I got sidetracked with other stuff.

Will try to find some time for i18n,
Dscho

  reply	other threads:[~2007-09-17  9:06 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-01  4:29 git-gui i18n status? Shawn O. Pearce
2007-09-01 23:42 ` Johannes Schindelin
2007-09-02  1:00   ` Junio C Hamano
2007-09-02  1:42   ` Shawn O. Pearce
2007-09-02  2:24     ` Shawn O. Pearce
2007-09-02 12:20       ` Johannes Schindelin
2007-09-16 12:03         ` Christian Stimming
2007-09-17  3:20           ` Shawn O. Pearce
2007-09-17  9:04             ` Johannes Schindelin [this message]
2007-09-02 12:29     ` Johannes Schindelin
2007-09-02 14:17   ` Michele Ballabio
  -- strict thread matches above, loose matches on Subject: below --
2007-09-02 15:09 Michele Ballabio

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

  List information: http://vger.kernel.org/majordomo-info.html

* 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.0709171002510.28586@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).