From: Stephan Beyer <s-beyer@gmx.net>
To: Christian Stimming <stimming@tuhh.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] gitk: Update German translation
Date: Sun, 25 May 2008 23:57:08 +0200 [thread overview]
Message-ID: <20080525215708.GB9564@leksak.fem-net> (raw)
In-Reply-To: <200805242248.23413.stimming@tuhh.de>
[-- Attachment #1: Type: text/plain, Size: 1348 bytes --]
Hi Christian,
> > I want to repeat my suggestions from the last mail:
> > 1. "Suche nächste/vorige Version nach _Beschreibung:_ [insert]"
> > 2. "Suche nächste/vorige Version nach _Pfaden:_ [insert]"
> > (or maybe "nach _Dateien:_", if it's commonly accepted that
> > directories are files, too.)
> > 3. "Suche nächste/vorige Version nach _Änderungen:_ [insert]"
> > which makes it much more clearer than the English original, imho.
>
> Okay, I've inserted your suggestions in my translation update. I'm not too
> sure about any translation of this part, but your proposal is maybe better
> than the existing one.
You can make yourself sure by trying the features or by reading the
source code. ;-)
Since I've translated them in that way, I know what they do and I use them
more often. So I'm pretty sure.
> > And I think a better translation for "pull" is
> > something that stresses the fact that "pull" = "fetch" + "merge",
> > something like "Holen und Zusammenführen".
>
> That's indeed an interesting suggestion. (Which bears the question why it is
> being called "pull" in English in the first place,
Well, this seems not to be clear to some users, since there is often
uncertainty about "pull" ;)
Regards,
Stephan
--
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-05-25 21:58 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-01 19:42 [PATCH] gitk: Update German translation Christian Stimming
2008-05-01 21:10 ` Stephan Beyer
2008-05-02 19:23 ` Christian Stimming
2008-05-03 1:24 ` Stephan Beyer
2008-05-07 20:56 ` Christian Stimming
2008-05-15 16:20 ` Stephan Beyer
2008-05-24 20:48 ` Christian Stimming
2008-05-25 21:57 ` Stephan Beyer [this message]
2008-05-02 19:36 ` [PATCH] gitk: German translation again updated Christian Stimming
2008-05-02 11:49 ` [PATCH] gitk: Update German translation Paul Mackerras
2008-05-02 18:33 ` Christian Stimming
2008-05-03 7:53 ` Paul Mackerras
2008-05-03 8:03 ` Christian Stimming
2008-05-02 12:56 ` Paul Mackerras
2008-05-02 18:30 ` Christian Stimming
-- strict thread matches above, loose matches on Subject: below --
2016-02-12 18:40 [PATCH] gitk: update " Ralf Thielow
2016-02-12 18:56 ` Stefan Beller
2016-02-12 19:17 ` Ralf Thielow
2016-03-19 6:56 ` Paul Mackerras
2010-01-27 19:30 [PATCH] gitk: Update " Christian Stimming
2009-09-25 20:41 Christian Stimming
2009-05-12 20:20 Christian Stimming
2008-01-09 21:24 Christian Stimming
2008-01-15 11:54 ` Paul Mackerras
2008-01-15 12:49 ` Christian Stimming
2008-01-08 20:56 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=20080525215708.GB9564@leksak.fem-net \
--to=s-beyer@gmx.net \
--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).