From: "Holger Hellmuth (IKS)" <hellmuth@ira.uka.de>
To: Ralf Thielow <ralf.thielow@gmail.com>
Cc: "Christian Stimming" <stimming@tuhh.de>,
"Jens Lehmann" <Jens.Lehmann@web.de>,
"Jan Engelhardt" <jengelh@inai.de>,
"Thomas Rast" <trast@inf.ethz.ch>,
"Ralph Haußmann" <ralph@scanmyfood.de>,
"Sven Fuchs" <svenfuchs@artweb-design.de>,
git <git@vger.kernel.org>, "Jan Krüger" <jk@jk.gs>
Subject: Re: English/German terminology, git.git's de.po, and pro-git
Date: Wed, 22 May 2013 17:52:10 +0200 [thread overview]
Message-ID: <519CE9AA.9010502@ira.uka.de> (raw)
In-Reply-To: <CAN0XMOK4oniunZz5KpC1x=JrY4yH4HnecxMSCyPF+kEyYRRjTw@mail.gmail.com>
Am 22.05.2013 17:16, schrieb Ralf Thielow:
>>> hunk = Bereich
>>
>> IMHO "Kontext" is better if you use a German word. Technically the context is
>> something else, but in a German text IMHO it fits nicer when explaining to the
>> user where he/she can select the n-th hunk.
>>
>
> Not sure if German users would know what "hunk" means, in case we
> leave it untranslated. And I'm not sure if I would understand "Kontext".
> I tend to leave it untranslated.
I don't think "Bereich" is a bad choice. As "hunk" is not a word with
special meaning in cvs and not used in any commands I don't see a lot of
reasons to keep it in english.
Alternative translations might be "Teilbereich", "Dateibereich".
"Kontext" would be very confusing IMHO
next prev parent reply other threads:[~2013-05-22 15:51 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-13 12:54 English/German terminology, git.git's de.po, and pro-git Thomas Rast
2013-05-13 13:57 ` Jan Engelhardt
2013-05-13 17:19 ` Jens Lehmann
2013-05-13 18:57 ` AW: " Ralph Haußmann
2013-05-13 19:25 ` Jan Engelhardt
2013-05-14 17:51 ` Ralf Thielow
2013-05-15 10:23 ` Holger Hellmuth (IKS)
2013-05-15 11:26 ` Jens Lehmann
2013-05-15 11:56 ` Jan Engelhardt
2013-05-15 12:27 ` Jens Lehmann
2013-05-15 13:14 ` Jan Engelhardt
2013-05-15 15:31 ` Holger Hellmuth (IKS)
2013-05-15 17:28 ` Jan Engelhardt
2013-05-16 5:57 ` Ralf Thielow
2013-05-16 8:48 ` Holger Hellmuth (IKS)
2013-05-19 16:06 ` Ralf Thielow
2013-05-19 16:56 ` Ralf Thielow
2013-05-20 4:01 ` Holger Hellmuth
2013-05-22 14:09 ` Ralf Thielow
2013-05-16 9:00 ` Thomas Rast
2013-05-19 16:49 ` Ralf Thielow
2013-05-19 16:53 ` Ralf Thielow
2013-05-20 19:41 ` Christian Stimming
2013-05-22 15:16 ` Ralf Thielow
2013-05-22 15:52 ` Holger Hellmuth (IKS) [this message]
2013-05-22 16:43 ` Jan Engelhardt
2013-05-23 18:16 ` Bernhard R. Link
2013-05-24 16:41 ` Ralf Thielow
2013-06-16 21:22 ` Jan Engelhardt
2013-05-24 16:51 ` Ralf Thielow
2013-05-13 16:30 ` Ralf Thielow
2013-05-16 10:49 ` 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=519CE9AA.9010502@ira.uka.de \
--to=hellmuth@ira.uka.de \
--cc=Jens.Lehmann@web.de \
--cc=git@vger.kernel.org \
--cc=jengelh@inai.de \
--cc=jk@jk.gs \
--cc=ralf.thielow@gmail.com \
--cc=ralph@scanmyfood.de \
--cc=stimming@tuhh.de \
--cc=svenfuchs@artweb-design.de \
--cc=trast@inf.ethz.ch \
/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).