From: Mark Struberg <struberg@yahoo.de>
To: Fabio Scotoni <fabio@esse.ch>, "Stephen R. van den Berg" <srb@cuci.nl>
Cc: git@vger.kernel.org
Subject: Re: German translation of git man pages
Date: Wed, 30 Jul 2008 11:21:12 +0000 (GMT) [thread overview]
Message-ID: <969890.11742.qm@web27801.mail.ukl.yahoo.com> (raw)
In-Reply-To: <20080730110602.GB20957@cuci.nl>
My personal opinion:
don't translate termini technici in technical documentations, but add a translated explanation of each in the preamble.
I've never read any german book or comment where e.g. 'a commit' has been translated to 'das Uebergebene'...
(Reminds me of some old Siemens BS2000 mainfraims back in the 80s. They translated really ALL terms to german, which was frankly completely unreadable)
LieGrü,
strub
--- Stephen R. van den Berg <srb@cuci.nl> schrieb am Mi, 30.7.2008:
> Von: Stephen R. van den Berg <srb@cuci.nl>
> Betreff: Re: German translation of git man pages
> An: "Fabio Scotoni" <fabio@esse.ch>
> CC: git@vger.kernel.org
> Datum: Mittwoch, 30. Juli 2008, 13:06
> Fabio Scotoni wrote:
> >Our native language is german and they don't like
> to read english
> >documentation. I already started translating but have
> some problems:
> >Should i translate "branch" with the
> appropriate german word or keep it
> >english? This is a Problem for "pull"
> "push" and the other actions as
> >well. Basically it's possible to copy words, but
> that isn't very
> >esthetical.
>
> A good translation will translate those words. However,
> since the
> commandline interface uses the English words, you'll be
> forced to
> re-explain that relationship a lot of times (using
> parenthesis, most
> likely).
__________________________________________________________
Gesendet von Yahoo! Mail.
Dem pfiffigeren Posteingang.
http://de.overview.mail.yahoo.com
next prev parent reply other threads:[~2008-07-30 11:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 8:53 German translation of git man pages Fabio Scotoni
2008-07-30 11:06 ` Stephen R. van den Berg
2008-07-30 11:21 ` Mark Struberg [this message]
2008-07-30 11:55 ` Matthias Kestenholz
2008-07-30 12:25 ` Stephan Beyer
2008-07-30 12:33 ` Stephan Beyer
2008-08-03 17:26 ` Fabio Scotoni
2008-08-04 18:43 ` Stephan Beyer
-- strict thread matches above, loose matches on Subject: below --
2008-07-30 14:05 Fabio Scotoni
2008-07-30 16:03 ` Petr Baudis
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=969890.11742.qm@web27801.mail.ukl.yahoo.com \
--to=struberg@yahoo.de \
--cc=fabio@esse.ch \
--cc=git@vger.kernel.org \
--cc=srb@cuci.nl \
/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).