From: Thomas Singer <thomas.singer@syntevo.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Has anyone looked at Gettext support for Git itself?
Date: Sun, 16 May 2010 18:53:12 +0200 [thread overview]
Message-ID: <4BF022F8.6080805@syntevo.com> (raw)
In-Reply-To: <AANLkTinlDF-aKDjwvgZEqtUgzW7MCIuElQ_RfJn_RkZp@mail.gmail.com>
> Have there
> been any discussions of adding internationalization support to Git
> itself? I.e. the interface messages that the core Git utilities emit.
>From me perspective of a developer who is invoking the Git executable from
our application: ensure that there is a way to tell Git to output text in a
fixed language, so other applications (e.g. ours) can parse the output.(1)
--
Best regards,
Thomas Singer
=============
syntevo GmbH
http://www.syntevo.com
http://blog.syntevo.com
(1) Yes, I know that this is not 100% safe, because messages can be
different in different Git version.
next prev parent reply other threads:[~2010-05-16 16:58 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
2010-05-22 11:01 ` Jan Hudec
2010-05-19 15:43 ` demerphq
2010-05-16 16:53 ` Thomas Singer [this message]
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=4BF022F8.6080805@syntevo.com \
--to=thomas.singer@syntevo.com \
--cc=avarab@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.