From: Thomas Rast <trast@student.ethz.ch>
To: Ralf Thielow <ralf.thielow@googlemail.com>
Cc: Christian Stimming <stimming@tuhh.de>, <jk@jk.gs>, <git@vger.kernel.org>
Subject: Re: [PATCH 2/5] l10n: de.po: translate "track" as "folgen"
Date: Mon, 7 May 2012 14:21:47 +0200 [thread overview]
Message-ID: <878vh46v1g.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <CAN0XMOJgp-i=nd_7ygX=WuaegK6zMRypxRYH8nfGw6FLPAA1Fg@mail.gmail.com> (Ralf Thielow's message of "Mon, 7 May 2012 13:08:17 +0200")
Ralf Thielow <ralf.thielow@googlemail.com> writes:
>> How about "beobachten" (for the English readers, roughly "observe") or
>> "beachten" ("pay attention to") for this meaning of tracking? The
>> latter even forms a nice group with "unbeachtet" and "ignoriert".
[...]
> I personally prefer "beobachten" for tracked files/contents and, as you
> said, "folgen" in the remote-tracking sense. But I wouldn't use
> "ignoriert" because it has another meaning in git.
But that fits right in, doesn't it? Files can be tracked, untracked, or
untracked-and-ignored.
Or am I missing something?
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-05-07 12:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 19:48 [PATCH 0/5] l10n: de.po: improvements Ralf Thielow
2012-05-04 19:48 ` [PATCH 1/5] l10n: add new members to German translation team Ralf Thielow
2012-05-04 19:48 ` [PATCH 2/5] l10n: de.po: translate "track" as "folgen" Ralf Thielow
2012-05-06 15:20 ` Christian Stimming
2012-05-07 10:09 ` Thomas Rast
2012-05-07 11:08 ` Ralf Thielow
2012-05-07 11:28 ` Christian Stimming
2012-05-07 12:21 ` Thomas Rast [this message]
2012-05-07 12:37 ` Ralf Thielow
2012-05-04 19:48 ` [PATCH 3/5] l10n: de.po: translate "remote" as "extern" Ralf Thielow
2012-05-04 19:48 ` [PATCH 4/5] l10n: de.po: collection of improvements Ralf Thielow
2012-05-04 19:48 ` [PATCH 5/5] l10n: de.po: unify translation of "ahead" and "behind" Ralf Thielow
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=878vh46v1g.fsf@thomas.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=jk@jk.gs \
--cc=ralf.thielow@googlemail.com \
--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 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.