From: Will Palmer <wmpalmer@gmail.com>
To: Thomas Singer <thomas.singer@syntevo.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: Has anyone looked at Gettext support for Git itself?
Date: Tue, 18 May 2010 14:33:31 +0100 [thread overview]
Message-ID: <1274189611.1294.10.camel@wpalmer.simply-domain> (raw)
In-Reply-To: <4BF25F7C.10303@syntevo.com>
On Tue, 2010-05-18 at 11:35 +0200, Thomas Singer wrote:
> ... and even worse, (s)he will most likely
> not be able to find a solution by searching google for this error message.
>
Other software projects make this a non-issue by reporting an "error
code" or something along those lines, along with the message. The code
is easily indexed, so that the message can be located by support staff
and, nowadays, google. I assume any internationalization effort would
require a message code of some sort be generated internally (if only to
look up which internationalized message to display), so doing something
as simple as outputting the internally-used code (even if that is just a
hash of the English version of the message) could solve this problem.
Having error messages pasted into #git in 14 different languages could
be annoying, but if those are 14 people who otherwise would not be using
git at all, then I expect we're looking at the wrong problem, and
internationalisation /should/ be a priority.
But what do I know? I speak English :)
next prev parent reply other threads:[~2010-05-18 13:33 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-15 22:10 Has anyone looked at Gettext support for Git itself? Ævar Arnfjörð Bjarmason
2010-05-16 0:03 ` Jakub Narebski
2010-05-16 1:12 ` Ævar Arnfjörð Bjarmason
2010-05-16 5:36 ` Dmitry Potapov
2010-05-16 13:12 ` Ævar Arnfjörð Bjarmason
2010-05-16 16:08 ` Jan Hudec
2010-05-16 17:37 ` Ævar Arnfjörð Bjarmason
2010-05-17 14:32 ` Thomas Rast
2010-05-17 14:53 ` Ævar Arnfjörð Bjarmason
2010-05-17 15:12 ` Thomas Rast
2010-05-17 17:59 ` Jan Hudec
2010-05-17 18:56 ` Will Palmer
2010-05-18 7:51 ` Michael J Gruber
2010-05-18 9:35 ` Thomas Singer
2010-05-18 13:33 ` Will Palmer [this message]
2010-05-22 11:01 ` Jan Hudec
2010-05-19 15:43 ` demerphq
2010-05-16 16:53 ` Thomas Singer
2010-05-17 15:04 ` Marc Weber
2010-05-18 7:12 ` Peter Krefting
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=1274189611.1294.10.camel@wpalmer.simply-domain \
--to=wmpalmer@gmail.com \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=thomas.singer@syntevo.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).