From: Erik Faye-Lund <kusmabite@gmail.com>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: "Dimitris Glezos" <glezos@indifex.com>,
"Ævar Arnfjörð" <avarab@gmail.com>,
"Git List" <git@vger.kernel.org>,
"Jonathan Nieder" <jrnieder@gmail.com>,
"Junio C Hamano" <gitster@pobox.com>
Subject: Re: Using Transifex in git.git
Date: Wed, 15 Jun 2011 15:21:49 +0200 [thread overview]
Message-ID: <BANLkTin9bhtB_OPMWCVsbtKBpRXp2o=uLA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTikQJYYd4sTJoDrL28Bo35+GpV3HgA@mail.gmail.com>
On Tue, Jun 14, 2011 at 7:57 AM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> I think it's a good idea to use a system like Transifex to manage
> translations for git.git, so that we can attract a large number of
> non-technical translators.
Are we sure we want non-technical translators to translate Git, a
highly technical program with many technical terms?
I'm guessing that Git probably should be translated by it's users,
because we have a lot of Git-jargon that is difficult for people who
doesn't know Git to translate. But perhaps an initial translation for
each language is enough to establish a language-specific translation
of all Git-jargon, and then afterwards we can get help from
non-technical people to improve the language? I'm just asking, I don't
know how Transifex works at all...
next prev parent reply other threads:[~2011-06-15 13:22 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-14 5:57 Using Transifex in git.git Ramkumar Ramachandra
2011-06-14 9:16 ` Andreas Ericsson
2011-06-14 10:12 ` Ramkumar Ramachandra
2011-06-14 9:37 ` Ævar Arnfjörð Bjarmason
2011-06-14 11:02 ` Ramkumar Ramachandra
2011-06-14 12:07 ` Andreas Ericsson
2011-06-15 7:33 ` Ramkumar Ramachandra
2011-06-15 8:22 ` Andreas Ericsson
2011-06-15 10:10 ` Ramkumar Ramachandra
2011-06-15 20:40 ` Ævar Arnfjörð Bjarmason
2011-06-15 20:58 ` Ævar Arnfjörð Bjarmason
2011-06-15 13:21 ` Erik Faye-Lund [this message]
2011-06-15 13:45 ` Michael Witten
2011-06-15 20:43 ` Ævar Arnfjörð Bjarmason
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='BANLkTin9bhtB_OPMWCVsbtKBpRXp2o=uLA@mail.gmail.com' \
--to=kusmabite@gmail.com \
--cc=artagnon@gmail.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=glezos@indifex.com \
--cc=jrnieder@gmail.com \
/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).