From: Johannes Gilger <heipei@hackvalue.de>
To: git@vger.kernel.org
Subject: Re: Translations in Git release?
Date: Mon, 26 Jan 2009 09:54:56 +0000 (UTC) [thread overview]
Message-ID: <glk19g$2f5$1@ger.gmane.org> (raw)
In-Reply-To: 60646ee10901250941s34f7accem1b74fc201e895a41@mail.gmail.com
On 2009-01-25, Dill <sarpulhu@gmail.com> wrote:
> Is there a plan to include translations of the Documentation within
> Git or should they exist outside of the project?
My oppinion on localization of software (and its documentation) is
generally a negative one.
- People who use software like git are (in my experience) people who
have a solid foundation of english, especially when it comes to
computer-topics.
- The effort that goes into translating the vast git documentation and
keeping it up-to-date isn't small, energy better spent in other areas.
- Translating a lot of technical terms into a language like german is
really ugly and not fun to read. I always prefer reading english
documentation and using non-localized versions of programs as it enables
me to easier partake in discussions about it and also enables me to
google for error messages without trying every different language the
message could be in ;)
But thats just me, if you want to start a translation effort knock
yourself out
Greetings,
Jojo
--
Johannes Gilger <heipei@hackvalue.de>
http://hackvalue.de/heipei/
GPG-Key: 0x42F6DE81
GPG-Fingerprint: BB49 F967 775E BB52 3A81 882C 58EE B178 42F6 DE81
next prev parent reply other threads:[~2009-01-26 9:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-25 17:41 Translations in Git release? Dill
2009-01-25 18:54 ` Jeff King
2009-01-26 9:54 ` Johannes Gilger [this message]
2009-01-26 10:07 ` Peter Krefting
2009-01-26 12:31 ` Translations [of Documentation] " Jakub Narebski
2009-01-26 13:27 ` Peter Krefting
2009-01-26 13:34 ` Miklos Vajna
2009-01-26 15:31 ` Jakub Narebski
2009-01-26 16:23 ` Mike Hommey
2009-01-26 19:30 ` Sverre Rabbelier
2009-01-27 7:01 ` Peter Krefting
2009-01-27 11:16 ` Jakub Narebski
2009-01-27 14:45 ` Peter Krefting
2009-01-26 19:58 ` Dill
2009-01-26 20:38 ` Junio C Hamano
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='glk19g$2f5$1@ger.gmane.org' \
--to=heipei@hackvalue.de \
--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).