All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Rast <trast@inf.ethz.ch>
To: Christian Stimming <stimming@tuhh.de>
Cc: "Thomas Rast" <trast@student.ethz.ch>,
	"Ralf Thielow" <ralf.thielow@googlemail.com>,
	"Jiang Xin" <worldhello.net@gmail.com>,
	"Git List" <git@vger.kernel.org>,
	"Junio C Hamano" <gitster@pobox.com>, "Jan Krüger" <jk@jk.gs>
Subject: Re: [PATCH de.po 5/5] de.po: collection of suggestions
Date: Thu, 3 May 2012 09:42:06 +0200	[thread overview]
Message-ID: <877gwtyalt.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <3137881.zK1NKVIFJ3@cs-pc> (Christian Stimming's message of "Wed, 2 May 2012 21:42:06 +0200")

Christian Stimming <stimming@tuhh.de> writes:

> As one of the earlier translators: I agree with most of those as well. Thanks 
> a lot. However, one small remark:
>
> Am Mittwoch, 2. Mai 2012, 15:49:27 schrieb Thomas Rast:
>> @@ -676,11 +675,11 @@ msgstr "hinter "
>> 
>>  #: wt-status.c:908 wt-status.c:911
>>  msgid "ahead "
>> -msgstr "über "
>> +msgstr "weiter: "
>> 
>>  #: wt-status.c:913
>>  msgid ", behind "
>> -msgstr ", hinter "
>> +msgstr ", zurückgefallen "
>> 
>>  #: builtin/add.c:62
>>  #, c-format
>> @@ -903,12 +902,12 @@ msgstr "Zweig '%s' zeigt auf keine Version"
>>  #: builtin/branch.c:396
>>  #, c-format
>>  msgid "behind %d] "
>> -msgstr "hinter %d] "
>> +msgstr "%d hinterher] "
>> 
>>  #: builtin/branch.c:398
>>  #, c-format
>>  msgid "ahead %d] "
>> -msgstr "vor %d] "
>> +msgstr "%d voraus] "
>
> In the above hunk, you said "ahead = weiter" and "behind = zurückgefallen", 
> but now you say "ahead = voraus" and "behind = hinterher". Is it helpful to 
> use two different translations, or shouldn't those rather be chosen 
> identically? The second set sounds somewhat better to me, but the more 
> important question is whether both hunks should use the same translations.

Yeah, sorry about that.  The whole thing is a mess because of the lego
going on.  It would probably be better to first patch the code into
shape so that it builds the displays in one step, and then translate
that.  As it stands, it's very hard to translate because wt-status.c
does not even let you reposition the number.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch

  reply	other threads:[~2012-05-03  7:42 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   ` [PATCH 0/5] de.po suggested updates Thomas Rast
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 [this message]
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=877gwtyalt.fsf@thomas.inf.ethz.ch \
    --to=trast@inf.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=trast@student.ethz.ch \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.