From: Jakub Narebski <jnareb@gmail.com>
To: Erick Mattos <erick.mattos@gmail.com>
Cc: Chris Johnsen <chris_johnsen@pobox.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org
Subject: Translating error messages in Git (was: Re: [PATCH v3] git checkout: create unparented branch by --orphan)
Date: Mon, 22 Mar 2010 09:06:41 -0700 (PDT) [thread overview]
Message-ID: <m3d3ywjq8p.fsf_-_@localhost.localdomain> (raw)
In-Reply-To: <55bacdd31003220714qa9fb915k9fe152019b4d88b4@mail.gmail.com>
Erick Mattos <erick.mattos@gmail.com> writes:
> After this wonderful English and modesty lessons, I started thinking:
> since Git is a worldwide spread software why it is not using gettext
> to have its translations? It would not be a hard job because gettext
> separates the job of translation from normal work flow with just minor
> changes to inline message constants.
Git uses gettext, but only for gitk and git-gui.
The problem is that git is written in C (which can use gettext), Perl
(which can use Locale::Maketext / Locale::Maketext::Gettext), but has
also some commands that are written in (POSIX) shell script. The
$"..." syntax for message localization is bash-ism, and additionally
it is deprecated
--
Jakub Narebski
Poland
ShadeHawk on #git
next prev parent reply other threads:[~2010-03-22 16:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-21 15:34 [PATCH v3] git checkout: create unparented branch by --orphan Erick Mattos
2010-03-21 17:14 ` Peter Baumann
2010-03-21 17:55 ` Erick Mattos
2010-03-21 19:37 ` Junio C Hamano
2010-03-21 21:15 ` Erick Mattos
2010-03-22 8:54 ` Michael J Gruber
2010-03-22 12:46 ` Chris Johnsen
2010-03-22 14:36 ` Erick Mattos
2010-03-21 21:38 ` Junio C Hamano
2010-03-22 12:43 ` Chris Johnsen
2010-03-22 14:14 ` Erick Mattos
2010-03-22 16:06 ` Jakub Narebski [this message]
2010-03-22 20:19 ` 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=m3d3ywjq8p.fsf_-_@localhost.localdomain \
--to=jnareb@gmail.com \
--cc=chris_johnsen@pobox.com \
--cc=erick.mattos@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).