git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Soria <sn_@gmx.net>
To: git@vger.kernel.org
Subject: Re: RFC: German translation vocabulary
Date: Sun, 16 Sep 2007 15:01:04 +0000 (UTC)	[thread overview]
Message-ID: <fcjgfg$56m$1@sea.gmane.org> (raw)
In-Reply-To: 200709161438.37733.stimming@tuhh.de

Am Sun, 16 Sep 2007 14:38:37 +0200 schrieb Christian Stimming:



Hi Christian,

thank you for bringing up the topic, it's really worth discussing it.

> [commit] message - Meldung (Nachricht?; Source Safe: Kommentar)
I prefer "Kommentar" here. It describes better what the commit message is
about. "Meldung" has some co-notations that don't fit (like e.g.
"Meldung" often involes other people, like you "meldest" something to
somebody).
 
> I'm still rather unsure what to do about them. One problem here is that
> both words are used in several different meanings all at once. For
> example, the "commit [noun]" is used interchangeably with "revision".
> I'm actually inclined to translate it with "Version" for exactly that
> reason. And then "checkout": The noun is probably used interchangeably
> with "working copy". Hence, it could be translated as such. OTOH the
> verb means "to update the working copy", and it could be translated as
> such instead of one single word. This would leave only "commit [verb]"
> as the last tricky issue for which a single-word translation must be
> found. "übertragen" is my current favorite but I'm absolutely open for
> further proposals here.
> 
> As you can see in the glossary file, I'm still unhappy with the
> translations for those, but anyway here's the current status (not taking
> into account the discussion of the previous paragraph so far):
> 
Really hard. I would prefer some larger explanations if they fit into the
application and make sense on every label in the gui.


> msgid "commit [noun]"
> msgstr "Übertragung (Sendung?, Übergabe?, Einspielung?, Ablagevorgang?)"
Übertragung fits well, but for me it has a co-notation that something is
transfered from one point to another (e.g. using an internet connection)
So this translation would fit perfectly for centralized versioning
systems, where the changeset is really "transfered" to somewhere. I would
prefer the term "Einspielung" as I think it reflects better, that the
commit is locally.

David

  reply	other threads:[~2007-09-16 15:02 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-09-16 12:38 RFC: German translation vocabulary Christian Stimming
2007-09-16 15:01 ` David Soria [this message]
2007-09-16 15:07   ` David Kastrup
2007-09-16 15:08     ` David Kastrup
2007-09-16 15:12       ` David Soria
2007-09-16 17:23 ` Alexander Wuerstlein
2007-09-16 21:34   ` David Kastrup
2007-09-17  7:54     ` Alexander Wuerstlein
2007-09-17  9:17       ` Johannes Schindelin
2007-09-17 19:09         ` Christian Stimming
2007-09-17 12:42       ` David Kastrup
2007-09-16 19:44 ` Simon Richter
2007-09-16 21:36   ` David Kastrup
2007-09-16 20:11 ` RFC: Italian " Michele Ballabio
2007-09-16 20:21 ` RFC: German " Florian Weimer
2007-09-16 21:37   ` David Kastrup
2007-09-17 19:45   ` Christian Stimming
2007-09-17 19:56     ` Florian Weimer

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='fcjgfg$56m$1@sea.gmane.org' \
    --to=sn_@gmx.net \
    --cc=git@vger.kernel.org \
    /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).