From: Thomas Rast <trast@student.ethz.ch>
To: Ralf Thielow <ralf.thielow@googlemail.com>
Cc: "Jiang Xin" <worldhello.net@gmail.com>,
"Git List" <git@vger.kernel.org>,
"Junio C Hamano" <gitster@pobox.com>, "Jan Krüger" <jk@jk.gs>,
"Christian Stimming" <stimming@tuhh.de>
Subject: [PATCH 0/5] de.po suggested updates
Date: Wed, 2 May 2012 15:49:22 +0200 [thread overview]
Message-ID: <cover.1335966202.git.trast@student.ethz.ch> (raw)
In-Reply-To: <87d36n2f2r.fsf@thomas.inf.ethz.ch>
I wrote:
> Of course now that it has been released, we'll also have to file patches
> in the true open source spirit. Sigh.
So here goes.
[1/5] is actually intended for Junio to pick up, and makes a message
translatable that somehow got away last time.
The rest are for Ralf.
[2/5] does away with the "bare"->"leer" issue that I used as an
example earlier. There's precedent in git-gui :-( This does
raise the question if it's kosher to patch both git and git-gui
at the same time, but if we want to keep the translations in
sync it probably won't be the last such patch.
[3/5] collects all the "obvious" stuff
[4/5] and [5/5] gather the less-obvious stuff -- keep what you like.
Cheers,
Thomas
Thomas Rast (5):
stash: make "saved" message translatable
de.po: translate "bare" as "bloß"
de.po: hopefully uncontroversial fixes
de.po: translate "bad" as "ungültig" ("invalid")
de.po: collection of suggestions
git-gui/po/de.po | 4 +-
git-stash.sh | 2 +-
po/de.po | 153 +++++++++++++++++++++++++-----------------------------
3 files changed, 74 insertions(+), 85 deletions(-)
--
1.7.10.625.g300dcf
next prev parent reply other threads:[~2012-05-02 13:49 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-02 2:45 Please pull git-po master branch Jiang Xin
2012-05-02 5:17 ` Junio C Hamano
2012-05-02 7:54 ` Thomas Rast
2012-05-02 9:13 ` Ralf Thielow
2012-05-02 13:58 ` Thomas Rast
2012-05-02 19:14 ` Ralf Thielow
2012-05-02 19:44 ` Christian Stimming
2012-05-02 13:49 ` Thomas Rast [this message]
2012-05-02 13:49 ` [PATCH 1/5] stash: make "saved" message translatable Thomas Rast
2012-05-02 16:42 ` Junio C Hamano
2012-05-02 13:49 ` [PATCH de.po 2/5] de.po: translate "bare" as "bloß" Thomas Rast
2012-05-02 13:49 ` [PATCH de.po 3/5] de.po: hopefully uncontroversial fixes Thomas Rast
2012-05-02 13:49 ` [PATCH de.po 4/5] de.po: translate "bad" as "ungültig" ("invalid") Thomas Rast
2012-05-02 13:49 ` [PATCH de.po 5/5] de.po: collection of suggestions Thomas Rast
2012-05-02 18:36 ` Ralf Thielow
2012-05-02 19:43 ` Thomas Rast
2012-05-02 19:42 ` Christian Stimming
2012-05-03 7:42 ` Thomas Rast
2012-05-03 13:12 ` [PATCH on ab/i18n] branch: remove lego in i18n tracking info strings Nguyễn Thái Ngọc Duy
2012-05-04 16:10 ` Junio C Hamano
2012-05-06 13:06 ` Nguyen Thai Ngoc Duy
2012-05-02 17:52 ` [PATCH 0/5] de.po suggested updates Ralf Thielow
2012-05-02 19:13 ` Christian Stimming
2012-05-02 16:40 ` Please pull git-po master branch Junio C Hamano
2012-05-03 4:31 ` Jiang Xin
2012-05-03 6:47 ` Junio C Hamano
2012-05-03 10:19 ` Jiang Xin
2012-05-03 7:49 ` Thomas Rast
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=cover.1335966202.git.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jk@jk.gs \
--cc=ralf.thielow@googlemail.com \
--cc=stimming@tuhh.de \
--cc=worldhello.net@gmail.com \
/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).