From: Thomas Rast <trast@inf.ethz.ch>
To: Christian Stimming <stimming@tuhh.de>
Cc: Ralf Thielow <ralf.thielow@googlemail.com>, <jk@jk.gs>,
<git@vger.kernel.org>
Subject: Re: [PATCH 2/5] l10n: de.po: translate "track" as "folgen"
Date: Mon, 7 May 2012 12:09:38 +0200 [thread overview]
Message-ID: <87obq08fq5.fsf@thomas.inf.ethz.ch> (raw)
In-Reply-To: <1543115.9YNtu9coLS@cs-pc> (Christian Stimming's message of "Sun, 6 May 2012 17:20:46 +0200")
Christian Stimming <stimming@tuhh.de> writes:
> Am Freitag, 4. Mai 2012, 21:48:23 schrieb Ralf Thielow:
>> The word "track" was translated as "verfolgt"
>> which is not the correct word for it. We've
>> changed it to "folgen".
>
> I'm not so sure about this choice. We're talking about files which are tracked
> by git (i.e. being versioned) vs. files or content that are not tracked, i.e.
> those are just existing in the working copy's directory but are not tracked by
> git. I think from the point of view of git, the content of the files is being
> "verfolgt" vs. "nicht verfolgt", as git checks whether the content is changing
> vs. git doesn't check this. Saying "folgen" here rather sounds like git is
> following something, just as your twitter account is following other
> twitterers. Consider a choicebox "Änderungen dieser Datei verfolgen" vs.
> "Änderungen dieser Datei folgen". In the former case, git is the subject and
> it is tracking the file's content. In the latter case, the file is the subject
> and git is triggered into some action when the file content changes. I think
> the former fits the use case more.
Good point. In addition, both "folgen" and "verfolgen" have the problem
that several derived words sound funny; e.g. "verfolgt" and "folgend".
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".
You could use "folgen" in the remote-tracking sense instead?
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2012-05-07 10:09 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 [this message]
2012-05-07 11:08 ` Ralf Thielow
2012-05-07 11:28 ` Christian Stimming
2012-05-07 12:21 ` Thomas Rast
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=87obq08fq5.fsf@thomas.inf.ethz.ch \
--to=trast@inf.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 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).